66 lines
6.2 KiB
HTML
66 lines
6.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Journal receivers associated with a remote journal" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnrcvchn.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="rzakirjrnrcvrs" />
|
||
|
|
<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>Journal receivers associated with a remote journal</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakirjrnrcvrs"><a name="rzakirjrnrcvrs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal receivers associated with a remote journal</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>The receiver directory for a remote journal is maintained in the same way as the receiver directory is maintained for the related source journal. Consecutive receivers associated with a remote journal
|
||
|
|
are linked together to form a receiver chain. Receiver chain breaks are forced and maintained in a similar manner for local and remote journals.</p>
|
||
|
|
<p>However, the following are some other differences for remote journals and the journal receivers that were attached to remote journals:</p>
|
||
|
|
<ul><li>A remote journal does not have to have a currently attached journal receiver. However, if the remote journal is ready to receive journal entries, then it must have an attached receiver; all the journal
|
||
|
|
entries will be replicated to that attached receiver.</li>
|
||
|
|
<li>The receiver that is currently attached to a remote journal that is in the catch-up phase can be a different journal receiver than is currently attached to the source journal.</li>
|
||
|
|
<li>The receiver that is currently attached to an asynchronously maintained remote journal can be a different journal receiver than is currently attached to the source journal.</li>
|
||
|
|
<li>The receiver that is currently attached to a synchronously maintained remote journal is the same journal receiver as is currently attached to the source journal.</li>
|
||
|
|
<li>You can delete the journal receiver that is attached to a remote journal if the journal state of that journal is not *ACTIVE.</li>
|
||
|
|
<li>You can delete the journal receivers that are associated with a remote journal in any order, regardless of their position within the receiver directory chain.</li>
|
||
|
|
<li>The creation date and time stamps for remote journals are always those of the system on which the journals were created by the remote journal function. This is also true for journal receivers that were
|
||
|
|
attached to remote journals.</li>
|
||
|
|
<li>The save and restore date and time stamps for remote journals are always those of the system on which the save or restore operation took place. This is also true for the journal receivers that are associated
|
||
|
|
with the remote journals.</li>
|
||
|
|
<li>The attach and detach time stamps for a journal receiver that was attached to a remote journal are always those of the attach and detach time stamps of the local journal receiver.</li>
|
||
|
|
<li>When a journal receiver that is associated with a remote journal is saved, deleted or restored, the following journal entries are not deposited: <ul><li>J RD - Journal receiver deleted</li>
|
||
|
|
<li>J RF - Journal receiver saved, storage freed</li>
|
||
|
|
<li>J RR - Journal receiver restored</li>
|
||
|
|
<li>J RS - Journal receiver saved</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>For more information about journal receiver directory chains, see Keep track of journal receiver chains.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakirconcepts.htm" title="Remote journal management helps to efficiently replicate journal entries to one or more systems. You can use remote journal management with application programs to maintain a data replica. A data replica is a copy of the original data that resides on another iSeries server or independent disk pool. The original data resides on a primary system. Applications make changes to the original data during normal operations.">Remote journal concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrnrcvchn.htm" title="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.">Keep track of journal receiver chains</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|