Keywords › UNDERCUT Keyword—Transfer Resource Ownership

UNDERCUT Keyword—Transfer Resource Ownership

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

Use the UNDERCUT keyword to transfer resource ownership from one ACID to another.

Undercutting occurs when an administrator ADDS a prefix which is shorter than another resource prefix which is already owned. The use of the UNDERCUT keyword indicates that the transfer is intentional. If the UNDERCUT keyword is omitted, CA Top Secret issues an error message.

This prevents CA Top Secret administrators from unintentionally transferring or undercutting ownership.

When resource ownership is transferred from one owner to another, CA Top Secret automatically permits the old owner to have full access to the resource. To prevent the old owner from having full access to resources they no longer own use NOPERMIT.

A data set defined as SYS.01 is owned by ACID2. Since CA Top Secret supports generic prefixing, it will consider SYS.01 and SYS.01.02 to be generic prefixes for the same data set.

An administrator can only undercut prefixes within his scope of authority.

Undercutting only applies to prefixes, not to full resource names. Therefore, if USER. and USER01. were full minidisk names they could exist as separate minidisks.

Undercutting only applies to prefixes of the same resource type. Thus USER could exist as a minidisk, and USER01 could exist as a program.

This keyword has the following format:

TSS ADDTO(acid) resource(prefix)
                UNDERCUT

This keyword is used with:

• The commands CREATE and ADDTO
• The ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA
• RESOURCE(OWN) authority

Examples: UNDERCUT keyword

This example transfers ownership of SYS.01.02 from ACID2 to ACID1.

TSS ADDTO(ACID1) DSNAME(SYS.01)
                 UNDERCUT

This example prevents the old owner from having full access to resources they no longer own:

TSS ADDTO(NEWOWNER) DSNAME(SYS.01)
                    UNDERCUT 
                    NOPERMIT