Domain: | SECURITY-ADMINISTRATION |
Privileges: | GUARD-ADMINISTRATION, TSOS |
This command is used to add a pubset to the GUARDS administration again during operation when it is no longer under the control of GUARDS. This state can occur as a result of unexpected system behavior after system startup or after a pubset import.
In addition, the command can also be used to restore a guards catalog after an unsuccessful replacement attempt (see the CHANGE-GUARD-FILE command) if the error situation permits it. In addition to further system actions, the guards catalog is newly created and/or opened if its state requires it.
If the execution of the /REPAIR-GUARD-FILE command fails, carry out the following actions in the specified order to recover the error situation:
Recatalog or delete the current guards catalog $TSOS.SYSCAT.GUARDS.
You may have to force the closure of the guards catalog beforehand by means of the REPAIR-DISK-FILES command.
Export the relevant pubset.
Import the relevant pubset.
A new $TSOS.SYSCAT.GUARDS guards catalog is created because the defective catalog was deleted.Load the backup.
This is not necessary if you are certain that the defective guards catalog did not contain any guards.
Note the following, depending on the type of backup involved:
Backup with GUARDS-SAVE
The guards backed up are loaded directly into the newly created guards catalog. This concludes restoration.OR
Backup with ARCHIVE
The guards catalog backed up must be loaded under the name
$TSOS.SYSCAT.GUARDS.BAK. The replacement of the guard catalog must then be initiated by means of the /CHANGE-GUARD-FILE command.
This command can only be used by users with the TSOS or GUARD-ADMINISTRATION privilege. It is not MSCF- or RFA-capable.
This command cannot be used during an ARCHIVE backup or catalog replacement (CHANGE-GUARD-FILE).
Reason: During the backup or catalog replacement, a catalog lock is applied in order to prevent it being accessed by other tasks during this period. However, the /REPAIR-GUARD-FILE command cancels the catalog lock. This can lead to major conflicts during a backup run.
After a catalog replacement is terminated abnormally, however, it must be executed in order to cancel the locks.
REPAIR-GUARD-FILE |
PUBSET = <cat- id 1..4> |
PUBSET = <cat-id 1..4>
Specifies the pubset on which the guards catalog is to be restored.
The following naming conventions must be observed:
SYSCAT.GUARDS
Default name of the guards catalog to be changed to a valid state.
The restoration of the guards catalog involves the following measures:
The pubset is put under the control of GUARDS again. Message PRO1013 should then no longer appear when the guards catalog is accessed.
If necessary, a new GUARDS server task (PRnn) is created that serves the pubset.
Any catalog locks set for an ARCHIVE run or catalog change are canceled.
If the guards catalog is closed, it is opened.
If there is no guards catalog, one is created.
If the existing backup catalog is cataloged with BLKSIZE=(STD,2) it is renamed to SYSCAT.GUARDS.BAK.date.time. Then it is copied into a file with BLKSIZE=(STD,4) and the name SYSCAT.GUARDS.BAK. This file thus becomes the current backup catalog.
If the guards catalog on the pubset is cataloged with BLKSIZE=(STD,2) it is renamed to SYSCAT.GUARDS.date.time. Then it is copied into a new guards catalog with BLKSIZE=(STD,4) and the name SYSCAT.GUARDS. This guards catalog thus becomes the current guards catalog.
The command is rejected if the SYSCAT.GUARDS file is not a GUARDS catalog or if the version of the GUARDS catalog does not match the SECOS version used.
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command successfully executed | |
32 | PRO1001 | An internal error has occurred. A SERSLOG entry has been written for further analysis | |
64 | PRO1012 | The specified catalog is not defined or not accessible | |
64 | PRO1014 | The user is not authorized to execute the function | |
64 | PRO1020 | No more memory space available | |
64 | PRO1040 | The guards catalog is not a guards catalog | |
64 | PRO1041 | The version of the guards catalog is incorrect | |
64 | PRO1047 | It is not possible to restore a guards catalog on another system | |
64 | PRO1048 | The guards catalog is not on the control volume set of the SM pubset | |
64 | PRO1051 | The guards catalog does not contain a header record and is therefore not recognized as a guards catalog | |
64 | PRO1052 | DVS error when checking the guards catalog | |
64 | PRO1053 | DVS error when checking the version of the guards catalog | |
64 | PRO1054 | DVS error when closing and reopening the guards catalog | |
64 | PRO1056 | DVS error when creating the guards catalog | |
128 | PRO1045 | A master change is currently taking place | |
128 | PRO1046 | The pubset is under the control of SMPGEN because of the generation of an SM pubset |