The processes and results of each GUARDS-SAVE run are output to SYSOUT/SYSLST. The log structures are as follows:
Headers
General conditions
List of processed guards
List of cross references
This part of the log file is omitted if the search for references is disabled
(entrySELECT=*BY-ATTRIBUTES(RESOLVE=*NO)).Footers
Headers
The headers mark the start of the log and carry information about the GUARDS-SAVE function that created the log, the users that requested the function and the time of the request.
Example
%****************************************************************************** %GUARDS-SAVE BACKUP-GUARDS Started by User MARY 2017-12-07/14:11:58 % ------------------------- & *** Begin of Output *** %******************************************************************************
List of general conditions
This part of the log has the following contents, depending on the selected GUARDS-SAVE function:
Backup run (//BACKUP-GUARDS)
The basic data of the backup is logged, allowing the backup result to be reconstructed at a later time.
Basic data is as follows:name of the backup file
time of the backup
entries with which the user selected the guards to be saved (pubset, guard name, guard type and reference search)
Example
%****************************************************************************** %Backup File : :XXXX:$MARY.BACKUP-FILE %Backup Date : 2017-12-07/14:11:58 %Backup Pubset : XXXX % %Backup Guard : :XXXX:$MARY.* %Backup Type : COOWNERP, DEFAULTP, DEFPATTR, DEFPUID , STDAC , UNDEF %Backup Resolve : *YES %****************************************************************************** %Saved Guards : 6 %Faulty Guards : 1 %******************************************************************************
Restore run
(//RESTORE-GUARDS)
The basic data of the backup run with which the backup file was created is logged in the first part. This information is determined from the backup file. It corresponds mainly to a log of the backup run.
The second part contains entries with which the user selected the guards to be restored and the type of restoration.
The third parts logs the entries made for renaming carried out during restoration.
Example
%****************************************************************************** %Backup File : :XXXX:$MARY.BACKUP-FILE %Backup Date : 2017-12-07/14:11:58 %Backup Pubset : XXXX %Backup Guards : 6 % %Restore Guard : :XXXX:$MARY.* %Restore Type : COOWNERP, DEFAULTP, DEFPATTR, DEFPUID , STDAC , UNDEF %Restore Resolve : *YES %Restore Replace : *YES %Restore Target : *SYSTEM % %New Pubset-Id : *SAME %New User-Id : *SAME %New Name : *SAME %New Prog Pvs-Id : *SAME %****************************************************************************** %Restored Guards : 6 %Faulty Guards : 1 %******************************************************************************
Display run
(//SHOW-BACKUP-FILE)
The basic data of the backup run with which the backup file was created is logged in the first part. This information is determined from the backup file. It corresponds mainly to a log of the backup run.
The second part contains entries with which the user selected the guards to be displayed.
Example
%****************************************************************************** %Backup File : :XXXX:$MARY.BACKUP-FILE %Backup Date : 2017-12-07/14:11:58 %Backup Pubset : XXXX %Backup Guards : 6 % %Show Guard : :XXXX:$MARY.* %Show Type : COOWNERP, DEFAULTP, DEFPATTR, DEFPUID , STDAC , UNDEF %Show Resolve : *YES %****************************************************************************** %Selected Guards : 6 %Faulty Guards : 1 %******************************************************************************
List of processed guards
For each selected guard, a log is kept as to whether and in which form it was processed, or why it could not be processed.
The names of the guards that were processed without errors are listed first in alphabetical order.
Any guards that were not processed or were faulty are listed subsequently after a dashed line in alphabetical order.
The entries have the following structure:
Guard name
In each GUARDS-SAVE log, the processed guards are always listed with the name and path that was entered in the backup file at the time of backup.
This also applies for restoration runs in which renaming operations were carried out! Information on renaming operations that were carried out can only be found in the documented general conditions (see "List of general conditions").
Guard type
Cause of error
If an error occurs while a guard is being processed, a corresponding error code is logged in the form of a message number with prefix. The user can view the relevant error text with the /HELP command.
Status
The status of a guard is displayed as follows, depending on the selected GUARDS-SAVE function:
Backup (//BACKUP-GUARDS):
Status:
Explanation:
saved
The guard was saved.
only selected
The guard was selected but not saved.
only referenced
The guard was referenced but not saved.
undefined?????
If either of these two status messages appear, you should contact the system administrator because the status could not be set according to specifications by GUARDS-SAVE.
Restore (//RESTORE-GUARDS)
Status:
Explanation:
restored
The guard was restored under program control.
restored and path changed
The guard was restored with changed path name under program control.
generated
The commands for restoring the guard were generated.
generated and path changed
The commands for restoring the guard were generated.with changed path name
only selected
The guard was selected but not restored.
only referenced
The guard was referenced but not restored.
not deleted
The guard could not be deleted and was therefore also not restored.
(with: REPLACE-GUARD=*YES).deleted and not restored
The guard was deleted prior to restoration but was subsequently not restored.
(with: REPLACE-GUARD=*YES).not restored or overwritten
The guard to be restored already exists and may therefore not be restored.
(with: REPLACE-GUARD=*NO).
The guard cannot be restored for other reasons.incompletely restored
The guard was not fully restored.
undefined?????
If either of these two status messages appear, you should contact the system administrator because the status could not be set according to specifications by GUARDS-SAVE.
Display (//SHOW-BACKUP-FILE)
Status:
Explanation:
only selected
The guard was selected but the attributes were not displayed.
only referenced
The guard was referenced but the attributes were not displayed.
undefined?????
If either of these two status messages appear, you should contact the system administrator because the status could not be set according to specifications by GUARDS-SAVE.
Example
% % Alphabetical List of Saved and Faulty Guards % %============================================================================== %Guard Name Guard Type Error Status %---------- ---------- ----- ------ %:XXXX:$MARY.COOWNERP COOWNERP saved %:XXXX:$MARY.DEFAULTP DEFAULTP saved %:XXXX:$MARY.DEFPATTR DEFPATTR saved %:XXXX:$MARY.DEFPUID DEFPUID saved %:XXXX:$MARY.STDAC STDAC saved %:XXXX:$MARY.UNDEF UNDEF saved %-----------------------------------------------------------------------------%:XXXX:$LUZIFER.DEFPATTR -undefined- PRO1007 only referenced %==============================================================================
List of cross references
A log is kept on how the guards reference each other.
This part of the log is omitted if the search for references is disabled (entry SELECT=*BY-ATTRIBUTES(RESOLVE=*NO)).
In the first section, each guard that references other guards is listed in alphabetical order together with the names of these reference guards.
In the second section, each reference guard listed in alphabetical order together with the names of the guards that reference them.
An appropriate message is output if no references occur, for example because only guards of type STDAC are processed.
Example
%
% Alphabetical List of Cross References
%
%==============================================================================
%:XXXX:$MARY.COOWNERP COOWNERP -> :XXXX:$MARY.STDAC STDAC
%:XXXX:$MARY.DEFAULT DEFAULTP -> :XXXX:$LUZIFER.DEFPATTR -undefined%
-> :XXXX:$MARY.DEFPUID DEFPUID
%:XXXX:$MARY.DEFPATTR DEFPATTR -> :XXXX:$MARY.STDAC STDAC
%-----------------------------------------------------------------------------%:XXXX:$LUZIFER.DEFPATTR
-undefined- <- :XXXX:$MARY.DEFAULTP DEFAULTP
%:XXXX:$MARY.DEFPUID DEFPUID <- :XXXX:$MARY.DEFAULTP DEFAULTP
%:XXXX:$MARY.STDAC STDAC <- :XXXX:$MARY.COOWNERP COOWNERP
% <- :XXXX:$MARY.DEFPATTR DEFPATTR
%==============================================================================
The list appears as follows if no references occur:
% % Alphabetical List of Cross References % %============================================================================== %All guards without references %==============================================================================
Footers
The footers mark the end of the log and provide information on the GUARDS-SAVE function that created the log as well as which users requested which function and when.
Example
%****************************************************************************** %GUARDS-SAVE BACKUP-GUARDS Started by User MARY 2017-12-07/14:11:58 % ------------------------- & *** End of Output *** %******************************************************************************