84 lines
6.0 KiB
HTML
84 lines
6.0 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="Supported communications protocols for remote journals" />
|
||
|
|
<meta name="abstract" content="The remote journal function supports the following communications protocols for replicating the journal entries to the remote systems:" />
|
||
|
|
<meta name="description" content="The remote journal function supports the following communications protocols for replicating the journal entries to the remote systems:" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirprepare.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="rzakiprotocols" />
|
||
|
|
<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>Supported communications protocols for remote journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiprotocols"><a name="rzakiprotocols"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Supported communications protocols for remote journals</h1>
|
||
|
|
<div><p>The remote journal function supports the following communications
|
||
|
|
protocols for replicating the journal entries to the remote systems:</p>
|
||
|
|
<ul><li><strong>OptiConnect for i5/OS</strong>. If you want to use the OptiConnect for i5/OS<sup>®</sup> support,
|
||
|
|
you must purchase and install the required hardware and software for that
|
||
|
|
support. Refer to <a href="../rzau3/rzau3kickoff.htm">OptiConnect
|
||
|
|
for i5/OS</a> for
|
||
|
|
more information.</li>
|
||
|
|
<li><strong>Systems Network Architecture (SNA)</strong>. If you want to use SNA for
|
||
|
|
the transport, there are no additional software considerations. The software
|
||
|
|
support is in the base operating system. You must purchase whatever hardware
|
||
|
|
is appropriate for your configuration. For more information see <a href="http://publib.boulder.ibm.com/iseries/v5r1/ic2924/rzaqhindex.htm" target="_blank">SNA
|
||
|
|
Distribution Services</a> on the V5R1 Supplemental Manuals Web site.</li>
|
||
|
|
<li><strong>Transmission Control Protocol/Internet Protocol(TCP/IP)</strong>. If you
|
||
|
|
want to use TCP/IP for the transport, there are no additional software considerations.
|
||
|
|
The software support is in the base operating system. You must purchase whatever
|
||
|
|
hardware is appropriate for your configuration. Refer to <a href="../books/sc415420.pdf" target="_blank">TCP/IP Configuration and Reference</a> for
|
||
|
|
more information.<div class="note"><span class="notetitle">Note:</span> All remote journal TCP connections use the TCP local
|
||
|
|
port of 3777.</div>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>Specifying a relational database (RDB) directory entry will identify the
|
||
|
|
communications protocol that the remote journal function will use. The RDB
|
||
|
|
that is specified must meet the following rules:</p>
|
||
|
|
<ul><li>The communications protocol must be one of the remote journal function
|
||
|
|
supported protocols.</li>
|
||
|
|
<li>The remote location name in the RDB cannot refer to the *LOCAL database.</li>
|
||
|
|
<li>The RDB cannot use an application requester driver program (*ARDPGM) to
|
||
|
|
locate the target system.</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />When TCP communications are being used to connect to an independent
|
||
|
|
disk pool, the Relational Database (RDB) entry to the independent disk pool
|
||
|
|
must have the Relational database value set to the target system's local RDB
|
||
|
|
entry and the relational database alias value set to the independent disk
|
||
|
|
pool's name.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<p>For more information about creating relational databases, refer to the <a href="../ddp/rbal1kickoff.htm" target="_blank">Distributed
|
||
|
|
Database Programming</a>.</p>
|
||
|
|
<p>Security of the remote journal function is dependent on the communications
|
||
|
|
protocol security. The remote journal function does not alter the security
|
||
|
|
characteristics that are available.</p>
|
||
|
|
<p>The communications function that is identified by the RDB can be shared
|
||
|
|
by other activity. However, you may consider isolating the remote journal
|
||
|
|
function activity in order to have the best performance.</p>
|
||
|
|
</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 class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakirprepare.htm" title="This topic outlines the basic steps for preparing to use remote journals.">Prepare to use remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|