161 lines
10 KiB
HTML
161 lines
10 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="Journal state and delivery mode" />
|
||
|
|
<meta name="abstract" content="The journal state describes an attribute for a journal. The attribute value can be *ACTIVE, *INACTIVE (remote journal only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates that journal entries are currently allowed to be deposited into the journal. *STANDBY indicates that most journal entries are not deposited." />
|
||
|
|
<meta name="description" content="The journal state describes an attribute for a journal. The attribute value can be *ACTIVE, *INACTIVE (remote journal only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates that journal entries are currently allowed to be deposited into the journal. *STANDBY indicates that most journal entries are not deposited." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiconfirm.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="rzakistate" />
|
||
|
|
<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>Journal state and delivery mode</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakistate"><a name="rzakistate"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal state and delivery mode</h1>
|
||
|
|
<div><p>The <span class="uicontrol">journal state</span> describes an attribute
|
||
|
|
for a journal. The attribute value can be *ACTIVE, *INACTIVE (remote journal
|
||
|
|
only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates
|
||
|
|
that journal entries are currently allowed to be deposited into the journal.
|
||
|
|
*STANDBY indicates that most journal entries are not deposited.</p>
|
||
|
|
<p>You can view the journal state for a remote journal on a target system
|
||
|
|
that is associated with a journal on a source system in one of two ways:</p>
|
||
|
|
<ul><li><img src="./delta.gif" alt="Start of change" />When viewing the remote journal information of the local journal
|
||
|
|
from the source, *ACTIVE indicates that journal entries are currently being
|
||
|
|
replicated to that remote journal on the target system. *INACTIVE indicates
|
||
|
|
that journal entries are not currently being replicated.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />When viewing the journal attributes of the remote
|
||
|
|
journal from the target, *ACTIVE indicates that journal entries are currently
|
||
|
|
being received from the journal on the source system. *INACTIVE indicates
|
||
|
|
that the target journal is not ready to receive journal entries from the source
|
||
|
|
journal.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<p>The following table provides a summary of the journal type, delivery mode
|
||
|
|
and journal state interactions.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e35">Journal type</th>
|
||
|
|
<th valign="top" id="d0e37">Delivery mode</th>
|
||
|
|
<th valign="top" id="d0e39">Journal state</th>
|
||
|
|
<th valign="top" id="d0e41">Comments</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e35 ">*LOCAL</td>
|
||
|
|
<td valign="top" headers="d0e37 ">Not applicable</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*ACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">Objects journaled to the local journal can be changed, and entries
|
||
|
|
can also be deposited into the local journal using the Send Journal Entry
|
||
|
|
(SNDJRNE) command or the Send Journal Entry (QJOSJRNE) API interfaces. The
|
||
|
|
currently attached journal receiver may or may not be currently replicated
|
||
|
|
to one or more remote journals. This depends upon whether any remote journals
|
||
|
|
have been added to the local journal's definition, and if so, the current
|
||
|
|
journal state for each of those remote journals.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*LOCAL</td>
|
||
|
|
<td valign="top" headers="d0e37 ">Not applicable</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*STANDBY</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state of a local journal after the Change Journal (CHGJRN)
|
||
|
|
command specifying JRNSTATE(*STANDBY) is used to not allow deposits into the
|
||
|
|
local journal. The local can journal can also be in *STANDBY state after an
|
||
|
|
IPL if the local journal is in *STANDBY state when the system ends. <p>Objects
|
||
|
|
journaled to the local journal <strong>can</strong> be restored or changed, but most
|
||
|
|
journal entries are not deposited until the journal state for the local journal
|
||
|
|
is again changed to *ACTIVE. This can be performed by using the Change Journal
|
||
|
|
(CHGJRN) command specifying JRNSTATE(*ACTIVE).</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*SYNCPEND</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*ACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been activated using the
|
||
|
|
Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command and
|
||
|
|
the processing is still in the catch-up phase of remote journal activation.
|
||
|
|
Synchronous delivery mode was requested on the API invocation.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*SYNC</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*ACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been activated using the
|
||
|
|
Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command, after
|
||
|
|
catch-up has completed, and changes to the currently attached journal receiver
|
||
|
|
for the journal on the source system are being replicated synchronously to
|
||
|
|
the remote journal on the target system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*ASYNCPEND</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*ACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been activated using the
|
||
|
|
Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command and
|
||
|
|
the processing is still in the catch-up phase of remote journal activation.
|
||
|
|
Asynchronous delivery mode was requested on the API invocation.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*ASYNC</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*ACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been activated using the
|
||
|
|
Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command, after
|
||
|
|
catch-up has completed, and changes to the currently attached journal receiver
|
||
|
|
for the journal on the source system are being replicated asynchronously to
|
||
|
|
the remote journal on the target system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*SYNC</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*INACTPEND</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state of a remote journal, viewed from the target system
|
||
|
|
where some failure has occurred and either the system is in the process of
|
||
|
|
inactivating the remote journal, or unconfirmed journal entries exist in the
|
||
|
|
remote journal. See Confirmed and unconfirmed journal entries for more information.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*ASYNC</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*INACTPEND</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state of a remote journal, viewed from the target system
|
||
|
|
where some failure has occurred and the system is in the process of inactivating
|
||
|
|
the remote journal.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">*ASYNC</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*CTLINACT</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been made inactive using
|
||
|
|
the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command,
|
||
|
|
a controlled deactivate was requested on that call and that controlled deactive
|
||
|
|
has not yet completed.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e35 ">*REMOTE</td>
|
||
|
|
<td valign="top" headers="d0e37 ">Not applicable</td>
|
||
|
|
<td valign="top" headers="d0e39 ">*INACTIVE</td>
|
||
|
|
<td valign="top" headers="d0e41 ">This is the state after a remote journal has been added and associated
|
||
|
|
with a journal on a source system. However, the journal state for the added
|
||
|
|
remote journal has yet to be activated or has been made inactive using the
|
||
|
|
Change Journal State (QjoChangeJournalState) API, CHGRMTJRN command, or by
|
||
|
|
an IPL. No delivery mode is in effect for an inactive remote journal.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiconfirm.htm" title="For a local journal, all entries are confirmed entries. There is no concept of unconfirmed entries.">Confirmed and unconfirmed journal entries</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|