Domain: | SECURITY-ADMINISTRATION |
Privileges: | STD-PROCESSING, GUARD-ADMINISTRATION |
This command is used to modify the attributes of existing guards. If a name is specified in the NEW-NAME operand, the guard is renamed. Owners may only modify their own guards, while users with the privilege TSOS may modify any guard.
This command may be used under RFA if the source guard and destination guard are locally accessible on the same computer.
If the operand value *UNCHANGED is specified, the attributes which existed before the command was called remain unchanged.
MODIFY-GUARD-ATTRIBUTES |
GUARD-NAME = <filename 1..24 without-gen-vers> ,NEW-NAME = *SAME / <filename 1..24 without-gen-vers> ,SCOPE = *UNCHANGED / *USER-ID / *USER-GROUP / *HOST-SYSTEM ,USER-INFORMATION = *UNCHANGED / <c-string 1..80 with-low> |
GUARD-NAME = <filename 1..24 without-gen-vers>
Name of the guard to be modified. The actual name, without the catalog ID and user ID, is 8 characters long.
The specification of the system default ID in the guard name, e.g. $<filename> or $.<filename>, is not supported.
NEW-NAME = *SAME / <filename 1..24 without-gen-vers>
New name for the guard. The actual name, without the catalog ID and user ID, is 8 characters long. Specifying *SAME leaves the name unchanged.
Only a guard administrator may specify a different user ID when renaming a guard.
SCOPE =
Specifies who may use this guard to protect his/her objects. The administration rights (for deleting, changing or modifying a guard) remain the property of the guard’s owner.
The guard administrator is authorized to protect his or her own files with guards owned by someone else without the scope of these guards having to be set to *HOST-SYSTEM and without the need for group membership when SCOPE=*USER-GROUP is specified.
SCOPE = *USER-ID
Only the owner may use this guard, or the object owner with the privilege TSOS.
SCOPE = *USER-GROUP
All members of the owner’s user group may use this guard.
SCOPE = *HOST-SYSTEM
Any user may use this guard.
USER-INFORMATION = <c-string 1..80 with-low>
This permits input of any desired comment text for the guard.
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 | PRO1002 | Syntax error in the name of the guard | |
64 | PRO1006 | The specified guard already exists | |
64 | PRO1007 | The specified guard 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 | PRO1016 | Error in the MRS communication facility | |
64 | PRO1017 | Unknown user ID | |
64 | PRO1018 | The remote system is not available | |
64 | PRO1020 | No more memory space available | |
64 | PRO1021 | BCAM connection error | |
64 | PRO1022 | The BCAM connection has been interrupted | |
64 | PRO1025 | Remote copy is not possible | |
64 | PRO1029 | GUARDS is not available on the remote system | |
128 | PRO1009 | The specified guard is locked by another task | |
128 | PRO1036 | The guards catalog is locked |
Example
The existing guard GUARDEXA is to be modified such that it may be used by any user:
/modify-guard-attributes guard-name=guardexa,scope=*host-system
To check this, the attributes are then displayed:
|