ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaki_5.4.0.1/rzakijrnrcvchn.htm

139 lines
10 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Keep track of journal receiver chains" />
<meta name="abstract" content="Journal receivers that are associated with a journal (that is presently or previously attached to the journal) are linked in one or more receiver chains. Each journal receiver, except the first one, has a previous receiver that was detached when the current receiver was attached. Each journal receiver, except the one that is currently attached, also has a next receiver." />
<meta name="description" content="Journal receivers that are associated with a journal (that is presently or previously attached to the journal) are linked in one or more receiver chains. Each journal receiver, except the first one, has a previous receiver that was detached when the current receiver was attached. Each journal receiver, except the one that is currently attached, also has a next receiver." />
<meta name="DC.Relation" scheme="URI" content="rzakiswapdel.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakiwrkjrna.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaiu/rzaiurzaiu300.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakipartialtrans.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakicorrectorder.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakirjrnrcvrs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakicatchup.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="rzakijrnrcvchn" />
<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>Keep track of journal receiver chains</title>
</head>
<body id="rzakijrnrcvchn"><a name="rzakijrnrcvchn"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Keep track of journal receiver chains</h1>
<div><p>Journal receivers that are associated with a journal (that is presently
or previously attached to the journal) are linked in one or more <strong>receiver
chains</strong>. Each journal receiver, except the first one, has a previous receiver
that was detached when the current receiver was attached. Each journal receiver,
except the one that is currently attached, also has a next receiver.</p>
<p>The following figure illustrates the process by which journal receiver
chains are created. If you leave the previously attached receivers RCVA7 through
RCVA9 online, you can use them to apply changes, to remove changes, or to
display journal entries without restoring them first.</p>
<div class="section"><h4 class="sectiontitle">Journal receiver chain</h4><br /><img src="rzaki505.gif" longdesc="rzakidesc_4.htm" alt="Journal receiver chain" /><br /><p><img src="./delta.gif" alt="Start of change" />The figure above represents a journal receiver chain. It shows
four journal receivers for journal JRNA. Journal receivers RCVA7, RCVA8, and
RCVA9 are online. Journal receiver RCVA10 is currently attached to journal
JRNA. Journal receivers RCVA1 through RCVA6 are saved to backup media and
not are not on the system.<img src="./deltaend.gif" alt="End of change" /></p>
<p>If a complete copy of a receiver is missing
in a chain of journal receivers linked together in the previously described
relationship, the result is a <span class="uicontrol">chain break</span>. Avoid receiver
chain breaks. A receiver chain break indicates that any changes made between
the last entry in the last receiver in one chain and the first entry in the
first receiver in the next chain are not available in any journal receiver
on the system.</p>
<div class="note"><span class="notetitle">Note:</span> If you use save-while-active operations to save objects
before they reach a commitment boundary, it is crucial that you keep track
of your journal receiver chains.</div>
<p>Using a save-while-active operation
to save objects before they reach a commitment boundary can result in objects
saved to the media that have partial transactions. A break in a journal receiver
chain can prevent you from recovering these objects with partial transactions.</p>
<p>A
set of receivers for a journal that has one or more receiver chain breaks
has multiple receiver chains. Receiver chain breaks result from the following:</p>
<ul><li>You restored an old journal receiver and its next receiver is not on the
system.</li>
<li>A journal receiver was saved while it was attached, a partial receiver
is restored, and no complete copy of the receiver is on the system or restored.</li>
<li>A receiver that has not had its storage freed by a save operation is restored,
and the next receiver has had its storage freed by a save operation.</li>
<li>The journal is restored. All journal receivers associated with the previous
copy of the journal (before the journal was deleted and restored) will not
be in the same receiver chain as the currently attached journal receiver.</li>
<li>The user or the system deleted a damaged or destroyed journal receiver
from the middle of a chain.</li>
<li>A journal receiver from another system is restored. The journal receiver
will be associated with a journal at restore time if the associated library
and journal on the source system had the same library name and journal name
as the library and journal on the target system.</li>
<li>You chose to replicate specific receivers instead of all receivers in
the receiver directory chain. This occurred while replicating journal receivers
from a source system to a target system.</li>
</ul>
<p>You cannot use the following commands and API across multiple receiver
chains:</p>
<ul><li><a href="../cl/apyjrnchg.htm">Apply Journaled
Changes (APYJRNCHG) command</a></li>
<li><a href="../cl/apyjrnchgx.htm">Apply Journaled
Changes Extend (APYJRNCHGX) command</a></li>
<li><a href="../cl/rmvjrnchg.htm">Remove Journaled
Changes (RMVJRNCHG) command</a></li>
<li><a href="../cl/rcvjrne.htm">Receive Journal
Entries (RCVJRNE) command</a></li>
<li><a href="../cl/dspjrn.htm">Display Journal
(DSPJRN) command</a></li>
<li><a href="../cl/rtvjrne.htm">Retrieve Journal
Entries (RTVJRNE) command</a></li>
<li><a href="../cl/cmpjrnimg.htm">Compare Journal
Images CMPJRNIMG command</a></li>
<li><a href="../apis/QJORJRNE.htm">Retrieve
Journal Entries (QjoRetrieveJournalEntries) API</a></li>
</ul>
<p>If multiple receiver chains exist, you need to determine:</p>
<ul><li>Whether any journal entries are missing.</li>
<li>Whether your data will be valid if you use more than one receiver chain.</li>
</ul>
<p>If you decide to proceed, you must run a separate command for each
receiver chain.</p>
<p>You can use the Work with Journal Attributes (WRKJRNA)
command to display the receiver chain (F15) and work with journal receivers.
See Display information for journaled objects, journals, and receivers for
more information about the WRKJRNA command.</p>
<p>See the Save your server
while it is active link below for instructions for saving an object with transactions
in a partial state. See the Example: Recover objects with partial transactions
link for instructions for recovering objects with transactions in a partial
state.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiswapdel.htm" title="The management tasks that you need to perform most often for journaling are swapping journal receivers and saving and deleting journal receivers.">Swap, delete, and save journals and receivers</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzakirjrnrcvrs.htm" title="Journal receivers that are associated with a remote journal are exact replicas of the corresponding journal receivers that are associated with the journal on the source system.">Journal receivers associated with a remote journal</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzakiwrkjrna.htm" title="iSeries Navigator, Control Language commands, and APIs provide several ways you can display information about journaled objects, journals, and journal receivers.">Display information for journaled objects, journals, and receivers</a></div>
<div><a href="../rzaiu/rzaiurzaiu300.htm">Save your server while it is active</a></div>
<div><a href="rzakipartialtrans.htm" title="If you restore an object that was saved with a save-while-active operation that specified that the object can be saved before it reaches a commitment boundary, it can have partial transactions. To recover objects that are in a partial state you must perform an apply or a remove journaled changes operation.">Example: Recover objects with partial transactions</a></div>
<div><a href="rzakicorrectorder.htm" title="You must restore journals and their associated objects in the correct order.">Correct order for restoration of journaled objects</a></div>
<div><a href="rzakicatchup.htm" title="Catch-up refers to the process of replicating journal entries that existed in the journal receivers of the source journal before the remote journal was activated.">Catch-up phase for remote journals</a></div>
</div>
</div>
</body>
</html>