147 lines
10 KiB
HTML
147 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="Automatic deletion of journal receivers" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/XDLTRCV.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiu/rzaiurzaiu300.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakipartialtrans.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakideletercv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakicandidates.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirmaintanjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirdatarep.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="rzakiautodelete" />
|
||
|
|
<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>Automatic deletion of journal receivers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiautodelete"><a name="rzakiautodelete"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Automatic deletion of journal receivers</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>The system can only evaluate whether a receiver is needed for its own recovery
|
||
|
|
functions, such as recovering access paths or rolling back committed changes.
|
||
|
|
It cannot determine whether a receiver is needed to apply or remove journaled
|
||
|
|
changes.</p>
|
||
|
|
<div class="attention"><span class="attentiontitle">Attention:</span> Use automatic deletion of journal receivers with care
|
||
|
|
if you use save-while-active operations to save objects before they reach
|
||
|
|
a commitment boundary. Ensure that you save the journal receivers before the
|
||
|
|
system deletes them. If an object is saved before it reaches a commitment
|
||
|
|
boundary it can have partial transactions. To avoid data loss you must have
|
||
|
|
access to the journal receivers that were attached during the save-while-active
|
||
|
|
operation when you restore the objects with partial transactions.</div>
|
||
|
|
<p>The system will automatically delete journal receivers if you do one of
|
||
|
|
the following:</p>
|
||
|
|
<ul><li>Specify <span class="uicontrol">Delete receivers when no longer needed</span> in
|
||
|
|
the iSeries™ Navigator
|
||
|
|
Advanced Journal Attributes or Journal Properties dialog.</li>
|
||
|
|
<li>Specify DLTRCV (*YES) in the Create Journal (CRTJRN) or Change journal
|
||
|
|
(CHGJRN) commands.</li>
|
||
|
|
</ul>
|
||
|
|
<p>However, even if you select one of the previous items, the system cannot
|
||
|
|
delete the journal receiver if any of the following conditions is true:</p>
|
||
|
|
<ul><li>An exit program that is registered for the Delete Journal Receiver exit
|
||
|
|
point (QIBM_QJO_DLT_JRNRCV) indicates that the receiver is not eligible for
|
||
|
|
deletion.</li>
|
||
|
|
<li>A journal has remote journals associated with it, and one or more of the
|
||
|
|
associated remote journals does not have a full copy of this receiver.</li>
|
||
|
|
<li>The system could not get the appropriate locks that are required to complete
|
||
|
|
the operation.</li>
|
||
|
|
<li>The exit program registration facility was not available to determine
|
||
|
|
if any exit programs were registered.</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you use system delete-receiver support, you must ensure that your environment
|
||
|
|
is suitable. You must also regularly check the QSYSOPR message queue and the
|
||
|
|
message queues that are assigned to your journals.</p>
|
||
|
|
<ul><li>If the system cannot complete the DLTJRNRCV command for any of the above
|
||
|
|
reasons, it retries every 10 minutes (or the value you specify on the DLTRCVDLY
|
||
|
|
parameter). It sends a CPI70E6 message to the journal's message queue, and
|
||
|
|
to QSYSOPR message queue. If this occurs, you might want to determine why
|
||
|
|
the operation cannot be performed and either correct the condition or run
|
||
|
|
the DLTJRNRCV command.</li>
|
||
|
|
<li>If the system cannot complete the command for any other reason, it sends
|
||
|
|
a CPI70E1 message to the message queue that is assigned to the journal. If
|
||
|
|
you have not specifically assigned a message queue to the journal, the message
|
||
|
|
will be sent to the QSYSOPR message queue. Look at the messages in QHST to
|
||
|
|
determine the problem. After you correct the problem, use the DLTJRNRCV command
|
||
|
|
on the specific journal receiver.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Do not select to have the detached journal receiver deleted if you might
|
||
|
|
need it for recovery or if you want to save it before it is deleted. The system
|
||
|
|
does not save the journal receiver before deleting it. The system does not
|
||
|
|
issue the warning message (CPA7025) that it sends if a user tries to delete
|
||
|
|
a receiver that has not been saved.</p>
|
||
|
|
<p>Examples of when you might specify automatic journal deletion include:</p>
|
||
|
|
<ul><li>You are journaling only because it is required to use commitment control.</li>
|
||
|
|
<li>You are journaling for explicit access-path protection.</li>
|
||
|
|
<li>You are replicating the journal receiver to another system through the
|
||
|
|
remote journal function, and that system is providing the backup copy of the
|
||
|
|
journal receiver.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Delay the next attempt to delete a journal receiver</h4><p>If
|
||
|
|
you are using the CRTJRN or CHGJRN command, you can use the Delete Receiver
|
||
|
|
Delay Time (DLTRCVDLY) parameter. The system waits the time you specify (in
|
||
|
|
minutes) with the DLTRCVDLY parameter before its next attempt to delete a
|
||
|
|
journal receiver that is associated with the journal when one of the following
|
||
|
|
is true:</p>
|
||
|
|
<ul><li>The system cannot allocate a needed object.</li>
|
||
|
|
<li>You are using an exit program, and the exit program votes no.</li>
|
||
|
|
<li>You are using remote journaling and the receiver has not been replicated
|
||
|
|
to all the remote journals.</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you do not specify this parameter, the system waits ten minutes,
|
||
|
|
which is the default.</p>
|
||
|
|
<p>Save your server while it is active has instructions
|
||
|
|
for saving an object with transactions in a partial state. Example: Recover
|
||
|
|
objects with partial transactions has instructions for recovering objects
|
||
|
|
with partial transactions.</p>
|
||
|
|
</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="rzakimanorsysmng.htm" title="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.">Manual versus system journal-receiver management</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><a href="rzakirmaintanjrn.htm" title="As with local journals, regularly save and delete your journal receivers to minimize the amount of online auxiliary storage which is used by the journal receivers.">Journal receiver management with remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="../rzaiu/rzaiurzaiu300.htm">Save your server while it is active</a></div>
|
||
|
|
<div><a href="rzakipartialtrans.htm" title="If you restore an object that was saved with a save-while-active operation that specified that the object can be saved before it reaches a commitment boundary, it can have partial transactions. To recover objects that are in a partial state you must perform an apply or a remove journaled changes operation.">Example: Recover objects with partial transactions</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><a href="../cl/chgjrn.htm">Change journal (CHGJRN) command</a></div>
|
||
|
|
<div><a href="../apis/XDLTRCV.htm">Delete Journal Receiver exit point (QIBM_QJO_DLT_JRNRCV) API</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rzakirdatarep.htm" title="In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only.">Scenario: Data replication environment for remote journals</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|