Domain: | SECURITY-ADMINISTRATION |
Privileges: | STD-PROCESSING, GUARD-ADMINISTRATION |
This command is used to delete guards.
DELETE-GUARD |
GUARD-NAME = <filename 1..24 without-gen-vers with-wild(40)> ,DIALOG-CONTROL = *STD / *NO / *GUARD-CHANGE / *USER-ID-CHANGE / *CATALOG-CHANGE |
GUARD-NAME =<filename 1..24 without-gen-vers-with-wild(40)>
Specifies the guards to be deleted. The name may contain wildcards. Only guard administrators may specify wildcards in the user ID.
The specification of the system default ID in the guard name, e.g. $<filename> or $.<filename>, is not supported.
DIALOG-CONTROL =
The user can use the command in a guided dialog and can define the type of dialog that is to be performed. Dialog control has no effect in batch mode and thus corresponds to the setting DIALOG-CONTROL=*NO.
DIALOG-CONTROL = *STD
For each selected guard, the user can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the name of the guard is specified using wildcards
It is possible to abort the command.
DIALOG-CONTROL = *NO
The command is executed for every selected guard without any query being issued.
DIALOG-CONTROL = *GUARD-CHANGE
For each selected guard, the user can decide in interactive mode whether or not the command should be executed. Dialog control is performed regardless of whether or not the name of the guard is specified using wildcards.
It is possible to abort the command.
DIALOG-CONTROL = *USER-ID-CHANGE
This guided dialog can only be used by guard administrators.
For each selected user ID, the system administrator can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the user ID in the name of the guard is specified using wildcards.
It is possible to abort the command.
DIALOG-CONTROL = *CATALOG-CHANGE
For each selected catalog ID, the user can decide in interactive mode whether or not the command should be executed. However, dialog control is only performed if the catalog ID in the name of the guard is specified using wildcards.
It is possible to abort the command.
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command successfully executed | |
2 | 0 | PRO1011 | The command was aborted at the user’s request |
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 | 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 | PRO1014 | The user is not authorized to execute this function | |
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 | PRO1023 | There is no guard matching the selection criteria | |
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
Two guards are to be deleted from a list of four guards, using the dialog option DIALOG-CONTROL=*GUARD-CHANGE:
|