friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaki_5.4.0.1/rzakifixlength.htm

1685 lines
111 KiB
HTML
Raw Permalink Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<?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="Layouts for the fixed-length portion of journal entries" />
<meta name="abstract" content="Use this topic to determine layouts for the fixed-length portion of journal entries." />
<meta name="description" content="Use this topic to determine layouts for the fixed-length portion of journal entries." />
<meta name="DC.Relation" scheme="URI" content="rzakicodes.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakifinder.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakidsplyjrnentry.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakiformatdbout.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="rzakifixlength" />
<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>Layouts for the fixed-length portion of journal entries</title>
</head>
<body id="rzakifixlength"><a name="rzakifixlength"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Layouts for the fixed-length portion of journal entries</h1>
<div><p>Use this topic to determine layouts for the fixed-length portion
of journal entries.</p>
<div class="section" id="rzakifixlength__TBLJENTID"><a name="rzakifixlength__TBLJENTID"><!-- --></a><h4 class="sectiontitle">TYPE1 field descriptions of the fixed-length
portion of a journal entry</h4><p>These fields are shown when you request
*TYPE1 for the output file format or the entry type format. The uppercase
field names shown in parentheses are used in the system-supplied output file
QSYS/QADSPJRN. The field names that are in italics are the variable names
for these fields in the <span class="apiname">QjoRetrieveJournalEntries</span> API header
file. These variables are under the type definition for the RJNE0100 format.
The <span class="apiname">QjoRetrieveJournalEntries</span> API header is in the QJOURNAL.H
file of the QSYSINC library.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="9.090909090909092%" id="d0e40">Relative offset</th>
<th valign="top" width="27.27272727272727%" id="d0e42">Field</th>
<th valign="top" width="18.181818181818183%" id="d0e44">Format</th>
<th valign="top" width="45.45454545454545%" id="d0e46">Description</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">1</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Entry length (JOENTL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. <p>If the journal
entry has the incomplete data indicator on, then this length does not include
that additional data which could be pointed to. This length includes the length
of the data that is actually returned, which includes entry specific data
of up to 32 766 bytes.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">6</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Sequence number (JOSEQN, <var class="varname">Seq_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. <p>This field can contain a -1 if receiver-size
option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence
number is larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">16</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Journal code (JOCODE, <var class="varname">Jrn_Code</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Identifies the primary category of the journal entry: <ul class="simple"><li><strong>A</strong> = System accounting entry</li>
<li><strong>B</strong> = Integrated file system operation</li>
<li><strong>C</strong> = Commitment control operation</li>
<li><strong>D</strong> = Database file operation</li>
<li><strong>E</strong> = Data area operation</li>
<li><strong>F</strong> = Database file member operation</li>
<li><strong>I</strong> = Internal operation</li>
<li><strong>J</strong> = Journal or receiver operation</li>
<li><strong>L</strong> = License management</li>
<li><strong>M</strong> = Network management data</li>
<li><strong>P</strong> = Performance tuning entry</li>
<li><strong>Q</strong> = Data queue operation</li>
<li><strong>R</strong> = Operation on a specific record</li>
<li><strong>S</strong> = Distributed mail services</li>
<li><strong>T</strong> = Audit trail entry</li>
<li><strong>U</strong> = User-generated entry (added by the <span class="cmdname">SNDJRNE</span> command
or <span class="apiname">QJOSJRNE</span> API)</li>
</ul>
<p>The journal codes are described in more detail in Journal code descriptions.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">17</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Entry type (JOENTT, <var class="varname">Entry_Type</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (2)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Further identifies the type of user-created or system-created entry.
See the Journal code finder for descriptions of the entry types.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">19</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Date stamp (JODATE)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (6)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the system date when the entry was added and is in the format
of the job attribute DATFMT. The system cannot assure that the date stamp
is always in ascending order for sequential journal entries because you can
change the value of the system date.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">25</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Time stamp (JOTIME)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Corresponds to the system time (in the format hhmmss) when the entry
was added. The system cannot assure that the time stamp is always in ascending
order for sequential journal entries because you can change the value of the
system time.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">31</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Job name (JOJOB, <var class="varname">Job_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the name of the job that added the entry.<div class="note"><span class="notetitle">Notes:</span> <ol><li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED is given for the job name.</li>
<li>If the job name was not available when the journal entry was deposited,
then *NONE is written for the job name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">41</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">User name (JOUSER, <var class="varname">User_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the user profile name of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">51</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Job number (JONBR, <var class="varname">Job_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the job number of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">57</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Program name (JOPGM, <var class="varname">Program_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true: <ul><li>The program name does not apply to this journal entry.</li>
<li>The program name was not available when the journal entry was made.</li>
</ul>
<p>For example, the program name is not available if the program was
destroyed.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>If the program that deposited the journal entry is an original program
model program, this data will be complete. Otherwise, this data will be unpredictable.</li>
<li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, *OMITTED is given for the program name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">67</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Object name (JOOBJ, <var class="varname">Object</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the name of the object for which the journal entry was added.<sup>1</sup> This
is blank for some entries. <p>If the journaled object is an integrated file
system object, then this field is the first 10 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">77</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Library name (JOLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the name of the library containing the object<sup>1</sup>. <p>If
the journaled object is an integrated file system object, then the first 6
characters of this field are the last 6 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">87</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Member name (JOMBR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Specifies the name of the physical file member or is blank if the object
is not a physical file<sup>1</sup>.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">97</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Count/relative record number (JOCTRR, <var class="varname">Count_Rel_Rec_Num</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. The following tables show specific values for this field,
if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCE">Change end of
data journal entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTNR">CHGJRN journal
entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
</ul>
<p>This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the count or relative record number is
larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">107</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Indicator flag (JOFLAG, <var class="varname">Indicator_Flag</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Contains an indicator for the operation. The following tables show
specific values for this field, if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIU">IPL and in-use
journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTBR">Journal code
R (all journal entry types except IL)</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTRB">ROLLBACK journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTJM">Start-journal
journal entries</a></li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">108</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Commit cycle identifier (JOCCID, <var class="varname">Commit_Cycle_Id</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. <p>The commit cycle identifier
is found in every journal entry that is associated with a commitment transaction.
If the journal entry was not made as part of a commitment transaction, this
field is zero.</p>
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the commit cycle identifier is larger
than 9 999 999 999.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">118</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Incomplete data (JOINCDAT, <var class="varname">Incomplete_Data</var>) </td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Indicates whether this entry has data that is not being retrieved for
one of the following reasons: <ul><li>The length of the entry-specific data exceeds 32 766 bytes.</li>
<li>The entry is associated with a database file that has one or more fields
of data type BLOB (binary large object), CLOB (character large object), or
DBCLOB (double-byte character large object).</li>
</ul>
<p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data</li>
<li><strong>1</strong> = This entry has incomplete data.</li>
</ul>
<p>Any data which is marked as incomplete, can only be viewed by using
either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any
of the following parameters:</p>
<ul><li>ENTFMT(*TYPEPTR)</li>
<li>ENTFMT(*JRNENTFMT)</li>
<li>RTNPTR (with any value specified other than *NONE)</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">119</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Minimized entry specific data (JOMINESD, <var class="varname">Min_ESD</var>) </td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Indicates whether this entry has minimized entry specific data. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data</li>
<li><strong>1</strong> = This entry has incomplete data.</li>
<li><strong>2</strong> = This entry has entry specific data that has been minimized
on field boundaries.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e40 ">120</td>
<td valign="top" width="27.27272727272727%" headers="d0e42 ">Reserved field (JORES)</td>
<td valign="top" width="18.181818181818183%" headers="d0e44 ">Char (6)</td>
<td valign="top" width="45.45454545454545%" headers="d0e46 ">Always contains zeros. Contains hexadecimal zeros in the output file.</td>
</tr>
<tr><td colspan="4" valign="top" headers="d0e40 d0e42 d0e44 d0e46 "><div class="note"><span class="notetitle">Note:</span> <p><sup>1</sup>If the journal receiver
was attached prior to installing V4R2M0 on your system, then the following
items are true:</p>
<ul><li>If *ALLFILE is specified for the FILE parameter on the <span class="cmdname">DSPJRN</span>, <span class="cmdname">RCVJRNE</span>,
or <span class="cmdname">RTVJRNE</span> command, then the fully qualified name is the
most recent name of the file when the newest receiver in the receiver range
was the attached receiver and when the file was still being journaled.</li>
<li>If a file name is specified or if library *ALL is specified on the FILE
parameter, the current fully qualified name of the file appears in the converted
journal entry.</li>
</ul>
<p>If the journal receiver was attached while V4R2M0 or a later release
was running on the system, the fully qualified name is the name of the object
at the time the journal entry was deposited.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="rzakifixlength__TBLTYPE2"><a name="rzakifixlength__TBLTYPE2"><!-- --></a><h4 class="sectiontitle">*TYPE2 field descriptions of the fixed-length
portion of a journal entry</h4><p>These fields are shown when you request
*TYPE2 for the output file format or the entry type format. The uppercase
field names shown in parentheses are used in the system-supplied output file
QSYS/QADSPJR2. The field names that are in italics are the variable names
for these fields in the <span class="apiname">QjoRetrieveJournalEntries</span> API header
file. These variables are under the type definition for the RJNE0100 format.
The <span class="apiname">QjoRetrieveJournalEntries</span> API header is in the QJOURNAL.H
file of the QSYSINC library.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="9.090909090909092%" id="d0e497">Offset</th>
<th valign="top" width="27.27272727272727%" id="d0e499">Field</th>
<th valign="top" width="18.181818181818183%" id="d0e501">Format</th>
<th valign="top" width="45.45454545454545%" id="d0e503">Description</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">1</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Entry length (JOENTL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. <p>If the journal
entry has the incomplete data indicator on, then this length does not include
that additional data which could be pointed to. This length includes the length
of the data that is actually returned, which includes entry specific data
of up to 32 766 bytes.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">6</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Sequence number (JOSEQN, <var class="varname">Seq_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. <p>This field can contain a -1 if receiver-size
option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence
number is larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">16</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Journal code (JOCODE, <var class="varname">Jrn_Code</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Identifies the primary category of the journal entry:<ul class="simple"><li><strong>A</strong> = System accounting entry</li>
<li><strong>B</strong> = Integrated file system operation</li>
<li><strong>C</strong> = Commitment control operation</li>
<li><strong>D</strong> = Database file operation</li>
<li><strong>E</strong> = Data area operation</li>
<li><strong>F</strong> = Database file member operation</li>
<li><strong>I</strong> = Internal operation</li>
<li><strong>J</strong> = Journal or receiver operation</li>
<li><strong>L</strong> = License management</li>
<li><strong>M</strong> = Network management data</li>
<li><strong>P</strong> = Performance tuning entry</li>
<li><strong>Q</strong> = Data queue operation</li>
<li><strong>R</strong> = Operation on a specific record</li>
<li><strong>S</strong> = Distributed mail services</li>
<li><strong>T</strong> = Audit trail entry</li>
<li><strong>U</strong> = User-generated entry (added by the <span class="cmdname">SNDJRNE</span> command
or <span class="apiname">QJOSJRNE</span> API)</li>
</ul>
<p>The journal codes are described in more detail in Journal code descriptions.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">17</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Entry type (JOENTT, <var class="varname">Entry_Type</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (2)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Further identifies the type of user-created or system-created entry.
See the Journal code finder for descriptions of the entry types.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">19</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Date stamp (JODATE)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (6)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the system date when the entry was added and is in the format
of the job attribute DATFMT. The system cannot assure that the date stamp
is always in ascending order for sequential journal entries because you can
change the value of the system date.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">25</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Time stamp (JOTIME)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Corresponds to the system time (in the format hhmmss) when the entry
was added. The system cannot assure that the time stamp is always in ascending
order for sequential journal entries because you can change the value of the
system time.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">31</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Job name (JOJOB, <var class="varname">Job_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the job that added the entry.<div class="note"><span class="notetitle">Notes:</span> <ol><li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED is given for the job name.</li>
<li>If the job name was not available when the journal entry was deposited,
then *NONE is written for the job name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">41</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">User name (JOUSER, <var class="varname">User_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the user profile name of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">51</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Job number (JONBR, <var class="varname">Job_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the job number of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">57</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Program name (JOPGM, <var class="varname">Program_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true: <ul><li>The program name does not apply to this journal entry.</li>
<li>The program name was not available when the journal entry was made.</li>
</ul>
<p>For example, the program name is not available if the program was
destroyed.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>If the program that deposited the journal entry is an original program
model program, this data will be complete. Otherwise, this data will be unpredictable.</li>
<li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, *OMITTED is given for the program name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">67</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Object name (JOOBJ, <var class="varname">Object</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the object for which the journal entry was added.<sup>1</sup> This
is blank for some entries. <p>If the journaled object is an integrated file
system object, then this field is the first 10 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">77</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Library name (JOLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the library containing the object<sup>1</sup>. <p>If
the journaled object is an integrated file system object, then the first 6
characters of this field are the last 6 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">87</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Member name (JOMBR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the physical file member or is blank if the object
is not a physical file<sup>1</sup>.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">97</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 "> Count/relative record number (JOCTRR, <var class="varname">Count_Rel_Rec_Num</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. The following tables show specific values for this field,
if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCE">Change end of
data journal entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTNR">CHGJRN journal
entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
</ul>
<p>This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the count or relative record number is
larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">107</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Indicator flag (JOFLAG, <var class="varname">Indicator_Flag</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Contains an indicator for the operation. The following tables show
specific values for this field, if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIU">IPL and in-use
journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTBR">Journal code
R (all journal entry types except IL)</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTRB">ROLLBACK journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTJM">Start-journal
journal entries</a></li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">108</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Commit cycle identifier (JOCCID, <var class="varname">Commit_Cycle_Id</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. <p>The commit cycle identifier
is found in every journal entry that is associated with a commitment transaction.
If the journal entry was not made as part of a commitment transaction, this
field is zero.</p>
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the commit cycle identifier is larger
than 9 999 999 999.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">118</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">User profile (JOUSPF, <var class="varname">User_Profile</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the user profile under which the job was running
when the entry was created. <div class="note"><span class="notetitle">Note:</span> If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">128</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">System name (JOSYNM, <var class="varname">System_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (8)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Specifies the name of the system on which the entry is being displayed,
printed, retrieved, or received if the journal receiver was attached prior
to installing V4R2M0 on the system. If the journal receiver was attached while
the system was running V4R2M0 or a later release, the system name is the system
where the journal entry was actually deposited.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">136</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Incomplete data (JOINCDAT, <var class="varname">Incomplete_Data</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Indicates whether this entry has data that is not being retrieved for
one of the following reasons: <ul><li>The length of the entry-specific data exceeds 32 766 bytes.</li>
<li>The entry is associated with a database file that has one or more fields
of data type BLOB (binary large object), CLOB (character large object), or
DBCLOB (double-byte character large object).</li>
</ul>
<p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data</li>
<li><strong>1</strong> = This entry has incomplete data</li>
</ul>
<p>Any data which is marked as incomplete, can only be viewed by using
either the <span class="apiname">QjoRetrieveJournalEntries</span> API, or the command <span class="cmdname">RCVJRNE</span> with
any of the following parameters:</p>
<ul><li>ENTFMT(*TYPEPTR)</li>
<li>ENTFMT(*JRNENTFMT)</li>
<li>RTNPTR (with any value specified other than *NONE)</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">137</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Minimized entry specific data (JOMINESD, <var class="varname">Min_ESD</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Indicates whether this entry has minimized entry specific data. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has complete entry specific data.</li>
<li><strong>1</strong> = This entry has minimized entry specific data.</li>
<li><strong>2</strong> = This entry has entry specific data that has been minimized
on field boundaries.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e497 ">138</td>
<td valign="top" width="27.27272727272727%" headers="d0e499 ">Reserved field (JORES)</td>
<td valign="top" width="18.181818181818183%" headers="d0e501 ">Char (18)</td>
<td valign="top" width="45.45454545454545%" headers="d0e503 ">Always contains zeros. Contains hexadecimal zeros in the output file.</td>
</tr>
<tr><td colspan="4" valign="top" headers="d0e497 d0e499 d0e501 d0e503 "><div class="note"><span class="notetitle">Note:</span> <p><sup>1</sup> If the journal receiver
was attached prior to installing V4R2M0 on your system, then the following
items are true:</p>
<ul><li>If *ALLFILE is specified for the FILE parameter on the <span class="cmdname">DSPJRN</span>, <span class="cmdname">RCVJRNE</span>,
or <span class="cmdname">RTVJRNE</span> command, then the fully qualified name is the
most recent name of the file when the newest receiver in the receiver range
was the attached receiver and when the file was still being journaled.</li>
<li>If a file name is specified or if library *ALL is specified on the FILE
parameter, the current fully qualified name of the file appears in the converted
journal entry.</li>
</ul>
<p>If the journal receiver was attached while V4R2M0 or a later release
was running on the system, the fully qualified name is the name of the object
at the time the journal entry was deposited.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="rzakifixlength__TBLTYPE3"><a name="rzakifixlength__TBLTYPE3"><!-- --></a><h4 class="sectiontitle">*TYPE3 field descriptions of the fixed-length
portion of a journal entry</h4><p>These fields are shown when you request
*TYPE3 for the output file format or the entry type format. The uppercase
field names shown in parentheses are used in the system-supplied output file
QSYS/QADSPJR3. The field names that are in italics are the variable names
for these fields in the <span class="apiname">QjoRetrieveJournalEntries</span> API header
file. These variables are under the type definition for the RJNE0100 format.
The <span class="apiname">QjoRetrieveJournalEntries</span> API header is in the QJOURNAL.H
file of the QSYSINC library.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="9.090909090909092%" id="d0e986">Offset</th>
<th valign="top" width="27.27272727272727%" id="d0e988">Field</th>
<th valign="top" width="18.181818181818183%" id="d0e990">Format</th>
<th valign="top" width="45.45454545454545%" id="d0e992">Description</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">1</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Entry length (JOENTL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. <p>If the journal
entry has the incomplete data indicator on, then this length does not include
that additional data which could be pointed to. This length includes the length
of the data that is actually returned, which includes entry specific data
of up to 32 766 bytes.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">6</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Sequence number (JOSEQN, <var class="varname">Seq_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Zoned decimal (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. <p>This field can contain a -1 if receiver-size
option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence
number is larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">16</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Journal code (JOCODE, <var class="varname">Jrn_Code</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Identifies the primary category of the journal entry:<ul class="simple"><li><strong>A</strong> = System accounting entry</li>
<li><strong>B</strong> = Integrated file system operation</li>
<li><strong>C</strong> = Commitment control operation</li>
<li><strong>D</strong> = Database file operation</li>
<li><strong>E</strong> = Data area operation</li>
<li><strong>F</strong> = Database file member operation</li>
<li><strong>I</strong> = Internal operation</li>
<li><strong>J</strong> = Journal or receiver operation</li>
<li><strong>L</strong> = License management</li>
<li><strong>M</strong> = Network management data</li>
<li><strong>P</strong> = Performance tuning entry</li>
<li><strong>Q</strong> = Data queue operation</li>
<li><strong>R</strong> = Operation on a specific record</li>
<li><strong>S</strong> = Distributed mail services</li>
<li><strong>T</strong> = Audit trail entry</li>
<li><strong>U</strong> = User-generated entry (added by the <span class="cmdname">SNDJRNE</span> command
or <span class="apiname">QJOSJRNE</span> API)</li>
</ul>
<p>The journal codes are described in more detail in Journal code descriptions.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">17</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Entry type (JOENTT, <var class="varname">Entry_Type</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (2)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Further identifies the type of user-created or system-created entry.
See the Journal code finder for descriptions of the entry types.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">19</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Time stamp (JOTMST, <var class="varname">Time_Stamp</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (26)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 "> Corresponds to the system date and time when the journal entry was
added in the journal receiver. The time stamp is in SAA<sup>®</sup> format. The system cannot assure that
the time stamp is always in ascending order for sequential journal entries
because you can change the value of the system time.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">45</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Job name (JOJOB, <var class="varname">Job_Name</var>) <sup>1</sup></td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the job that added the entry.<div class="note"><span class="notetitle">Notes:</span> <ol><li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED is given for the job name.</li>
<li>If the job name was not available when the journal entry was deposited,
then *NONE is written for the job name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">55</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">User name (JOUSER, <var class="varname">User_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the user profile name of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">65</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Job number (JONBR, <var class="varname">Job_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the job number of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">71</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Program name (JOPGM, <var class="varname">Program_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true: <ul><li>The program name does not apply to this journal entry.</li>
<li>The program name was not available when the journal entry was made.</li>
</ul>
<p>For example, the program name is not available if the program was
destroyed.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>If the program that deposited the journal entry is an original program
model program, this data will be complete. Otherwise, this data will be unpredictable.</li>
<li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, *OMITTED is given for the program name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">81</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Object name (JOOBJ, <var class="varname">Object</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the object for which the journal entry was added.<sup>1</sup> This
is blank for some entries. <p>If the journaled object is an integrated file
system object, then this field is the first 10 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">91</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Library name (JOLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the library containing the object<sup>1</sup>. <p>If
the journaled object is an integrated file system object, then the first 6
characters of this field are the last 6 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">101</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Member name (JOMBR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the physical file member or is blank if the object
is not a physical file<sup>1</sup>.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">111</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 "> Count/relative record number (JOCTRR, <var class="varname">Count_Rel_Rec_Num</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCE">Change end of
data journal entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTNR">CHGJRN journal
entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
</ul>
<p>This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the count or relative record number is
larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">121</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Indicator flag (JOFLAG, <var class="varname">Indicator_Flag</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Contains an indicator for the operation. The following tables show
specific values for this field, if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIU">IPL and in-use
journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTBR">Journal code
R (all journal entry types except IL)</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTRB">ROLLBACK journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTJM">Start-journal
journal entries</a></li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">122</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Commit cycle identifier (JOCCID, <var class="varname">Commit_Cycle_Id</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. <p>The commit cycle identifier
is found in every journal entry that is associated with a commitment transaction.
If the journal entry was not made as part of a commitment transaction, this
field is zero.</p>
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the commit cycle identifier is larger
than 9 999 999 999.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">132</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">User profile (JOUSPF, <var class="varname">User_Profile</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the user profile under which the job was running
when the entry was created.<div class="note"><span class="notetitle">Note:</span> If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">142</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">System name (JOSYNM, <var class="varname">System_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (8)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Specifies the name of the system on which the entry
is being displayed, printed, retrieved, or received if the journal receiver
was attached prior to installing V4R2M0 on the system. If the journal receiver
was attached while the system was running V4R2M0 or a later release, the system
name is the system where the journal entry was actually deposited.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">150</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Incomplete data (JOINCDAT, <var class="varname">Incomplete_Data</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Indicates whether this entry has data that is not being
retrieved for one of the following reasons: <ul><li>The length of the entry-specific data exceeds 32 766 bytes.</li>
<li>The entry is associated with a database file that has one or more fields
of data type BLOB (binary large object), CLOB (character large object), or
DBCLOB (double-byte character large object).</li>
</ul>
<p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data</li>
<li><strong>1</strong> = This entry has incomplete data.</li>
</ul>
<p>Any data which is marked as incomplete, can only be viewed by using
either the <span class="apiname">QjoRetrieveJournalEntries</span> API, or the command <span class="cmdname">RCVJRNE</span> with
any of the following parameters:</p>
<ul><li>ENTFMT(*TYPEPTR)</li>
<li>ENTFMT(*JRNENTFMT)</li>
<li>RTNPTR (with any value specified other than *NONE)</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">151</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Minimized entry specific data (JOMINESD, <var class="varname">Min_ESD</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Indicates whether this entry has minimized entry specific
data. <p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has complete entry specific data.</li>
<li><strong>1</strong> = This entry has minimized entry specific data.</li>
<li><strong>2</strong> = This entry has entry specific data that has been minimized
on field boundaries.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e986 ">152</td>
<td valign="top" width="27.27272727272727%" headers="d0e988 ">Reserved field (JORES)</td>
<td valign="top" width="18.181818181818183%" headers="d0e990 ">Char (18)</td>
<td valign="top" width="45.45454545454545%" headers="d0e992 ">Always contains zeros. Contains hexadecimal zeros in
the output file.</td>
</tr>
<tr><td colspan="4" valign="top" headers="d0e986 d0e988 d0e990 d0e992 "><div class="note"><span class="notetitle">Note:</span> <p><sup>1</sup>If the journal receiver
was attached prior to installing V4R2M0 on your system, then the following
items are true:</p>
<ul><li>If *ALLFILE is specified for the FILE parameter on the <span class="cmdname">DSPJRN</span>, <span class="cmdname">RCVJRNE</span>,
or <span class="cmdname">RTVJRNE</span> command, then the fully qualified name is the
most recent name of the file when the newest receiver in the receiver range
was the attached receiver and when the file was still being journaled.</li>
<li>If a file name is specified or if library *ALL is specified on the FILE
parameter, the current fully qualified name of the file appears in the converted
journal entry.</li>
</ul>
<p>If the journal receiver was attached while V4R2M0 or a later release
was running on the system, the fully qualified name is the name of the object
at the time the journal entry was deposited.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="rzakifixlength__TBLTYPE4"><a name="rzakifixlength__TBLTYPE4"><!-- --></a><h4 class="sectiontitle">*TYPE4 field descriptions of the fixed-length
portion of a journal entry</h4><p>These fields are shown when you request
*TYPE4 for the output file format or the entry type format. The uppercase
field names shown in parentheses are used in the system-supplied output file
QSYS/QADSPJR4. The field names which are in italics are the variable names
for these fields in the <span class="apiname">QjoRetrieveJournalEntries</span> API header
file. These variables are under the type definition for the RJNE0100 format.
The <span class="apiname">QjoRetrieveJournalEntries</span> API header is in the QJOURNAL.H
file of the QSYSINC library.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="9.090909090909092%" id="d0e1474">Offset</th>
<th valign="top" width="27.27272727272727%" id="d0e1476">Field</th>
<th valign="top" width="18.181818181818183%" id="d0e1478">Format</th>
<th valign="top" width="45.45454545454545%" id="d0e1480">Description</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">1</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Entry length (JOENTL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. <p>If the journal
entry has the incomplete data indicator on, then this length does not include
that additional data which could be pointed to. This length includes the length
of the data that is actually returned, which includes entry specific data
of up to 32 766 bytes.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">6</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Sequence number (JOSEQN, <var class="varname">Seq_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Zoned decimal (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. <p>This field can contain a -1 if receiver-size
option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence
number is larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">16</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Journal code (JOCODE, <var class="varname">Jrn_Code</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Identifies the primary category of the journal entry:<ul class="simple"><li><strong>A</strong> = System accounting entry</li>
<li><strong>B</strong> = Integrated file system operation</li>
<li><strong>C</strong> = Commitment control operation</li>
<li><strong>D</strong> = Database file operation</li>
<li><strong>E</strong> = Data area operation</li>
<li><strong>F</strong> = Database file member operation</li>
<li><strong>I</strong> = Internal operation</li>
<li><strong>J</strong> = Journal or receiver operation</li>
<li><strong>L</strong> = License management</li>
<li><strong>M</strong> = Network management data</li>
<li><strong>P</strong> = Performance tuning entry</li>
<li><strong>Q</strong> = Data queue operation</li>
<li><strong>R</strong> = Operation on a specific record</li>
<li><strong>S</strong> = Distributed mail services</li>
<li><strong>T</strong> = Audit trail entry</li>
<li><strong>U</strong> = User-generated entry (added by the <span class="cmdname">SNDJRNE</span> command
or <span class="apiname">QJOSJRNE</span> API)</li>
</ul>
<p>The journal codes are described in more detail in Journal code descriptions.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">17</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Entry type (JOENTT, <var class="varname">Entry_Type</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (2)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Further identifies the type of user-created or system-created entry.
See the Journal code finder for descriptions of the entry types.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">19</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Time stamp (JOTMST, <var class="varname">Time_Stamp</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (26)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Corresponds to the system date and time when the journal entry was
added in the journal receiver. The time stamp is in SAA format. The system cannot assure that
the time stamp is always in ascending order for sequential journal entries
because you can change the value of the system time.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">45</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Job name (JOJOB, <var class="varname">Job_Name</var>) <sup>1</sup></td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the job that added the entry. <div class="note"><span class="notetitle">Notes:</span> <ol><li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED is given for the job name.</li>
<li>If the job name was not available when the journal entry was deposited,
then *NONE is written for the job name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">55</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">User name (JOUSER, <var class="varname">User_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the user profile name of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">65</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Job number (JONBR, <var class="varname">Job_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Zoned (6,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the job number of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">71</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Program name (JOPGM, <var class="varname">Program_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true: <ul><li>The program name does not apply to this journal entry.</li>
<li>The program name was not available when the journal entry was made.</li>
</ul>
<p>For example, the program name is not available if the program was
destroyed.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>If the program that deposited the journal entry is an original program
model program, this data will be complete. Otherwise, this data will be unpredictable.</li>
<li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, *OMITTED is given for the program name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">81</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Object name (JOOBJ, <var class="varname">Object</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the object for which the journal entry was added.<sup>1</sup> This
is blank for some entries. <p>If the journaled object is an integrated file
system object, then this field is the first 10 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">91</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Library name (JOLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the library containing the object<sup>1</sup>. <p>If
the journaled object is an integrated file system object, then the first 6
characters of this field are the last 6 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">101</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Member name (JOMBR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the physical file member or is blank if the object
is not a physical file<sup>1</sup>.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">111</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Count/relative record number (JOCTRR, <var class="varname">Count_Rel_Rec_Num</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCE">Change end of
data journal entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTNR">CHGJRN journal
entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
</ul>
<p>This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the count or relative record number is
larger than 9 999 999 999.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">121</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Indicator flag (JOFLAG, <var class="varname">Indicator_Flag</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Contains an indicator for the operation. The following tables show
specific values for this field, if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIU">IPL and in-use
journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTBR">Journal code
R (all journal entry types except IL)</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTRB">ROLLBACK journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTJM">Start-journal
journal entries</a></li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">122</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Commit cycle identifier (JOCCID, <var class="varname">Commit_Cycle_Id</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Zoned (10,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. <p>The commit cycle identifier
is found in every journal entry that is associated with a commitment transaction.
If the journal entry was not made as part of a commitment transaction, this
field is zero.</p>
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3)
is selected and the actual value of the commit cycle identifier is larger
than 9 999 999 999.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">132</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">User profile (JOUSPF, <var class="varname">User_Profile</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the user profile under which the job was running
when the entry was created.<div class="note"><span class="notetitle">Note:</span> If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">142</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">System name (JOSYNM, <var class="varname">System_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (8)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the name of the system on which the entry is being displayed,
printed, retrieved, or received if the journal receiver was attached prior
to installing V4R2M0 on the system. If the journal receiver was attached while
the system was running V4R2M0 or a later release, the system name is the system
where the journal entry was actually deposited.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">150</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Journal identifier (JOJID, <var class="varname">Jid</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char(10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Specifies the journal identifier (JID) for the object. When journaling
is started for an object, the system assigns a unique JID to that object.
The JID remains constant even if the object is renamed or moved. However,
if journaling is stopped, there is no guarantee that the JID will be the same
if journaling is started again for the same object. <p>If no JID is associated
with the entry, this field has hexadecimal zeros.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">160</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Referential constraint (JORCST, <var class="varname">Referential_Constraint</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char(1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Indicates whether this entry was recorded for actions that occurred
on records that are part of a referential constraint. <p>The possible values
are:</p>
<ul class="simple"><li><strong>0</strong> = This entry was not created as part of a referential constraint.</li>
<li><strong>1</strong> = This entry was created as part of a referential constraint.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">161</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Trigger (JOTGR, <var class="varname">Trigger</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char(1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Indicates whether this entry was created as result of a trigger program. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry was not created as the result of a trigger
program.</li>
<li><strong>1</strong> = This entry was created as the result of a trigger program.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">162</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Incomplete data (JOINCDAT, <var class="varname">Incomplete_Data</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Indicates whether this entry has data that is not being retrieved for
one of the following reasons: <ul><li>The length of the entry-specific data exceeds 32 766 bytes.</li>
<li>The entry is associated with a database file that has one or more fields
of data type BLOB (binary large object), CLOB (character large object), or
DBCLOB (double-byte character large object).</li>
</ul>
<p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data.</li>
<li><strong>1</strong> = This entry has incomplete data.</li>
</ul>
<p>Any data which is marked as incomplete, can only be viewed by using
either the <span class="apiname">QjoRetrieveJournalEntries</span> API, or the command <span class="cmdname">RCVJRNE</span> with
any of the following parameters:</p>
<ul><li>ENTFMT(*TYPEPTR)</li>
<li>ENTFMT(*JRNENTFMT)</li>
<li>RTNPTR (with any value specified other than *NONE)</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">163</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Ignored by <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> (JOIGNAPY, <var class="varname">Ignore_during_APYRMV</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Indicates whether this journal entry will be ignored by the execution
of the <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> commands,
even though normally this journal entry type has an effect during those command
invocations. <p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry is not ignored by the <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> commands.</li>
<li><strong>1</strong> = This entry is ignored by the <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> commands.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">164</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Minimized entry specific data (JOMINESD, <var class="varname">Min_ESD</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Indicates whether this entry has minimized entry specific data. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has complete entry specific data.</li>
<li><strong>1</strong> = This entry has minimized entry specific data.</li>
<li><strong>2</strong> = This entry has entry specific data that has been minimized
on field boundaries.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e1474 ">165</td>
<td valign="top" width="27.27272727272727%" headers="d0e1476 ">Reserved area (JORES)</td>
<td valign="top" width="18.181818181818183%" headers="d0e1478 ">Char (5)</td>
<td valign="top" width="45.45454545454545%" headers="d0e1480 ">Always contains zeros. Contains hexadecimal zeros in the output file.</td>
</tr>
<tr><td colspan="4" valign="top" headers="d0e1474 d0e1476 d0e1478 d0e1480 "><div class="note"><span class="notetitle">Note:</span> <sup>1</sup>If the journal receiver
was attached prior to installing V4R2M0 on your system, then the following
items are true:<ul><li>If *ALLFILE is specified for the FILE parameter on the <span class="cmdname">DSPJRN</span>, <span class="cmdname">RCVJRNE</span>,
or <span class="cmdname">RTVJRNE</span> command, then the fully qualified name is the
most recent name of the file when the newest receiver in the receiver range
was the attached receiver and when the file was still being journaled.</li>
<li>If a file name is specified or if library *ALL is specified on the FILE
parameter, the current fully qualified name of the file appears in the converted
journal entry.</li>
</ul>
<p>If the journal receiver was attached while V4R2M0 or a later release
was running on the system, the fully qualified name is the name of the object
at the time the journal entry was deposited.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="rzakifixlength__TBLTYPE5"><a name="rzakifixlength__TBLTYPE5"><!-- --></a><h4 class="sectiontitle">*TYPE5 field descriptions of the fixed-length
portion of a journal entry</h4><p>These fields are shown when you request
*TYPE5 for the output file format or the entry type format. The uppercase
field names shown in parentheses are used in the system-supplied output file
QSYS/QADSPJR5. The field names that are italics are the variable names for
these fields in the <span class="apiname">QjoRetrieveJournalEntries</span> API header
file. These variables are under the type definition for the RJNE0200 format.
The <span class="apiname">QjoRetrieveJournalEntries</span> API header is in the QJOURNAL.H
file of the QSYSINC library.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="9.090909090909092%" id="d0e2068">Offset</th>
<th valign="top" width="27.27272727272727%" id="d0e2070">Field</th>
<th valign="top" width="18.181818181818183%" id="d0e2072">Format</th>
<th valign="top" width="45.45454545454545%" id="d0e2074">Description</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">1</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Entry length (JOENTL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. <p>If the journal
entry has the incomplete data indicator on, then this length does not include
that additional data which could be pointed to. This length includes the length
of the data that is actually returned, which includes entry specific data
of up to 32 766 bytes.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">6</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Sequence number (JOSEQN, <var class="varname">Seq_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (20)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">26</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Journal code (JOCODE, <var class="varname">Jrn_Code</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Identifies the primary category of the journal entry:<ul class="simple"><li><strong>A</strong> = System accounting entry</li>
<li><strong>B</strong> = Integrated file system operation</li>
<li><strong>C</strong> = Commitment control operation</li>
<li><strong>D</strong> = Database file operation</li>
<li><strong>E</strong> = Data area operation</li>
<li><strong>F</strong> = Database file member operation</li>
<li><strong>I</strong> = Internal operation</li>
<li><strong>J</strong> = Journal or receiver operation</li>
<li><strong>L</strong> = License management</li>
<li><strong>M</strong> = Network management data</li>
<li><strong>P</strong> = Performance tuning entry</li>
<li><strong>Q</strong> = Data queue operation</li>
<li><strong>R</strong> = Operation on a specific record</li>
<li><strong>S</strong> = Distributed mail services</li>
<li><strong>T</strong> = Audit trail entry</li>
<li><strong>U</strong> = User-generated entry (added by the <span class="cmdname">SNDJRNE</span> command
or <span class="apiname">QJOSJRNE</span> API)</li>
</ul>
<p>The journal codes are described in more detail in Journal code descriptions.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">27</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Journal entry type (JOENTT, <var class="varname">Entry_Type</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (2)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Further identifies the type of user-created or system-created entry.
See the Journal code finder for descriptions of the entry types.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">29</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Time stamp (JOTSTP)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (26)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Corresponds to the system date and time when the journal entry was
added in the journal receiver. The time stamp is in SAA format. The system cannot assure that
the time stamp is always in ascending order for sequential journal entries
because you can change the value of the system time.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">55</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Job name (JOJOB, <var class="varname">Job_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the job that added the entry. <div class="note"><span class="notetitle">Notes:</span> <ol><li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED is given for the job name.</li>
<li>If the job name was not available when the journal entry was deposited,
then *NONE is written for the job name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">65</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">User name (JOUSER, <var class="varname">User_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the user profile name of the user that started the job. <div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">75</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Job number (JONBR, <var class="varname">Job_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (6, 0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the job number of the user that started the job.<div class="note"><span class="notetitle">Note:</span> If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">81</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Program name (JOPGM, <var class="varname">Program_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true: <ul><li>The program name does not apply to this journal entry.</li>
<li>The program name was not available when the journal entry was made.</li>
</ul>
<p>For example, the program name is not available if the program was
destroyed.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>If the program that deposited the journal entry is an original program
model program, this data will be complete. Otherwise, this data will be unpredictable.</li>
<li>If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, *OMITTED is given for the program name.</li>
</ol>
</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">91</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Program library name (JOPGMLIB, <var class="varname">Program_Library_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The name of the library that contains the program that added the library.
If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED will be returned for the program library
name. <p>IF *NONE is returned for Program name, then *NONE is also returned
for the program library name.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">101</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Program library ASP device name (JOPGMDEV, <var class="varname">Program_ASP_Device_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The name of the ASP device that contains the program. If a RCVSIZOPT
or a FIXLENDTA option was specified that omitted the collection of this information,
then *OMITTED will be returned for the program library ASP device name. <p>IF
*NONE is returned for Program name, then *NONE is also returned for the program
library ASP device name.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">111</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Program library ASP number (JOPGMASP, <var class="varname">Program_ASP</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The number for the auxiliary storage pool that contains the program
that added the journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified
that omitted the collection of this information, then hexadecimal 0 will be
returned for the program library ASP number.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">116</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Object name (JOOBJ, <var class="varname">Object</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the object for which the journal entry was added.<sup>1</sup> This
is blank for some entries. <p>If the journaled object is an integrated file
system object, then this field is the first 10 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">126</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Object library (JOLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the library containing the object<sup>1</sup>. <p>If
the journaled object is an integrated file system object, then the first 6
characters of this field are the last 6 bytes of the file identifier.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">136</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Member name (JOMBR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the physical file member or is blank if the object
is not a physical file<sup>1</sup>.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">146</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Count or relative record number (JOCTRR, <var class="varname">Count_Rel_Rec_Num</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (20)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to type of journal entry.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">166</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Indicator flag (JOFLAG, <var class="varname">Indicator_Flag</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Contains an indicator for the operation. The following tables show
specific values for this field, if applicable: <ul><li><a href="rzakivarlength.htm#rzakivarlength__TBLENTAY">APYJRNCHG and
RMVJRNCHG journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTCM">COMMIT journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIZ">INZPFM journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTIU">IPL and in-use
journal entries</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTBR">Journal code
R (all journal entry types except IL)</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTRB">ROLLBACK journal
entry</a></li>
<li><a href="rzakivarlength.htm#rzakivarlength__TBLENTJM">Start-journal
journal entries</a></li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">167</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Commit control ID (JOCCID, <var class="varname">Commit_Cycle_Identifier </var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (20)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. <p>The commit cycle identifier
is found in every journal entry that is associated with a commitment transaction.
If the journal entry was not made as part of a commitment transaction, this
field is zero.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">187</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">User profile (JOUSPF, <var class="varname">User_profile</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the user profile under which the job was running
when the entry was created.<div class="note"><span class="notetitle">Note:</span> If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.</div>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">197</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">System name (JOSYNM, <var class="varname">System_Name</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (8)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the name of the system on which the entry is being displayed,
printed, retrieved, or received if the journal receiver was attached prior
to installing V4R2M0 on the system. If the journal eceiver was attached while
the system was running V4R2M0 or a later release, the system name is the system
where the journal entry was actually deposited.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">205</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Journal identifier (JOJID, <var class="varname">Jid</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Specifies the journal identifier (JID) for the object. When journaling
is started for an object, the system assigns a unique JID to that object.
The JID remains constant even if the object is renamed or moved. However,
if journaling is stopped, there is no guarantee that the JID will be the same
if journaling is started again for the same object. <p>If no JID is associated
with the entry, this field has hexadecimal zeros.</p>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">215</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Referential constraint (JORCST, <var class="varname">Referential_Constraint</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Indicates whether this entry was recorded for actions that occurred
on records that are part of a referential constraint. <p>The possible values
are:</p>
<ul class="simple"><li><strong>0</strong>  = This entry was not created as part of a referential
constraint.</li>
<li><strong>1</strong>  = This entry was created as part of a referential constraint.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">216</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Trigger (JOTGR, <var class="varname">Trigger</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Indicates whether this entry was created as result of a trigger program. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong>  = This entry was not created as the result of a trigger
program.</li>
<li><strong>1</strong>  = This entry was created as the result of a trigger program.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">217</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Incomplete data (JOINCDAT, <var class="varname">Incomplete_Data</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Indicates whether this entry has data that is not being retrieved for
one of the following reasons: <ul><li>The length of the entry-specific data exceeds 32 766 bytes.</li>
<li>The entry is associated with a database file that has one or more fields
of data type BLOB (binary large object), CLOB (character large object), or
DBCLOB (double-byte character large object).</li>
</ul>
<p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has all possible data</li>
<li><strong>1</strong> = This entry has incomplete data.</li>
</ul>
<p>Any data which is marked as incomplete, can only be viewed by using
either the <span class="apiname">QjoRetrieveJournalEntries</span> API, or the command <span class="cmdname">RCVJRNE</span> with
any of the following parameters:</p>
<ul><li>ENTFMT(*TYPEPTR)</li>
<li>ENTFMT(*JRNENTFMT)</li>
<li>RTNPTR (with any value specified other than *NONE)</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">218</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Ignored by <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> (JOIGNAPY, <var class="varname">Ignore_during_APYRMV</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Indicates whether this journal entry will be ignored by the execution
of the APYJRNCHG or RMVJRNCHG commands, even though normally this journal
entry type has an effect during those command invocations. <p>The possible
values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry is not ignored by the <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> commands.</li>
<li><strong>1</strong> = This entry is ignored by the <span class="cmdname">APYJRNCHG</span> or <span class="cmdname">RMVJRNCHG</span> commands.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">219</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Minimized entry-specific data (JOMINESD, <var class="varname">Min_ESD</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Indicates whether this entry has minimized entry specific data. <p>The
possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry has complete entry specific data.</li>
<li><strong>1</strong> = This entry has minimized entry specific data.</li>
<li><strong>2</strong> = This entry has entry specific data that has been minimized
on field boundaries.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">220</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Object indicator (JOOBJIND, <var class="varname">Object_Name_Indicator</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">An indicator with respect to the information in the object field<sup>2</sup>.
The valid values are: <ul class="simple"><li><strong>0</strong> = Either the journal entry has no object information or
the object information in the journal entry header does not necessarily reflect
the name of the object at the time the journal entry was deposited into the
journal.</li>
<li><strong>1</strong> = The object information in the journal entry header
reflects the name of the object at the time the journal entry was deposited
into the journal.</li>
<li><strong>2</strong> = The object information in the journal entry header
does not necessarily reflect the name of the object at the time the journal
entry was deposited into the journal. The object information may be returned
as a previously known name for the object prior to the journal entry being
deposited into the journal or be returned as *UNKNOWN.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">221</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">System sequence number (JOSYSSEQ, <var class="varname">System_Sequence_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (20)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The system sequence number indicates the relative sequence of when
this journal entry was deposited into the journal. You can use the sequence
number to sequentially order journal entries that are in separate journal
receivers. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted
the collection of this information, then hexadecimal 0 will be returned for
the system sequence number.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">241</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Receiver name (JORCV)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The name assigned to the journal receiver</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">251</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Receiver library name (JORCVLIB)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The name of the library in which the journal receiver resides.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">261</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Receiver library ASP device name (JORCVDEV)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (10)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The name of the ASP device for journal receivers that reside on an
independent disk pool</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">271</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Receiver library ASP number (JORCVASP)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The number of the ASP on which the journal receiver resides.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">276</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Arm number (JOARM, <var class="varname">Arm_Number</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (5,0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The number of the disk arm that contains the journal entry.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">281</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Thread identifier (JOTHDX, <var class="varname">Thread_ID</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Hexadecimal (8)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Identifies the thread within the process that added the journal entry.
If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then hexadecimal 0 will be returned for the thread identifier.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">289</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Thread identifier formatted (JOTHD)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (16)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">See Thread identifier.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">305</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Address family (JOADF, <var class="varname">Address_Family</var>)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The address family identifies the format of the remote address for
this journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified that
omitted the collection of this information, then 0 will be returned for the
address family. <p>The possible values are:</p>
<ul class="simple"><li><strong>0</strong> = This entry was not associated with any remote address.</li>
<li><strong>4</strong> = The format of the remote address is Internet protocol
version 4.</li>
<li><strong>6</strong> = The format of the remote address is Internet protocol version
6.</li>
</ul>
</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">306</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Remote port (JORPORT)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Zoned (5, 0)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The remote port of a the journal entries. If a RCVSIZOPT or a FIXLENDTA
option was specified that omitted the collection of this information, then
hexadecimal 0 will be returned for the remote port.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">311</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Remote address (JORADR)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (46)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The remote address of a the journal entries. If a RCVSIZOPT or a FIXLENDTA
option was specified that omitted the collection of this information, then
hexadecimal 0 will be returned for the remote address.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">357</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Logical unit of work (JOLUW)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (39)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The logical unit of work identifies entries to be associated with a
given unit of work, usually within a commit cycle. If a RCVSIZOPT or a FIXLENDTA
option was specified that omitted the collection of this information, then
blanks will be returned for the logical unit of work.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">396</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Transaction identifier (JOXID)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (140)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">See the QSYSINC/H.XA header file for the layout of this data. If a
RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then the displacement to the transaction identifier is
0 and no transaction identifier is returned.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">536</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Object type (JOOBJTYP)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (7)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The type of object associated with this entry. (*FILE, *DTAARA, etc)</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">543</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">File type indicator (JOFILTYP)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (1)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The type of object associated with this entry. ('0'
is physical, '1' is logical)</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">544</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Nested commit level (JOCMTLVL)</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (7)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">The nested transaction level at which this entry was
deposited.</td>
</tr>
<tr><td valign="top" width="9.090909090909092%" headers="d0e2068 ">551</td>
<td valign="top" width="27.27272727272727%" headers="d0e2070 ">Reserved</td>
<td valign="top" width="18.181818181818183%" headers="d0e2072 ">Char (5)</td>
<td valign="top" width="45.45454545454545%" headers="d0e2074 ">Reserved area. It always contains hexadecimal zeros.</td>
</tr>
<tr><td colspan="4" valign="top" headers="d0e2068 d0e2070 d0e2072 d0e2074 "><div class="note"><span class="notetitle">Notes:</span> <p><sup>1</sup>If
the journal receiver was attached prior to installing V4R2M0 on your system,
then the following items are true:</p>
<ul><li>If *ALLFILE is specified for the FILE parameter on the <span class="cmdname">DSPJRN</span>, <span class="cmdname">RCVJRNE</span>,
or <span class="cmdname">RTVJRNE</span> command, then the fully qualified name is the
most recent name of the file when the newest receiver in the receiver range
was the attached receiver and when the file was still being journaled.</li>
<li>If a file name is specified or if library *ALL is specified on the FILE
parameter, the current fully qualified name of the file appears in the converted
journal entry.</li>
</ul>
<p>If the journal receiver was attached while V4R2M0 or a later release
was running on the system, the fully qualified name is the name of the object
at the time the journal entry was deposited.</p>
<p><sup>2</sup>This value
will be returned only when retrieving journal entries from a remote journal
and the remote journal is currently being caught up from its source journal.
A remote journal is being caught up from its source journal when the <span class="cmdname">Change
Remote Journal (CHGRMTJRN)</span> command or <span class="apiname">Change Journal State
(QjoChangeJournalState)</span> API is called and is currently replicating
journal entries to the remote journal. After the call to the <span class="cmdname">CHGRMTJRN</span> command
or <span class="apiname">QjoChangeJournalState</span> API returns, the remote journal
is maintained with a synchronous or asynchronous delivery mode, and the remote
journal is no longer being caught up.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div><div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzakicodes.htm" title="This topic provides a description of all of the journal codes and categories.">Journal code descriptions</a></div>
<div><a href="rzakidsplyjrnentry.htm" title="Use the Display Journal (DSPJRN) command to display journal entries. The entries are displayed at a work station, printed, or written to an output file. You cannot directly access the journal entries in the form in which they are contained in the journal receivers.">Display and print journal entries</a></div>
<div><a href="rzakiformatdbout.htm" title="When you direct the output of the Display Journal (DSPJRN) command to a database file, the system creates the output file records in a standard format.">Format of database output files</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>
Reference in New Issue Copy Permalink