80 lines
6.7 KiB
HTML
80 lines
6.7 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="Activate and inactivate remote journals" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiremotekickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiactiverep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakireldtabase.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiinactivate.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirretrievejrn.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="rzakiactive" />
|
||
|
|
<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 and inactivate remote journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiactive"><a name="rzakiactive"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Activate and inactivate remote journals</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Inactivating a remote journal means ending the replication of journal entries
|
||
|
|
from the source journal to the remote journal. Inactivating a remote journal
|
||
|
|
can be performed from the source or target systems. However, the preferred
|
||
|
|
method is to inactivate from the source system.</p>
|
||
|
|
<p>If this is the first time the remote journal is being activated, activating
|
||
|
|
a remote journal creates one or more journal receivers on the target system.
|
||
|
|
Activating the remote journal also establishes the connection between the
|
||
|
|
source and remote journal so that journal entry replication can begin.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />If the remote journal has previously been activated, the system
|
||
|
|
may or may not create additional receivers on the target system. This would
|
||
|
|
occur prior to establishing the connection between the source and remote journal
|
||
|
|
so that journal entry replication can resume.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />You must be aware if library redirection is in effect for the
|
||
|
|
remote journal when you activate or inactivate a remote journal.
|
||
|
|
If it is in effect, any library name processing will substitute the redirected
|
||
|
|
library name for the library name that is used for the operation on the target
|
||
|
|
system.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>See the following for instructions on activating and inactivating remote
|
||
|
|
journals:</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiactiverep.htm">Activate the replication of journal entries to a remote journal</a></strong><br />
|
||
|
|
In order to activate the replication of journal entries to a given remote journal, the following must be true:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakireldtabase.htm">Relational database considerations for remote journal state</a></strong><br />
|
||
|
|
Once a remote journal is activated, the remote journal function will work with the communications configuration defined by the specified relational database (RDB) entry as long as the remote journal is active. However, the information will be taken from the RDB at the point in time when the remote journal was activated. Therefore, even if the definition of the RDB entry is changed while a remote journal has a journal state of *ACTIVE, none of those changes will take effect immediately.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiinactivate.htm">Inactivate the replication of journal entries to a remote journal</a></strong><br />
|
||
|
|
When you end replication of journal entries to a remote journal, it is recommended that the replication of entries be ended from the source system whenever possible, rather than from the target system. Usually, ending replication from the target system for a remote journal is only necessary when the source system has failed, and the system has not ended the remote journal function.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiremotekickoff.htm" title="Use remote journal management to establish journals and journal receivers on a remote system that are associated with specific journals and journal receivers on a local system. Remote journal management replicates journal entries from the local system to the journals and journal receivers that are located on the remote system after they have been established.">Remote journal management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakirretrievejrn.htm" title="During the catch-up phase, journal entries that have been replicated to the target system can be retrieved from the remote journal.">Retrieve journal entries from a remote journal during the catch-up phase</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>
|