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

92 lines
5.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="Timestamp processing with save-while-active" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu310.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu358.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.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="rzaiu328" />
<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>Timestamp processing with save-while-active</title>
</head>
<body id="rzaiu328"><a name="rzaiu328"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Timestamp processing with save-while-active</h1>
<div><p>The save-active-time for an object can be useful when you determine which
recovery procedures to use after you restore objects from the media. All of
the changes made to the object before the save active timestamp will be present
for the object on the save-while-active media. The changes made to the object
after the save active timestamp will not be present for the object on the
save-while-active media.</p>
<p>If you specify UPDHST(*YES) on the save command, the server records the
date and time that it performs a save operation for an object. The server
takes the timestamp early during the save preprocessing phase. The timestamp
identifies when the save operation started for the object. This timestamp
is the <span class="uicontrol">save-time</span> for the object. Multiple objects that
you save with one save request will have the same save time if they all reside
in the same library. This timestamp displays in the <span class="uicontrol">save date/time</span> field
when you use the Display Object Description (DSPOBJD) command displays.</p>
<p>The save-while-active function introduces an additional timestamp that
relates to save processing. This additional timestamp is the save-active-time
for an object. The <span class="uicontrol">save-active-time</span> identifies the
time an object that you saved with the save-while-active function object reached
the checkpoint. The save-active-time is the same for all of the objects that
reach a checkpoint together.</p>
<p>When you use the Display Object Description (DSPOBJD) command, the save-active-time
displays in the <span class="uicontrol">save active date/time</span> field. The server
only updates the save-active-time for an object if you specify UPDHST(*YES)
on the save command when you request the save-while-active operation.</p>
<p>Some objects do not require special save-while-active checkpoint processing.
Therefore the save-while-active timestamp is the same time that the object's
description is saved. Examples of this are object types *JOBQ and *OUTQ that
have only their descriptions saved, not their contents. This is also true
for files that do not have any members.</p>
<p>For physical file members, the <span class="uicontrol">last save date/time</span> information
that the DSPFD command identifies is either the last save-time or the last
save-active-time. The information that displays depends on which type of save
operation you last performed for each of the members.</p>
<p>The recovery considerations do not apply if you are using the save-while-active
function to reduce your save-outage time.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu310.htm">Save-while-active function</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaiurzaiu358.htm">Recommended recovery procedures after eliminating save-outage time</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="recoveryprocedureconsiderations"><a name="recoveryprocedureconsiderations"><!-- --></a><h2 class="topictitle2">Recovery procedure considerations</h2>
<div><p>This consideration applies to journaled objects that are saved with the
save-while-active function. The start of save journal entry in
journal contains both the save-time and save-active-time. The object saved
journal entry in the journal also contains both the save-time and save-active-time.
Look for the journal entry that identifies when the journaled file member
reached the checkpoint. All journal entries after this journal entry for a
journaled object will not be reflected in the data that is saved during a
save-while-active operation. This information may be useful when you determine
what recovery procedures are necessary after restoring journaled objects from
the save-while-active media.</p>
</div>
</div>
</body>
</html>