130 lines
8.6 KiB
HTML
130 lines
8.6 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="Activate the replication of journal entries to a remote journal" />
|
||
|
<meta name="abstract" content="In order to activate the replication of journal entries to a given remote journal, the following must be true:" />
|
||
|
<meta name="description" content="In order to activate the replication of journal entries to a given remote journal, the following must be true:" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiactive.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakicatchup.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiaddremj.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakisynch.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakisrcjrnrcv.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJOCHGST.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgrmtjrn.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiriplconsid.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakirdatarep.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovdtails.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="rzakiactiverep" />
|
||
|
<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>Activate the replication of journal entries to a remote journal</title>
|
||
|
</head>
|
||
|
<body id="rzakiactiverep"><a name="rzakiactiverep"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Activate the replication of journal entries to a remote journal</h1>
|
||
|
<div><p>In order to activate the replication of journal entries to a given
|
||
|
remote journal, the following must be true:</p>
|
||
|
<div class="section"><ul><li>The remote journal that you wish to activate must not have a journal state
|
||
|
of *ACTIVE. For instance, this might seem to be a reasonable request if you
|
||
|
wanted to simply change the delivery mode from synchronous to asynchronous.
|
||
|
However, the remote journal must be inactive before you can activate it.</li>
|
||
|
<li>The remote journal that you wish to activate must not be actively replicating
|
||
|
journal entries to other remote journals, as in a cascade configuration. You
|
||
|
must inactivate the remote journals that are immediately downstream before
|
||
|
activating the remote journal.</li>
|
||
|
</ul>
|
||
|
<p>You need to provide the following input in order to activate the replication
|
||
|
of journal entries to a remote journal on a target system:</p>
|
||
|
<ul><li>The journal name and library on the source system from which journal entries
|
||
|
will be replicated.</li>
|
||
|
<li>The remote journal name and library on the target system to which journal
|
||
|
entries will be replicated.</li>
|
||
|
<li>A relational database directory entry, which identifies the target system
|
||
|
and other necessary communications information.</li>
|
||
|
<li>The delivery mode to be used. Specify either synchronous or asynchronous
|
||
|
delivery mode.</li>
|
||
|
<li>The journal receiver from which to start journal entry replication which
|
||
|
defines the starting point for journal entry replication.</li>
|
||
|
<li>If an asynchronous delivery mode was specified, then the <span class="uicontrol">sending
|
||
|
task priority</span> may also be specified. If a value is not specified,
|
||
|
the system selects a default priority, which is higher than what the user
|
||
|
can specify for this value. Setting this value too large may cause a greater
|
||
|
journal entry latency or lag.</li>
|
||
|
</ul>
|
||
|
<p>To activate the remote journal, proceed as follows:</p>
|
||
|
</div>
|
||
|
<ol><li><span>In the <strong>iSeries™ Navigator</strong> window, expand the system you
|
||
|
want to use.</span></li>
|
||
|
<li><span>Expand <span class="uicontrol">Databases</span>.</span></li>
|
||
|
<li><span>Expand the database that contains the journal.</span></li>
|
||
|
<li><span>Expand <span class="uicontrol">Schemas</span>.</span></li>
|
||
|
<li><span>Click the schema that contains the journal that has the associated
|
||
|
remote journal that you want to activate.</span></li>
|
||
|
<li><span>Right-click the journal, and select <span class="uicontrol">Properties</span>.</span></li>
|
||
|
<li><span>On the <span class="uicontrol">Journal Properties</span> dialog, click <span class="uicontrol">Remote
|
||
|
Journals</span>.</span></li>
|
||
|
<li><img src="./delta.gif" alt="Start of change" /><span>On the <strong>Remote Journals </strong>dialog,
|
||
|
select the remote journal in the list of remote journals, and then click <strong>Activate</strong> to
|
||
|
activate the selected remote journal.</span><img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
</ol>
|
||
|
<div class="section"><p>You can also activate the replication of journal entries from a
|
||
|
journal on a source system to a remote journal on a target system by using
|
||
|
one of the following methods:</p>
|
||
|
<ul><li>The Change Journal State (QjoChangeJournalState) API</li>
|
||
|
<li>The Change Remote Journal (CHGRMTJRN) command</li>
|
||
|
</ul>
|
||
|
<p>Both the QjoChangeJournalState API and the CHGRMTJRN command must
|
||
|
be issued from the source system.</p>
|
||
|
<p>The activation of the remote journal
|
||
|
can be a long running process. This may occur if there are a large number
|
||
|
of journal receivers and entries that initially must be caught-up in the remote
|
||
|
journal.</p>
|
||
|
<p>Catch-up phase for remote journals has more detailed information
|
||
|
about the catch-up phase.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<ul class="ullinks">
|
||
|
<li class="ulchildlink"><strong><a href="rzakicatchup.htm">Catch-up phase for remote journals</a></strong><br />
|
||
|
<span class="uicontrol">Catch-up</span> refers to the process of replicating
|
||
|
journal entries that existed in the journal receivers of the source journal
|
||
|
before the remote journal was activated.</li>
|
||
|
</ul>
|
||
|
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiactive.htm" title="Activating a remote journal means starting and then maintaining the replication of journal entries from a source journal to a remote journal. Activating a remote journal always occurs from the source system.">Activate and inactivate remote journals</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="rzakisynch.htm" title="The terms asynchronously maintained and synchronously maintained both describe a remote journal function delivery mode for journal entry replication.">Synchronous and asynchronous delivery mode for remote journals</a></div>
|
||
|
<div><a href="rzakisrcjrnrcv.htm" title="When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start.">Where the replication of journal entries start</a></div>
|
||
|
<div><a href="rzakiriplconsid.htm" title="This topic discusses the considerations for remote journaling when you restart the server.">Remote journal considerations when restarting the server</a></div>
|
||
|
</div>
|
||
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
<div><a href="rzakiaddremj.htm" title="This topic provides instructions for adding a remote journal.">Add remote journals</a></div>
|
||
|
<div><a href="rzakirecovdtails.htm" title="A description of the recovery process for remote journaling.">Details: Recovery for remote journaling scenario</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="../apis/QJOCHGST.htm">Change Journal State (QjoChangeJournalState) API</a></div>
|
||
|
<div><a href="../cl/chgrmtjrn.htm">Change Remote Journal (CHGRMTJRN) command</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>
|