ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaiu_5.4.0.1/rzaiurzaiu360.htm

101 lines
5.3 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="Example: Eliminate save-outage time for libraries" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu348.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="rzaiu360" />
<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>Example: Eliminate save-outage time for libraries</title>
</head>
<body id="rzaiu360"><a name="rzaiu360"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Example: Eliminate save-outage time for libraries</h1>
<div><div class="section"> <p>This example shows a typical use of the save-while-active function
to eliminate a save-outage time. Your exact use of the function may differ,
based on your specific application requirements.</p>
<p>This example uses
two libraries, LIB1, and LIB2. Both libraries contain only journaled objects
and the journals for those objects. The changes made to the journaled objects
may or may not be made under commitment control.</p>
<p>This example demonstrates
a save-while-active operation that does not end the applications that are
making changes to the objects in these libraries. Not ending the applications
introduces additional restore considerations for the recovery operation after
you restore the objects from the save-while-active media.</p>
<p>Eliminate
the save-outage time with the following steps: </p>
</div>
<ol><li class="stepexpand"><span></span> Submit the following command as an individual batch
job:
<pre>SAVLIB LIB(LIB1 LIB2) DEV(TAP01) SAVACT(*SYNCLIB) +
SAVACTWAIT(600) +
SAVACTMSGQ(QSYSOPR) +
ACCPTH(*YES)
</pre>
<div class="note"><span class="notetitle">Note:</span> You can also use the SAVOBJ or SAVCHGOBJ commands, depending on your
specific needs.</div>
<p>The server waits 10 minutes, as specified by the SAVACTWAIT parameter,
to resolve each lock conflict and for any active commitment definitions to
reach a commitment boundary during checkpoint processing.</p>
<p>By specifying ACCPTH(*YES), you are also saving access paths for the logical
files. Access paths, in most cases, will not be built after restoring the
files from this save media.</p>
<p>The recovery procedures needed when restoring objects from this media are
dependent upon each of the database members in LIB1 and LIB2 being updated
with the timestamp of this save operation.</p>
</li>
<li class="stepexpand"><span>When checkpoint processing is complete, QSYSOPR receives message
CPI3712 as specified by the SAVACTMSGQ parameter. Until the QSYSOPR message
queue receives the CPI3712 message, <a href="rzaiurzaiu350.htm#rzaiu350">monitor
lock conflicts</a> that the save-while-active job may encounter.</span></li>
<li class="stepexpand"><span>Wait for the save-while-active job to complete.</span></li>
<li class="stepexpand"><span>After the batch job has completed, verify that all of the required
objects were saved. If lock conflicts prevented some of the objects from being
saved, you should issue the original save command again after resolving any
and all lock conflicts.</span></li>
<li class="stepexpand"><span></span> Save the receiver containing the earliest start of
save entry from each journal being used to journal the objects in libraries
LIB1 and LIB2. You can get the earliest receiver from the OUTFILE on the save
command. If the attached journal receivers do not reside in library LIB1 or
LIB2, then you must issue separate save requests to save each of the attached
receivers.
<div class="p">Save all of the attached receivers with the following command. Multiple
save commands may be necessary for this step.It is not necessary to use the
save-while-active function when saving journal receivers. The following command
defaults to SAVACT(*NO).
<pre>SAVOBJ OBJ(attached-receiver) +
LIB(attached-receiver-library) +
OBJTYPE(*JRNRCV) +
DEV(TAP01)</pre>
</div>
</li>
</ol>
<div class="section"></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu348.htm" title="Use the save-while-active function to eliminate your save-outage time.">Eliminate your save-outage time</a></div>
</div>
</div>
</body>
</html>