151 lines
10 KiB
HTML
151 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="Where the replication of journal entries start" />
|
||
|
|
<meta name="abstract" content="When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start." />
|
||
|
|
<meta name="description" content="When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplanrjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirdiskpool.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiactiverep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakicatchup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirdatarep.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="rzakisrcjrnrcv" />
|
||
|
|
<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>Where the replication of journal entries start</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakisrcjrnrcv"><a name="rzakisrcjrnrcv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Where the replication of journal entries start</h1>
|
||
|
|
<div><p>When you specify a journal receiver for remote journaling, you
|
||
|
|
are specifying where the replication of journal entries will start.</p>
|
||
|
|
<p>You can choose from the following options:</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Attached receiver on target system</h4><p>The replication
|
||
|
|
of journal entries starts with the journal receiver that is currently attached
|
||
|
|
to the remote journal on the target system. The journal entries are replicated
|
||
|
|
from the corresponding journal receiver that is associated with the journal
|
||
|
|
on the source system. The replication starts with the journal entries that
|
||
|
|
follow the last journal entry that currently exists in the attached journal
|
||
|
|
receiver on the target system.</p>
|
||
|
|
<p>The remote journal on the target system
|
||
|
|
might not have an attached journal receiver. If this occurs, the journal receiver
|
||
|
|
that is currently attached to the journal on the source system is created
|
||
|
|
on the target system. That journal receiver is then attached to the remote
|
||
|
|
journal on the target system. Then journal entries are replicated starting
|
||
|
|
with the first journal entry in the journal receiver that is currently attached
|
||
|
|
to the journal on the source system.</p>
|
||
|
|
<p>If the journal on the source system
|
||
|
|
does not have an attached journal receiver, no journal entries can be replicated,
|
||
|
|
and an error is returned. This is only possible in the case of a remote journal
|
||
|
|
that is associated with another remote journal.</p>
|
||
|
|
<p>To use this option specify
|
||
|
|
one of the following:</p>
|
||
|
|
<ul><li><img src="./delta.gif" alt="Start of change" />Use the *ATTACHED special value for the Starting
|
||
|
|
journal receiver (STRJRNRCV) parameter on the Change Remote Journal (CHGRMTJRN)
|
||
|
|
command.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li>Use the <span class="uicontrol">*ATTACHED</span> special value for the Starting
|
||
|
|
journal receiver <span class="uicontrol">(STRJRNRCV)</span>parameter on the <span class="uicontrol">Change
|
||
|
|
Remote Journal (CHGRMTJRN)</span> command. </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Attached receiver on source system only</h4><p>The replication
|
||
|
|
of journal entries starts with the journal receiver that is currently attached
|
||
|
|
to the journal on the source system.</p>
|
||
|
|
<p>If the corresponding journal receiver
|
||
|
|
exists and is attached to the remote journal on the target system, journal
|
||
|
|
entries are replicated. Replication starts with the journal entries that follow
|
||
|
|
the last journal entry that currently exists in the attached journal receiver
|
||
|
|
on the target system. Otherwise, if the corresponding journal receiver exists
|
||
|
|
but is not attached to the remote journal on the target system, no journal
|
||
|
|
entries can be replicated. The system returns an error.</p>
|
||
|
|
<p>If the corresponding
|
||
|
|
journal receiver does not exist on the target system, the journal receiver
|
||
|
|
is created and attached to the remote journal on the target system. Journal
|
||
|
|
entries then are replicated starting with the first journal entry in the journal
|
||
|
|
receiver that is currently attached to the journal on the source system.</p>
|
||
|
|
<p>If
|
||
|
|
the journal on the source system does not have an attached journal receiver,
|
||
|
|
journal entries cannot be replicated, and the system returns an error. This
|
||
|
|
is only possible in the case of a remote journal that is associated with another
|
||
|
|
remote journal.</p>
|
||
|
|
<p>To use this option specify one of the following:</p>
|
||
|
|
<ul><li><img src="./delta.gif" alt="Start of change" />Use the *SRCSYS special value for the Starting journal receiver
|
||
|
|
(STRJRNRCV) parameter on the Change Remote Journal (CHGRMTJRN) command.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><span class="uicontrol">Use attached receiver on source system only</span> in
|
||
|
|
the <span class="uicontrol">Activate</span> dialog in iSeries™ Navigator.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Qualified journal receiver name</h4><p>The replication
|
||
|
|
of journal entries starts with the specified journal receiver name for the
|
||
|
|
journal on the source system.</p>
|
||
|
|
<p>If the corresponding journal receiver
|
||
|
|
exists and is attached to the remote journal on the target system, journal
|
||
|
|
entries are replicated. Replication starts with the journal entries that follow
|
||
|
|
the last journal entry that currently exists in the attached journal receiver
|
||
|
|
on the target system. Otherwise, if the corresponding journal receiver exists
|
||
|
|
but is not attached to the remote journal on the target system, no journal
|
||
|
|
entries can be replicated. The system returns an error.</p>
|
||
|
|
<p>If the corresponding
|
||
|
|
journal receiver does not exist on the target system, the journal receiver
|
||
|
|
is created and attached to the remote journal on the target system. Journal
|
||
|
|
entries then are replicated starting with the first journal entry in the specified
|
||
|
|
journal receiver.</p>
|
||
|
|
<p>If the journal on the source system is not associated
|
||
|
|
with the specified journal receiver, no journal entries can be replicated,
|
||
|
|
and an error is returned.</p>
|
||
|
|
<p>The creation of any receiver on the target
|
||
|
|
system by the change journal state processing is performed as though the receiver
|
||
|
|
was being saved and restored to the target system. Therefore, the ownership
|
||
|
|
of the receiver on a target system will follow the same rules as with the
|
||
|
|
existing save and restore functions. If the user profile which owns the receiver
|
||
|
|
on the source system is on the target system, then that profile will own the
|
||
|
|
created receiver on the target system. If the user profile does not exist
|
||
|
|
on the target system, then the profile QDFTOWN will own the receiver on the
|
||
|
|
target system.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />Additionally, information such as the audit
|
||
|
|
attributes, public authority, and primary group of the source journal receiver
|
||
|
|
at the time it was attached to the source journal will be incorporated into
|
||
|
|
the created journal receiver on the target system. If the owner, owner's authority,
|
||
|
|
public authority, primary group, or audit attributes of the source system's
|
||
|
|
receiver are changed, those changes will be propagated to the target system
|
||
|
|
when the next receiver is attached to the target journal. Changes made to
|
||
|
|
other private authorities of the source system's receiver must be maintained
|
||
|
|
separately on the target system.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>If the library for the journal receiver
|
||
|
|
resides in an ASP, the journal receiver will be created in that ASP. The remote
|
||
|
|
journal function does not support nonlibrary ASPs for the ASP of the remote
|
||
|
|
journal receiver. See Journal receiver disk pool considerations for more information.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplanrjrn.htm" title="The following topics provide detailed information for planning to set up remote journals:">Plan for remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakirdiskpool.htm" title="The receiver configuration is the disk pool the receiver resides in, and how the data for the receiver is spread across the disk arms within that disk pool.">Journal receiver disk pool considerations</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakiactiverep.htm" title="In order to activate the replication of journal entries to a given remote journal, the following must be true:">Activate the replication of journal entries to a remote journal</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 class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rzakirdatarep.htm" title="In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only.">Scenario: Data replication environment for remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|