77 lines
4.8 KiB
HTML
77 lines
4.8 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="Methods to save journal receivers" />
|
||
|
|
<meta name="abstract" content="Following are three methods to save journal receivers. The first method saves journal receivers individually. The two other methods save the journal receiver automatically." />
|
||
|
|
<meta name="description" content="Following are three methods to save journal receivers. The first method saves journal receivers individually. The two other methods save the journal receiver automatically." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisavjrnrcv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.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="rzakisavbyname" />
|
||
|
|
<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>Methods to save journal receivers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakisavbyname"><a name="rzakisavbyname"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Methods to save journal receivers</h1>
|
||
|
|
<div><p>Following are three methods to save journal receivers. The first
|
||
|
|
method saves journal receivers individually. The two other methods save the
|
||
|
|
journal receiver automatically.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save journal receivers individually</h4><p>Use the Work
|
||
|
|
with Journal Attributes (WRKJRNA) command to display the receiver directory
|
||
|
|
for each journal. The receiver directory tells which journal receivers have
|
||
|
|
not yet been saved. Then use the Save Object (SAVOBJ) command to save them.</p>
|
||
|
|
<p>The
|
||
|
|
advantage to using this technique is that each journal receiver is saved only
|
||
|
|
once. You will not have problems with duplicate names and partial receivers
|
||
|
|
if you need to restore. The disadvantage to this technique is that it requires
|
||
|
|
manual effort to determine the names of the journal receivers to be saved.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save journal receivers by name - Automated method 1</h4><p>You
|
||
|
|
can use a combination of system journal-receiver management and a control
|
||
|
|
language (CL) program to automate most journal management tasks. Do the following:</p>
|
||
|
|
<ul><li>Specify a threshold size for the journal receiver.</li>
|
||
|
|
<li>Specify MNGRCV(*SYSTEM), DLTRCV(*NO), and a message queue for the journal.</li>
|
||
|
|
<li>Use a CL program to monitor the journal message queue for the message
|
||
|
|
(CPF7020) that indicates that the system has successfully detached the journal
|
||
|
|
receiver.</li>
|
||
|
|
<li>Your CL program can then save the receiver that was detached and optionally
|
||
|
|
delete it.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save journal receivers by name - Automated method 2</h4><p>An
|
||
|
|
alternate method of automatically saving journal receivers is to use a high
|
||
|
|
level language program that uses the Retrieve Journal Information (QjoRetrieveJournalInformation)
|
||
|
|
API. The program can use this API to determine the journal receiver directory
|
||
|
|
and which receivers are not saved. The program can then save the journal receivers
|
||
|
|
that are not marked as saved. You can set up this program to run on a regular
|
||
|
|
basis or as part of normal processing.</p>
|
||
|
|
<p>See CL Programming
|
||
|
|
for information about control language programming.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakisavjrnrcv.htm" title="You must save the journal receivers when they are no longer attached, so that you have all the journal entries saved.">Save journals and journal receivers</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rbam6/rbam6clmain.htm" target="_blank">CL Programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|