206 lines
15 KiB
HTML
206 lines
15 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="task" />
|
||
|
|
<meta name="DC.Title" content="Delete journal receivers" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiswapdel.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnmssgque.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautodelete.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiinactivate.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/XDLTRCV.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakideletejrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecovrcvdmg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakipointer.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirmaintanjrn.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="rzakideletercv" />
|
||
|
|
<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>Delete journal receivers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakideletercv"><a name="rzakideletercv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Delete journal receivers</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiswapdel.htm" title="The management tasks that you need to perform most often for journaling are swapping journal receivers and saving and deleting journal receivers.">Swap, delete, and save journals and receivers</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<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="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="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="rzakipointer.htm" title="Under certain conditions, not all of the journal entry data will be immediately retrievable from a journal entry. Instead, part of the journal entry information will include pointers to additional journal entry-specific data.">Work with pointers in journal entries</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="rzakiinactivate.htm" title="When you end replication of journal entries to a remote journal, it is recommended that the replication of entries be ended from the source system whenever possible, rather than from the target system. Usually, ending replication from the target system for a remote journal is only necessary when the source system has failed, and the system has not ended the remote journal function.">Inactivate the replication of journal entries to a remote journal</a></div>
|
||
|
|
<div><a href="rzakideletejrn.htm" title="Each journal on the system causes additional time and resource to be used when you restart the system or vary on an independent disk pool after an abnormal end. If you no longer need a journal, you can delete it.">Delete journals</a></div>
|
||
|
|
<div><a href="rzakirecovrcvdmg.htm" title="If a journal receiver becomes damaged, the system sends message CPF8136 or message CPF8137 to the system operator and the job log.">Recover a damaged journal receiver</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/XDLTRCV.htm">QIBM_QJO_DLT_JRNRCV exit point</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="howdeljrnlrec"><a name="howdeljrnlrec"><!-- --></a><h2 class="topictitle2">How to determine whether to delete a journal receiver</h2>
|
||
|
|
<div><div class="section"><p>When you are determining whether to delete a journal receiver,
|
||
|
|
consider the following:</p>
|
||
|
|
<ul><li>Journal receivers you need for recovery.</li>
|
||
|
|
<li>Journal receivers you do not need for recovery.</li>
|
||
|
|
<li>Where the journal receiver is in the receiver chain.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="journalrecrecovery"><a name="journalrecrecovery"><!-- --></a><h2 class="topictitle2">Journal receivers you need for recovery</h2>
|
||
|
|
<div><div class="section"><p>Do not delete a journal receiver that has not been saved if you
|
||
|
|
need that journal for recovery. Any journal receiver that you need to perform
|
||
|
|
an apply or remove journaled changes operation is needed for recovery.</p>
|
||
|
|
<div class="attention"><span class="attentiontitle">Attention:</span> Use care when you delete journal receivers if you use save-while-active
|
||
|
|
operations to save objects before they reach a commitment boundary. Ensure
|
||
|
|
that you save the journal receivers before you delete them. If an object is
|
||
|
|
saved before it reaches a commitment boundary it can have partial transactions.
|
||
|
|
If you need to restore objects with partial transactions, you must have access
|
||
|
|
to the journal receivers that were attached during the partial transactions
|
||
|
|
to avoid data loss.</div>
|
||
|
|
<p>To determine if a journal receiver has been saved,
|
||
|
|
in iSeries™ Navigator,
|
||
|
|
right-click the journal receiver, and select <span class="uicontrol">Properties</span>.
|
||
|
|
If the <span class="uicontrol">Saved</span> field shows no date, then you have not
|
||
|
|
saved the journal receiver.</p>
|
||
|
|
<p>If you have saved the journal receiver,
|
||
|
|
but the journaled objects are not saved, then you still need that journal
|
||
|
|
receiver for recovery. If you have space on your system, wait to delete journal
|
||
|
|
receivers until it is unlikely that you need them for a recovery. (You saved
|
||
|
|
the journaled object). Restoring journal receivers before applying or removing
|
||
|
|
journaled changes may significantly increase your recovery time.</p>
|
||
|
|
<p>Although
|
||
|
|
it is not recommended, the system does not prevent you from deleting a receiver
|
||
|
|
you detached and is not saved or that is required to provide adequate recovery.
|
||
|
|
If you try to delete a journal receiver that was once attached but has not
|
||
|
|
been saved, the system issues an inquiry message. You can then continue or
|
||
|
|
cancel the delete operation. You can use the system reply list to specify
|
||
|
|
the reply the system is to send for this inquiry message (rather than explicitly
|
||
|
|
responding to each inquiry message).</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="journalrecerecovery"><a name="journalrecerecovery"><!-- --></a><h2 class="topictitle2">Journal receivers you do not need for a recovery</h2>
|
||
|
|
<div><div class="section"><p><img src="./delta.gif" alt="Start of change" />If you are journaling only for access path protection
|
||
|
|
or commitment control, most likely you do not need the journal receivers to
|
||
|
|
recover journaled changes. You do not need to save these journal receivers
|
||
|
|
before deleting them.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>To make your journaling tasks easier, you can
|
||
|
|
even automate the deletion of these journal receivers by specifying the following:</p>
|
||
|
|
<ul><li>Specify system journal-receiver management.</li>
|
||
|
|
<li>Specify automatic deletion of journal receivers.</li>
|
||
|
|
</ul>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />When you specify automatic deletion of journal receivers,
|
||
|
|
the system does not send a message when it deletes a journal receiver. By
|
||
|
|
specifying automatic deletion for journal receivers, you indicate that you
|
||
|
|
do not need the journal receivers for user recovery.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="wherejournalrechain"><a name="wherejournalrechain"><!-- --></a><h2 class="topictitle2">Where the journal receiver is in the receiver chain</h2>
|
||
|
|
<div><div class="section"><p>To ensure logical recovery, the system does not allow you to delete
|
||
|
|
a journal receiver from the middle of the receiver chain unless one of the
|
||
|
|
following conditions exists:</p>
|
||
|
|
<ul><li>The journal is using automatic deletion of journal receivers.</li>
|
||
|
|
<li>The journal is a remote journal.</li>
|
||
|
|
</ul>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />However, if a journal receiver is damaged, you can delete
|
||
|
|
it from the middle of the chain. If an attached journal receiver is damaged,
|
||
|
|
you must perform a change journal operation to detach the damaged receiver
|
||
|
|
before you can delete it.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="rulesdeljournal"><a name="rulesdeljournal"><!-- --></a><h2 class="topictitle2">Rules for deleting journal receivers</h2>
|
||
|
|
<div><div class="section"><p>The rules for deleting journal receivers are as follows:</p>
|
||
|
|
<ul><li>You cannot delete a journal receiver that is attached to a local journal.
|
||
|
|
You must perform a change journal operation to detach a journal receiver before
|
||
|
|
you delete it.</li>
|
||
|
|
<li>You must delete journal receivers in the same order they were attached
|
||
|
|
to a journal.</li>
|
||
|
|
<li>You can delete a damaged or inoperable receiver regardless of the previous
|
||
|
|
restriction. However, if an attached receiver is damaged, you must detach
|
||
|
|
it before you delete it.</li>
|
||
|
|
<li>You cannot delete a journal receiver that is attached to a remote journal
|
||
|
|
if the remote journal has a journal state of active. If you attempt to delete
|
||
|
|
a receiver that is attached to a remote journal, the system sends the inquiry
|
||
|
|
message <samp class="codeph">CPA705E</samp>. The results of the reply to the message
|
||
|
|
are the same as those that occur with message <samp class="codeph">CPA7025</samp>.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="procdeljournalrec"><a name="procdeljournalrec"><!-- --></a><h2 class="topictitle2">Procedure for deleting journal receivers</h2>
|
||
|
|
<div><div class="section">Proceed as follows:</div>
|
||
|
|
<ol><li><span>In the <span class="uicontrol">iSeries Navigator</span> window, expand
|
||
|
|
the system you want to use.</span></li>
|
||
|
|
<li><span>Expand <span class="uicontrol">Databases</span>.</span></li>
|
||
|
|
<li><span>Expand the database that you want to work with and <span class="uicontrol">Schemas</span>.</span></li>
|
||
|
|
<li><span>Click the schema you want to work with.</span></li>
|
||
|
|
<li><span>Right-click the journal receiver you want to delete and click <span class="uicontrol">Delete</span>.</span></li>
|
||
|
|
<li><span>At the <span class="uicontrol">Confirm Object Deletion</span> dialog click <span class="uicontrol">Delete</span>.</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>You can also use the <span class="cmdname">Delete Journal Receiver (DLTJRNRCV)</span> command
|
||
|
|
to delete journal receivers. If you use the <span class="cmdname">DLTJRNRCV</span> command,
|
||
|
|
an exit point is available to use with an exit program to help automate journal
|
||
|
|
receiver deletion.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested2" xml:lang="en-us" id="exitpointdltjrnrcv"><a name="exitpointdltjrnrcv"><!-- --></a><h3 class="topictitle3">Exit point for the <span class="cmdname">DLTJRNRCV</span> command</h3>
|
||
|
|
<div><div class="section"><p>One example of using this exit point is a situation where your
|
||
|
|
application is using the data in the journal receiver. The application is
|
||
|
|
dependent on the journal receiver being present until your application processing
|
||
|
|
is complete. By registering an exit program with the QIBM_QJO_DLT_JRNRCV exit
|
||
|
|
point, the program will be called every time a journal receiver is deleted
|
||
|
|
from the system. If your program determines that your application is not yet
|
||
|
|
done with the receiver, it can indicate that the journal receiver is not eligible
|
||
|
|
for deletion.</p>
|
||
|
|
<p>If you must delete the receiver regardless of what an
|
||
|
|
exit program indicates, you can specify *IGNEXITPGM for the DLTOPT parameter
|
||
|
|
on the DLTJRNRCV command. This parameter value requests that any user exit
|
||
|
|
programs that are registered for QIBM_QJO_DLT_JRNRCV exit point be ignored.</p>
|
||
|
|
<p>You
|
||
|
|
can also use the following values for the DLTOPT parameter:</p>
|
||
|
|
<dl><dt class="dlterm">*IGNTGTRCV</dt>
|
||
|
|
<dd>Ignore target receiver. If you specify this value, the system does not
|
||
|
|
verify that all remote journals that are associated with this journal, and
|
||
|
|
are immediately downstream on a target system, have full copies of this journal
|
||
|
|
receiver. The delete operation will continue, even if a remote journal does
|
||
|
|
not have a full copy.</dd>
|
||
|
|
<dt class="dlterm">*IGNINQMSG</dt>
|
||
|
|
<dd>Ignore inquiry message. Inquiry message CPA7025 will not be presented,
|
||
|
|
even if this receiver has not been fully saved. Also, inquiry message CPA705E
|
||
|
|
is not presented to the user even if the receiver is attached to a remote
|
||
|
|
journal. The delete operation continues.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|