Resources › DCSS Resource Class—Secure Segments

DCSS Resource Class—Secure Segments

Valid on z/VM.

Use DCSS to secure discontiguous Saved Segments/Named Saved Systems (NSS).

Note: DCSS/NSS protection does not apply to DCSSs/NSSs that are IPLed.

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

TSS ADDTO(acid) DCSS(name,name,...)

Prefix length

One to eight characters

Capacity of list

One to five prefixes per command

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

TSS PERMIT(acid) DCSS(name(s))
                 ACCESS(access levels)

Prefix length

One to eight characters

Capacity of list

One to five prefixes per TSS command

DCSS is used with:

• The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOOWNS, and WHOHAS
• The DCSS ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
• The DCSS ACID types User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
• DCSS(OWN) authority to ADD or REMOVE ownership of DCSSs from ACIDs
• DCSS(XAUTH) authority to PERMIT or REVOKE access to DCSSs

The administrator can:

• Specify any or all of the following access levels: SHR, NOSHR, FIND, PURGE, ALL, and NONE. If ACCESS is not specified, CA Top Secret defaults to SHR access.
• Use the following methods to control access to DCSSs: Expiration, Facility, Time/Day, and Actions.

Example: DCSS resource class

This example protects the DCSS named SAS by assigning ownership to the Engineering Department (ENGDEPT):

TSS ADDTO(ENGDEPT) DCSS(SAS)

This example removes ownership:

TSS REMOVE(ENGDEPT) DCSS(SAS)

This example permits a user in the Engineering Department to use the program product, SAS:

TSS PERMIT(ENGUSER) DCSS(SAS)

This example revokes access:

TSS REVOKE(ENGUSER) DCSS(SAS)