134 lines
7.6 KiB
HTML
134 lines
7.6 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="reference" />
|
||
|
<meta name="DC.Title" content="Determine objects that the server saved (save messages)" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu253.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiusaveoutput.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiusaveoutput.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu004.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="rzaiu254" />
|
||
|
<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>Determine objects that the server saved (save messages)</title>
|
||
|
</head>
|
||
|
<body id="rzaiu254"><a name="rzaiu254"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Determine objects that the server saved (save messages)</h1>
|
||
|
<div><div class="section"><p>Save messages show the number of objects that the server saved.
|
||
|
The message help of the completion message includes the volume identifiers
|
||
|
of the first 75 volumes of save media that the server used. The server uses
|
||
|
these identifiers to update the status information of each object that the
|
||
|
server saved. The message data contains this information, the last volume
|
||
|
ID, and either the last device that the server used or the save file that
|
||
|
the server used.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> The server performs overlap processing during normal
|
||
|
save operations. The server can write some libraries to the media while the
|
||
|
server preprocesses other libraries. Occasionally the job log contains preprocessing
|
||
|
and completion messages that appear in a different order than the order in
|
||
|
which the server wrote libraries to the media.</div>
|
||
|
<p>If a single command
|
||
|
saves multiple libraries, a final completion message (CPC3720 or CPC3721)
|
||
|
also contains the last device that the server used.</p>
|
||
|
</div>
|
||
|
<div class="section"><h4 class="sectiontitle">Information in Output Files</h4><p>Most save commands create
|
||
|
output that shows what the server saved. Depending on which command you use,
|
||
|
you can direct this output to a printer (OUTPUT(*PRINT)), a database file
|
||
|
(OUTPUT(*OUTFILE)), a stream file, or a user space. The default for save commands
|
||
|
is not to create output. You must request it each time you run the save command.
|
||
|
You can change the default for the OUTPUT parameter for save commands by using
|
||
|
the Change Command Default (CHGCMDDFT) command.</p>
|
||
|
<p>You can do one of two
|
||
|
things: print the output and store it with your media, or create a program
|
||
|
to analyze and report on the information in the output file.</p>
|
||
|
<div class="p">You can
|
||
|
use the OUTPUT parameter with these commands:
|
||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="void" border="0" rules="none"><tbody><tr><td align="left" valign="top" width="15.052732502396932%">SAV</td>
|
||
|
<td align="left" valign="top" width="14.956855225311601%">SAVDLO</td>
|
||
|
<td align="left" valign="top" width="15.532118887823588%">SAVSAVFDTA</td>
|
||
|
<td valign="top" width="54.45829338446788%">SAVSYSINF</td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="15.052732502396932%">SAVCFG</td>
|
||
|
<td align="left" valign="top" width="14.956855225311601%">SAVLIB</td>
|
||
|
<td align="left" valign="top" width="15.532118887823588%">SAVSECDTA</td>
|
||
|
<td valign="top" width="54.45829338446788%"> </td>
|
||
|
</tr>
|
||
|
<tr><td align="left" valign="top" width="15.052732502396932%">SAVCHGOBJ</td>
|
||
|
<td align="left" valign="top" width="14.956855225311601%">SAVOBJ</td>
|
||
|
<td align="left" valign="top" width="15.532118887823588%">SAVSYS</td>
|
||
|
<td valign="top" width="54.45829338446788%"> </td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
</div>
|
||
|
</div>
|
||
|
<p>If you use an output file for the SAVDLO command, the server
|
||
|
uses the file format QSYS/QAOJSAVO.OJSDLO. Use the Display File Field Description
|
||
|
(DSPFFD) command to look for the file layout. </p>
|
||
|
<p>If you use an output
|
||
|
file for any of the other commands that are listed above, the server uses
|
||
|
the file format QSYS/QASAVOBJ.QSRSAV.</p>
|
||
|
<p>The SAVCHGOBJ, SAVLIB, SAVOBJ,
|
||
|
and SAV commands have an information type (INFTYPE) parameter to specify how
|
||
|
much detail you want in the output. See Interpret output from save commands
|
||
|
for more information.</p>
|
||
|
<p>The SAV command does not support sending output
|
||
|
to an output file. You can send output from the SAV command to a stream file
|
||
|
or to a user space. Interpret output from save (SAV) and restore (RST) shows
|
||
|
the layout for the stream file or user space.</p>
|
||
|
<p>The on-line information
|
||
|
for the save commands tells the names of the model database output files they
|
||
|
use for output.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> The output file that you specify is in use throughout
|
||
|
the save operation. Therefore, the server cannot save it as part of the operation.
|
||
|
Depending on how you perform your save operation, you may see a CPF379A message
|
||
|
in the joblog for the output file. If you want to save the output file after
|
||
|
your save operation has completed, use the SAVOBJ command.</div>
|
||
|
<p>These
|
||
|
are some messages that you may see during the verification process:</p>
|
||
|
<p><span class="uicontrol">Message
|
||
|
CPF3797</span>: Objects from library <your library name> not saved.
|
||
|
Save limit exceeded.</p>
|
||
|
<p><span class="uicontrol">Message CPC3701</span>: Sent for
|
||
|
each library that is saved to media.</p>
|
||
|
<p><span class="uicontrol">Message CPC3718 </span>:
|
||
|
Completion message for SAVSYSINF command</p>
|
||
|
<p><span class="uicontrol">Message CPC3722</span>:
|
||
|
Sent for each library that is saved to a save file.</p>
|
||
|
<p><span class="uicontrol">Message
|
||
|
CPC9410</span>: Completion message for SAVDLO command to media.</p>
|
||
|
<p><span class="uicontrol">Message
|
||
|
CPC9063</span>: Completion message for SAVDLO command to save file.</p>
|
||
|
<p><span class="uicontrol">Message
|
||
|
CPC370C</span>: Completion message for SAV command to media.</p>
|
||
|
<p><span class="uicontrol">Message
|
||
|
CPC370D</span>: Completion message for SAV command to save file.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu253.htm" title="Verify what the server saved explains techniques to audit your save strategy. You will learn which objects the server saved, which objects the server did not save, and when the server last saved an object.">Verify what the server saved</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="rzaiurzaiu004.htm">Interpret output from save (SAV) and restore (RST)</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="rzaiusaveoutput.htm">Interpret output from save commands</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|