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

87 lines
5.4 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="The wait time (SAVACTWAIT) parameter" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu302.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu350.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="rzaiu307" />
<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>The wait time (SAVACTWAIT) parameter</title>
</head>
<body id="rzaiu307"><a name="rzaiu307"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">The wait time (SAVACTWAIT) parameter</h1>
<div><p>Specifies the amount of time to wait for an object that is in use, or for
transactions with pending changes to reach a commit boundary, before continuing
the save operation. </p>
<p>You can specify three wait time elements in the SAVACTWAIT parameter.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu302.htm" title="Use these options to specify how you will use the save-while-active function.">Parameters for the save-while-active function</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaiurzaiu350.htm">Monitor your save-while-active operation</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="conceptSunDec051611152004"><a name="conceptSunDec051611152004"><!-- --></a><h2 class="topictitle2">Object locks </h2>
<div><p>The default value is 120 seconds. You can specify the amount of time to
wait for the object to become available. You can specify any number of seconds
from 0 to 99999 for object locks, or *NOMAX to have the save-while-active
operation wait indefinitely. If you end your applications before starting
the save operation, specify 0 seconds. If you do not end your applications,
specify a value large enough for your applications to make the objects available.</p>
<p>If an object is not available during checkpoint processing, the save-while-active
operation will wait up to the specified number of seconds for the object to
become available. While waiting for an object, the save operation does nothing
else. The save operation may have to wait for several objects. The total time
that the save-while-active operation waits may be much longer than the value
specified. If an object does not become available within the specified time,
the object is not saved, but the save operation continues.</p>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="conceptSunDec051611312004"><a name="conceptSunDec051611312004"><!-- --></a><h2 class="topictitle2">Commit record changes</h2>
<div><p> The default value is *LOCKWAIT. You can specify any number of seconds
from 0 to 99999 for transactions with pending record changes. You use *NOCMTBDY
to save objects without waiting for commit boundaries. If you use *NOMAX,
the save-while-active operation will wait indefinitely. If 0 is specified,
all objects being saved must be at commit boundaries.</p>
<p>After the save-while-active operation allocates a group of objects that
it is synchronizing, it may then wait this many seconds for all jobs that
are using the same journals as these objects to reach commitment boundaries.
If these jobs do not reach commitment boundaries within the specified time,
the save operation ends. After 30 seconds, a CPI8365 message
is sent to the QSYSOPR message queue for each job for which the save-while-active
operation is waiting.</p>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="conceptSunDec051611512004"><a name="conceptSunDec051611512004"><!-- --></a><h2 class="topictitle2">Commit object changes</h2>
<div><p> The default value is *LOCKWAIT. You can specify the amount of time to
wait for transactions with Data Definition Language (DDL) object changes or
any API commitment resource that is added without the option to allow normal
save processing. If you use *NOMAX there is no maximum wait time. You can
specify any number of seconds from 0 to 99999. If 0 is specified, and only
one name is specified for the Objects (OBJ) parameter, and *FILE is the only
value specified for the Object types (OBJTYPE) parameter, the system will
save the object without requiring the types of transactions that are listed
above to reach a commit boundary. </p>
</div>
</div>
</body>
</html>