129 lines
8.2 KiB
HTML
129 lines
8.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="task" />
|
||
|
|
<meta name="DC.Title" content="When the system ends applying or removing journaled changes" />
|
||
|
|
<meta name="abstract" content="The system ends applying or removing journaled changes as a result from one of the following items:" />
|
||
|
|
<meta name="description" content="The system ends applying or removing journaled changes as a result from one of the following items:" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiapyjrnchg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrncodes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiqajrnchg.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakiendappy" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>When the system ends applying or removing journaled changes</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiendappy"><a name="rzakiendappy"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">When the system ends applying or removing journaled changes</h1>
|
||
|
|
<div><p>The system ends applying or removing journaled changes as a result
|
||
|
|
from one of the following items:</p>
|
||
|
|
<div class="section"><ul><li>Certain journaled entries</li>
|
||
|
|
<li>A format error for a database physical file (such as an undefined entry
|
||
|
|
for that file member)</li>
|
||
|
|
<li>A logical error for a database physical file (such as updating a record
|
||
|
|
that has not been inserted or a duplicate key exception)</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />A logical error for a data queue (such as inserting
|
||
|
|
a keyed entry into a non-keyed queue)<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Unexpected error processing an entry<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<p>When one of the previous items occur, the apply or remove journaled
|
||
|
|
changes action can end either for the object or for the entire apply or remove
|
||
|
|
operation. You can determine this behavior by using the Object Error Option
|
||
|
|
(OBJERROPT) parameter on the Apply Journaled Changes (APYJRNCHG), Apply Journaled
|
||
|
|
Changes Extend (APYJRNCHGX), or Remove Journaled Changes (RMVJRNCHG) commands.</p>
|
||
|
|
<p>When
|
||
|
|
OBJERROPT(*END) is specified, for entries that end applying or removing journaled
|
||
|
|
changes, a message identifying the reason for the end is placed in the job
|
||
|
|
log, and the corresponding change is not made to the object. The message contains
|
||
|
|
the sequence number of the journal entry on which the failing condition was
|
||
|
|
detected. When OBJERROPT(*CONTINUE) is specified, message CPD7016 indicates
|
||
|
|
what entry the apply or removed stopped at, and the reason code. This information
|
||
|
|
is also available in the output file if one was generated. To correct the
|
||
|
|
problem do the following:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li><span>Analyze the error.</span></li>
|
||
|
|
<li><span>Make the necessary correction.</span></li>
|
||
|
|
<li><span>Start applying or removing journal changes again using the appropriate
|
||
|
|
sequence number.</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>For example, if the entry that causes a RMVJRNCHG command to end
|
||
|
|
is entry code F of type RG, you must reorganize the physical file member referred
|
||
|
|
to in the journal entry. Use the same options that were originally specified
|
||
|
|
on the reorganize request when the journal entry was recorded in the journal
|
||
|
|
receiver. Resume removing journal changes by starting with the journal entry
|
||
|
|
that follows the 'F RG' reorganize physical file member journal entry.</p>
|
||
|
|
<p>When
|
||
|
|
you apply or remove journaled changes you also have the option to have the
|
||
|
|
system send information about the operation to an output file. You can specify
|
||
|
|
whether information is sent about all objects in the operation or only objects
|
||
|
|
that have errors. To specify that the system sends information to an output
|
||
|
|
file use the Output (OUTPUT) option on the APYJRNCHG, APYJRNCHGX, or RMVJRNCHG
|
||
|
|
commands.</p>
|
||
|
|
<p>The APYJRNCHG, APYJRNCHGX, and RMVJRNCHG commands send an
|
||
|
|
escape message and ends the operation if any required journal receiver defined
|
||
|
|
by the RCVRNG parameter is not on the system and associated with the journal.
|
||
|
|
Use the WRKJRNA command to select the Work with journal receiver directory
|
||
|
|
display, to see which journal receivers are on the system and associated with
|
||
|
|
the journal. The escape message contains the name of the required journal
|
||
|
|
receiver if the reason code of message CPF7053 is 1 or if message CPF9801
|
||
|
|
is sent.</p>
|
||
|
|
<p>When the processing of applying or removing journaled changes
|
||
|
|
ends with an escape message, the objects can be partially changed. To determine
|
||
|
|
how many changes were applied or removed for each object do one of the following:</p>
|
||
|
|
<ul><li>Review the diagnostic messages in the job log prior to the final escape
|
||
|
|
message for each object.</li>
|
||
|
|
<li>Use the DSPJRN command to display the journal entries indicating completion
|
||
|
|
of the command.</li>
|
||
|
|
<li>If you specified to have the system send information to an output file,
|
||
|
|
review the output file. The output file contains a record for each object
|
||
|
|
that was processed. You can view that object's record to determine if processing
|
||
|
|
completed successfully for that object. </li>
|
||
|
|
</ul>
|
||
|
|
<p>The command completion journal entries by object type are as follows:</p>
|
||
|
|
<dl><dt class="dlterm">Database physical file members</dt>
|
||
|
|
<dd>F journal code and an entry type of AY or RC D journal code and entry
|
||
|
|
type of DD</dd>
|
||
|
|
<dt class="dlterm">Integrated file system objects</dt>
|
||
|
|
<dd>B journal code and entry type of AJ</dd>
|
||
|
|
<dt class="dlterm">Data area objects</dt>
|
||
|
|
<dd>E journal code and entry type of EQ or EX</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Data queue objects <img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd>Q journal code and entry type of QH</dd>
|
||
|
|
</dl>
|
||
|
|
<p>The <span class="uicontrol">Count</span> field in the journal entry
|
||
|
|
contains the number of journal entries that are applied or removed.</p>
|
||
|
|
<p>The
|
||
|
|
system puts out a maximum of 512 diagnostic messages from Apply or Remove
|
||
|
|
Journaled Changes. Therefore, it is recommended that you create an output
|
||
|
|
file to determine how many changes were applied or removed for each object.
|
||
|
|
For more information about the output file, see Use the apply and remove
|
||
|
|
journaled changes output file.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiapyjrnchg.htm" title="One of the primary advantages of journaling is its ability to return a journaled object to its current state since the last save.">Recover journaled objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrncodes.htm" title="The following table shows the actions that are taken by the Apply Journaled Changes (APYJRNCHG), Apply Journaled Changes Extend (APYJRNCHGX), or Remove Journaled Changes (RMVJRNCHG) command by journal code and entry type.">Actions of applying or removing journaled changes by journal code</a></div>
|
||
|
|
<div><a href="rzakiqajrnchg.htm" title="Use the apply and remove journaled changes output (QAJRNCHG) file to make a record of all the activity that occurs when you perform an apply or remove journaled changes operation.">Use the apply and remove journaled changes output file</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|