CHANGE-GUARD-FILE Change guards catalog

Domain:	SECURITY-ADMINISTRATION
Privileges:	GUARD-ADMINISTRATION

This command can be used to change the guards catalog while the system is running.

This command is only permitted for users with the GUARD-ADMINISTRATION privilege; it cannot be used under MSCF or RFA.

If an error occurs when a change is made, a recovery measure is initiated automatically in an attempt to restore the original state. The start, end and result of the catalog change and any recovery measure initiated are logged on the console.

Since the current guards catalog is constantly open during operation, a guards catalog saved with ARCHIVE can only be loaded as a backup catalog. The CHANGE-GUARD-FILE command must be used in order to replace the open, current guards catalog with the backup catalog.

CHANGE-GUARD-FILE      

PUBSET = <cat- id 1..4>

PUBSET = <cat-id 1..4>
Pubset on which the guards catalog is to be changed or loaded.

The following naming conventions must be observed:

• SYSCAT.GUARDS

  Current guards catalog

  Meaning:

  Before command is executed:	The guards catalog to be replaced
  After command is executed:	The guards catalog that has been replaced

• SYSCAT.GUARDS.BAK

  Guards catalog to replace the current guards catalog

  Meaning:

  
  

  Before command is executed:	The backup guards catalog
  After command is executed:	The current guards catalog

• SYSCAT.GUARDS.date.time

  Former guards catalog after replacement

The guards catalog is not changed unless the following conditions are met:

• The command must be executed under the user ID of a guards administrator.

• A file called SYSCAT.GUARDS must exist, it must be open, and it must be a valid guards catalog. In other words, it must have been created by the guards administrator.

• A file called SYSCAT.GUARDS.BAK must exist, it must be closed, and it must be a valid guards catalog. In other words, it must have been created by the guards administrator (for example, by renaming at recovery a guards catalog backed up with ARCHIVE).

• 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 needs repairing on account of a system error after the command is executed, an attempt must be made to correct the error with the REPAIR-GUARD-FILE command.

An empty guards catalog can be replaced with a guards catalog backed up with ARCHIVE.

CAUTION!
A guards catalog cannot be copied with the COPY-FILE command because this would destroy the identifier identifying the object as a guards catalog. This identifier is set by GUARDS when setting up an empty catalog. When the catalog is recatalogued using the MODIFY-FILE-ATTRIBUTES command, the identifier is retained.

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
	32	PRO1008	The current or replacement guards catalog does not exist
	64	PRO1012	The specified catalog is not defined or not accessible
	64	PRO1013	The pubset is not known to the GUARDS administration (the guards catalog was probably not opened at IMPORT-PUBSET)
	64	PRO1014	The user is not authorized to execute this function
	64	PRO1020	No more memory space available
	64	PRO1040	The current or replacement guards catalog is not a guards catalog
	64	PRO1041	The current or replacement guards catalog has the wrong version
	64	PRO1047	It is not possible to replace a guards catalog on another system
	64	PRO1048	The current or replacement guards catalog is not on the control volume set of the SM pubset
	64	PRO1049	The replacement guards catalog is open
	64	PRO1050	The current guards catalog is closed and is therefore not accepted for the replacement
	64	PRO1051	The current or replacement guards catalog does not contain a header record and is therefore not recognized as a guards catalog
	64	PRO1052	DVS error when checking the current or replacement guards catalog
	64	PRO1053	DVS error when checking the version of the replacement guards catalog
	64	PRO1054	DVS error when closing and reopening the guards catalog
	64	PRO1055	DVS error when renaming the guards catalog
	128	PRO1037	The guards catalog has already been changed
	128	PRO1038	The current guards catalog is locked by ARCHIVE
	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