Resources › APPCSI Resource Class—Secure APPC Side Information Files

APPCSI Resource Class—Secure APPC Side Information Files

Valid on z/OS, ESA 4.2.0 and above.

Use APPCSI to determine who can administer the APPC side information files. These files contain the symbolic destination node names used when one Transaction Program (TP) converses with another TP on a different node.

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

TSS ADDTO(acid) APPCSI(dbtoken.SYS1.symbolic)

dbtoken

One‑ to eight‑character database token associated with the side information file.

SYS1

Indicates that this APPCSI is available to all users on that node. A particular ACID can also be substituted for SYS1.

symbolic

One‑ to eight‑character symbolic destination name associated with the side information file.

In order to view the side information, the administrator requires READ access. In order to create, modify or delete these files, the administrator requires UPDATE access.

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

TSS PERMIT(acid) APPCSI(dbtoken.SYS1.symbolic) ACCESS(access)

In order to view the side information, the administrator requires READ access. In order to create, modify or delete these files, the administrator requires UPDATE access.

APPCSI 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
• MISC2(APPCLU) authority to ADD or REMOVE ownership of APPCSI resources from ACIDs
• MISC2(APPCLU) authority to PERMIT or REVOKE access to APPCSI resources

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