This function allows a user with the user ID TSOS or a guard administrator to enter user and group IDs in a user ID guard. These IDs qualify the object names more precisely throughout the pubset when default protection rules are defined.
If the user ID guard does not yet exist, it is implicitly created and assigned the guard type DEFPUID. The SCOPE in the guard’s administrative part is set to *USER-ID. If the user ID guard already exists, the SCOPE remains unchanged.
Any number of user and group IDs can be entered. If the condition area is full, no further entries are possible.
Macro | Operanden |
ADDUID | MF = C / D / L / M / E ,PREFIX = D / <name 1> ,MACID = EFB / <name 3> ,PARAM = <name 1..8> ,DIALOG = *STD / *NO / *UIDGUA / *USERID / *CATALOG / <var: enum-of _dialog_s:1> ,ERRMSG = *NO / *YES / <var: bit:1> ,UIDGUA = ’ ’ / <c-string 1..40: filename 1..24 without-gen-vers with-wild(40)> / <var: char:40> ,IDTYPES = array(20): *UID / *GRP / <var: enum-of _type_s:1> ,IDS = array(20): ’ ’ / <c-string 1..20: name 1..8 with-wild(20)> / *UNIVERS / <var: char:20> |
For a description of the parameters MF, PREFIX, MACID, PARAM see the “Executive Macros” manual [ 16 ].
DIALOG
Dialog control
The user can use the interface 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.
=*NO
The command is executed for every selected user ID guard without any query being issued.
=*UIDGUA
For each selected user ID guard, the user can decide in interactive mode whether or not the function should be executed. Dialog control is performed regardless of whether or not the name of the user ID guard is specified using wildcards.
It is possible to abort the function.
=*USERID
For each selected user ID, the user can decide in interactive mode whether or not the function should be executed. However, dialog control is only performed if the user ID in the name of the user ID guard is specified using wildcards.
It is possible to abort the function.
=*CATALOG
For each selected catalog ID, the user can decide in interactive mode whether or not the function should be executed. However, dialog control is only performed if the catalog ID in the name of the user ID guard is specified using wildcards.
It is possible to abort the function.
=*STD
For each selected user ID guard, the user can decide in interactive mode whether or not the function should be executed. However, dialog control is only performed if the name of the user ID guard is specified using wildcards.
It is possible to abort the command.
ERRMSG
Message output
The user can specify whether any errors which occur should be reported in a message. This might be required, for example, if the specified user ID is already entered and the function cannot therefore be applied to the guard.
=*NO
No messages are output.
=*YES
Messages are output.
UIDGUA
Name of the user ID guard
This operand designates the name of a guard of type DEFPUID in which the IDs are to be entered.
If wildcards are used in the name of the user ID guard, then the user IDs and group IDs are entered in multiple guards.
Only guard administrators are able to specify wildcards in the user ID.
A value must be specified for this operand. Only uppercase characters may be used!
IDTYPES
Type list
This operand can be used to specify arrays defining the types of IDs which can be specified using the IDS operand.
*UID
The ID is a user ID.
*GRP
The ID is a group ID.
IDS
List of IDs
This operand can be used to specify an array of IDs (without $) whose type has to be defined by means of the TYPE operand. The IDs may contain wildcards.
Only uppercase characters may be used!
*UNIVERS
User group *UNIVERSAL
Macro return codes
SC2 | SC1 | Maincode | Meaning |
X’00’ | X’00’ | X’0000’ | class A: CMD0001 |
X’02’ | X’00’ | X’3000’ | class A: DEF3000 |
X’02’ | X’00’ | X’3012’ | class A: DEF3003 |
X’01’ | X’3100’ | class B: DEF3100 | |
X’00’ | Invalid parameter address | ||
X’00’ | X’20’ | X’3200’ | class C: DEF3200 |
X’00’ | X’40’ | X’3302’ | class D: DEF3302 |
X’00’ | X’40’ | X’3303’ | class D: DEF3303 |
X’00’ | X’40’ | X’3306’ | class D: DEF3306 |
X’00’ | X’40’ | X’3308’ | class D: DEF3308 |
X’00’ | X’40’ | X’3309’ | class D: DEF3309 |
X’00’ | X’40’ | X’3313’ | class D: DEF3313 |
X’00’ | X’40’ | X’3314’ | class D: DEF3314 |
X’00’ | X’40’ | X’3315’ | class D: DEF3315 |
X’00’ | X’40’ | X’3400’ | class D: DEF3400 |
X’00’ | X’40’ | X’3402’ | class D: DEF3402 |
X’00’ | X’40’ | X’3403’ | class D: DEF3403 |
X’00’ | X’80’ | X’3900’ | class E: DEF3900 |
X’00’ | X’80’ | X’3901’ | class E: DEF3901 |
X’00’ | X’80’ | X’3902’ | class E: DEF3902 |
The precise cause of the error can be determined by calling the /HELP-MSG command with the error number specified in the table, e.g. /HELP-MSG DEF3902.