Determine objects that the server saved (save messages)

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.

Note: 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.

If a single command saves multiple libraries, a final completion message (CPC3720 or CPC3721) also contains the last device that the server used.

Information in Output Files

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.

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.

You can use the OUTPUT parameter with these commands:

SAV	SAVDLO	SAVSAVFDTA	SAVSYSINF
SAVCFG	SAVLIB	SAVSECDTA
SAVCHGOBJ	SAVOBJ	SAVSYS

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.

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.

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.

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.

The on-line information for the save commands tells the names of the model database output files they use for output.

Note: 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.

These are some messages that you may see during the verification process:

Message CPF3797: Objects from library <your library name> not saved. Save limit exceeded.

Message CPC3701: Sent for each library that is saved to media.

Message CPC3718 : Completion message for SAVSYSINF command

Message CPC3722: Sent for each library that is saved to a save file.

Message CPC9410: Completion message for SAVDLO command to media.

Message CPC9063: Completion message for SAVDLO command to save file.

Message CPC370C: Completion message for SAV command to media.

Message CPC370D: Completion message for SAV command to save file.