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)
One‑ to eight‑character database token associated with the side information file.
Indicates that this APPCSI is available to all users on that node. A particular ACID can also be substituted for SYS1.
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 administrator can use any of the following methods to control access to APPCSI resources: Expiration, Facility, Program Pathing, Time/Day, and Actions.
Prefixing and masking are both supported.
This example makes LSCA01 responsible for maintaining the side information file for the local system:
TSS ADDTO(LSCA01) APPCSI(TOKENA.SYS1.SYMDES1)
This example permits users in the Technical Services Department to view the APPCSI for the local system:
TSS PERMIT(TECHPROF) APPCSI(TOKENA.SYS1.SYMDES1)
ACCESS(READ)
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|