This macro is used to delete guards. Nonprivileged users may delete only guards under their own user IDS. The guard administrator may delete guards under any user IDE.
Macro | Operands |
DELGUAD | MF = D / L / C / M / E ,PREFIX = P / <name 1> ,MACID = ROM / <name 3> ,PARAM = <name 1..8> ,NAME = <c-string: filename 1..40 without-gen-vers with-wild> / <c-string: partial-filename 2..40 with-wild> / <var: char(40)> / (<reg: A(char(40))>) ,DIALOG = *STD / *NO / *GUARD / *USERID / *CATALOG / <var: enum DIALOG> / (<reg: enum DIALOG>) |
For a description of the parameters MF, PREFIX, MACID, PARAM see the “Executive Macros” manual [16].
NAME
Name of the guard to be deleted. This name may contain wildcards, but it must be entered in uppercase letters.
DIALOG
specifies the dialog guidance:
=*STD
The following defaults apply:
in batch mode: | *NO |
in dialog mode: | *GUARD if NAME contains wildcards |
*NO if NAME does not contain wildcards |
=*NO
The function is executed without further questions for the guards matching the NAME specification.
=*GUARD
For each guard, the caller may select *NO / *YES to specify whether the function is to be executed. The response TERMINATE terminates execution of the command even if all matching guards have not yet been handled.
=*USERID
This may be specified only by guard administrators.
If the user ID contains wildcards, the system asks, each time the user ID changes, whether the function is to be executed for the named user ID. The permissible responses are the same as for *GUARD.
=*CATALOG
If the catalog ID contains wildcards, the system asks, each time the catalog ID changes, whether the function is to be executed for this catalog. The permissible responses are the same as for *GUARD.
Macro return codes
SC2 | SC1 | Maincode | Meaning |
X’01’ | X’1000’ | The specified operand value lies outside the permitted range. The invalid operand is stored as a symbolic value in SC2 | |
X’20’ | X’1001’ | An internal error has occurred. A SERSLOG entry has been written for further analysis | |
X’40’ | X’1002’ | Syntax error in the guard name | |
X’40’ | X’1003’ | Memory for the parameter area not allocated with the required length | |
X’40’ | X’1007’ | The specified guard does not exist | |
X’80’ | X’1009’ | The specified guard is locked by another task | |
X’02’ | CMD | X’1011’ | Command was terminated at user’s request |
X’40’ | X’1012’ | The specified catalog is not defined or not accessible | |
X’40’ | X’1013’ | The pubset is not known to the GUARDS administration (the guards catalog was probably not opened at IMPORT-PUBSET) | |
X’40’ | X’1014’ | The user is not authorized to execute this function | |
X’40’ | X’1016’ | Error in the MRS communication facility | |
X’40’ | X’1017’ | Unknown user ID | |
X’40’ | X’1018’ | The remote system is not available | |
X’40’ | X’1020’ | No more memory space available | |
X’40’ | X’1021’ | BCAM connection error | |
X’40’ | X’1022’ | The BCAM connection has been interrupted | |
X’40’ | X’1023’ | There is no guard matching the selection criteria | |
X’40’ | X’1029’ | GUARDS is not available on the remote system | |
X’80’ | X’1036’ | The guards catalog is locked |