Resources › APPCTP Resource Class—Secure APPC Transaction Programs

APPCTP Resource Class—Secure APPC Transaction Programs

Valid on z/OS, ESA 4.2.0 and above only.

Use APPCTP to secure APPC transaction programs (TPs) and TP profiles. An access level of READ or UPDATE allows the ACID to maintain the TP profile data set (which contains the TP class and JCL required to run the TP) while an access level of EXECUTE allows the ACID to run the TP.

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

TSS ADDTO(acid) APPCTP(dbtoken.level.tpname)

Capacity of list

One to five names per TSS command

dbtoken

One‑ to‑ eight character database token associated with the TP profile.

level

Represents one of the following:

SYS1

If the TP is available to all users who can access the LU.

groupid

If the TP is only available to a particular group.

acid

If the TP is only available to a particular user.

tpname

One‑ to ‑64 character TP name.

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

TSS PERMIT(acid) APPCTP(dbtoken.level.tpname)

Capacity of list

One to five names per TSS command.

APPCTP is used with:

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

The administrator can use any of the following methods to control access to APPCTP resources: Expiration, Program Pathing, Time/Day, and Actions.

Masking

Prefixing and masking are both supported.

Examples: APPCTP resource class

The security administrator for APPC resources (LSCA01 in our examples) should create an APPCTP profile for each TP profile, using generic prefixing where appropriate. ACIDs requiring use of the TPs should then be given the appropriate access.

This example makes LSCA01 responsible for maintaining TPB (which is accessible to all users from LU02):

TSS ADDTO(LSCA01) APPCTP(TOKENA.SYS1.TPB)
                  ACCESS(UPDATE)

This example allows users with the TECHPROF Profile to run TPB:

TSS PERMIT(TECHPROF) APPCTP(TOKENA.SYS1.TPB)
                     ACCESS(EXECUTE)