Resources › DCT Resource Class—Secure CICS DCT Data

DCT Resource Class—Secure CICS DCT Data

Valid on z/OS and z/VSE.

Use DCT to secure transient data entries in the CICS Destination Control Table (DCT).

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

TSS ADDTO(acid) DCT(oper,oper,oper,...)

Prefix length

One to eight characters

Capacity of list

One to five CICS destinations per TSS command

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

TSS PERMIT(acid) DCT(prefix(es))
                 ACCESS(access levels)

Prefix length

One to eight characters

Capacity of list

One to five prefixes per TSS command

DCT is used with:

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

The administrator can:

• Specify any or all of the following access levels: INQUIRE, SET, ALL, FEOV, NONE, PURGE, READ, WRITE, INSTALL, nad COLLECT. If ACCESS is not specified, CA Top Secret defaults to READ access. For CICS 4.1 and above, WRITE access is required because reading a DCT record is destructive.
• Use any of the following methods to control access to DCTs: Expiration, Facility, Pathing, Time/Day, and Actions.

Examples: DCT resource class

This example protects a CICS destination by assigning ownership to the Corporate Level Division (CORPCICS):

TSS ADDTO(CORPCICS) DCT(PRT6)

This example removes ownership:

TSS REMOVE(CORPCICS) DCT(PRT6)

This example permits a user full access to the installation's DCTs:

TSS PERMIT(USER05) DCT(DCT1) ACCESS(ALL)

This example revokes access:

TSS REVOKE(USER05) DCT(DCT1)