153 lines
12 KiB
HTML
153 lines
12 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="Manual versus system journal-receiver management" />
|
|||
|
|
<meta name="abstract" content="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers." />
|
|||
|
|
<meta name="description" content="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakinamercv.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakithreshold.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnmssgque.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtjrn.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakithreshold.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiswapjrnrcv.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisizeoptions.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanagejrn.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiswapjrnrcv.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakideletercv.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiibmjrn.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijkldev.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakicandidates.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="rzakimanorsysmng" />
|
|||
|
|
<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>Manual versus system journal-receiver management</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzakimanorsysmng"><a name="rzakimanorsysmng"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Manual versus system journal-receiver management</h1>
|
|||
|
|
<div><p>When you create a journal with iSeries Navigator or the Create
|
|||
|
|
Journal (CRTJRN) command, you can select to have either system managed or
|
|||
|
|
user managed journal receivers.</p>
|
|||
|
|
<p>The default for the CRTJRN command is to have the system manage the journal
|
|||
|
|
receivers.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">User journal-receiver management</h4><p>If you specify
|
|||
|
|
user journal receiver management, you are responsible for changing the journal
|
|||
|
|
receiver when it approaches its storage threshold. If you choose this option,
|
|||
|
|
you can have the system send a message to a message queue when the journal
|
|||
|
|
receiver approaches its storage threshold.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">System journal-receiver management</h4><p>If you use system
|
|||
|
|
journal-receiver management, you can avoid having to do some journal management
|
|||
|
|
chores. However, if you are journaling for recovery purposes, you need to
|
|||
|
|
ensure that you save all journal receivers that have not been saved, not just
|
|||
|
|
the currently attached receiver. Also, if you are journaling for recovery
|
|||
|
|
purposes, be sure to specify that the system does not automatically delete
|
|||
|
|
receivers when no longer needed. Automatic deletion of journal receivers
|
|||
|
|
describes this option.</p>
|
|||
|
|
<p>If you use system journal-receiver management,
|
|||
|
|
you must ensure that your environment is suitable and that you regularly check
|
|||
|
|
the QSYSOPR message queue and the message queues assigned to your journals.</p>
|
|||
|
|
<p>If
|
|||
|
|
the system cannot complete the change journal operation because it cannot
|
|||
|
|
obtain the necessary locks, it retries every 10 minutes (or as specified by
|
|||
|
|
the MNGRCVDLY parameter). It sends messages (CPI70E5) to the journal's message
|
|||
|
|
queue and to the QSYSOPR message queue. If this occurs, you may want to determine
|
|||
|
|
why the operation cannot be performed and either correct the condition or
|
|||
|
|
swap the journal receiver your self with iSeries™ Navigator or the CHGJRN command.</p>
|
|||
|
|
<p>If
|
|||
|
|
the system cannot complete the change journal operation for any reason other
|
|||
|
|
than lock conflicts, it temporarily discontinues system journal-receiver management
|
|||
|
|
for that journal and sends a message (CPI70E3) to the message queue assigned
|
|||
|
|
to the journal or to the QSYSOPR message queue. This might occur because a
|
|||
|
|
journal receiver already exists with the name that it would generate. Look
|
|||
|
|
at the messages in the QHST job log to determine the problem. After you correct
|
|||
|
|
the problem, perform a swap journal operation to do the following:</p>
|
|||
|
|
<ul><li>Create a new journal receiver</li>
|
|||
|
|
<li>Detach the current receiver and attach a new journal receiver</li>
|
|||
|
|
<li>The system then resumes system journal-receiver management.</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">System journal-receiver management when you restart the system</h4><p>When
|
|||
|
|
you restart the system or vary on an independent disk pool, the system performs
|
|||
|
|
a CHGJRN command to change the journal receiver and reset the journal sequence
|
|||
|
|
number.</p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> If the journal has *MAXOPT3 specified as a receiver size
|
|||
|
|
option, the sequence number is not reset when you restart the
|
|||
|
|
system or vary on an independent disk pool unless the sequence number is approaching
|
|||
|
|
the maximum sequence number allowed.</div>
|
|||
|
|
<p>Also, if the journal is attached
|
|||
|
|
while a maximum receiver-size option is specified, the system attempts to
|
|||
|
|
perform a CHGJRN command to reset the sequence number when the following is
|
|||
|
|
true:</p>
|
|||
|
|
<ul><li>When the sequence number exceeds 9 900 000 000 if RCVSIZOPT(*MAXOPT1)
|
|||
|
|
or RCVSIZOPT (*MAXOPT2) is in effect for the journal.</li>
|
|||
|
|
<li>When the sequence number exceeds 18 446 644 000 000 000 000
|
|||
|
|
if RCVSIZOPT(*MAXOPT3) is in effect for the journal.</li>
|
|||
|
|
</ul>
|
|||
|
|
<p>For all other journal receivers, the system attempts this CHGJRN when
|
|||
|
|
the sequence number exceeds 2 147 000 000. </p>
|
|||
|
|
<p>The system
|
|||
|
|
does not reset the journal sequence number when you restart the system or
|
|||
|
|
vary on an independent disk pool if the entries in the receiver may be needed
|
|||
|
|
for commitment control recovery.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Delay automatic journal change</h4><p>If you use the CRTJRN
|
|||
|
|
or CHGJRN command, you can use the Manage Receiver Delay Time (MNGRCVDLY)
|
|||
|
|
parameter. When you use system journal-receiver management for a journal,
|
|||
|
|
if the system cannot allocate an object needed to attach a new journal receiver
|
|||
|
|
to the journal, it will wait the length of time that you specify in the MNGRCVDLY
|
|||
|
|
parameter before its next attempt to attach the new journal receiver. If you
|
|||
|
|
do not specify this parameter, the system will wait ten minutes, which is
|
|||
|
|
the default.</p>
|
|||
|
|
<p>The following topics have information related to management
|
|||
|
|
of journal receivers:</p>
|
|||
|
|
<ul><li>Automatic deletion of journal receivers</li>
|
|||
|
|
<li>Threshold (disk space) for journal receivers</li>
|
|||
|
|
<li>Swap journal receivers</li>
|
|||
|
|
<li>Receiver size options for journals</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnjrnsu.htm" title="The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal.">Plan setup for journals</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|||
|
|
<div><a href="rzakinamercv.htm" title="When you create a journal receiver either with iSeries Navigator or the Create Journal Receiver (CRTJRNRCV) command, you assign a name to the journal receiver.">Naming conventions for journal receivers</a></div>
|
|||
|
|
<div><a href="rzakithreshold.htm" title="When you create a journal receiver with iSeries Navigator or the Create Journal Receiver (CRTJRNRCV) command, you specify a disk space threshold that indicates when you want the system to warn you or take action.">Threshold (disk space) for journal receivers</a></div>
|
|||
|
|
<div><a href="rzakijrnmssgque.htm" title="When you create or change a journal, you can specify where the system sends messages that are associated with the journal. In addition, you can create a program to monitor this message queue and handle any messages associated with the journal. The system also sends messages that are related to the remote journal function to this message queue.">Journal message queue</a></div>
|
|||
|
|
<div><a href="rzakiautodelete.htm" title="If you choose system journal receiver management, you can also have the system delete journal receivers that are no longer needed for recovery. You can only specify this if you are using system journal receiver management.">Automatic deletion of journal receivers</a></div>
|
|||
|
|
<div><a href="rzakisizeoptions.htm" title="A journal receiver holds journal entries that you might use for recovery and entries that the system might use for recovery. For example, you might use record level entries, such as database record changes, and file level entries, such as the entry for opening or closing a file. Also, the system writes entries that you never see or use, such as entries for explicitly journaled access paths, for SMAPP, or for commitment control.">Receiver size options for journals</a></div>
|
|||
|
|
<div><a href="rzakimanagejrn.htm" title="Provides tasks to manage your journaling environment.">Manage journals</a></div>
|
|||
|
|
<div><a href="rzakiibmjrn.htm" title="The operating system and some licensed programs use journals to provide audit trails and assist with recovery.">Work with IBM-supplied journals</a></div>
|
|||
|
|
<div><a href="rzakijkldev.htm" title="JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often.">JKLDEV</a></div>
|
|||
|
|
<div><a href="rzakicandidates.htm" title="Journals that you are currently replicating, or that you plan to replicate, in their entirety to one or more systems, are excellent candidates for the remote journal function.">Journals that are good candidates for remote journal management</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|||
|
|
<div><a href="rzakiswapjrnrcv.htm" title="An important task for journal management is to swap (or change) journal receivers. You typically swap journal receivers when they reach their storage threshold. You can swap journal receivers either with iSeries Navigator or with the Change Journal (CHGJRN) command. If you use system journal-receiver management, the system changes journal receivers for you.">Swap journal receivers</a></div>
|
|||
|
|
<div><a href="rzakideletercv.htm" title="Journal receivers can quickly use a lot of auxiliary storage space. Therefore an important journal management task is to delete journal receivers after you no longer need them.">Delete journal receivers</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|||
|
|
<div><a href="../cl/crtjrn.htm">Create Journal (CRTJRN) command</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|