80 lines
7.4 KiB
HTML
80 lines
7.4 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="Remote journal management" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakikickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplanrjrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirsettingup.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiremrjrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiactive.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirmanage.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirscenarios.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihowwrks.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrn.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="rzakiremotekickoff" />
|
|
<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>Remote journal management</title>
|
|
</head>
|
|
<body id="rzakiremotekickoff"><a name="rzakiremotekickoff"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Remote journal management</h1>
|
|
<div><p>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.</p>
|
|
<p>Remote journal management allows you to establish journals and journal receivers on a remote system or to establish journal and receivers on independent disk pools that are associated with specific journals
|
|
and journal receivers on a local system. The remote journaling function can replicate journal entries from the local system to the journals and journal receivers that are located on the remote system or
|
|
independent disk pools after they have been established.</p>
|
|
<p>Use the following information to set up remote journal management:</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzakirconcepts.htm">Remote journal concepts</a></strong><br />
|
|
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 <span class="uicontrol">data replica</span>. A
|
|
data replica is a copy of the <span class="uicontrol">original data</span> 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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiplanrjrn.htm">Plan for remote journals</a></strong><br />
|
|
The following topics provide detailed information for planning to set up remote journals:</li>
|
|
<li class="ulchildlink"><strong><a href="rzakirsettingup.htm">Set up remote journals</a></strong><br />
|
|
These topics describe the steps you would use to create and work with a remote journal network or environment. They discuss how to establish and maintain one remote journal that is associated with one local journal.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiremrjrn.htm">Remove remote journals</a></strong><br />
|
|
You must be aware whether library redirection is in effect for the remote journal when you remove 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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiactive.htm">Activate and inactivate remote journals</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakirmanage.htm">Manage remote journals</a></strong><br />
|
|
Managing the remote journal function requires basic tasks such as:</li>
|
|
<li class="ulchildlink"><strong><a href="rzakirscenarios.htm">Scenarios: Remote journal management and recovery</a></strong><br />
|
|
These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakikickoff.htm" title="Journal management provides a means by which you can record the activity of objects on your system. When you use journal management, you create an object called a journal. The journal records the activities of the objects you specify in the form of journal entries. The journal writes the journal entries in another object called a journal receiver.">Journal management</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakihowwrks.htm" title="Use journal management to create an object called a journal. Use a journal to define which objects you want to protect. You can have more than one journal on your system. A journal can define protection for more than one object.">How journal management works</a></div>
|
|
<div><a href="rzakiplnjrn.htm" title="This topic provides you with the information you need to ensure you have enough disk space, to plan what objects to journal, and to plan which journaling options to use.">Plan for journal management</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |