Introduction to resource security

Transaction security controls access to CICS® transactions. Resource security provides a further level of security, by controlling access to the resources used by the CICS transactions. The implication of this is that a user who is authorized to invoke a particular CICS transaction may not be authorized to access files, PSBs, or other general resources used within the transaction. Unlike transaction security, which cannot be turned off for individual transactions, you can control resource security checking at the individual transaction level.

Resources defined to CICS to support application programming languages are also subject to security checking if resource or command security checking is specified. For example, if a PL/I program abends, it may attempt to write diagnostic information to the CPLI transient data queue. If resource checking is active, and the user is not authorized to write to the CPLI transient data queue, the program will terminate with an APLI abend.

You control who can access the general resources used by CICS transactions, by: