60 lines
4.1 KiB
HTML
60 lines
4.1 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="Release-to-release considerations for remote journals" />
|
|
<meta name="abstract" content="Release-to-release considerations for remote journals are discussed in this topic." />
|
|
<meta name="description" content="Release-to-release considerations for remote journals are discussed in this topic." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.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="rzakireleases" />
|
|
<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>Release-to-release considerations for remote journals</title>
|
|
</head>
|
|
<body id="rzakireleases"><a name="rzakireleases"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Release-to-release considerations for remote journals</h1>
|
|
<div><p>Release-to-release considerations for remote journals are discussed
|
|
in this topic.</p>
|
|
<p>The release-to-release considerations for remote journals are:</p>
|
|
<ul><li>Information APAR II12556 contains a list of program temporary fixes (PTF)
|
|
to apply for V5R1 support of remote journaling.</li>
|
|
<li>If you specify RCVSIZOPT(*MAXOPT2) on the journal that you attach a journal
|
|
receiver to, you cannot replicate the journal receivers to any remote journals
|
|
on any systems at a release prior to V5R1M0.</li>
|
|
<li>If you specify minimized-entry specific data (MINENTDTA) for either *FILE
|
|
or *DTAARA on the journal to which you attached a journal receiver, you cannot
|
|
replicate the journal receivers to any remote journals on any systems at a
|
|
release before V5R1M0.</li>
|
|
<li><img src="./delta.gif" alt="Start of change" />If you specify minimized-entry specific data (MINENTDTA) for
|
|
*FLDBDY on the journal to which you attached a journal receiver, you cannot
|
|
replicate the journal receivers to any remote journals on any systems at a
|
|
release before V5R4M0.<img src="./deltaend.gif" alt="End of change" /></li>
|
|
<li> If you specify RCVSIZOPT(*MAXOPT3) on the journal that you attach a journal
|
|
receiver to, you cannot replicate the journal receivers to any remote journals
|
|
on any systems at a release prior to V5R3M0. </li>
|
|
<li><img src="./delta.gif" alt="Start of change" />If JRNOBJLMT(*MAX10M) is specified for a local journal, the
|
|
remote journal must exist on a system at a release of V5R4M0 or later.<img src="./deltaend.gif" alt="End of change" /></li>
|
|
</ul>
|
|
</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>
|
|
</body>
|
|
</html> |