friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14ed2849c6
ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/rtvjrne.htm

1846 lines
84 KiB
HTML
Raw Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Retrieve Journal Entry (RTVJRNE)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="RTVJRNE.Top_Of_Page"></a>
<h2>Retrieve Journal Entry (RTVJRNE)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>Compiled CL program or interpreted REXX (*BPGM *IPGM *BREXX *IREXX)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#RTVJRNE.PARAMETERS.TABLE">Parameters</a><br>
<a href="#RTVJRNE.COMMAND.EXAMPLES">Examples</a><br>
<a href="#RTVJRNE.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="RTVJRNE"></a>
<p>The Retrieve Journal Entry (RTVJRNE) command allows you to get a particular journal entry and place the results in CL variables. The CL variables contain information, such as the sequence number of the retrieved entry, and are useful in automating certain types of recovery functions. The search for a journal entry can be restricted to an object, to a range of journal receivers, to a range of journal entries, to a journal code, to an entry type, to a job, to a program, to a user profile, or to a commit cycle identifier. Multiple limitation criteria can be specified. If more than one journal entry satisfies the search values specified, the first occurrence of a journal entry satisfying all of the specified search values is returned. If there is no journal entry satisfying the search values specified, the command ends with an escape message, and the return CL variables (RTNSEQNBRLRG, RTNSEQNBR, RTNJRNCDE, RTNENTTYP, RTNRCV, RTNRCVLIB and RTNJRNE) remain the same.
</p>
<p>The order of the search through the journal entries can be ascending or descending. The search order is determined by the value specified in the SEARCH parameter. The value for the FROM parameter must come before the value specified for the TO parameter in the specified search order.
</p>
<p>The CL prompt for this command lists the minimum length for retrieved variables next to the correct parameters. For character variables, a single number is shown. For decimal variables, two numbers are shown. The first number indicates the minimum variable length, and the second number indicates the minimum number of decimal positions.
</p>
<p><b>Restrictions:</b>
</p>
<ul>
<li>If the sequence number is reset in the range of the receivers specified, the first occurrence of FROMENTLRG or FROMENT is used, if they are specified. If TOENTLRG or TOENT is specified, the first occurance after the FROMENTLRG or FROMENT entry is used, if FROMENTLRG or FROMENT is specified. Otherwise the first occurance is used.
</li>
<li>The FILE, OBJ, OBJPATH, OBJFID, SUBTREE, PATTERN, JRNCDE, ENTTYP, JOB, PGM, USRPRF, CCIDLRG, CMTCYCID, and DEPENT parameters can be used to specify a subset of all available entries within a range of journal entries.
<ul>
<li>If no values are specified using these parameters, all available journal entries are retrieved.
</li>
<li>If more than one of these parameters are specified, then a journal entry must satisfy all of the values specified on these parameters, except when *IGNFILSLT or *IGNOBJSLT is specified on the JRNCDE parameter.
</li>
<li>If a journal code is specified on the JRNCDE parameter and *IGNFILSLT is the second element of that journal code, then journal entries with the specified journal code are selected if they satisfy all selection criteria except what is specified on the FILE parameter.
</li>
<li>If a journal code is specified on the JRNCDE parameter and *IGNOBJSLT is the second element of that journal code, then journal entries with the specified journal code are selected if they satisfy all selection criteria except what is specified on the OBJ, OBJPATH, OBJFID, SUBTREE, and PATTERN parameters.
</li>
</ul>
</li>
<li>The JOB, PGM, and USRPRF parameters cannot be used to specify selection criteria if one or more journal receivers in the specified receiver range was attached to the journal when a receiver size option (RCVSIZOPT) or a fixed length data option (FIXLENDTA) that would have omitted this data was in effect.
</li>
<li>If more than the maximum number of objects is identified (32767 objects), an error occurs and no entries are retrieved. This restriction is ignored if *ALLFILE is specified or no objects are specified.
</li>
<li>When journal caching is being used, entries that are in the cache are not retrievable.
</li>
</ul>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="RTVJRNE.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.JRN"><b>JRN</b></a></td>
<td valign="top">Journal</td>
<td valign="top"><i>Qualified object name</i></td>
<td valign="top" rowspan="3">Required, Positional 1</td>
</tr>
<tr>
<td valign="top">Qualifier 1: Journal</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top" rowspan="5"><a href="#RTVJRNE.FILE"><b>FILE</b></a></td>
<td valign="top">Journaled physical file</td>
<td valign="top">Single values: *ALLFILE<br>Other values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="5">Optional, Positional 2</td>
</tr>
<tr>
<td valign="top">Element 1: File</td>
<td valign="top">
<i>Qualified object name</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Qualifier 1: File</td>
<td valign="top"><i>Name</i>, *ALL</td>
</tr><tr>
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top">Element 2: Member</td>
<td valign="top">
<i>Name</i>, <b><u>*FIRST</u></b>, *ALL, *NONE</td>
</tr>
<tr>
<td valign="top" rowspan="6"><a href="#RTVJRNE.OBJ"><b>OBJ</b></a></td>
<td valign="top">Objects</td>
<td valign="top">Values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="6">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Object</td>
<td valign="top">
<i>Qualified object name</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Qualifier 1: Object</td>
<td valign="top"><i>Name</i>, *ALL</td>
</tr><tr>
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top">Element 2: Object type</td>
<td valign="top">
*FILE, *DTAARA, *DTAQ</td>
</tr>
<tr>
<td valign="top">Element 3: Member, if data base file</td>
<td valign="top">
<i>Name</i>, <b><u>*FIRST</u></b>, *ALL, *NONE</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.OBJPATH"><b>OBJPATH</b></a></td>
<td valign="top">Objects</td>
<td valign="top">Values (up to 300 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Name</td>
<td valign="top">
<i>Path name</i></td>
</tr>
<tr>
<td valign="top">Element 2: Include or omit</td>
<td valign="top">
<b><u>*INCLUDE</u></b>, *OMIT</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.OBJFID"><b>OBJFID</b></a></td>
<td valign="top">File identifier</td>
<td valign="top">Values (up to 300 repetitions): <i>Hexadecimal value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.SUBTREE"><b>SUBTREE</b></a></td>
<td valign="top">Directory subtree</td>
<td valign="top"><b><u>*NONE</u></b>, *ALL</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="7"><a href="#RTVJRNE.RCVRNG"><b>RCVRNG</b></a></td>
<td valign="top">Range of journal receivers</td>
<td valign="top">Single values: <b><u>*CURRENT</u></b>, *CURCHAIN<br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="7">Optional, Positional 3</td>
</tr>
<tr>
<td valign="top">Element 1: Starting journal receiver</td>
<td valign="top">
<i>Qualified object name</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Qualifier 1: Starting journal receiver</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top">Element 2: Ending journal receiver</td>
<td valign="top">
Single values: <b><u>*CURRENT</u></b><br>Other values: <i>Qualified object name</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Qualifier 1: Ending journal receiver</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.PATTERN"><b>PATTERN</b></a></td>
<td valign="top">Name pattern</td>
<td valign="top">Values (up to 20 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Pattern</td>
<td valign="top">
<i>Character value</i>, <b><u>*</u></b></td>
</tr>
<tr>
<td valign="top">Element 2: Include or omit</td>
<td valign="top">
<b><u>*INCLUDE</u></b>, *OMIT</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.FROMENTLRG"><b>FROMENTLRG</b></a></td>
<td valign="top">Starting large sequence number</td>
<td valign="top"><i>Character value</i>, <b><u>*FIRST</u></b>, *LAST</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.FROMTIME"><b>FROMTIME</b></a></td>
<td valign="top">Starting date and time</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Starting date</td>
<td valign="top">
<i>Date</i></td>
</tr>
<tr>
<td valign="top">Element 2: Starting time</td>
<td valign="top">
<i>Time</i></td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.TOENTLRG"><b>TOENTLRG</b></a></td>
<td valign="top">Ending large sequence number</td>
<td valign="top"><i>Character value</i>, <b><u>*LAST</u></b>, *FIRST</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.TOTIME"><b>TOTIME</b></a></td>
<td valign="top">Ending date and time</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Ending date</td>
<td valign="top">
<i>Date</i></td>
</tr>
<tr>
<td valign="top">Element 2: Ending time</td>
<td valign="top">
<i>Time</i></td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.SEARCH"><b>SEARCH</b></a></td>
<td valign="top">Search</td>
<td valign="top"><b><u>*ASCEND</u></b>, *DESCEND</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#RTVJRNE.JRNCDE"><b>JRNCDE</b></a></td>
<td valign="top">Journal codes</td>
<td valign="top">Single values: <b><u>*ALL</u></b>, *CTL<br>Other values (up to 16 repetitions): <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Journal code value</td>
<td valign="top">
A, B, C, D, E, F, J, L, M, P, Q, R, S, T, U</td>
</tr>
<tr>
<td valign="top">Element 2: Journal code selection</td>
<td valign="top">
<b><u>*ALLSLT</u></b>, *IGNFILSLT, *IGNOBJSLT</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.ENTTYP"><b>ENTTYP</b></a></td>
<td valign="top">Journal entry types</td>
<td valign="top">Single values: <b><u>*ALL</u></b>, *RCD<br>Other values (up to 300 repetitions): <i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="4"><a href="#RTVJRNE.JOB"><b>JOB</b></a></td>
<td valign="top">Job name</td>
<td valign="top">Single values: <b><u>*ALL</u></b>, *<br>Other values: <i>Qualified job name</i></td>
<td valign="top" rowspan="4">Optional</td>
</tr>
<tr>
<td valign="top">Qualifier 1: Job name</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: User</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 3: Number</td>
<td valign="top">000000-999999</td>
</tr><tr>
<td valign="top"><a href="#RTVJRNE.PGM"><b>PGM</b></a></td>
<td valign="top">Program</td>
<td valign="top"><i>Name</i>, <b><u>*ALL</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.USRPRF"><b>USRPRF</b></a></td>
<td valign="top">User profile</td>
<td valign="top"><i>Name</i>, <b><u>*ALL</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.CCIDLRG"><b>CCIDLRG</b></a></td>
<td valign="top">Commit cycle large identifier</td>
<td valign="top"><i>Character value</i>, <b><u>*ALL</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.DEPENT"><b>DEPENT</b></a></td>
<td valign="top">Dependent entries</td>
<td valign="top"><b><u>*ALL</u></b>, *NONE</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.ENTFMT"><b>ENTFMT</b></a></td>
<td valign="top">Entry format</td>
<td valign="top"><b><u>*TYPE1</u></b>, *TYPE2, *TYPE3, *TYPE4, *TYPE5</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.FMTMINDTA"><b>FMTMINDTA</b></a></td>
<td valign="top">Format minimized data</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.NULLINDLEN"><b>NULLINDLEN</b></a></td>
<td valign="top">Null value indicators length</td>
<td valign="top">1-8000</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.INCENT"><b>INCENT</b></a></td>
<td valign="top">Include entries</td>
<td valign="top"><b><u>*CONFIRMED</u></b>, *ALL</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.FROMENT"><b>FROMENT</b></a></td>
<td valign="top">Starting sequence number</td>
<td valign="top">1-9999999999, <b><u>*FIRST</u></b>, *LAST</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.TOENT"><b>TOENT</b></a></td>
<td valign="top">Ending sequence number</td>
<td valign="top">1-9999999999, <b><u>*LAST</u></b>, *FIRST</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.CMTCYCID"><b>CMTCYCID</b></a></td>
<td valign="top">Commit cycle identifier</td>
<td valign="top">1-9999999999, <b><u>*ALL</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNSEQLRG"><b>RTNSEQLRG</b></a></td>
<td valign="top">CL var for RTNSEQLRG (20)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNJRNCDE"><b>RTNJRNCDE</b></a></td>
<td valign="top">CL var for RTNJRNCDE (1)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNENTTYP"><b>RTNENTTYP</b></a></td>
<td valign="top">CL var for RTNENTTYP (2)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNRCV"><b>RTNRCV</b></a></td>
<td valign="top">CL var for RTNRCV (10)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNRCVLIB"><b>RTNRCVLIB</b></a></td>
<td valign="top">CL var for RTNRCVLIB (10)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNJRNE"><b>RTNJRNE</b></a></td>
<td valign="top">CL var for RTNJRNE (1)</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#RTVJRNE.RTNSEQNBR"><b>RTNSEQNBR</b></a></td>
<td valign="top">CL var for RTNSEQNBR (10 0)</td>
<td valign="top"><i>Decimal number</i></td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="RTVJRNE.JRN"></a>
<h3>Journal (JRN)</h3>
<p>Specifies the journal from which the journal entry is retrieved.
</p>
<p>This is a required parameter.
</p>
<p><b>Qualifier 1: Journal</b>
</p>
<dl>
<dt><b><i>journal-name</i></b></dt>
<dd>Specify the name of the journal.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is searched. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>library-name</i></b></dt>
<dd>Specify the name of the library to be searched.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.FILE"></a>
<h3>Journaled physical file (FILE)</h3>
<p>Specifies a maximum of 300 files whose journal entries are retrieved. This parameter also specifies the file member whose journal entries are to be retrieved.
</p>
<p>To determine which journal entries are to be retrieved, based on the specified file member name, the following is done:
</p>
<ul>
<li>If the journal is a local journal, and if the specified file member currently exists on the system, the journal identifier id determined from the specified file member. All journal entries in the specified receiver range for that journal identifier are retrieved.
</li>
<li>If the journal is a remote journal, or if the specified file member does not currently exist on the system, the specified receiver range is searched to determine all possible journal identifiers that are associated with the specified file member. All journal entries in the specified receiver range for those journal identifiers are retrieved. Specify the library name or *CURLIB to have entries returned for the file.
<p>There may be more than one journal identifier associated with a specified object within the specified receiver range. This can happen when a journaled object is deleted, and then a new object is created with the same name and journaled to the same journal.
</p>
</li>
</ul>
<p><b>Notes:</b>
</p>
<ol>
<li>The journal identifier is the unique identifier associated with the object when journaling is started for that object. The journal identifier stays constant, even if the object is renamed, moved, or restored. See the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter for more information.
</li>
<li>When specifying a database file on this parameter, journal entries with the following journal code values are retrieved only if they satisfy the values specified on the other parameters:
<ul>
<li>Journal code D (database file-level information entries).
</li>
<li>Journal code F (file member-level information entries).
</li>
<li>Journal code R (record-level information entries).
</li>
<li>Journal code U (user-generated entries).
</li>
<li>Other journal codes, if *IGNFILSLT is specified on that journal code. If *ALLSLT is specified on that journal code, no journal entries with that code are retrieved.
</li>
</ul>
</li>
</ol>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*ALLFILE</b></dt>
<dd>The search for the entry being retrieved is not limited to a specified file name. All journal entries are retrieved, regardless of which objects, if any, the entries are associated with.
</dd>
</dl>
<p><b>Element 1: File</b>
</p>
<p><b>Qualifier 1: File</b>
</p>
<dl>
<dt><b>*ALL</b></dt>
<dd>Journal entries for all physical files in the specified library (the library name must be specified) whose journaled changes are currently in the journal receiver are retrieved. If *ALL is specified and the user does not have the required authority to all of the files, an error occurs, and the command ends.
</dd>
<dt><b><i>physical-file-name</i></b></dt>
<dd>Specify the name of the database physical file for which a journal entry is retrieved.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is searched. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>library-name</i></b></dt>
<dd>Specify the name of the library to be searched.
</dd>
</dl>
<p><b>Element 2: Member</b>
</p>
<dl>
<dt><b><u>*FIRST</u></b></dt>
<dd>Journal entries for the database file and the first member in the file are retrieved.
</dd>
<dt><b>*ALL</b></dt>
<dd>Journal entries for the database file and all the currently existing members in the file are retrieved.
</dd>
<dt><b>*NONE</b></dt>
<dd>Only entries for the database file are retrieved. Entries for members of the file are not retrieved.
</dd>
<dt><b><i>member-name</i></b></dt>
<dd>Specify the name of the member for which an entries are retrieved.
</dd>
</dl>
<p>If *ALL is specified for the file-name element, this member name is used for all applicable files in the library. For example, if library-name/*ALL *FIRST is specified on the FILE parameter, the journal entries of the first members of all applicable files in the specified library are retrieved.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.OBJ"></a>
<h3>Objects (OBJ)</h3>
<p>Specifies a maximum of 300 qualified object names whose journal entries are to be retreived The possible object types are *FILE, *DTAARA, and *DTAQ. If *FILE is specified, this parameter also specifies the name of the file member whose journal entries are to be retrieved.
</p>
<p>Either the FILE parameter may be specified, or one or more of the object parameters (OBJ, OBJPATH, or OBJFID) may be specified, but not both.
</p>
<p>To determine which journal entries are to be retrieved, based on the specified object name, the following is done:
</p>
<ul>
<li>If the journal is a local journal, and if the specified object currently exists on the system, the journal identifier is determined from the specified object. All journal entries in the specified receiver range for that journal identifier are retrieved.
</li>
<li>If the journal is a remote journal, or if the specified object does not currently exist on the system, the specified receiver range is searched to determine all possible journal identifiers that are associated with the specified object. All journal entries in the specified receiver range for those journal identifiers are retrieved. Specify the library name or *CURLIB to have entries returned for an object.
<p>There may be more than one journal identifier associated with a specified object within the specified receiver range. This can happen when a journaled object is deleted, and then a new object is created with the same name and journaled to the same journal.
</p>
</li>
</ul>
<p><b>Notes:</b>
</p>
<ol>
<li>The journal identifier is the unique identifier associated with the object when journaling is started for that object. The journal identifier stays constant, even if the object is renamed, moved or restored. See the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter for more information.
</li>
<li>When specifying an object on this parameter, journal entries with the following journal code values are retrieved only if they satisfy the values specified on the other parameters in addition to the object name specification:
<ul>
<li>Journal code D (database file-level information entries).
</li>
<li>Journal code E (data area information entries).
</li>
<li>Journal code F (file member-level information entries).
</li>
<li>Journal code Q (data queue information entries).
</li>
<li>Journal code R (record-level information entries).
</li>
<li>Journal code U (user-generated entries).
</li>
<li>Other journal codes, if *IGNOBJSLT is the second element of the journal code. If *ALLSLT is the second element of the journal code, no journal entries with that code are retrieved.
</li>
</ul>
</li>
</ol>
<p><b>Element 1: Object</b>
</p>
<p><b>Qualifier 1: Object</b>
</p>
<dl>
<dt><b>*ALL</b></dt>
<dd>Journal entries for all objects of the specified object type in the specified library (the library name must be specified) whose journaled changes are currently in the journal receiver are retrieved. The library name must be specified. If *ALL is specified and the user does not have the required authority for all objects in the library, a message is sent and the command ends.
</dd>
<dt><b><i>object-name</i></b></dt>
<dd>Specify the name of the object whose journaled changes are to be retrieved.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is searched. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>library-name</i></b></dt>
<dd>Specify the name of the library to be searched.
</dd>
</dl>
<p><b>Element 2: Object type</b>
</p>
<p>Specify the object type of the object whose journaled changes are to be retrieved.
</p>
<dl>
<dt><b>*FILE</b></dt>
<dd>Entries for database files and database file members are retrieved.
</dd>
<dt><b>*DTAARA</b></dt>
<dd>Entries for data areas are retrieved.
</dd>
<dt><b>*DTAQ</b></dt>
<dd>Entries for data queues are retrieved.
</dd>
</dl>
<p><b>Element 3: Member, if data base file</b>
</p>
<p>Specify the name of the member in the file whose journal entries are to be retrieved. If *ALL is specified for the first part of this parameter, the value specified for the member name is used for all applicable files in the library. For example, if *FIRST is specified, the journal entries of the first member of all applicable files in the specified library are retrieved.
</p>
<p>
<b>Note: </b>If the specified object type is not *FILE, the member name element value is ignored.
</p>
<dl>
<dt><b><u>*FIRST</u></b></dt>
<dd>Journal entries for the database file and the first member in the file are retrieved.
</dd>
<dt><b>*ALL</b></dt>
<dd>Journal entries for the database file and all the currently existing members in the file are retrieved.
</dd>
<dt><b>*NONE</b></dt>
<dd>Only entries for the database file are retrieved. Entries for members of the file are not retrieved.
</dd>
<dt><b><i>member-name</i></b></dt>
<dd>Specify the name of the member for which an entries are retrieved.
</dd>
</dl>
<p>If *ALL is specified for the object-name element, this member name is used for all applicable files in the library. For example, if library-name/*ALL *FILE *FIRST is specified on the OBJ parameter, the journal entries of the first members of all applicable files in the specified library are retrieved.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.OBJPATH"></a>
<h3>Objects (OBJPATH)</h3>
<p>Specifies a maximum of 300 objects whose journal entries are to be retrieved. Only objects whose path name identifies an object of type *STMF, *DIR or *SYMLNK that are in the "root" ('/'), QOpenSys, and user-defined file systems are supported. All other objects are ignored.
</p>
<p>This parameter is not valid for remote journals.
</p>
<p>Either the FILE parameter may be specified, or one or more of the object parameters (OBJ, OBJPATH, or OBJFID) may be specified, but not both.
</p>
<p>Only objects that are currently linked with the specified path name and have a journal identifier associated with them are used in journal entry selection. If the specified object does exist, the journal identifier associated with that link is used for journal entry selection. If a specified object does not exist or does not have a journal identifier associated with it, that link is not used in selecting journal entries and no error is sent.
</p>
<p><b>Notes:</b>
</p>
<ol>
<li>The journal identifier is the unique identifier associated with the object when journaling is started for that object. The journal identifier stays constant, even if the object is renamed, moved or restored. See the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter for more information.
</li>
<li>When specifying an object on this parameter, journal entries with the following journal code values are retrieved only if they satisfy the values specified on the other parameters in addition to the object name specification:
<ul>
<li>Journal code B (integrated file system information entries).
</li>
<li>Journal code U (user-generated entries).
</li>
<li>Other journal codes, if *IGNOBJSLT is the second element of the journal code. If *ALLSLT is the second element of the journal code, no journal entries with that code are retrieved.
</li>
</ul>
</li>
</ol>
<p><b>Element 1: Name</b>
</p>
<dl>
<dt><b><i>path-name</i></b></dt>
<dd>Entries for objects identified by the path name are retrieved.
<p>A pattern can be specified in the last part of the path name. An asterisk (*) matches any number of characters and a question mark (?) matches a single character. If the path name is qualified or contains a pattern, it must be enclosed in apostrophes. Symbolic links within the path name will not be followed. If the path name begins with the tilde character, then the path is assumed to be relative to the appropriate home directory.
</p>
<p>Additional information about path name patterns is in the Integrated file system information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
</dd>
</dl>
<p><b>Element 2: Include or omit</b>
</p>
<p>The second element specifies whether names that match the path name should be included or omitted from the operation. Note that in determining whether a name matches a pattern, relative name patterns are always treated as relative to the current working directory.
</p>
<p>
<b>Note: </b>The SUBTREE parameter specifies whether the subtrees are included or omitted.
</p>
<dl>
<dt><b><u>*INCLUDE</u></b></dt>
<dd>The objects that match the object name pattern are to be included in determining what journal entries are retrieved, unless overridden by an *OMIT specification.
</dd>
<dt><b>*OMIT</b></dt>
<dd>The objects that match the object name pattern are not to be included in determining what journal entries are retrieved. This overrides an *INCLUDE specification and is intended to be used to omit a subset of a previously selected pattern.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.OBJFID"></a>
<h3>File identifier (OBJFID)</h3>
<p>Specifies a maximum of 300 file identifiers (FID) whose journal entries are to be retrieved. FIDs are a unique identifier associated with integrated file system related objects. This field is input in hexadecimal format. Only objects whose FID identifies an object of type *STMF, *DIR or *SYMLNK that are in the "root" ('/'), QOpenSys, and user-defined file systems are supported. All other objects are ignored.
</p>
<p>Either the FILE parameter may be specified, or one or more of the object parameters (OBJ, OBJPATH, or OBJFID) may be specified, but not both.
</p>
<p>To determine which journal entries are to be received, based on the specified file identifier, the following is done:
</p>
<ul>
<li>If the journal is a local journal, and if the specified object currently exists on the system, the journal identifier is determined from the specified object. All journal entries in the specified receiver range for that journal identifier are retrieved.
</li>
<li>If the journal is a remote journal, or if the specified object does not currently exist on the system, the specified receiver range is searched to determine all possible journal identifiers that are associated with the specified object. All journal entries in the specified receiver range for those journal identifiers are retrieved.
</li>
</ul>
<p><b>Notes:</b>
</p>
<ol>
<li>The journal identifier is the unique identifier associated with the object when journaling is started for that object. The journal identifier stays constant, even if the object is renamed, moved or restored. See the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter for more information.
</li>
<li>When specifying an object on this parameter, journal entries with the following journal code values are retrieved only if they satisfy the values specified on the other parameters in addition to the object name specification:
<ul>
<li>Journal code B (integrated file system information entries).
</li>
<li>Journal code U (user-generated entries).
</li>
<li>Other journal codes, if *IGNOBJSLT is the second element of the journal code. If *ALLSLT is the second element of the journal code, no journal entries with that code are retrieved.
</li>
</ul>
</li>
</ol>
<dl>
<dt><b><i>file-identifier</i></b></dt>
<dd>Entries for objects identified with the FID are retrieved.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.SUBTREE"></a>
<h3>Directory subtree (SUBTREE)</h3>
<p>Specifies whether the directory subtrees are included in determining the objects for which journal entries are to be retrieved.
</p>
<p>
<b>Note: </b>This parameter is only valid if one or more path names were specified on the OBJPATH parameter.
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>Only the objects that match the selection criteria are processed. The objects within selected directories are not implicitly processed.
</dd>
<dt><b>*ALL</b></dt>
<dd>All objects that meet the selection criteria are processed in addition to the entire subtree of each directory that matches the selection criteria. The subtree includes all sub-directories and the objects within those sub-directories.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RCVRNG"></a>
<h3>Range of journal receivers (RCVRNG)</h3>
<p>Specifies the starting (first) and ending (last) journal receivers used in the search for a journal entry to be retrieved. The system starts the search with the starting journal receiver (as specified by the first value) and proceeds through the receiver chain until the ending journal receiver (as specified by the second value) is processed.
</p>
<p>If *ASCEND is specified for the <b>Search</b> prompt (SEARCH parameter), journal receivers must be specified in the order of oldest to newest. If *DESCEND is specified for the <b>Search (SEARCH)</b> parameter, journal receivers must be specified in the order of newest to oldest.
</p>
<p>
<b>Note: </b>If the maximum number of receivers (2045) in the range is surpassed, an error occurs and no journal entries are retrieved.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>The journal receiver that is currently attached when starting to retrieve journal entries is used.
</dd>
<dt><b>*CURCHAIN</b></dt>
<dd>The journal receiver chain that includes the journal receiver that is currently attached when starting to retrieve journal entries is used. This receiver chain does not cross a break in the chain. If there is a break in the chain, the receiver range is from the most recent break in the chain through the receiver that is attached when starting to retrieve journal entries.
</dd>
</dl>
<p><b>Element 1: Starting journal receiver</b>
</p>
<p><b>Qualifier 1: Starting journal receiver</b>
</p>
<dl>
<dt><b><i>starting-journal-receiver-name</i></b></dt>
<dd>Specify the name of the first journal receiver that contains journal entries to be retrieved.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the journal receiver. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>library-name</i></b></dt>
<dd>Specify the library where the journal receiver is located.
</dd>
</dl>
<p><b>Element 2: Ending journal receiver</b>
</p>
<p><b>Qualifier 1: Ending journal receiver</b>
</p>
<dl>
<dt><b><u>*CURRENT</u></b></dt>
<dd>The journal receiver that is currently attached when starting to retrieve journal entries is used.
</dd>
<dt><b><i>ending-journal-receiver</i></b></dt>
<dd>Specify the name of the last journal receiver containing journal entries to be searched. If the end of the receiver chain is reached before a receiver of this name is found, an error message is sent and no journal entry is retrieved.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the journal receiver. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>library-name</i></b></dt>
<dd>Specify the library where the journal receiver is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.PATTERN"></a>
<h3>Name pattern (PATTERN)</h3>
<p>Specifies a maximum of 20 patterns to be used to include or omit objects for which journal entries are to be retrieved.
</p>
<p>Only the last part of the path name will be considered for the name pattern match. Path name delimiters are not allowed in the name pattern. An asterisk (*) matches any number of characters and a question mark (?) matches a single character. If the path name is qualified or contains a pattern, it must be enclosed in apostrophes.
</p>
<p>If the Name Pattern parameter is not specified the default will be to match all patterns.
</p>
<p>
<b>Note: </b>This parameter is only valid if one or more path names were specified on the OBJPATH parameter.
</p>
<p><b>Element 1: Pattern</b>
</p>
<dl>
<dt><b><u>'*'</u></b></dt>
<dd>All objects that match the input OBJPATH parameter are to be included.
</dd>
<dt><b><i>name-pattern</i></b></dt>
<dd>Specify the pattern to be used to include or omit objects for which journal entries are retrieved. Only the last part of the path name will be considered for the name pattern match. Path name delimiters are not allowed in the name pattern.
</dd>
</dl>
<p>If the Name Pattern parameter is not specified the default will be to match all patterns.
</p>
<p>Additional information about path name patterns is in the Integrated file system information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
<p><b>Element 2: Include or omit</b>
</p>
<p>The second element specifies whether names that match the pattern should be included or omitted from the operation. Note that in determining whether a name matches a pattern, relative name patterns are always treated as relative to the current working directory.
</p>
<p>
<b>Note: </b>The SUBTREE parameter specifies whether directory subtrees are included or omitted.
</p>
<dl>
<dt><b><u>*INCLUDE</u></b></dt>
<dd>The objects that match the object name pattern are included in the operation, unless overridden by an *OMIT specification.
</dd>
<dt><b>*OMIT</b></dt>
<dd>The objects that match the object name pattern are not to be included in the operation. This overrides an *INCLUDE specification and is intended to be used to omit a subset of a previously selected pattern.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.FROMENTLRG"></a>
<h3>Starting large sequence number (FROMENTLRG)</h3>
<p>Specifies the first journal entry considered for retrieval.
</p>
<p>
<b>Note: </b>You can specify a value for either the <b>Starting sequence number (FROMENT)</b> parameter or the <b>Starting large sequence number (FROMENTLRG)</b> parameter, but not for both.
</p>
<dl>
<dt><b><u>*FIRST</u></b></dt>
<dd>The first journal entry in the specified journal receiver range is the first entry considered for retrieval. If SEARCH(*DESCEND) is specified, FROMENT(*FIRST) is valid only if TOENTLRG(*FIRST) or TOENT(*FIRST) is also specified.
</dd>
<dt><b>*LAST</b></dt>
<dd>The last journal entry in the specified journal receiver range is the first entry considered for retrieval. If SEARCH(*ASCEND) is specified, FROMENT(*LAST) is valid only if TOENTLRG(*LAST) or TOENT(*LAST) is also specified.
</dd>
<dt><b><i>starting-sequence-number</i></b></dt>
<dd>The journal entry with the assigned sequence number is the first entry considered for retrieval. The possible range is 1 to 18,446,744,073,709,551,600.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.FROMTIME"></a>
<h3>Starting date and time (FROMTIME)</h3>
<p>Specifies the date and time of the first journal entry considered for retrieval. The first journal entry found with the specified date and time or the next later journal entry is the starting point for the search.
</p>
<p><b>Element 1: Starting date</b>
</p>
<dl>
<dt><b><i>starting-date</i></b></dt>
<dd>Specify the date. The starting date and time of the first journal entry occurring at or after the specified date and time becomes the starting point for the search.
</dd>
</dl>
<p><b>Element 2: Starting time</b>
</p>
<dl>
<dt><b><i>starting-time</i></b></dt>
<dd>Specify the time. The starting date and time of the first journal entry occurring at or after the specified date and time becomes the starting point for the search.
<p>The time can be specified in 24-hour format with or without a time separator:
</p>
<ul>
<li>With a time separator, specify a string of 5 or 8 digits where the time separator specified for your job is used to separate the hours, minutes, and seconds. If you enter this command from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator specified for your job is used, this command will fail.
</li>
<li>Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where <b>hh</b> = hours, <b>mm</b> = minutes, and <b>ss</b> = seconds.
</li>
</ul>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.TOENTLRG"></a>
<h3>Ending large sequence number (TOENTLRG)</h3>
<p>Specifies the last journal entry considered for retrieval.
</p>
<p>
<b>Note: </b>You can specify a value for either the <b>Ending sequence number (TOENT)</b> parameter or the <b>Ending large sequence number (TOENTLRG)</b> parameter, but not for both.
</p>
<dl>
<dt><b><u>*LAST</u></b></dt>
<dd>The search continues until the last journal entry in the journal receiver range specified is processed. If SEARCH(*DESCEND) is specified, TOENT(*LAST) is valid only if FROMENTLRG(*LAST) or FROMENT(*LAST) is also specified.
</dd>
<dt><b>*FIRST</b></dt>
<dd>The search continues until the first journal entry in the journal receiver range specified is processed. If SEARCH(*ASCEND) is specified, TOENT(*FIRST) is only valid if FROMENTLRG(*LAST) or FROMENT(*FIRST) is also specified.
</dd>
<dt><b><i>ending-sequence-number</i></b></dt>
<dd>Specify the sequence number of the final journal entry considered for retrieval. The possible range is 1 to 18,446,744,073,709,551,600.
</dd>
</dl>
<p>
<b>Note: </b>The values specified for the FROMENT and TOENT parameter can be the same. For example, FROMENT(234) and TOENT(234) can be specified.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.TOTIME"></a>
<h3>Ending date and time (TOTIME)</h3>
<p>Specifies the date and time of the last entry considered for retrieval. The first journal entry found with the specified date and time, or the latest earlier journal entry is the ending point for the search.
</p>
<p><b>Element 1: Ending date</b>
</p>
<dl>
<dt><b><i>ending-date</i></b></dt>
<dd>Specify the ending date. The ending date and time of the journal entry occurring at or before the specified date and time becomes the ending point for the search.
</dd>
</dl>
<p><b>Element 2: Ending time</b>
</p>
<dl>
<dt><b><i>ending-time</i></b></dt>
<dd>Specify the time. The ending date and time of the journal entry occurring at or before the specified date and time becomes the ending point for the search.
<p>The time can be specified in 24-hour format with or without a time separator:
</p>
<ul>
<li>Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds.
</li>
<li>With a time separator, specify a string of 5 or 8 digits where the time separator specified for your job is used to separate the hours, minutes, and seconds. If you enter this command from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator specified for your job is used, this command will fail.
</li>
</ul>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.SEARCH"></a>
<h3>Search (SEARCH)</h3>
<p>Specifies the order in which the journal entries are searched to retrieve an entry.
</p>
<dl>
<dt><b><u>*ASCEND</u></b></dt>
<dd>The journal entries are searched in ascending order (from the oldest entry to the newest entry).
</dd>
<dt><b>*DESCEND</b></dt>
<dd>The journal entries are searched in descending order (from the newest entry to the oldest entry).
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.JRNCDE"></a>
<h3>Journal codes (JRNCDE)</h3>
<p>Specifies the journal codes of the journal entries being considered for retrieval.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search for the entry is not limited to a specified journal code.
</dd>
<dt><b>*CTL</b></dt>
<dd>The journal entries considered for retrieval are those used to control the journal functions. The journal codes are <b>J</b> and <b>F</b>.
</dd>
</dl>
<p><b>Element 1: Journal code value</b>
</p>
<dl>
<dt><b><i>journal-code</i></b></dt>
<dd>Specify the journal code to which journal entries are limited. Only journal entries with the specified journal code are retrieved.
<p>An explanation of the journal codes that can be specified is in the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
</dd>
</dl>
<p><b>Element 2: Journal code selection</b>
</p>
<dl>
<dt><b><u>*ALLSLT</u></b></dt>
<dd>The journal entries with the specified journal code are retrieved only if all other selection parameters are satisfied.
</dd>
<dt><b>*IGNFILSLT</b></dt>
<dd>Journal entries having the specified journal code are retrieved only if all selection parameters, except the FILE parameter, are satisfied.
<p>
<b>Note: </b>This value is not valid for journal codes D, F, and R. This value is not valid if the OBJ, OBJPATH, or OBJFID parameters are specified.
</p>
</dd>
<dt><b>*IGNOBJSLT</b></dt>
<dd>Journal entries having the specified journal code are retrieved only if all selection parameters are satisfied except OBJ, OBJPATH, OBJFID, SUBTREE, and PATTERN.
<p>
<b>Note: </b>This value is not valid for journal codes B, D, E, F, Q, and R. This value is not valid if the FILE parameter is specified.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.ENTTYP"></a>
<h3>Journal entry types (ENTTYP)</h3>
<p>Specifies whether to limit the journal entries retrieved to those of a specified journal entry type.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search for the entry is not limited to a particular entry type.
</dd>
<dt><b>*RCD</b></dt>
<dd>Only entries that have an entry type for record-level operations are retrieved. The following entry types are valid: BR, DL, DR, IL, PT, PX, UB, UP, and UR.
</dd>
</dl>
<p><b>Other values</b>
</p>
<dl>
<dt><b><i>entry-type</i></b></dt>
<dd>Specify the entry type that limits the search for the entry. Only journal entries that contain the specified entry type are considered for retrieval. Up to 300 valid entry types can be specified. More information on entry types is in the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.JOB"></a>
<h3>Job name (JOB)</h3>
<p>Specifies that the journal entries searched for retrieval are limited to the journal entries for the specified job.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search is not limited to entries for a specified job.
</dd>
<dt><b>*</b></dt>
<dd>The search is limited to entries for the current job.
</dd>
</dl>
<p><b>Other values</b>
</p>
<dl>
<dt><b><i>job-identifier</i></b></dt>
<dd>Specify the job name, the user name, and the job number of the job to use. You can also specify that the job name only, or that the job name and the user name be used.
<dl>
<dt><b><i>job-name</i></b></dt>
<dd>Specify the job name of the job.
</dd>
<dt><b><i>user-name</i></b></dt>
<dd>Specify the user name of the job.
</dd>
<dt><b><i>job-number</i></b></dt>
<dd>Specify the system-assigned job number.
</dd>
</dl>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.PGM"></a>
<h3>Program (PGM)</h3>
<p>Specifies that the journal entries considered for retrieval are limited to the journal entries created by the specified program.
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search is not limited to entries for a specified program.
</dd>
<dt><b><i>program-name</i></b></dt>
<dd>Specify the name of the program whose journal entries are considered for retrieval.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.USRPRF"></a>
<h3>User profile (USRPRF)</h3>
<p>Specifies that the journal entries considered for retrieval are limited to the journal entries for a specified user profile.
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The retrieval of journal entries is not limited to entries for a specified user profile.
</dd>
<dt><b><i>user-profile-name</i></b></dt>
<dd>Specify the name of the user profile whose journal entries are considered for retrieval.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.CCIDLRG"></a>
<h3>Commit cycle large identifier (CCIDLRG)</h3>
<p>Specifies that the journal entries considered for retrieval are limited to the journal entries containing the specified commit cycle identifier. A commit cycle consists of all journal entries sharing the same commit cycle identifier. A journal entry's commit cycle identifier can be displayed by using the Display Journal (DSPJRN) command and entering option five.
</p>
<p>
<b>Note: </b>You can input a value for either the <b>Commit cycle identifier</b> field (CMTCYCID) or the <b>Commit cycle large identifier</b> field (CCIDLRG) but not for both.
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search is not limited to entries for a specified commit cycle identifier.
</dd>
<dt><b><i>commit-cycle-identifier</i></b></dt>
<dd>Specify the commit cycle identifier of the journal entries to be retrieved. The possible range is 1 to 18,446,744,073,709,551,600.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.DEPENT"></a>
<h3>Dependent entries (DEPENT)</h3>
<p>Specifies whether to retrieve the journal entries recording actions
</p>
<ul>
<li>that occur as a result of a trigger program
</li>
<li>on records that are part of a referential constraint
</li>
<li>that will be ignored during an Apply Journaled Changes (APYJRNCHG) or Remove Journaled Changes (RMVJRNCHG) operation.
</li>
</ul>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The journal entries relating to trigger programs, referential constraints and the entries which will be ignored by an Apply or Remove Journaled Changes operations are retrieved.
</dd>
<dt><b>*NONE</b></dt>
<dd>The journal entries relating to trigger programs, referential constraints and the entries which will be ignored by an Apply or Remove Journaled Changes operations are not retrieved.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.ENTFMT"></a>
<h3>Entry format (ENTFMT)</h3>
<p>Specifies the format of the retrieved journal entry. For a description of what is represented by each of the fields in the journal entry, see the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
<p>Lists showing detailed information on the format of the retrieved journal entries are in the RTNJRNE parameter description.
</p>
<p>
<b>Note: </b>If ENTFMT(*TYPE1) or ENTFMT(*TYPE2) is not specified, the NULLINDLEN parameter must be specified.
</p>
<p>
<b>Note: </b>If the <b>Receiver size options</b> field (RCVSIZOPT) for the journal was specified as *MAXOPT3, the sequence number, commit cycle identifier, the count of entries applied or removed or relative record number fields can reach a maximum value of 18,446,744,073,709,551,600. The length of these fields for the ENTFMT(*TYPE1), ENTFMT(*TYPE2), ENTFMT(*TYPE3), and ENTFMT(*TYPE4) formats is defined to hold a 10 digit number. Only the *TYPE5 format has fields large enough to hold this maximum value. When returning these fields for a format other than *TYPE5, if a sequence number, commit cycle identifier, or count of entries applied or removed or relative record number larger than 10 digits is found, the field is set to -1 for that entry.
</p>
<dl>
<dt><b><u>*TYPE1</u></b></dt>
<dd>The retrieved journal entries are formatted to include the minimum information that can be specified.
</dd>
<dt><b>*TYPE2</b></dt>
<dd>The retrieved journal entries include the information returned when ENTFMT(*TYPE1) is specified, and the user profile field, which gives the name of the user who logged the retrieved journal entries, and the name of the system on which the entry was sent.
</dd>
<dt><b>*TYPE3</b></dt>
<dd>The retrieved journal entries include the information returned when ENTFMT(*TYPE2) is specified, and the null value indicators.
</dd>
<dt><b>*TYPE4</b></dt>
<dd>The retrieved journal entries include the information returned when ENTFMT(*TYPE3) is specified, the journal identifier, the physical file trigger indicator, and the referential constraint indicator.
</dd>
<dt><b>*TYPE5</b></dt>
<dd>The retrieved journal entries include the information returned when OUTFILFMT(*TYPE4) is specified, in addition to the program library name, the program library ASP device name, the program library ASP number, the system sequence number, the logical unit of work, the transaction identifier, the thread identifier, the remote address, the address family, the remote port, the arm number, the receiver name, the receiver library name, the receiver library ASP device name and the receiver library ASP number.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.FMTMINDTA"></a>
<h3>Format minimized data (FMTMINDTA)</h3>
<p>Specifies whether entry specific data which has been minimized on field boundaries will be returned in a readable format.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>The journal entries which have entry specific data that has been minimized on field boundaries will not be returned in a readable format. Therefore, the entry specific data may not be viewable.
</dd>
<dt><b>*YES</b></dt>
<dd>The journal entries which have entry specific data that has been minimized on field boundaries will be returned in a readable format. Therefore, the entry specific data is viewable and may be used for auditing purposes. The fields that were changed are accurately reflected. The fields that were not changed and were not recorded display default data and are indicated by a value of 'F9'X in the null value indicators field.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.NULLINDLEN"></a>
<h3>Null value indicators length (NULLINDLEN)</h3>
<p>Specify the length used for the null value indicators portion of the retrieved entry. This parameter is not valid if ENTFMT(*TYPE1) or ENTFMT(*TYPE2) is specified. Valid values range from 1 to 8000 bytes. If the retrieved journal entry has fewer null value indicators than the specified field length, the trailing bytes in the null value indicators field is set to 'F0'X.
</p>
<p>Null value indicators are present in journal entries for record level operations as follows:
</p>
<ol>
<li>The corresponding physical file has null capable fields.
</li>
<li>The record image has been minimized in the entry specific data.
</li>
</ol>
<p>If the record image has not been minimized in the entry specific data, then there is one null value indicator per field in the physical file. Each indicator is one character long and can be either:
</p>
<ul>
<li>'F0'X = Corresponding field is not null.
</li>
<li>'F1'X = Corresponding field is null.
</li>
</ul>
<p>If the record image has been minimized on file field boundaries in the entry specific data and FMTMINDTA(*YES) was specified on the RCVJRNE command, then there is one null value indicator per field in the physical file. Each indicator is one character long and can be either:
</p>
<ul>
<li>'F0'X = Corresponding field is not null.
</li>
<li>'F1'X = Corresponding field is null.
</li>
<li>'F9'X = Corresponding field was not changed and the default value for the field is returned.
</li>
</ul>
<p>If the record image has been minimized on file field boundaries in the entry specific data and FMTMINDTA(*NO) was specified on the RTVJRNE command, then an internal value is returned for the null value indicator.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.INCENT"></a>
<h3>Include entries (INCENT)</h3>
<p>Specifies whether only the confirmed, or both the confirmed and unconfirmed, journal entries are retrieved. This parameter only applies when converting journal entries for output from a remote journal.
</p>
<p>Confirmed entries are those journal entries which have been sent to this remote journal and the state of the Input/Output (I/O) to auxiliary storage for the same journal entries on the local journal is known.
</p>
<p>Unconfirmed entries are those journal entries which have been sent to this remote journal, but the state of the Input/Output (I/O) to auxiliary storage for the same journal entries on the local journal is not known, or the object name information for those journal entries is not yet known to the remote journal. Unconfirmed journal entries can only exist within the attached receiver of a remote journal. This only applies if synchronous delivery mode is being used for a particular remote journal.
</p>
<dl>
<dt><b><u>*CONFIRMED</u></b></dt>
<dd>Only those journal entries which have been confirmed are retrieved.
</dd>
<dt><b>*ALL</b></dt>
<dd>All confirmed and unconfirmed journal entries are retrieved.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.FROMENT"></a>
<h3>Starting sequence number (FROMENT)</h3>
<p>Specifies the first journal entry considered for retrieval.
</p>
<p>
<b>Note: </b>You can specify a value for either the <b>Starting sequence number (FROMENT)</b> parameter or the <b>Starting large sequence number (FROMENTLRG)</b> parameter, but not for both.
</p>
<dl>
<dt><b><u>*FIRST</u></b></dt>
<dd>The first journal entry in the specified journal receiver range is the first entry considered for retrieval. If SEARCH(*DESCEND) is specified, FROMENT(*FIRST) is valid only if TOENTLRG(*FIRST) or TOENT(*FIRST) is also specified.
</dd>
<dt><b>*LAST</b></dt>
<dd>The last journal entry in the specified journal receiver range is the first entry considered for retrieval. If SEARCH(*ASCEND) is specified, FROMENT(*LAST) is valid only if TOENTLRG(*LAST) or TOENT(*LAST) is also specified.
</dd>
<dt><b><i>starting-sequence-number</i></b></dt>
<dd>The journal entry with the assigned sequence number is the first entry considered for retrieval. The possible range is 1 to 9,999,999,999.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.TOENT"></a>
<h3>Ending sequence number (TOENT)</h3>
<p>Specifies the last journal entry considered for retrieval.
</p>
<p>
<b>Note: </b>You can specify a value for either the <b>Ending sequence number (TOENT)</b> parameter or the <b>Ending large sequence number (TOENTLRG)</b> parameter, but not for both.
</p>
<dl>
<dt><b><u>*LAST</u></b></dt>
<dd>The search continues until the last journal entry in the journal receiver range specified is processed. If SEARCH(*DESCEND) is specified, TOENT(*LAST) is valid only if FROMENTLRG(*LAST) or FROMENT(*LAST) is also specified.
</dd>
<dt><b>*FIRST</b></dt>
<dd>The search continues until the first journal entry in the journal receiver range specified is processed. If SEARCH(*ASCEND) is specified, TOENT(*FIRST) is only valid if FROMENTLRG(*LAST) or FROMENT(*FIRST) is also specified.
</dd>
<dt><b><i>ending-sequence-number</i></b></dt>
<dd>Specify the sequence number of the final journal entry considered for retrieval. The possible range is 1 to 9,999,999,999.
</dd>
</dl>
<p>
<b>Note: </b>The values specified for the FROMENT and TOENT parameter can be the same. For example, FROMENT(234) and TOENT(234) can be specified.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.CMTCYCID"></a>
<h3>Commit cycle identifier (CMTCYCID)</h3>
<p>Specifies that the journal entries considered for retrieval are limited to the journal entries containing the specified commit cycle identifier. A commit cycle consists of all journal entries sharing the same commit cycle identifier. A journal entry's commit cycle identifier can be displayed by using the Display Journal (DSPJRN) command and entering option five.
</p>
<p>
<b>Note: </b>You can input a value for either the <b>Commit cycle identifier</b> field (CMTCYCID) or the <b>Commit cycle large identifier</b> field (CCIDLRG) but not for both.
</p>
<dl>
<dt><b><u>*ALL</u></b></dt>
<dd>The search is not limited to entries for a specified commit cycle identifier.
</dd>
<dt><b><i>commit-cycle-identifier</i></b></dt>
<dd>Specify the commit cycle identifier of the journal entries to be retrieved. The possible range is 1 to 9,999,999,999.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNSEQLRG"></a>
<h3>CL var for RTNSEQLRG (20) (RTNSEQLRG)</h3>
<p>Specifies the name of the program CL character variable into which the journal entry sequence number of the retrieved journal entry is copied. If a CL variable name is not specified, the journal entry sequence number is not copied into the program. The specified variable must be a character variable that has a length of twenty positions. If the retrieved sequence number is shorter than the length of the field, the number is padded on the right with blanks.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNJRNCDE"></a>
<h3>CL var for RTNJRNCDE (1) (RTNJRNCDE)</h3>
<p>Specifies the name of the program CL character variable into which the journal code of the retrieved journal entry is copied. If a CL variable name is not specified, the journal code of the retrieved journal entry is not copied into the program. The specified variable must be a character variable with a minimum length of 1 character. If the length of the variable is longer than 1 character, it is padded on the right with blanks.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNENTTYP"></a>
<h3>CL var for RTNENTTYP (2) (RTNENTTYP)</h3>
<p>Specifies the name of the program CL character variable into which the entry type of the retrieved journal entry is copied. If a CL variable name is not specified, the entry type of the retrieved journal entry is not copied into the program. The specified variable must be a character variable with a minimum length of 2 characters. If the length of the variable is longer than 2 characters, it is padded on the right with blanks.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNRCV"></a>
<h3>CL var for RTNRCV (10) (RTNRCV)</h3>
<p>Specifies the name of the program CL character variable into which the journal receiver name from which the returned journal entry was retrieved is copied. If the CL variable name is not specified, the journal receiver name is not copied into the program. The specified variable must be a character variable with a minimum length of 10 characters. If the length of the variable is longer than 10 characters, it is padded on the right with blanks.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNRCVLIB"></a>
<h3>CL var for RTNRCVLIB (10) (RTNRCVLIB)</h3>
<p>Specifies the name of the CL character variable into which the name of the library containing the receiver of the retrieved journal entry is copied. If the CL variable name is not specified, the journal receiver library name is not copied into the program. The specified variable must be a character variable with a minimum length of 10 characters. If the length of the variable is longer than 10 characters, it is padded on the right with blanks.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNJRNE"></a>
<h3>CL var for RTNJRNE (1) (RTNJRNE)</h3>
<p>Specifies the name of the program CL character variable into which the retrieved journal entry is copied. If a CL variable name is not specified, the retrieved journal entry is not copied into the program. The specified variable must be a character variable. If the retrieved journal entry is longer than the variable's field length, the entry is truncated. If the entry is shorter, it is padded on the right with blanks.
</p>
<p>The following lists show detailed information on the format of the retrieved journal entries.
</p>
<p>The journal entry can be retrieved in one of the following possible formats:
</p>
<p>If ENTFMT(*TYPE1) is specified, then the format of the fields in the retrieved entry is as follows:
</p>
<table border="1">
<tr>
<td>
<p>
<pre>
Field Name Field Attributes
--------------------- ----------------------------
ENTRY LENGTH TYPE(*DEC) LEN(5 0)
SEQUENCE NUMBER (1) TYPE(*DEC) LEN(10 0)
JOURNAL CODE TYPE(*CHAR) LEN(1)
JOURNAL ENTRY TYPE TYPE(*CHAR) LEN(2)
DATE TYPE(*CHAR) LEN(6)
TIME TYPE(*DEC) LEN(6 0)
JOB NAME TYPE(*CHAR) LEN(10)
USER NAME TYPE(*CHAR) LEN(10)
JOB NUMBER TYPE(*DEC) LEN(6 0)
PROGRAM NAME TYPE(*CHAR) LEN(10)
OBJECT NAME TYPE(*CHAR) LEN(10)
OBJECT LIBRARY TYPE(*CHAR) LEN(10)
MEMBER NAME TYPE(*CHAR) LEN(10)
COUNT/RRN (2) TYPE(*DEC) LEN(10 0)
FLAG TYPE(*CHAR) LEN(1)
COMMIT CYCLE ID (3) TYPE(*DEC) LEN(10 0)
INCOMPLETE DATA TYPE(*CHAR) LEN(1)
MINIMIZED ENTRY DATA TYPE(*CHAR) LEN(1)
RESERVED TYPE(*CHAR) LEN(6)
ENTRY-SPECIFIC DATA TYPE(*CHAR) LEN(up to 32642)
Notes:
(1) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the sequence number is larger than 10
digits.
(2) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the count of entries applied or removed
or relative record number is larger than 10 digits.
(3) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the commit cycle identifier is larger
than 10 digits.
</pre>
</p>
</td>
</tr>
</table>
<p>If ENTFMT(*TYPE2) is specified, then the format of the fields in the retrieved entry is as follows:
</p>
<table border="1">
<tr>
<td>
<p>
<pre>
Field Name Field Attributes
--------------------- ----------------------------
ENTRY LENGTH TYPE(*DEC) LEN(5 0)
SEQUENCE NUMBER (1) TYPE(*DEC) LEN(10 0)
JOURNAL CODE TYPE(*CHAR) LEN(1)
JOURNAL ENTRY TYPE TYPE(*CHAR) LEN(2)
DATE TYPE(*CHAR) LEN(6)
TIME TYPE(*DEC) LEN(6 0)
JOB NAME TYPE(*CHAR) LEN(10)
USER NAME TYPE(*CHAR) LEN(10)
JOB NUMBER TYPE(*DEC) LEN(6 0)
PROGRAM NAME TYPE(*CHAR) LEN(10)
OBJECT NAME TYPE(*CHAR) LEN(10)
OBJECT LIBRARY TYPE(*CHAR) LEN(10)
MEMBER NAME TYPE(*CHAR) LEN(10)
COUNT/RRN (2) TYPE(*DEC) LEN(10 0)
FLAG TYPE(*CHAR) LEN(1)
COMMIT CYCLE ID (3) TYPE(*DEC) LEN(10 0)
USER PROFILE TYPE(*CHAR) LEN(10)
SYSTEM NAME TYPE(*CHAR) LEN(8)
INCOMPLETE DATA TYPE(*CHAR) LEN(1)
MINIMIZED ENTRY DATA TYPE(*CHAR) LEN(1)
RESERVED TYPE(*CHAR) LEN(18)
ENTRY-SPECIFIC DATA TYPE(*CHAR) LEN(up to 32612)
Notes:
(1) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the sequence number is larger than 10
digits.
(2) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the count of entries applied or removed
or relative record number is larger than 10 digits.
(3) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the commit cycle identifier is larger
than 10 digits.
</pre>
</p>
</td>
</tr>
</table>
<p>
<b>Note: </b>If ENTFMT(*TYPE3) is specified, the following information is not available in this format:
</p>
<ul>
<li>Incomplete Data indicating if the journal entry data is incomplete due to either LOB fields or Byte Stream File operations.
</li>
<li>Minimized Entry Specific Data indicating if the journal entry has minimized entry specific data because the journal had MINENTDTA specified for the object type of the journal entry.
</li>
</ul>
<p>See the Journal Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter for more information on the incomplete data indicator, the minimized entry specific data indicator, and these journal entries.
</p>
<p>If ENTFMT(*TYPE3) is specified and a value is specified on the NULLINDLEN parameter, the format of the retrieved journal entry is as follows:
</p>
<table border="1">
<tr>
<td>
<p>
<pre>
Field Name Field Attributes
--------------------- ----------------------------
ENTRY LENGTH TYPE(*DEC) LEN(5 0)
SEQUENCE NUMBER (3) TYPE(*DEC) LEN(10 0)
JOURNAL CODE TYPE(*CHAR) LEN(1)
JOURNAL ENTRY TYPE TYPE(*CHAR) LEN(2)
TIMESTAMP TYPE(*TIMESTAMP) LEN(26)
JOB NAME TYPE(*CHAR) LEN(10)
USER NAME TYPE(*CHAR) LEN(10)
JOB NUMBER TYPE(*DEC) LEN(6 0)
PROGRAM NAME TYPE(*CHAR) LEN(10)
OBJECT NAME TYPE(*CHAR) LEN(10)
OBJECT LIBRARY TYPE(*CHAR) LEN(10)
MEMBER NAME TYPE(*CHAR) LEN(10)
COUNT/RRN (4) TYPE(*DEC) LEN(10 0)
FLAG TYPE(*CHAR) LEN(1)
COMMIT CYCLE ID (5) TYPE(*DEC) LEN(10)
USER PROFILE TYPE(*CHAR) LEN(10)
SYSTEM NAME TYPE(*CHAR) LEN(8)
NULL VALUE INDICATORS TYPE(*CHAR) field-length (1)
ENTRY-SPECIFIC DATA TYPE(*CHAR) ((up to 32618)
minus (field length)) (2)
Notes:
(1) The length of this field is the length
specified on the NULLINDLEN parameter.
(2) The length of this portion of the entry
depends on the length specified on the RTNJRNE
parameter and the length specified on the
NULLINDLEN parameter.
(3) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the sequence number is larger than 10
digits.
(4) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the count of entries applied or removed
or relative record number is larger than 10 digits.
(5) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the commit cycle identifier is larger
than 10 digits.
</pre>
</p>
</td>
</tr>
</table>
<p>If ENTFMT(*TYPE4) is specified and a value is specified on the NULLINDLEN parameter, the format of the retrieved journal entry is as follows:
</p>
<table border="1">
<tr>
<td>
<p>
<pre>
Field Name Field Attributes
--------------------- ----------------------------
ENTRY LENGTH TYPE(*DEC) LEN(5 0)
SEQUENCE NUMBER (3) TYPE(*DEC) LEN(10 0)
JOURNAL CODE TYPE(*CHAR) LEN(1)
JOURNAL ENTRY TYPE TYPE(*CHAR) LEN(2)
TIMESTAMP TYPE(*TIMESTAMP) LEN(26)
JOB NAME TYPE(*CHAR) LEN(10)
USER NAME TYPE(*CHAR) LEN(10)
JOB NUMBER TYPE(*DEC) LEN(6 0)
PROGRAM NAME TYPE(*CHAR) LEN(10)
OBJECT NAME TYPE(*CHAR) LEN(10)
OBJECT LIBRARY TYPE(*CHAR) LEN(10)
MEMBER NAME TYPE(*CHAR) LEN(10)
COUNT/RRN (4) TYPE(*DEC) LEN(10 0)
FLAG TYPE(*CHAR) LEN(1)
COMMIT CYCLE ID (5) TYPE(*DEC) LEN(10)
USER PROFILE TYPE(*CHAR) LEN(10)
SYSTEM NAME TYPE(*CHAR) LEN(8)
JOURNAL IDENTIFIER TYPE(*CHAR) LEN(10)
REF CONSTRAINT TYPE(*CHAR) LEN(1)
TRIGGER TYPE(*CHAR) LEN(1)
INCOMPLETE DATA TYPE(*CHAR) LEN(1)
IGNORE DURING TYPE(*CHAR) LEN(1)
APYJRNCHG OR RMVJRNCHG
MINIMIZED ENTRY DATA TYPE(*CHAR) LEN(1)
RESERVED TYPE(*CHAR) LEN(5)
NULL VALUE INDICATORS TYPE(*CHAR) field-length (1)
ENTRY-SPECIFIC DATA TYPE(*CHAR) ((up to 32598)
minus (field length)) (2)
Notes:
(1) The length of this field is the length
specified on the NULLINDLEN parameter.
(2) The length of this portion of the entry
depends on the length specified on the RTNJRNE
parameter and the length specified on the
NULLINDLEN parameter.
(3) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the sequence number is larger than 10
digits.
(4) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the count of entries applied or removed
or relative record number is larger than 10 digits.
(5) When the RCVSIZOPT of the journal is *MAXOPT3, this field
will be set to -1 if the commit cycle identifier is larger
than 10 digits.
</pre>
</p>
</td>
</tr>
</table>
<p>If ENTFMT(*TYPE5) is specified and a value is specified on the NULLINDLEN parameter, the format of the retrieved journal entry is as follows:
</p>
<table border="1">
<tr>
<td>
<p>
<pre>
Field Name Field Attributes
--------------------- ----------------------------
ENTRY LENGTH TYPE(*DEC) LEN(5 0)
SEQUENCE NUMBER TYPE(*CHAR) LEN(20)
JOURNAL CODE TYPE(*CHAR) LEN(1)
JOURNAL ENTRY TYPE TYPE(*CHAR) LEN(2)
TIMESTAMP TYPE(*TIMESTAMP) LEN(26)
JOB NAME TYPE(*CHAR) LEN(10)
USER NAME TYPE(*CHAR) LEN(10)
JOB NUMBER TYPE(*DEC) LEN(6 0)
PROGRAM NAME TYPE(*CHAR) LEN(10)
PROGRAM LIBRARY NAME TYPE(*CHAR) LEN(10)
PROGRAM ASP DEVICE TYPE(*CHAR) LEN(10)
NAME
PROGRAM ASP NUMBER TYPE(*DEC) LEN(5 0)
OBJECT NAME TYPE(*CHAR) LEN(10)
OBJECT LIBRARY TYPE(*CHAR) LEN(10)
MEMBER NAME TYPE(*CHAR) LEN(10)
COUNT/RRN TYPE(*CHAR) LEN(20)
FLAG TYPE(*CHAR) LEN(1)
COMMIT CYCLE ID TYPE(*CHAR) LEN(20)
USER PROFILE TYPE(*CHAR) LEN(10)
SYSTEM NAME TYPE(*CHAR) LEN(8)
JOURNAL IDENTIFIER TYPE(*CHAR) LEN(10)
REF CONSTRAINT TYPE(*CHAR) LEN(1)
TRIGGER TYPE(*CHAR) LEN(1)
INCOMPLETE DATA TYPE(*CHAR) LEN(1)
IGNORE DURING TYPE(*CHAR) LEN(1)
APYJRNCHG OR RMVJRNCHG
MINIMIZED ENTRY DATA TYPE(*CHAR) LEN(1)
OBJECT INDICATOR TYPE(*CHAR) LEN(1)
SYSTEM SEQUENCE TYPE(*CHAR) LEN(20)
NUMBER
RECEIVER NAME TYPE(*CHAR) LEN(10)
RECEIVER LIBRARY NAME TYPE(*CHAR) LEN(10)
RECEIVER ASP DEVICE TYPE(*CHAR) LEN(10)
NAME
RECEIVER ASP NUMBER TYPE(*DEC) LEN(5 0)
ARM NUMBER TYPE(*DEC) LEN(5 0)
THREAD IDENTIFIER TYPE(*CHAR) LEN(8)
THREAD IDENTIFIER HEX TYPE(*CHAR) LEN(16)
ADDRESS FAMILY TYPE(*CHAR) LEN(1)
REMOTE PORT TYPE(*DEC) LEN(5 0)
REMOTE ADDRESS TYPE(*CHAR) LEN(46)
LOGICAL UNIT OF WORK TYPE(*CHAR) LEN(39)
TRANSACTION IDENTIFIER TYPE(*CHAR) LEN(140)
OBJECT TYPE TYPE(*CHAR) LEN(7)
FILE TYPE INDICATOR TYPE(*CHAR) LEN(1)
NESTED COMMIT LEVEL TYPE(*DEC) LEN(7 0)
RESERVED TYPE(*CHAR) LEN(5)
NULL VALUE INDICATORS TYPE(*CHAR) field-length (1)
ENTRY-SPECIFIC DATA TYPE(*CHAR) ((up to 32212)
minus (field length)) (2)
Notes:
(1) The length of this field is the length
specified on the NULLINDLEN parameter.
(2) The length of this portion of the entry
depends on the length specified on the RTNJRNE
parameter and the length specified on the
NULLINDLEN parameter.
</pre>
</p>
</td>
</tr>
</table>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="RTVJRNE.RTNSEQNBR"></a>
<h3>CL var for RTNSEQNBR (10 0) (RTNSEQNBR)</h3>
<p>Specifies the name of the program CL decimal variable into which the journal entry sequence number of the retrieved journal entry is copied. If a CL variable name is not specified, the journal entry sequence number is not copied into the program. The specified variable must be a decimal variable that has a length of ten positions with no decimal positions. If the sequence number is larger than 9,999,999,999, this value is set to -1, left-aligned and padded on the right with blanks. Use the <b>CL var for RTNSEQLRG (20) (RTNSEQLRG)</b> parameter to retrieve a value larger than 9,999,999,999.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="RTVJRNE.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1</b>
</p>
<p>Assume the following variables are specified:
</p>
<p>
<pre>
DCL &amp;SEQ TYPE(*DEC) LEN(10 0)
DCL &amp;JRNENT TYPE(*CHAR) LEN(200)
DCL &amp;RCVNAME TYPE(*CHAR) LEN(10)
DCL &amp;RCVLIB TYPE(*CHAR) LEN(10)
</pre>
</p>
<p>and this command is run:
</p>
<p>
<pre>
RTVJRNE JRN(MYLIB/JRNA) ENTTYP(PR) +
RTNSEQNBR(&amp;SEQ) RTNJRNE(&amp;JRNENT)
</pre>
</p>
<p>Since no starting journal entry is specified in this command, the first entry from the journal receiver that is currently attached to the journal JRNA in the library MYLIB, when starting to retrieve entries, is considered for retrieval. The first entry in any receiver is always an identifier for the previously-attached receiver. This first receiver entry is known as a type PR entry, and it contains the name of the previously attached receiver in its entry-specific data. The PR entry is the first entry in ascending order in the currently attached receiver; when it is found, the entry is placed into a CL variable named &amp;JRNENT.
</p>
<p>Change Variable (CHGVAR) can then be used to separate the name and library of the previous journal receiver, found in the entry specific data, as follows:
</p>
<p>
<pre>
CHGVAR &amp;RCVNAME (%SST(&amp;JRNENT 126 10))
CHGVAR &amp;RCVLIB (%SST(&amp;JRNENT 136 10))
</pre>
</p>
<p><b>Example 2</b>
</p>
<p>Assume the following variables are specified:
</p>
<p>
<pre>
DCL &amp;ENTNO TYPE(*DEC) LEN(10 0)
DCL &amp;JCODE TYPE(*CHAR) LEN(1)
DCL &amp;ETYPE TYPE(*CHAR) LEN(2)
DCL &amp;RCVNAME TYPE(*CHAR) LEN(10)
DCL &amp;RCVLIB TYPE(*CHAR) LEN(10)
DCL &amp;JENTRY TYPE(*CHAR) LEN(205)
</pre>
</p>
<p>and this command is run:
</p>
<p>
<pre>
RTVJRNE JRN(MYLIB/JRNLA) OBJ(LIB1/A *FILE MBR3) +
RCVRNG(RCVLIB/RCV30 RCVLIB/RCV27) ORDER(*DESCEND) +
JRNCDE(R) ENTTYP(UP DL) JOB(000666/QPGMR/PRESTRT) +
PGM(WAKEUP) USRPRF(MAC7) ENTFMT(*TYPE2) +
RTNSEQNBR(&amp;ENTNO) RTNJRNCDE(&amp;JCODE) +
RTNENTTYP(&amp;ETYPE) RTNRCV(&amp;RCVNAME) +
RTNRCVLIB(&amp;RCVLIB) RTNJRNE(&amp;JENTRY)
</pre>
</p>
<p>This command gets a journal entry, searching in descending order the journal receiver chain from receiver RCV30 in library RCVLIB to receiver RCV27 in library RCVLIB, journaled through journal JRNLA in library MYLIB, and copies the entry into the specified CL variables. The retrieved entry is an UPDATE or DELETE entry with journal code R from member MBR3 in file A in library LIB1, created in job 000666/QPGMR/PRESTRT in program WAKEUP by user profile MAC7. The retrieved journal entry includes the user profile field. The sequence number of the retrieved entry is copied into CL variable &amp;ENTNO. The journal code of the retrieved entry is copied into CL variable &amp;JCODE. The entry type of the retrieved entry is copied into CL variable &amp;ETYPE. The name of the journal receiver from which the returned entry was retrieved is copied into &amp;RCVNAME. The library name of the journal receiver from which the returned entry was retrieved is copied into &amp;RCVLIB.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="RTVJRNE.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF7002</b></dt>
<dd>File &amp;1 in library &amp;2 not a physical file.
</dd>
<dt><b>CPF7006</b></dt>
<dd>Member &amp;3 not found in file &amp;1 in &amp;2.
</dd>
<dt><b>CPF7007</b></dt>
<dd>Cannot allocate member &amp;3 file &amp;1 in &amp;2.
</dd>
<dt><b>CPF701B</b></dt>
<dd>Journal recovery of an interrupted operation failed.
</dd>
<dt><b>CPF705C</b></dt>
<dd>INCENT(*ALL) not allowed for a local journal.
</dd>
<dt><b>CPF7053</b></dt>
<dd>Values for RCVRNG parameter not correct; reason code &amp;1.
</dd>
<dt><b>CPF7054</b></dt>
<dd>FROM and TO values not valid.
</dd>
<dt><b>CPF7055</b></dt>
<dd>Maximum number of objects exceeded.
</dd>
<dt><b>CPF7057</b></dt>
<dd>*LIBL not allowed with FILE(*ALL) or OBJ(*ALL).
</dd>
<dt><b>CPF7060</b></dt>
<dd>Object not found and not journaled in specified receiver range.
</dd>
<dt><b>CPF7061</b></dt>
<dd>Conversion of journal entries failed.
</dd>
<dt><b>CPF7062</b></dt>
<dd>No entries converted or received from journal &amp;1.
</dd>
<dt><b>CPF7065</b></dt>
<dd>Entry type (ENTTYP) not valid for journal code (JRNCDE).
</dd>
<dt><b>CPF7072</b></dt>
<dd>Retrieval of journal entry failed.
</dd>
<dt><b>CPF7073</b></dt>
<dd>No entry retrieved from journal &amp;1 in &amp;2.
</dd>
<dt><b>CPF7074</b></dt>
<dd>RCVRNG for specified SEARCH not valid.
</dd>
<dt><b>CPF708D</b></dt>
<dd>Journal receiver found logically damaged.
</dd>
<dt><b>CPF709C</b></dt>
<dd>JOB, PGM, and USRPRF not valid for receiver range.
</dd>
<dt><b>CPF70A9</b></dt>
<dd>OBJPATH parameter not valid for a remote journal.
</dd>
<dt><b>CPF70AC</b></dt>
<dd>File identifier &amp;1 not found.
</dd>
<dt><b>CPF9801</b></dt>
<dd>Object &amp;2 in library &amp;3 not found.
</dd>
<dt><b>CPF9802</b></dt>
<dd>Not authorized to object &amp;2 in &amp;3.
</dd>
<dt><b>CPF9803</b></dt>
<dd>Cannot allocate object &amp;2 in library &amp;3.
</dd>
<dt><b>CPF9809</b></dt>
<dd>Library &amp;1 cannot be accessed.
</dd>
<dt><b>CPF9810</b></dt>
<dd>Library &amp;1 not found.
</dd>
<dt><b>CPF9820</b></dt>
<dd>Not authorized to use library &amp;1.
</dd>
<dt><b>CPF9822</b></dt>
<dd>Not authorized to file &amp;1 in library &amp;2.
</dd>
<dt><b>CPF9825</b></dt>
<dd>Not authorized to device &amp;1.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#RTVJRNE.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink