111 lines
8.0 KiB
HTML
111 lines
8.0 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
|||
|
|
<!DOCTYPE html
|
|||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|||
|
|
<html lang="en-us" xml:lang="en-us">
|
|||
|
|
<head>
|
|||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|||
|
|
<meta name="security" content="public" />
|
|||
|
|
<meta name="Robots" content="index,follow" />
|
|||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|||
|
|
<meta name="DC.Type" content="concept" />
|
|||
|
|
<meta name="DC.Title" content="Considerations for entries which contain minimized entry-specific data" />
|
|||
|
|
<meta name="abstract" content="Reduce the size of journal receivers by specifying minimized entry-specific data on the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands." />
|
|||
|
|
<meta name="description" content="Reduce the size of journal receivers by specifying minimized entry-specific data on the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiwrkjrninfo.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiminendta.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtjrn.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgjrn.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakifinder.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakivarlength.htm" />
|
|||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
|
<meta name="DC.Format" content="XHTML" />
|
|||
|
|
<meta name="DC.Identifier" content="rzakiwrkminendta" />
|
|||
|
|
<meta name="DC.Language" content="en-us" />
|
|||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|||
|
|
<!-- US Government Users Restricted Rights -->
|
|||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|||
|
|
<title>Considerations for entries which contain minimized entry-specific data</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzakiwrkminendta"><a name="rzakiwrkminendta"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Considerations for entries which contain minimized entry-specific data</h1>
|
|||
|
|
<div><p>Reduce the size of journal receivers by specifying minimized entry-specific
|
|||
|
|
data on the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands.</p>
|
|||
|
|
<p>If you have selected to use the MINENTDTA parameter for the journal, then
|
|||
|
|
some of your journal entries' entry-specific data will be minimized. The entries
|
|||
|
|
will only be minimized if the minimization technique will deposit a journal
|
|||
|
|
entry which is smaller in size than the complete entry would be. Use the
|
|||
|
|
Journal entry information finder to see which specific journal entry types
|
|||
|
|
can possibly be minimized. When the entry is minimized, the fixed-length portion
|
|||
|
|
of the journal entry will have the minimized entry-specific data indicator
|
|||
|
|
on. Currently, only data areas and database physical files can have their
|
|||
|
|
entry-specific data minimized.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Data area considerations</h4><p>The layout of the data
|
|||
|
|
area entries which are minimized is exactly the same as the layout if the
|
|||
|
|
entry was not minimized. The only difference is that only the bytes which
|
|||
|
|
actually changed are deposited rather than depositing all the bytes on the
|
|||
|
|
change request. See Update data area journal entries for the entry layout
|
|||
|
|
of the change data area entries.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Database physical file considerations</h4><p><img src="./delta.gif" alt="Start of change" />The
|
|||
|
|
layout of the minimized record changes entries is completely different than
|
|||
|
|
the layout when the entry is not minimized. If MINENTDTA(*FILE) is used, the
|
|||
|
|
data is not readable because sophisticated hash techniques are used in addition
|
|||
|
|
to only operating on actual changed bytes. Additionally, the Null-value-indicators
|
|||
|
|
field will be used, even if the file is not null capable, to provide additional
|
|||
|
|
information that can be used by database operations. Therefore, if you want
|
|||
|
|
to use the journal as an audit mechanism, you may not want to choose the MINENTDTA(*FILE)
|
|||
|
|
option for database physical files since you will not be able to read the
|
|||
|
|
actual change made.<img src="./deltaend.gif" alt="End of change" /></p>
|
|||
|
|
<p><img src="./delta.gif" alt="Start of change" />If minimized journal entries are collected
|
|||
|
|
on field boundaries using the MINENTDTA(*FLDBDY) option, the data within the
|
|||
|
|
journal entries may be displayed in the recognizable record layout of the
|
|||
|
|
file. When this option is used, fields that were not collected will display
|
|||
|
|
default data and the null value indicator table will use a new value to indicate
|
|||
|
|
which fields are showing the actual data versus which ones are showing default
|
|||
|
|
data because the fields were not collected. A ‘9’ in the null value field
|
|||
|
|
will indicate the data is not actual data and that it was filled in with default
|
|||
|
|
data. <img src="./deltaend.gif" alt="End of change" /></p>
|
|||
|
|
<p>Even if the file is not null capable, the Null value
|
|||
|
|
indicators field is used to provide additional information that can be used
|
|||
|
|
by database operations. Therefore, if you want to use the journal for auditing
|
|||
|
|
purposes, you may want to use the *FLDBDY value on the Minimized entry specific
|
|||
|
|
data (MINENTDTA) parameter for the CRTJRN and CHGJRN commands discussed below.
|
|||
|
|
</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">View minimized entry-specific data</h4><p><img src="./delta.gif" alt="Start of change" />The
|
|||
|
|
*FLDBDY value indicates that minimizing of record level changes should be
|
|||
|
|
done on field/column boundaries for all files journaled to the specified journal.
|
|||
|
|
Using the <span class="cmdname">Display Journal (DSPJRN)</span> command, entries are
|
|||
|
|
viewable to the screen, an outfile, or printed output. If a journal entry
|
|||
|
|
has been minimized on field boundaries, the value of 2 is returned in the
|
|||
|
|
Minimized entry specific data field of the *OUTFILE and in the Min field of
|
|||
|
|
the printed output. The <span class="cmdname">RCVJRNE</span> and <span class="cmdname">RTVJRNE</span> commands
|
|||
|
|
can also be used to view entries that were minimized on field boundaries by
|
|||
|
|
specifying *YES on the Format minimized data (FMTMINDTA) parameter. The <span class="apiname">QjoRetrieveJournalEntries</span> API
|
|||
|
|
can be used to view entries that were minimized on field boundaries by specifying
|
|||
|
|
*YES for the Format minimized data (FMTMINDTA) key.<img src="./deltaend.gif" alt="End of change" /></p>
|
|||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiwrkjrninfo.htm" title="Provides ways that you can display, retrieve, and receive journal entries.">Work with journal entry information</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|||
|
|
<div><a href="rzakiminendta.htm" title="On the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands, you can specify to allow for the deposit of minimized journal entries. This will decrease the size of your journal entries.">Minimized entry-specific data for journal entries</a></div>
|
|||
|
|
<div><a href="rzakivarlength.htm" title="The following tables contain the variable-length portion of the layouts for journal entries.">Layouts for variable-length portion of journal entries</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|||
|
|
<div><a href="../cl/crtjrn.htm">Create Journal (CRTJRN) command</a></div>
|
|||
|
|
<div><a href="../cl/chgjrn.htm">Change Journal (CHGJRN) command</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|||
|
|
<div><a href="rzakifinder.htm">Journal entry information finder</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|