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

143 lines
8.3 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="Save-while-active restrictions" />
<meta name="DC.Relation" scheme="URI" content="rzaiuswaconsid.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu310.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu334.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu343.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu319.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="rzaiu314" />
<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>Save-while-active restrictions</title>
</head>
<body id="rzaiu314"><a name="rzaiu314"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Save-while-active restrictions</h1>
<div><p>The following restrictions apply to all of the commands which provide the
save-while-active function. </p>
<ul><li>The save-while-active function is only available on the commands listed
in Save-while-active function.</li>
<li>You cannot use the save-while-active function in the following situations:
<ul><li>When all subsystems have ended. If you have ended all subsystems, the
save operation is the only user job that is active. It must finish before
you can restart your subsystems and applications. The following save operations
require that you end all subsystems. Therefore, you cannot use the save-while-active
function with these operations: <ul><li>Saving the system library</li>
<li>Saving all libraries</li>
<li>Saving the entire system</li>
</ul>
</li>
<li>When freeing or deleting storage during a save operation. If specifying
STG(*FREE) or STG(*DELETE) on a save command, or CHKFORMRK(*YES) on the SAVDLO
command, you cannot use the save-while-active function.</li>
</ul>
</li>
<li>You should not use the save-while-active function when the server is very
busy or when there is very little disk storage available. Before you save
large amounts of data (such as all user libraries), you should initially use
the save-while-active function on a limited amount of data. Using the save-while-active
feature on a limited amount of data will help you determine its impact on
your server's performance and storage.</li>
<li>You should not load, apply, or remove program temporary fixes (PTF)s when
running a save-while-active operation.</li>
<li>You must issue separate save commands to use the save-while-active function
for objects in libraries, document library objects, and objects in directories.
If you need to synchronize objects you are saving with different commands,
first end your applications until all of the objects have reached a checkpoint.
<ul><li>If you have only one media device, each command must finish before the
next can start. If you use the save-while-active function to reduce your save-outage
time, save folders and directories first. Save libraries last. Saving the
objects in this order will probably provide the greatest reduction in the
save-outage time.</li>
<li>If you have multiple media devices, and you use the save-while-active
function to reduce your save-outage time, save libraries, folders, and directories
concurrently. This will probably provide the greatest reduction in you save-outage
time.</li>
</ul>
</li>
<li>You cannot save objects that you create after the save operation begins.</li>
<li>You cannot save objects that other jobs are using during checkpoint processing. </li>
<li>Do not use System Service Tools (SST) functions for objects you are currently
saving by a save-while-active operation.</li>
</ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiuswaconsid.htm">Considerations and restrictions for the save-while-active function</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaiurzaiu310.htm">Save-while-active function</a></div>
<div><a href="rzaiurzaiu334.htm">Performance considerations for save-while-active</a></div>
<div><a href="rzaiurzaiu343.htm">Storage considerations for save-while-active</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzaiurzaiu319.htm">Save-while-active object locking rules</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="conceptSunDec051601502004"><a name="conceptSunDec051601502004"><!-- --></a><h2 class="topictitle2">Library restrictions</h2>
<div><ul><li>Full synchronization is not available when you use save all IBM<sup>®</sup> libraries
using SAVLIB LIB(*IBM).</li>
<li>If you have specified *NOCMTBDY for the SAVACTWAIT parameter, you cannot
save any *IBM library or any library that begins with Q (except for QGPL).</li>
</ul>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="conceptSunDec051602112004"><a name="conceptSunDec051602112004"><!-- --></a><h2 class="topictitle2">Integrated file system restrictions</h2>
<div><p>Consider the following when using the save-while-active function with the
SAV or SAVRST commands with integrated file systems: </p>
<ul><li>The wait time option is not available.</li>
<li>When you are saving objects in libraries or document library objects,
the considerations stated for those objects also apply.</li>
</ul>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="conceptSunDec051602302004"><a name="conceptSunDec051602302004"><!-- --></a><h2 class="topictitle2">Document library restrictions</h2>
<div><p>Consider the following considerations when you use the save-while-active
function to save document library objects. </p>
<ul><li>Full synchronization is not available. Only system-defined synchronization
is available.</li>
<li>Checkpoint notification is not available. This means that you cannot determine
when it would be safe to restart your applications that use document library
objects. When saving document library objects, the benefit of the save-while-active
function is that objects are allocated for a shorter time than with normal
save operations.</li>
<li>You may cannot save documents during save-while-active processing if a
reclaim operation (RCLDLO command) is running.</li>
<li>Folders may not be saved during save-while-active processing if a reorganize
operation (RGZDLO command) or a reclaim operation (RCLDLO command) is running.</li>
<li>Some applications use application programming interfaces (APIs) or shared
folders to work with a document like a personal computer. When they update
document data, they save the updates to a temporary file. The application
does not permanently write changes to the document until the application session
ends. Therefore these applications can update a document while a save-while-active
operation is running. <p>Other applications update documents directly as
the application receives data. For example, some spreadsheet applications
and image applications work this way. If this type of application updates
a document while a save-while-active operation is running, the application
does not save document. The job log receives Diagnostic messages CPF8A80:<span class="uicontrol">Document
in use</span> and CPF90AC:<span class="uicontrol">Document not saved</span>
to indicate that the application did not save the object because the object
was in use.</p>
</li>
</ul>
</div>
</div>
</body>
</html>