IPIC transaction, resource, and command security
- Attach a transaction (transaction security)
- Access all the resources that the transaction is programmed to use. These levels are called resource security, surrogate user security, and command security
Transaction security
As in a single-system environment, the security requirements of a transaction are specified when the transaction is defined, as described in Transaction security.
- The link user ID must have sufficient authority to initiate the transaction (see IPIC link security).
- If anything other than USERAUTH(LOCAL) has been specified, user security is in force. The user who is making the request must therefore have sufficient authority to access the system and to initiate the transaction.
Resource and command security
Resource and command security in an intercommunication environment are handled in much the same way as in a single-system environment.
CEDA DEFINE TRANSACTION
.
RESSEC(YES)
CMDSEC(YES)
.
If a TRANSACTION definition specifies resource security checking, using RESSEC(YES), both the link and the user must have sufficient authority for the resources that the attached transaction accesses.
If a TRANSACTION definition specifies command security checking, using CMDSEC(YES), both the link and the user must have sufficient authority for any of the system programming commands shown in Table 1 that the attached transaction issues.
For further guidance on specifying resource and command security, see Resource security and CICS command security.