friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0332907f0f
ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/QJORJRNI.htm

3032 lines
97 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">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Retrieve Journal Information (QjoRetrieveJournalInformation) API</title>
<!-- Begin Header Records -->
<!-- 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. -->
<!-- JC1 SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
<!-- at RCHVMW2 on 17 Feb 1999 at 11:05:09 -->
<!-- Change history -->
<!-- 010402 V5R2 47URKM Added standby and cache info -->
<!-- 010402 V5R2 Ray Added various new journal attributes info -->
<!-- 011024 V5R2 47UDFZ Clarified key offsets -->
<!-- 030531 v5r3 mel clarified inactive and standby -->
<!-- 031028 v5r3 trs clarified standby further -->
<!-- 040217 v5r4 akf clarified *INACTPEND state further-->
<!-- 040520 v5r4 trs add D99768 JRNOBJLMT and new format RJRN0200 -->
<!-- 040927 v5r4 trs add D99814 journal recovery count to RJRN0200 -->
<!-- 050517 v5r4 mel minor clarifications -->
<!-- 050912 v5r4 trs clarify paragraph on estimation value -->
<!--File Edited by Kersten Oct 2001 -->
<!--End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="Top_Of_Page"></a>
<!-- Java sync-link -->
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<h2>Retrieve Journal Information (QjoRetrieveJournalInformation) API</h2>
<div class="box" style="width: 70%;">
<br>
&nbsp;&nbsp;Required Parameter Group:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">1</td>
<td align="left" valign="top" width="50%">Receiver variable</td>
<td align="left" valign="top" width="20%">Output</td>
<td align="left" valign="top" width="20%">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Length of receiver variable</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">Qualified journal name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(20)</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="left" valign="top">Format name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(8)</td>
</tr>
<tr>
<td align="center" valign="top">5</td>
<td align="left" valign="top">Journal information to retrieve</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(*)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Omissible Parameter:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">6</td>
<td align="left" valign="top" width="50%">Error Code</td>
<td align="left" valign="top" width="20%">I/O</td>
<td align="left" valign="top" width="20%">Char(*)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Service Program Name: QJOURNAL<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Header File: QSYSINC/H.QJOURNAL <br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Yes<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The Retrieve Journal Information (QjoRetrieveJournalInformation) API
provides access to journal-related information to help manage a journal
environment, including a remote journal environment.</p>
<p>Various types of journal information are provided by the API. General
information, similar to information reported by using the Work with Journal
Attributes (WRKJRNA) CL command, and additional information are contained in
the header section. If requested, information is provided for the journal
receiver directory, journaled objects, and remote journals.</p>
<br>
<h3>Authorities and Locks</h3>
<dl>
<dt><em>Journal Authority</em></dt>
<dd>*OBJOPR and some data authority other than *EXECUTE</dd>
<dt><em>Journal Library Authority</em></dt>
<dd>*EXECUTE</dd>
<dt><em>Journal Lock</em></dt>
<dd>*SHRRD</dd>
</dl>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Receiver variable</strong></dt>
<dd>OUTPUT; CHAR(*)
<p>The receiver variable that is to receive the information requested. You can
specify the size of the area smaller than the format requested as long as you
specify the length of receiver variable parameter correctly. As a result, the
API returns only the data the area can hold.</p>
</dd>
<dt><strong>Length of receiver variable</strong></dt>
<dd>INPUT; BINARY(4)
<p>The length of the receiver variable provided. The length of receiver
variable parameter may be specified up to the size of the receiver variable
specified in the user program. If the length of receiver variable parameter
specified is larger than the allocated size of the receiver variable specified
in the user program, the results are not predictable. The minimum length is 8
bytes
<img src="v5r4adelta.gif" alt="Start of change">
if format RJRN0100 is specified.
The minimum length is 1 byte if format RJRN0200 is specified.
<p><strong>Note:</strong>The format name determines what units are used for
the fields <strong>Length of receiver variable</strong>,
<strong>Bytes returned</strong>, and
<strong>Bytes available</strong>.
If format RJRN0100 is specified, the information is in one byte units.
If format RJRN0200 is specified, the information is in 4K (4096 bytes) units.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
</dd>
<dt><strong>Qualified journal name</strong></dt>
<dd>INPUT; CHAR(20)
<p>The name of the journal and its library from which the journal attributes
and information are to be retrieved. The first 10 characters contain the
journal name, and the second 10 characters contain the library name. The
special values supported for the library name follow:</p>
<table width="100%" cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*LIBL</em></td>
<td align="left" valign="top">Library list</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURLIB</em></td>
<td align="left" valign="top">Current library</td>
</tr>
</table>
<br>
</dd>
<dt>
<strong>Format name</strong></dt>
<dd>INPUT; CHAR(8)
<p>Format RJRN0100
<img src="v5r4adelta.gif" alt="Start of change">
and RJRN0200 are the only supported
formats that are used by this API.
For more information, see
<a href="#HDRRJNIFMT">RJRN0100/RJRN0200 format</a>.</p>
<img src="v5r4adeltaend.gif" alt="End of change">
</dd>
<dt><strong>Journal information to retrieve</strong></dt>
<dd>INPUT; CHAR(*)
<p>Information to be retrieved that is associated with the journal. The
information must be in the following format:</p>
<dl>
<dt><em>Number of variable length records</em></dt>
<dd>BINARY(4)</dd>
<dd>The total number of all of the variable length records. If this field is
zero, no variable length records are processed, and no key information will be
retrieved.</dd>
<dt><em>Variable length records</em></dt>
<dd>CHAR(*)</dd>
<dd>The types of information that should be retrieved. For the specific format
of the variable length record, see <a href="#HDRRJRNIVL">Format for Variable
Length Record</a>.</dd>
</dl>
</dd>
</dl>
<br>
<h3>Omissible Parameter</h3>
<dl>
<dt><strong>Error code</strong></dt>
<dd>I/O; CHAR(*)
<p>The structure in which to return error information. For the format of the
structure, see <a href="../apiref/error.htm#hdrerrcod">Error Code Parameter</a>. If this
parameter is omitted, diagnostic and escape messages are issued to the
application.</p>
</dd>
</dl>
<br>
<h3><a name="HDRRJRNIVL">Format for Variable Length Record</a></h3>
<p>The following table defines the format for the variable length records.</p>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Length of variable length record</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Key</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of data</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Data</td>
</tr>
</table>
<p>If the length of the data is longer than the key field's data length, the
data will be truncated at the right.</p>
<p>If the length of the data is shorter than the key field's data length and
the key contains binary data, an error message is issued. If the key does not
contain binary data, the field is padded with blanks.</p>
<p>It is not an error to specify a key more than once. If duplicate keys are
specified, the last specified value for that key is used.</p>
<p>Each variable length record must be 4-byte aligned. If not, unpredictable
results may occur.</p>
<br>
<h3><a name="HDRRJRNI1">Field Descriptions</a></h3>
<p><strong>Data.</strong> The data that is used to determine how the journal
information should be retrieved. All values are validity checked.</p>
<p><strong>Key.</strong> Identifies specific information to be retrieved about
the journal. See <a href="#HDRRJRNIKY">Keys</a> for the list of valid keys.</p>
<p><strong>Length of data.</strong> The length of the key information.</p>
<p><strong>Length of variable length record.</strong> The length of the
variable length record. This field is used to get the addressability of the
next variable length record.</p>
<br>
<h3><a name="HDRRJRNIKY">Keys</a></h3>
<p>The following table lists the valid keys for the key field area of the
variable length record.</p>
<table border width="80%">
<!-- cols="10 15 75" -->
<tr>
<th align="center" valign="bottom">Key</th>
<th align="left" valign="bottom">Input Type</th>
<th align="left" valign="bottom">Field</th>
</tr>
<tr>
<td align="center" valign="top">1</td>
<td align="left" valign="top">N/A</td>
<td align="left" valign="top">Journal receiver directory information</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Journaled object information</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">CHAR(38)</td>
<td align="left" valign="top">Remote journal information</td>
</tr>
</table>
<p><img src="v5r4adelta.gif" alt="Start of change"><strong>Note:</strong>If you are only interested in summary information
about journaled objects, this information is available
with format RJRN0100 or format RJRN0200.
Key 2 provides detailed information about journaled objects.
<p><strong>Note:</strong>The number of objects journaled to the
journal can be significant. The time to return the journaled object
information (key 2) can also be significant. The space needed to return
this information can be more than 2 gigabytes (2,147,483,647).</p>
<p>To get an approximation of the space needed to return
the journaled object information (key 2), specify a
value of -1 in the input variable
<strong>Length of receiver variable</strong>. By doing this, the API
will return in the <strong>Bytes available</strong> field the calculated
size of space that is needed to return the journaled object information
without attempting on this request to get any journaled object
information. Since only the calculations will be done, the API will be able
to return the requested information quickly. The value of
<strong>Bytes available</strong> returned will be in 4K units
if format RJRN0200 was specified.
</p>
<p><strong>Note:</strong> At least 8 bytes must be available in the
<strong>Receiver variable</strong> return area to return the
<strong>Bytes available</strong> information. Only these 8 bytes of information
will be returned when the <strong>Length of receiver variable</strong> is set to -1.
<img src="v5r4adeltaend.gif" alt="End of change"></p>
<br>
<h3><a name="HDRRJRNI2">Field Descriptions</a></h3>
<p><strong>Journaled object information.</strong> The list of objects that are
journaled to the specified journal of specific object types. The input key
value indicates what journaled object information to retrieve. The object types
that are supported for retrieval are *FILE, *DTAARA, *DTAQ, *DIR, *STMF, and
*SYMLNK. The possible values follow:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td valign="top"><em>*ALL</em></td>
<td valign="top">All objects that are journaled to the journal, of the object
types supported for retrieval with this key, are returned.</td>
</tr>
<tr>
<td valign="top"><em>*ALLIFS</em></td>
<td valign="top">Only the following object types that are journaled to the
journal are returned: *DIR, *STMF, and *SYMLNK.</td>
</tr>
<tr>
<td valign="top"><em>Object type</em></td>
<td valign="top">Only the objects of the specified object type that are
journaled to the journal are returned.
<p><strong>Note:</strong> The following object types cannot be specified
individually in this field: *DIR, *STMF, and *SYMLNK. To retrieve these object
types, specify *ALLIFS.</p>
</td>
</tr>
</table>
<p>For output values, see <a href="#HDRRJRNIK2">Key 2 Output Section</a>.</p>
<p><strong>Journal receiver directory information.</strong> The journal
receiver directory information that is returned for the journal. Journal
receiver directory information can be retrieved for local and remote journals.
There are no input values for this key. For output values, see <a href=
"#HDRRJRNIK1">Key 1 Output Section</a>.</p>
<p><strong>Remote journal information.</strong> The remote journal information
that is returned. Remote journal information can be retrieved for local and
remote journals. The input key value indicates what remote journal information
to retrieve. The possible values follow:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td valign="top"><em>Char(18)</em></td>
<td valign="top">The relational database directory entry information as
follows:
<dl>
<dt><em>*ALL</em></dt>
<dd>All remote journal information is returned.</dd>
<dt><em>Relational database directory entry</em></dt>
<dd>Only the remote journal information for the specified relational database
directory entry is to be returned.</dd>
</dl>
</td>
</tr>
<tr>
<td valign="top"><em>Char(20)</em></td>
<td valign="top">The remote journal name information as follows:
<dl>
<dt><em>*ALL</em></dt>
<dd>All remote journals that are associated with the specified relational
database directory entry are returned.</dd>
</dl>
</td>
</tr>
<tr>
<td valign="top"><em>Qualified remote journal name</em></td>
<td valign="top">Only the remote journal information for the specified journal
that is associated with the specified relational database directory entry is to
be returned. The first 10 characters contain the remote journal name, and the
second 10 characters contain the library name.</td>
</tr>
</table>
<p>For output values, see <a href="#HDRRJRNIK3">Key 3 Output Section</a>.<br>
</p>
<h3><img src="v5r4adelta.gif" alt="Start of change"><a name="HDRRJNIFMT">RJRN0100/RJRN0200 format</a></h3>
<p>The structure of the information returned is determined by the specified
format name. For detailed descriptions of the fields, see <a href=
"#HDRRJRNIFL">Field Descriptions</a>.
<p><strong>Note:</strong>The format name determines what units are used
for the fields <strong>Bytes returned</strong> and
<strong>Bytes available</strong>.
If format RJRN0100 is specified, the information is in one byte units.
If format RJRN0200 is specified, the information is in 4K (4096 bytes) units.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
<table width="80%" border>
<tr>
<th align="center" colspan="2">Offset</th>
<th align="left" rowspan="2">Type</th>
<th align="left" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Bytes returned</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Bytes available</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to key information</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Journal name</td>
</tr>
<tr>
<td align="center" valign="top">22</td>
<td align="center" valign="top">16</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Journal library name</td>
</tr>
<tr>
<td align="center" valign="top">32</td>
<td align="center" valign="top">20</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Auxiliary storage pool (ASP)</td>
</tr>
<tr>
<td align="center" valign="top">36</td>
<td align="center" valign="top">24</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Message queue name</td>
</tr>
<tr>
<td align="center" valign="top">46</td>
<td align="center" valign="top">2E</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Message queue library name</td>
</tr>
<tr>
<td align="center" valign="top">56</td>
<td align="center" valign="top">38</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Manage receiver option</td>
</tr>
<tr>
<td align="center" valign="top">57</td>
<td align="center" valign="top">39</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Delete receiver option</td>
</tr>
<tr>
<td align="center" valign="top">58</td>
<td align="center" valign="top">3A</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Receiver size option *RMVINTENT</td>
</tr>
<tr>
<td align="center" valign="top">59</td>
<td align="center" valign="top">3B</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Receiver size option *MINFIXLEN</td>
</tr>
<tr>
<td align="center" valign="top">60</td>
<td align="center" valign="top">3C</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Receiver size option *MAXOPT1</td>
</tr>
<tr>
<td align="center" valign="top">61</td>
<td align="center" valign="top">3D</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Receiver size option *MAXOPT2</td>
</tr>
<tr>
<td align="center" valign="top">62</td>
<td align="center" valign="top">3E</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Receiver size option *MAXOPT3</td>
</tr>
<tr>
<td align="center" valign="top">63</td>
<td align="center" valign="top">3F</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved
</td>
</tr>
<tr>
<td align="center" valign="top">65</td>
<td align="center" valign="top">41</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journal type</td>
</tr>
<tr>
<td align="center" valign="top">66</td>
<td align="center" valign="top">42</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Remote journal type</td>
</tr>
<tr>
<td align="center" valign="top">67</td>
<td align="center" valign="top">43</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journal state</td>
</tr>
<tr>
<td align="center" valign="top">68</td>
<td align="center" valign="top">44</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journal delivery mode</td>
</tr>
<tr>
<td align="center" valign="top">69</td>
<td align="center" valign="top">45</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Local journal name</td>
</tr>
<tr>
<td align="center" valign="top">79</td>
<td align="center" valign="top">4F</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Local journal library name</td>
</tr>
<tr>
<td align="center" valign="top">89</td>
<td align="center" valign="top">59</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Local journal system</td>
</tr>
<tr>
<td align="center" valign="top">97</td>
<td align="center" valign="top">61</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Source journal name</td>
</tr>
<tr>
<td align="center" valign="top">107</td>
<td align="center" valign="top">6B</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Source journal library name</td>
</tr>
<tr>
<td align="center" valign="top">117</td>
<td align="center" valign="top">75</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Source journal system</td>
</tr>
<tr>
<td align="center" valign="top">125</td>
<td align="center" valign="top">7D</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Redirected receiver library name</td>
</tr>
<tr>
<td align="center" valign="top">135</td>
<td align="center" valign="top">87</td>
<td align="left" valign="top">CHAR(50)</td>
<td align="left" valign="top">Journal text</td>
</tr>
<tr>
<td align="center" valign="top">185</td>
<td align="center" valign="top">B9</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Minimize entry specific data for data areas</td>
</tr>
<tr>
<td align="center" valign="top">186</td>
<td align="center" valign="top">BA</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Minimize entry specific data for files</td>
</tr>
<tr>
<td align="center" valign="top">187</td>
<td align="center" valign="top">BB</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">195</td>
<td align="center" valign="top">C3</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journal Cache</td>
</tr>
<tr>
<td align="center" valign="top">196</td>
<td align="center" valign="top">C4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of attached journal receivers</td>
</tr>
<tr>
<td align="center" valign="top">200</td>
<td align="center" valign="top">C8</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Attached journal receiver name</td>
</tr>
<tr>
<td align="center" valign="top">210</td>
<td align="center" valign="top">D2</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Attached journal receiver library name</td>
</tr>
<tr>
<td align="center" valign="top">220</td>
<td align="center" valign="top">DC</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Local journal system associated with the attached
journal receiver</td>
</tr>
<tr>
<td align="center" valign="top">228</td>
<td align="center" valign="top">E4</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Source journal system associated with the
attached journal receiver</td>
</tr>
<tr>
<td align="center" valign="top">236</td>
<td align="center" valign="top">EC</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Attached dual journal receiver name</td>
</tr>
<tr>
<td align="center" valign="top">246</td>
<td align="center" valign="top">F6</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Attached dual journal receiver library name</td>
</tr>
<tr>
<td align="center" valign="top">256</td>
<td align="center" valign="top">100</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Manage receiver delay</td>
</tr>
<tr>
<td align="center" valign="top">260</td>
<td align="center" valign="top">104</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Delete receiver delay</td>
</tr>
<tr>
<td align="center" valign="top">264</td>
<td align="center" valign="top">108</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">ASP device name</td>
</tr>
<tr>
<td align="center" valign="top">274</td>
<td align="center" valign="top">112</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Local journal ASP group name</td>
</tr>
<tr>
<td align="center" valign="top">284</td>
<td align="center" valign="top">11C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Source journal ASP group name</td>
</tr>
<tr>
<td align="center" valign="top">294</td>
<td align="center" valign="top">126</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data JOB</td>
</tr>
<tr>
<td align="center" valign="top">295</td>
<td align="center" valign="top">127</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data USR</td>
</tr>
<tr>
<td align="center" valign="top">296</td>
<td align="center" valign="top">128</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data PGM</td>
</tr>
<tr>
<td align="center" valign="top">297</td>
<td align="center" valign="top">129</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data PGMLIB</td>
</tr>
<tr>
<td align="center" valign="top">298</td>
<td align="center" valign="top">12A</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data SYSSEQ</td>
</tr>
<tr>
<td align="center" valign="top">299</td>
<td align="center" valign="top">12B</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data RMTADR</td>
</tr>
<tr>
<td align="center" valign="top">300</td>
<td align="center" valign="top">12C</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data THD</td>
</tr>
<tr>
<td align="center" valign="top">301</td>
<td align="center" valign="top">12D</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data LUW</td>
</tr>
<tr>
<td align="center" valign="top">302</td>
<td align="center" valign="top">12E</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Fixed length data XID</td>
</tr>
<tr>
<td align="center" valign="top">
<img src="v5r4adelta.gif" alt="Start of change">303</td>
<td align="center" valign="top">12F</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">307</td>
<td align="center" valign="top">133</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journaled object limit</td>
</tr>
<tr>
<td align="center" valign="top">308</td>
<td align="center" valign="top">134</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled objects</td>
</tr>
<tr>
<td align="center" valign="top">312</td>
<td align="center" valign="top">138</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled files</td>
</tr>
<tr>
<td align="center" valign="top">316</td>
<td align="center" valign="top">13C</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled members</td>
</tr>
<tr>
<td align="center" valign="top">320</td>
<td align="center" valign="top">140</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled data areas</td>
</tr>
<tr>
<td align="center" valign="top">324</td>
<td align="center" valign="top">144</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled data queues</td>
</tr>
<tr>
<td align="center" valign="top">328</td>
<td align="center" valign="top">148</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled integrated file system objects of type
*DIR, *STMF, and *SYMLNK</td>
</tr>
<tr>
<td align="center" valign="top">332</td>
<td align="center" valign="top">14C</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of journaled access paths</td>
</tr>
<tr>
<td align="center" valign="top">336</td>
<td align="center" valign="top">150</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Total number of commitment definitions</td>
</tr>
<tr>
<td align="center" valign="top">340</td>
<td align="center" valign="top">154</td>
<td align="left" valign="top">BINARY(4) UNSIGNED</td>
<td align="left" valign="top">Journal recovery count</td>
</tr>
<tr>
<td align="center" valign="top">344</td>
<td align="center" valign="top">158</td>
<td align="left" valign="top">CHAR(104)</td>
<td align="left" valign="top">Reserved
<img src="v5r4adeltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td align="center" valign="top">448</td>
<td align="center" valign="top">1C0</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of keys in key section</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong>These fields
repeat for each key specified.</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Key</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to start of key information</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of key information header section</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of entries</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of each entry in key information list
section</td>
</tr>
</table>
<br>
<h3><a name="HDRRJRNIK1">Key 1 Output Section</a></h3>
<table border width="80%">
<!-- cols="10 10 20 60" -->
<tr>
<th align="CENTER" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields are returned when the journal receiver directory key information is
specified. Otherwise, they will not be used.</td>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Total number of journal
receivers</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total size of journal receivers</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total size of journal receivers multiplier</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields repeat for each journal receiver that is returned.</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Journal receiver name</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Journal receiver library name</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(5)</td>
<td align="left" valign="top">Journal receiver number</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Journal receiver attached date and time</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Journal receiver status</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Journal receiver saved date and time</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Local journal system associated with the journal
receiver</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Source journal system associated with the journal
receiver</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Journal receiver size</td>
</tr>
<tr>
<td align="center" valign="top"><br>
</td>
<td align="center" valign="top"><br>
</td>
<td align="left" valign="top">CHAR(56)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<h3><a name="HDRRJRNIK2">Key 2 Output Section</a></h3>
<table border width="80%">
<!-- cols="10 10 20 60" -->
<tr>
<th align="CENTER" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields are returned when the journaled object information key is specified.
Otherwise, they will not be used.</td>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Total number of journaled files</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total number of journaled members</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total number of journaled data areas</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total number of journaled data queues</td>
</tr>
<tr>
<td align="center" valign="top">16</td>
<td align="center" valign="top">10</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total number of journaled integrated
file system objects of type *DIR, *STMF, and *SYMLNK</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields repeat for each journaled object that is returned.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object type</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object name</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object library name</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Object file identifier</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<h3><a name="HDRRJRNIK3">Key 3 Output Section</a></h3>
<table border width="80%">
<!-- cols="10 10 20 60" -->
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields are returned when the remote journal information key is specified.
Otherwise, they will not be used.</td>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Total number of remote journals</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The following
fields repeat for each remote journal that is returned.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(18)</td>
<td align="left" valign="top">Relational database directory entry</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Remote journal name</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Remote journal library name</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Remote journal receiver library name</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Controlled-inactivate journal information journal
receiver</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Controlled-inactivate journal information journal
receiver library</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Controlled-inactivate journal information
sequence number</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Remote journal type</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Remote journal state</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Remote journal delivery mode</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Sending task priority</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Controlled-inactivate journal information
sequence number - long</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(60)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(512)</td>
<td align="left" valign="top">Relational database directory entry details</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(348)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<h3><a name="HDRRJRNIFL">Field Descriptions</a></h3>
<p><strong>Attached dual journal receiver library name.</strong> The name of
the library that contains the dual journal receiver.</p>
<p>This field is blank if there is no dual receiver.</p>
<p><strong>Attached dual journal receiver name.</strong> The journal receiver
that was attached at the same time as the attached journal receiver.</p>
<p>This field is blank if there is no dual receiver.</p>
<p><strong>Attached journal receiver library name.</strong> The name of the
library that contains the attached journal receiver. This field will be blank
if no journal receivers are attached.</p>
<p><strong>Attached journal receiver name.</strong> The name of the journal
receiver that is currently attached to this journal. This field will be blank
if no journal receivers are attached.</p>
<p><strong>Auxiliary storage pool (ASP).</strong> The number of the auxiliary
storage pool to which storage for the object is allocated.</p>
<p><strong>ASP device name.</strong>
The name of the independent auxiliary storage pool (ASP) to which storage for
the object is allocated. *SYSBAS is used to indicate the system ASP and all
basic user ASPs.</p>
<p><strong>Bytes available.</strong> The number of bytes of data available to
be returned. All available data is returned if enough space is provided.</p>
<p><img src="v5r4adelta.gif" alt="Start of change">
<strong>Note:</strong>The format name determines what units are used for this field.
If format RJRN0100 is specified, the information is in one byte units.
If format RJRN0200 is specified, the information is in 4K (4096 bytes) units.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
<p><strong>Bytes returned.</strong> The number of bytes of data returned.</p>
<p><img src="v5r4adelta.gif" alt="Start of change">
<strong>Note:</strong>The format name determines what units are used for this field.
If format RJRN0100 is specified, the information is in one byte units.
If format RJRN0200 is specified, the information is in 4K (4096 bytes) units.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
<p><strong>Controlled-inactivate journal information journal receiver.</strong>
The name of the journal receiver that contains the controlled inactivate
journal information sequence number.</p>
<p>This field will be blank unless the remote journal state is *CTLINACT.</p>
<p><strong>Controlled-inactivate journal information journal receiver
library.</strong> The library of the journal receiver that contains the
controlled inactivate journal information sequence number.</p>
<p>This field will be blank unless the remote journal state is *CTLINACT.</p>
<p><strong>Controlled-inactivate journal information sequence number.</strong>
The sequence number of the last journal entry that was queued for replication
before the Change Remote Journal (CHGRMTJRN) command or the Change Journal
State (QjoChangeJournalState) API was called to start a controlled inactivate
of the remote journal.</p>
<p>This field will be 0 unless the remote journal state is *CTLINACT.</p>
<p>This field will be -1 if the value could not fit in the specified Binary(4)
field. The complete value will be in the Controlled-inactivate journal
information sequence number - long field.</p>
<p><strong>Controlled-inactivate journal information sequence number -
long.</strong> This is the same field as Controlled-inactivate journal
information sequence number except the information is in a Char(20) field which
is treated as Zoned(20,0).</p>
<p><strong>Delete receiver
delay.</strong> The delay time (in minutes) between attempts to delete journal
receivers associated with this journal if the delete receiver option is a 1.
The default is 10 minutes. </p>
<p><strong>Delete receiver option.</strong> Whether the system deletes detached
journal receivers that are associated with this journal when they are no longer
needed for IPL recovery.</p>
<table cellpadding="3">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The system does not delete detached journal
receivers that are associated with this journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The system deletes detached journal receivers
that are associated with this journal.</td>
</tr>
</table>
<br>
<p> <strong>Fixed length data
*JOB.</strong> Indicates whether the job name will be stored when journal
entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the job name.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the job name.</td>
</tr>
</table>
<p><strong>Fixed length data *LUW.</strong> Indicates whether the logical unit
of work identifier will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the logical unit of work identifier.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal may
include the logical unit of work identifier.</td>
</tr>
</table>
<p><strong>Fixed length data *PGM.</strong> Indicates whether the program name
will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the program name.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the program name.</td>
</tr>
</table>
<p><strong>Fixed length data *PGMLIB.</strong> Indicates whether the program
library name will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the program library name and library ASP information.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the program library name and library ASP information.</td>
</tr>
</table>
<p><strong>Fixed length data *RMTADR.</strong> Indicates whether the remote
address will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the remote address.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal may
include the remote address.</td>
</tr>
</table>
<p><strong>Fixed length data *SYSSEQ.</strong> Indicates whether the system
sequence number will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the system sequence number.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the system sequence number.</td>
</tr>
</table>
<p><strong>Fixed length data *THD.</strong> Indicates whether the thread
identifier will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the thread identifier.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the thread identifier.</td>
</tr>
</table>
<p><strong>Fixed length data *USR.</strong> Indicates whether the user name
will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the user name.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will
include the user name.</td>
</tr>
</table>
<p><strong>Fixed length data *XID.</strong> Indicates whether the transaction
identifier will be stored when journal entries are deposited.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries deposited to the journal will not
include the transaction identifier.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries deposited to the journal may
include the transaction identifier.</td>
</tr>
</table>
<p> <strong>Journal
cache.</strong> Specifies whether journal entries were cached before being
written out to disk.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries are written to disk immediately
if needed to assure single-system recovery.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries are written to main memory. When
there are several journal entries in main memory then the journal entries are
written from main memory to disk. If the application performs large numbers of
changes, this may result in fewer synchronous disk writes resulting in improved
performance. However, is is <strong>not recommended</strong> to use this option
if it is unacceptable to lose even one recent change in the event of a system
failure where the contents of main memory are not preserved. This type of
journaling is directed primarily toward batch jobs and may not be suitable for
interactive applications where single system recovery is the primary reason for
using journaling.
<p><strong>Note:</strong>Applications using commitment control will likely see
less performance improvement because commitment control already performs some
journal caching. </p>
</td>
</tr>
</table>
<p><strong>Journal delivery mode.</strong> The journal delivery mode that is
being used to replicate journal entries to this journal.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Not applicable. This is a local journal or this
remote journal is not *ACTIVE or not *CTLINACT.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*ASYNC. Journal entries are being delivered or
replicated asynchronously.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*SYNC. Journal entries are being delivered or
replicated synchronously.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">*ASYNCPEND. Journal entries are to be delivered
or replicated asynchronously, but the journal is currently in catch-up
mode.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">*SYNCPEND. Journal entries are to be delivered or
replicated synchronously, but the journal is currently in catch-up mode.</td>
</tr>
</table>
<p><strong>Journal library name.</strong> The name of the library that contains
the journal.</p>
<p><strong>Journal name.</strong> The name of the journal.</p>
<p><strong>Journal receiver attached date and time.</strong> The date and time
that this journal receiver was attached to the journal. For a journal receiver
attached to a *REMOTE journal, this is the date and time that the journal
receiver was attached on the local system. This field is in the CYYMMDDHHMMSS
format as follows:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td><em>C</em></td>
<td>Century, where 0 indicates years 19<em>xx</em> and 1 indicates years
20<em>xx</em>.</td>
</tr>
<tr>
<td><em>YY</em></td>
<td>Year</td>
</tr>
<tr>
<td><em>MM</em></td>
<td>Month</td>
</tr>
<tr>
<td><em>DD</em></td>
<td>Day</td>
</tr>
<tr>
<td><em>HH</em></td>
<td>Hour</td>
</tr>
<tr>
<td><em>MM</em></td>
<td>Minute</td>
</tr>
<tr>
<td><em>SS</em></td>
<td>Second</td>
</tr>
</table>
<p><strong>Journal receiver library name.</strong> The name of the library that
contains the journal receiver.</p>
<p><strong>Journal receiver name.</strong> The name of the journal
receiver.</p>
<p><strong>Journal receiver number.</strong> A number that is associated with a
journal receiver and assigned by the system, which is relative to all other
journal receivers in the journal receiver directory at this time. For a given
journal receiver, this number will change as journal receivers are added and
deleted from the directory. The first 2 digits identify the journal chain
number and the last 3 digits identify the journal receiver number within the
chain.</p>
<p>A chain identifies a group of journal receivers that are contiguous, which
allows the system to process entries across journal receivers within the same
chain.</p>
<p>The chain number starts with zero and is incremented sequentially each time
a new chain is needed. For example, new chains are started when a damaged
journal receiver is recovered by restoring a partial version.</p>
<p>Within a chain, each newly attached journal receiver is given a journal
receiver number starting with one and incrementing sequentially to 999.</p>
<p>When you journal to dual journal receivers, both journal receivers are
assigned the same number.</p>
<p><strong>Journal receiver saved date and time.</strong> The date and time
that the journal receiver was last saved. This field is in the CYYMMDDHHMMSS
format, which is described in the journal receiver attached date and time field
description.</p>
<p><strong>Journal receiver size.</strong> The number of kilobytes of auxiliary
disk storage used by this journal receiver.</p>
<p>This field will be zero if the journal receiver is damaged.</p>
<p><strong>Journal receiver status.</strong> The status of the journal
receiver. The status can be one of the following:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The journal receiver is currently attached to the
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The journal receiver is online. The journal
receiver has not been saved, and it has been detached from the journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">The journal receiver was saved after it was
detached. The journal receiver storage was not freed when it was saved.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">The journal receiver was saved after it was
detached. The journal receiver storage was freed when it was saved.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">The journal receiver status is partial for one of
the following reasons:
<ul>
<li>It was restored from a version that was saved while it was attached to the
journal. Additional journal entries may have been written that were not
restored.</li>
<li>It was one of a pair of dual journal receivers, and it was found damaged
while attached to the journal. The journal receiver has since been detached.
This journal receiver is considered partial because additional journal entries
may have been written to the dual journal receiver.</li>
<li>It is associated with a remote journal and it does not contain all the
journal entries that are in the corresponding journal receiver associated with
the source journal.</li>
</ul>
</td>
</tr>
</table>
<p>
<img src="v5r4adelta.gif" alt="Start of change">
<strong>Journal recovery count.</strong> The journal recovery count allows a
user to choose between faster abnormal IPL or independent ASP vary on
recovery and decreased run time
processing. The value specified influences the frequency with which journaled
objects are forced to auxiliary storage as those objects are changed. The
specified journal recovery count indicates the approximate number of journaled
changes that would need to be recovered during journal synchronization for this
journal in the event of an abnormal IPL or vary on.
Specifying a smaller value decreases the
number of changes that would need to be recovered from this journal in the
event of an
abnormal IPL or vary on
by increasing the frequency with which changed objects are forced.
Specifying a larger value increases the number of changes that would need to be
recovered for this journal during an abnormal IPL or vary on
by decreasing the frequency with
which changed objects are forced. Changing this value may affect overall system
performance as it affects the utilization of auxiliary storage devices.</p>
<p>
All journals are created with the system default journal recovery count.
If a value other than the system default is specified, the system default
journal recovery count will no longer be in effect for this journal.
</p>
<p>
The operating system is shipped with a system default journal
recovery count of 250,000. If there is a need to change the system
default journal recovery count for all newly created journals and
all existing journals that have the system default (*SYSDFT)
specified for their journal recovery count, please refer to the
Change Journal Recovery Count (QJOCHRVC) API.
</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The value is set to the system default
journal recovery count.
</td>
</tr>
<tr>
<td align="left" valign="top"><em>10000-2000000000</em></td>
<td align="left" valign="top">Specifies the approximate
number of journal entries
that may need to be recovered from this journal during an abnormal IPL
or vary on.
<img src="v5r4adeltaend.gif" alt="End of change">
</td>
</tr>
</table>
<p><strong>Journal state.</strong> An indication as to whether journal entries
are currently being sent to a journal. For a remote journal, this is whether
the journal is actively receiving journal entries from the source system
journal.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">*INACTIVE. If this is a remote journal, this means journal
entries cannot be received from a source journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*ACTIVE. If this is a local journal, this means
journal entries can be deposited to this journal. If this is a remote journal,
this means journal entries can be received from a source journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*FAILED. If this is a remote journal, this means
journal entries cannot be received from a source journal due to a remote
journal function failure, for example, a communications failure. Before
inactivating the remote journal by using the Change Remote Journal (CHGRMTJRN)
command or by calling the Change Journal State (QjoChangeJournalState) API, you
may want to receive, retrieve, or display any unconfirmed entries from this
journal.
<p>This value does not apply to local journals.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">*INACTPEND. If this is a remote journal, this
means a request is being processed to set the journal state to *INACTIVE.
<img src="v5r4adelta.gif" alt="Start of change">
Or, the remote journal was a target in a synchronous environment and the
environment has gone down, leaving unconfirmed entries in the journal.
<img src="v5r4adeltaend.gif" alt="End of change"><br>
<br>
<p>This value does not apply to local journals.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">*STANDBY. If this is a local journal,
this means that most journal entries are not deposited into the journal
and there will be no errors indicating that the entry was not deposited.
While in standby state, journaling can be started or stopped, however using
explicit commitment control is not allowed.
Also, databases files that have referential integrity constraints or data
links defined cannot be used when a journal is in standby state. The
operating system needs to use commitment control for these functions. However,
referential integrity constraints can be used in standby state if RESTRICT
is specified on the ON UPDATE or ON DELETE attribute for the constraint.
<p>This value applies only to local journals.</p>
</td>
</tr>
</table>
<p><strong>Journal text.</strong> The text description of the journal.</p>
<p><strong>Journal type.</strong> The journal type defines the scope of the
journal and some of its characteristics. The valid journal types follow:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">*LOCAL</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*REMOTE</td>
</tr>
</table>
<p>
<img src="v5r4adelta.gif" alt="Start of change">
<strong>Journaled object limit.</strong>
The journaled object limit defines how many objects can be journaled to
the journal. The valid journaled object limits follow:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">up to 250,000 objects</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">up to 10,000,000 objects<img src="v5r4adeltaend.gif" alt="End of change"></td>
</tr>
</table>
<p><strong>Key.</strong> Specific information retrieved about the journal.</p>
<p><strong>Length of key information header section.</strong> The length of the
header information in the given keys information section. The header is
followed by the list information section, which is a repeating list of entries
for the given key.</p>
<p><strong>Length of each entry in key information list section.</strong> The
length of an entry within a specific list that is returned for a given key.</p>
<p><strong>Local journal ASP
group name.</strong> The name of the independent auxiliary storage pool (ASP)
group of the local journal. *SYSBAS is used to indicate the system ASP and all
basic user ASPs. The local journal is the journal that is the initiator of the
original journal deposit that has been replicated downstream to this
journal.</p>
<p>This field is blank if there is no local journal.</p>
<p><strong>Local journal library name.</strong> The library name of the local
journal. The local journal is the journal that is the initiator of the original
journal deposit that has been replicated downstream to this journal.</p>
<p>This field is blank if there is no local journal.</p>
<p><strong>Local journal name.</strong> The journal name of the local journal.
The local journal is the journal that is the initiator of the original journal
deposit that has been replicated downstream to this journal.</p>
<p>This field is blank if there is no local journal.</p>
<p><strong>Local journal system.</strong> The system name of the local journal.
The local journal is the journal that is the initiator of the original journal
deposit that has been replicated downstream to this journal.</p>
<p>This system name is determined when the remote journal is activated by using
the Change Remote Journal (CHGRMTJRN) command or by calling the Change Journal
State (QjoChangeJournalState) API. The name is based on the current system name
at that time as seen by using the Display Network Attributes (DSPNETA)
command.</p>
<p>This field is blank if there is no local journal.</p>
<p>This field is *UNKNOWN if no journal receiver is currently attached or if
the journal receiver is damaged or destroyed.</p>
<p><strong>Local journal system associated with the attached journal
receiver.</strong> If this attached journal receiver is associated with a
remote journal, this field is the system name of the local journal. See the
local journal system field for more information.</p>
<p><strong>Local journal system associated with the journal receiver.</strong>
If this journal receiver was associated with a remote journal, this field is
the system name of the local journal. See the local journal system field for
more information.</p>
<p><strong>Manage receiver
delay.</strong> The delay time (in minutes) between attempts to attach new
journal receivers to this journal if the manage receiver option is a value of
1. The default is 10 minutes.</p>
<p>Zero is returned when the journal is a remote journal.</p>
<p><strong>Manage receiver option.</strong> Whether the system or user manages
the changing of journal receivers; that is, detaching the currently attached
journal receivers and attaching new journal receivers. This option is
applicable only for local journals and is blank for remote journals. Possible
values follow:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The user manages the changing of journal
receivers by issuing the Change Journal (CHGJRN) command to attach new journal
receivers and detach old journal receivers.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The system manages the changing of journal
receivers. When an attached journal receiver reaches its size threshold, the
system creates and attaches new journal receivers, and detaches the currently
attached journal receivers. Additionally, during an initial program load (IPL),
the system performs a Change Journal (CHGJRN) command to change journal
receivers and reset the journal sequence number if the journal is not needed to
complete commitment-control IPL recovery.</td>
</tr>
</table>
<p><strong>Message queue library name.</strong> The name of the library that
contains the message queue.</p>
<p><strong>Message queue name.</strong> The name of the message queue that is
associated with this journal. This message queue will receive various messages
that describe the operations on the journal. For example, if the threshold
value of the attached journal receiver is exceeded during journaling and the
journal currently is being managed by the user, a CPF7099 message is sent to
this message queue. If the journal is being managed by the system, then CPF7020
is sent to this message queue when the change journal has successfully
completed. Messages issued by the remote journal support will also be sent to
this message queue. The MNGRCV parameter on the Create Journal (CRTJRN) command
or on the Change Journal (CHGJRN) command) specifies whether the journal is
being managed by the user or by the system.</p>
<p><strong>Minimize entry specific data for data areas.</strong> Whether
journal entries for data areas may have minimized entry specific data. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries for data areas will have complete
entry specific data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries for data areas may have minimized
entry specific data.
</td>
</tr>
</table>
<p><strong>Minimize entry specific data for files.</strong> Whether journal
entries for files may have minimized entry specific data. The possible values
are:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Journal entries for files will have complete
entry specific data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Journal entries for files may have minimized
entry specific data.
<img src="v5r4adelta.gif" alt="Start of change">
The minimizing does not occur on field boundaries.
Therefore, the entry specific data may not be viewable
and may not be used for auditing purposes.
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Journal entries for files may have minimized
entry specific data. The minimizing occurs on
field boundaries. Therefore, the entry specific data will be viewable and
may be used for auditing purposes.
<img src="v5r4adeltaend.gif" alt="End of change">
</td>
</tr>
</table>
<p><strong>Number of attached journal receivers.</strong> The number of journal
receivers that are currently attached to the journal. If this number is two,
the dual journal receiver information is returned. If this number is one or
zero, the dual journal receiver information is returned as blanks. If this
number is zero, the journal receiver information is returned as blanks, and if
the journal receiver directory key is specified, there will be no entries
returned.</p>
<p><strong>Number of entries.</strong> The number of entries that are contained
within the specific list of information returned for a given key.</p>
<p><strong>Number of keys in key section.</strong> The number of keys that are
listed in the key section with specific information returned.</p>
<p><strong>Object file identifier.</strong> The file identifier (FID) of the
integrated file system object that is journaled to the specified journal.</p>
<p>This field will be blank if the object type field is not the special value
*IFS.</p>
<p><strong>Object library name.</strong> The name of the library that contains
the object that is journaled to the specified journal.</p>
<p>
<img src="v5r4adelta.gif" alt="Start of change">
This field will be contain *DIR, *SYMLNK, or *STMF if the object type
field is the special value *IFS.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
<p><strong>Object name.</strong> The name of the object that is journaled to
the specified journal.</p>
<p>This field will be blank if the object type field is the special value
*IFS.</p>
<p><strong>Object type.</strong> The type of the object that is journaled to
the specified journal.</p>
<p><strong>Note:</strong> If the object is of type *DIR, *SYMLNK, or *STMF, the
object type listed will be the special value *IFS.</p>
<p><strong>Offset to key information.</strong> The offset from the start of the
format to the key information section.
Specifically, this offset points to the Number of keys in key section field.
</p>
<p><strong>Offset to start of key information.</strong> The offset from the
start of the key section,
which starts immediately after the Number of keys in key section field,
to the specific information
returned for a given key.</p>
<p><strong>Receiver size option *MAXOPT1.</strong> Whether the journal receiver
attached to the journal can have a maximum receiver size of approximately one
terabyte (1,099,511,627,776 bytes) and a maximum sequence number of
9,999,999,999. Additionally, the maximum size of the journal entry that can be
deposited is 15,761,440 bytes. Journal receivers attached to a journal while
this option is in effect cannot be saved and restored to any releases prior to
V4R5M0, nor can they be replicated to any remote journals on any systems at
releases prior to V4R5M0. This option is applicable only for local journals and
is blank for remote journals.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately 1.9 gigabytes and a
maximum sequence number of 2,147,483,136, if neither *MAXOPT2 nor
*MAXOPT3 is
specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately one terabyte
(1,099,511,627,776 bytes) and a maximum sequence number of 9,999,999,999.
Additionally, the maximum size of the journal entry that can be deposited is
15,761,440 bytes.</td>
</tr>
</table>
<p><strong>Receiver size option *MAXOPT2.</strong> Whether the journal receiver
attached to the journal can have a maximum receiver size of approximately one
terabyte (1,099,511,627,776 bytes) and a maximum sequence number of
9,999,999,999. Additionally, the maximum size of the journal entry which can be
deposited is 4,000,000,000 bytes. Journal receivers attached to a journal while
this option is in effect cannot be saved and restored to any releases prior to
V5R1M0, nor can they be replicated to any remote journals on any systems at
releases prior to V5R1M0. This option is applicable only for local journals and
is blank for remote journals.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately 1.9 gigabytes and a
maximum sequence number of 2,147,483,136, if neither *MAXOPT1 nor
*MAXOPT3 is
specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately one terabyte
(1,099,511,627,776 bytes) and a maximum sequence number of 9,999,999,999.
Additionally, the maximum size of the journal entry that can be deposited is
4,000,000,000 bytes.</td>
</tr>
</table>
<p><strong>Receiver size option *MAXOPT3.</strong> Whether the journal receiver
attached to the journal can have a maximum receiver size of approximately one
terabyte (1,099,511,627,776 bytes) and a maximum sequence number of
18,446,744,073,709,551,600. Additionally, the maximum size of the journal entry
which can be
deposited is 4,000,000,000 bytes. Journal receivers attached to a journal while
this option is in effect cannot be saved and restored to any releases prior to
V5R3M0, nor can they be replicated to any remote journals on any systems at
releases prior to V5R3M0. This option is applicable only for local journals and
is blank for remote journals.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately 1.9 gigabytes and a
maximum sequence number of 2,147,483,136, if neither *MAXOPT1 nor *MAXOPT2 is
specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The journal receivers attached to the journal
will have a maximum journal receiver size of approximately one terabyte
(1,099,511,627,776 bytes) and a maximum sequence number of
18,446,744,073,709,551,600.
Additionally, the maximum size of the journal entry that can be deposited is
4,000,000,000 bytes.</td>
</tr>
</table>
<p><strong>Receiver size option
*MINFIXLEN.</strong> The size of the journal entries that are deposited into
the attached journal receivers is reduced by the automatic removal of
all fixed length data such as job
name, machine sequence number, and so on. This option is applicable only for local journals and is blank for remote journals.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The journal entries that are deposited include
all of the fixed length data such as
job name, system sequence number, and so on.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The journal entries that are deposited do not
include any of the fixed length data such as job name, system sequence number,
and so on. </td>
</tr>
</table>
<p><strong>Receiver size option *RMVINTENT.</strong> Whether the size of the
receivers that are attached to the journal are reduced by automatic removal of
the internal system entries. Removal occurs only for entries that are required
for initial program load (IPL) recovery when those entries are no longer
required. This option is applicable only for local journals and is blank for
remote journals.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Blank is returned when the journal is a remote
journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The internal system entries are not automatically
removed when they are no longer needed for recovery.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The internal system entries are automatically
removed when they are no longer needed for recovery.</td>
</tr>
</table>
<p><strong>Redirected receiver library name.</strong> For a local or *TYPE1
remote journal, this field gives the redirected receiver library name that is
currently in place on this journal's local journal for any downstream journal
receivers associated with *TYPE1 remote journals.</p>
<p>This field is set to *NONE if no receiver library redirection was specified
when *TYPE1 remote journals were added.</p>
<p>This field is set to the redirected receiver library name that is currently
in place on this remote journal if the specified journal is a *TYPE2 remote
journal.</p>
<p><strong>Relational database directory entry.</strong> The name of the
relational database directory entry that is associated with the remote
journal.</p>
<p><strong>Relational database directory entry details.</strong> The details
that are associated with the relational database directory entry. To view the
format of this information, which is a copy of a record in the relational
database directory file, use the Display File Field Description (DSPFFD)
command on the RDB directory logical file, QADBXRMTNM, in library QSYS.</p>
<p><strong>Remote journal delivery mode.</strong> The remote journal delivery
mode that is being used to replicate journal entries to the remote journal.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Not applicable. The remote journal is not *ACTIVE
or not *CTLINACT.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*ASYNC. Journal entries are being delivered or
replicated asynchronously.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*SYNC. Journal entries are being delivered or
replicated synchronously.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">*ASYNCPEND. Journal entries are to be delivered
or replicated asynchronously, but the remote journal is currently in catch-up
mode.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">*SYNCPEND. Journal entries are to be delivered or
replicated synchronously, but the remote journal is currently in catch-up
mode.</td>
</tr>
</table>
<p><strong>Remote journal library name.</strong> The library name of the remote
journal that is directly downstream of this journal.</p>
<p>This field is blank if there is no remote journal.</p>
<p><strong>Remote journal name.</strong> The name of the remote journal that is
directly downstream of this journal.</p>
<p>This field is blank if there is no remote journal.</p>
<p><strong>Remote journal receiver library name.</strong> The library name of
the remote journal receiver that is directly downstream of this journal.</p>
<p>This field is blank if there is no remote journal or if one was not
specified on the Add Remote Journal (ADDRMTJRN) command or the Add Remote
Journal (QjoAddRemoteJournal) API.</p>
<p><strong>Remote journal state.</strong> An indication as to whether the
remote journal is actively receiving journal entries from the source system
journal.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">*INACTIVE. The remote journal is not ready to
receive any journal entries from its source journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*ACTIVE. The remote journal is ready to receive
any journal entries from its source journal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*FAILED. The remote journal is not ready to
receive any journal entries from its source journal due to a remote journal
function failure, for example, a communications failure. You will need to
inactivate the remote journal by using the Change Remote Journal (CHGRMTJRN)
command or by calling the Change Journal State (QjoChangeJournalState)
API.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">*CTLINACT. The remote journal is in the process
of a controlled inactivate. Therefore, the remote journal will be receiving
those journal entries that were already queued for replication when the Change
Remote Journal (CHGRMTJRN) command or the Change Journal State
(QjoChangeJournalState) API requested to inactivate the remote journal.
However, no entries deposited after that request will be replicated to the
remote journal.</td>
</tr>
</table>
<p><strong>Remote journal type.</strong> The type of remote journal that was
created, and that influences characteristics of the remote journal such as
journal receiver restore options, redirection capabilities, and remote journal
association support. The possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Local journal</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*TYPE1 remote journal</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*TYPE2 remote journal</td>
</tr>
</table>
<p><strong>Reserved.</strong> The bytes reserved to align binary fields or for
future use.</p>
<p><strong>Sending task priority.</strong> If the remote journal delivery mode
is *ASYNC, this is the priority of the sending task on the source system.</p>
<p>If the remote journal delivery mode is not *ASYNC, or the remote journal
state is *INACTIVE, this field is -1.</p>
<p><strong>Source journal ASP
group name.</strong> The name of the independent auxiliary storage pool (ASP)
group of the source journal. *SYSBAS is used to indicate the system ASP and all
basic user ASPs. The source journal is the journal that is directly upstream
from this journal. </p>
<p>This field is blank if there is no source journal.</p>
<p><strong>Source journal library name.</strong> The library name of the source
journal. The source journal is the journal that is directly upstream of this
journal.</p>
<p>This field is blank if there is no source journal, if no journal receiver is
currently attached, or if the journal receiver is damaged or destroyed.</p>
<p><strong>Source journal name.</strong> The journal name of the source
journal. The source journal is the journal that is directly upstream of this
journal.</p>
<p>This field is blank if there is no source journal.</p>
<p>This field is *UNKNOWN if no journal receiver is currently attached, or if
the journal receiver is damaged.</p>
<p><strong>Source journal system.</strong> The system name of the source
journal. The source journal is the journal that is directly upstream of this
journal.</p>
<p>This system name is determined when the remote journal is activated by using
the Change Remote Journal (CHGRMTJRN) command or by calling the Change Journal
State (QjoChangeJournalState) API. The name is based on the current system name
at that time as seen by using the Display Network Attributes (DSPNETA)
command.</p>
<p>This field is blank if there is no source journal, if no journal receiver is
currently attached, or if the journal receiver is damaged.</p>
<p><strong>Source journal system associated with the attached journal
receiver.</strong> If this attached journal receiver is associated with a
remote journal, this field is the system name of the source journal. See the
source journal system field for more information.</p>
<p><strong>Source journal system associated with the journal receiver.</strong>
If this journal receiver was associated with a remote journal, this field is
the system name of the source journal. See the source journal system field for
more information.</p>
<p><img src="v5r4adelta.gif" alt="Start of change">
<strong>Total number of journaled access paths.</strong> The total number
of access paths that are currently being journaled to this journal.</p>
<p><strong>Total number of journaled commitment definitions.</strong>
The total number of commitment definitions that are currently being
implicitly journaled to this journal.
<img src="v5r4adeltaend.gif" alt="End of change"></p>
<p><strong>Total number of journaled data areas.</strong> The total number of
data areas that are currently being journaled to this journal.</p>
<p><strong>Note:</strong> This field will be set
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure
<img src="v5r4adeltaend.gif" alt="End of change">
only if data areas were requested to be returned by the
journaled object information key. Otherwise it will be 0
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return
structure. This value will always be returned in the base format structure.
<img src="v5r4adeltaend.gif" alt="End of change"></p>
<p><strong>Total number of journaled data queues.</strong> The total number of
data queues that are currently being journaled to this journal.</p>
<p><strong>Note:</strong> This field will be set
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure
<img src="v5r4adeltaend.gif" alt="End of change">
only if data queues were requested to be returned by the
journaled object information key. Otherwise it will be 0
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure.
This value will always be returned in the base format structure.
<img src="v5r4adeltaend.gif" alt="End of change"></p>
<p><strong>Total number of journaled files.</strong> The total number of files
that are currently being journaled to this journal.</p>
<p><strong>Note:</strong> This field will be set
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure
<img src="v5r4adeltaend.gif" alt="End of change">
only if files were requested to be
returned by the journaled object information key. Otherwise it will be 0
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure.
This value will always be returned in the base format structure.
<img src="v5r4adeltaend.gif" alt="End of change"></p>
<p><strong>Total number of journaled
<img src="v5r4adelta.gif" alt="Start of change">
integrated file system objects
<img src="v5r4adeltaend.gif" alt="End of change">
of type *DIR, *STMF, and
*SYMLNK.</strong> The total number of integrated file system objects of type
*DIR, *STMF, and *SYMLNK that are currently being journaled to this
journal.</p>
<p><strong>Note:</strong>This field will be set
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure only if
integrated file system objects
<img src="v5r4adeltaend.gif" alt="End of change">
were requested to be returned by the journaled object information key.
Otherwise it will be 0
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure.
This value will always be returned in the base format structure.
<img src="v5r4adeltaend.gif" alt="End of change">
</p>
<p><strong>Total number of journaled members.</strong> The total number of file
members that are currently being journaled to this journal.</p>
<p><strong>Note:</strong>This field will be set
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure
<img src="v5r4adeltaend.gif" alt="End of change">
only if files were requested to be
returned by the journaled object information key. Otherwise it will be 0
<img src="v5r4adelta.gif" alt="Start of change">
in the key 2 return structure.
This value will always be returned in the base format structure.
</p>
<p><strong>Total number of journaled objects.</strong>
This is the total of all objects journaled
to the journal. This count includes explicitly journaled objects such as
files, file members, access paths,
data areas, data queues and integrated file system objects.
This count also includes implicitly journaled objects such as
journal receivers, commitment definitions, and
objects journaled for system recovery purposes.</p>
<p><strong>Note:</strong>
The summation of these total number of object fields may give a number
that is higher or lower than the value returned in the
<strong>total number of journaled objects</strong> field.
This is possible because the total number of objects includes some
objects journaled by the system for system recovery purposes.
Also, all of the total fields can be actively changing while retrieving the
values.<img src="v5r4adeltaend.gif" alt="End of change"></p>
<p><strong>Total number of journal receivers.</strong> The total number of
journal receivers that are associated with the journal.</p>
<p><strong>Total number of remote journals.</strong> The total number of remote
journals that are directly downstream of this journal.</p>
<p><strong>Total size of journal receivers.</strong> The total size of the
journal receivers in number of kilobytes of auxiliary disk storage that are
associated with the journal. The size is in units of the total size of journal
receivers multiplier. The total size is equal to or smaller than the total size
multiplied by the total size of journal receivers multiplier.</p>
<p><strong>Total size of journal receivers multiplier.</strong> The value to
multiply the total size of journal receivers by to get the true total size. The
value is 1 if the total size of journal receivers is smaller than 2,147,483,647
kilobytes and 1024 if it is larger.</p>
<br>
<h3>Error Messages</h3>
<table width="100%" cellpadding="3">
<tr>
<th align="left" valign="top">Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td width="15%" valign="top">CPF24B4 E</td>
<td width="85%" valign="top">Severe error while addressing parameter list.</td>
</tr>
<tr>
<td valign="top">CPF3CF1 E</td>
<td valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C21 E</td>
<td valign="top">Format name &amp;1 is not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C24 E</td>
<td valign="top">Length of the receiver variable is not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C4D E</td>
<td valign="top">Length &amp;1 for key &amp;2 not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C82 E</td>
<td valign="top">Key &amp;1 not valid for API &amp;2.</td>
</tr>
<tr>
<td valign="top">CPF3C88 E</td>
<td valign="top">Number of variable length records &amp;1 is not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C90 E</td>
<td valign="top">Literal value cannot be changed.</td>
</tr>
<tr>
<td valign="top">CPF694B E</td>
<td valign="top">Length &amp;1 of variable record for key &amp;2 not
valid.</td>
</tr>
<tr>
<td valign="top">CPF694C E</td>
<td valign="top">Variable length record data for key &amp;1 not valid.</td>
</tr>
<tr>
<td valign="top">CPF6948 E</td>
<td valign="top">Length of the receiver variable &amp;1 is not valid.</td>
</tr>
<tr>
<td valign="top"><img src="v5r4adelta.gif" alt="Start of change">
CPF69A9 E</td>
<td valign="top">Internal error detected, error code &2.
<img src="v5r4adeltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td valign="top">CPF701B E</td>
<td valign="top">Journal recovery of interrupted operation failed.</td>
</tr>
<tr>
<td valign="top">CPF702C E</td>
<td valign="top">An attached receiver has previously been destroyed.</td>
</tr>
<tr>
<td valign="top">CPF708D E</td>
<td valign="top">Journal receiver found logically damaged.</td>
</tr>
<tr>
<td valign="top">CPF8100 E</td>
<td valign="top">All CPF81xx messages could be returned. xx is from 01 to
FF.</td>
</tr>
<tr>
<td valign="top">CPF9801 E</td>
<td valign="top">Object &amp;2 in library &amp;3 not found.</td>
</tr>
<tr>
<td valign="top">CPF9802 E</td>
<td valign="top">Not authorized to object &amp;2 in &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9803 E</td>
<td valign="top">Cannot allocate object &amp;2 in library &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9810 E</td>
<td valign="top">Library &amp;1 not found.</td>
</tr>
<tr>
<td valign="top">CPF9820 E</td>
<td valign="top">Not authorized to use library &amp;1.</td>
</tr>
<tr>
<td valign="top">CPF9872 E</td>
<td valign="top">Program or service program &amp;1 in library &amp;2 ended.
Reason code &amp;3.</td>
</tr>
</table>
<br>
<hr>
API introduced: V4R2
<hr>
<table cellpadding="2" cellspacing="2" align="center">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"jc1.htm">Journal and Commit APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink