This macro deletes access conditions.
Macro | Operands |
REMSAC | MF = D / L / C / M / E ,PREFIX = P / <name 1> ,MACID = ROX / <name 3> ,MGMTPRE = P / <name 1> ,MGMTMAC = ROZ / <name 3> ,PARAM = <name 1..8> ,GUARD*= <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))>) ,SUBTYPE*= *ALL / *USER / *GROUP / *OTHER / *ALLUSER / <var: enum SUBTYPE> / (<reg: enum SUBTYPE>) ,SUBIDS = *NO / *ALL / array(20): <c-string: name 1..8> / <var: char(8)> / (<reg: A(char(8))>) ,DIALOG = *STD / *NO / *GUARD / *USERID / *CATALOG / <var: enum DIALOG> / (<reg: enum DIALOG>) ,ERRMSG =*NO / *YES |
For a description of the parameters MF, PREFIX, MACID, PARAM see the “Executive Macros” manual [16].
Operands marked with an asterisk (*) are mandatory operands for MF=L. The values specified for SUBTYPE and DIALOG refer to the DSECT of the SACMGMT macro.
MGMTPRE and MGMTMAC
specify the prefix for the global DSECTS, constants and equates. This prefix consists of the values specified for the two operands MGMTPRE and MGMTMAC, which are concatenated in this order.
If a prefix is used, it must match the prefix specified for the PREFIX operand in the SACMGMT macro; otherwise, compilation errors will occur.
GUARD
Name of the guard to be processed. This name may contain wildcards, but it must be entered in uppercase letters. Only the guard administrator may specify wildcards in the user ID. This operand is mandatory for MF=L.
SUBTYPE
specifies the subject type for which access conditions are to be deleted.
=*ALL
All access conditions are to be deleted.
=*USER
User IDs whose access conditions are to be deleted.
=*GROUP
User groups whose access conditions are to be deleted.
=*OTHER
Access conditions for all other users are to be deleted.
=*ALLUSER
Access conditions for *ALLUSER are to be deleted.
SUBIDS
specifies, for SUBTYPE =*GROUP or SUBTYPE=*USER, which individual entries are to be deleted. Since only one entry exists for SUBTYPE=*ALLUSER and for SUBTYPE=*OTHER, no SUBIDs can be specified for these two SUBTYPES.
=*NO
No access conditions are to be deleted.
=*ALL
All access conditions for the specified SUBTYPE are to be deleted.
=array(20)
As for the definition of the access conditions, up to 20 individual definitions which are to be deleted can be specified here.
DIALOG
In interactive (dialog) mode, the user may use the function in a guided dialog. In batch mode, DIALOG=*NO is always assumed, even if other values are specified.
=*STD
In interactive mode: *GUARD (see below)
In batch mode: *NO
=*NO
The function is executed without further questions for each guard which matches the selection criteria.
=*GUARD
For each guard which matches the selection criteria, the user can decide in a dialog what is to be done:
NO: | Do not execute the function |
YES: | Execute the function |
TERMINATE: | Terminate the function, even if there are further guards which match the selection criteria. |
=*USERID
This guided dialog can only be used by system administrators.
If the user ID contains wildcards, a dialog is started each time the user ID changes to permit the user to decide whether the user ID corresponding to the selection is to be processed. The dialog can be controlled in the same way as for *GUARD.
=*CATALOG
If the catalog ID contains wildcards, a dialog is started each time the catalog ID changes to permit the user to decide whether the guards under this catalog ID are to be processed by the function. The dialog can be controlled in the same way as for *GUARD.
ERRMSG
specifies whether error messages are to be displayed on the terminal.
=*NO
Error messages are not to be displayed.
=*YES
Error messages are to be displayed.
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 or not accessible | |
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’1015’ | The specified subject does not exist in the guard | |
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’1028’ | Invalid guard type | |
X’40’ | X’1029’ | GUARDS is not available on the remote system | |
X’02’ | X’40’ | X’1035’ | The command was not executed |
X’80’ | X’1036’ | The guards catalog is locked | |
X’80’ | X’1038’ | The guards catalog is locked by ARCHIVE |