Resources › UR1/UR2 Resource Class—Secure Resource Restrictions

UR1/UR2 Resource Class—Secure Resource Restrictions

Valid on z/OS, z/VSE, and z/VM.

Use UR1/UR2 to secure general installation‑defined resource restrictions as account codes.

When used with TSS ADDTO/REMOVE, this resource class has the following format:

TSS ADDTO(acid) UR1(oper,oper,...)|UR2(oper,oper,...)

Prefix length

One to eight characters

Capacity of list

One to five prefixes per TSS command

When used with TSS PERMIT/REVOKE, this resource class has the following format:

TSS PERMIT(acid) UR1(p‑fix)|UR2(p‑fix)
                 ACCESS(access levels)

Prefix length

One to forty‑four characters

Capacity of list

One to five prefixes per TSS command

This keyword is used with:

• The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOHAS, and WHOOWNS
• The ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
• The UR1/UR2 keywords are used with the ACID types: User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
• UR1/UR2(OWN) authority to ADD or REMOVE UR1/UR2 resources from ACIDs
• UR1/UR2(XAUTH) authority to permit or revoke access to UR1/UR2 resources

The administrator can:

• Specify the access levels: ALL, NONE, READ, WRITE, and UPDATE. If access is not specified, CA Top Secret defaults to READ access.
• Use any of the following methods to control access to user‑defined resources: Expiration, Facility, Program Pathing, Time/Day, and Actions.