Defining the transactions in a managed CICS region

For CICS® regions that are capable of running with an external security manager, it might be necessary to define the transactions that run in a CICS region managed by CICSPlex® SM to the ESM.

About this task

If transaction–attach security is active in a CICS region (that is, SEC=YES and XTRAN=YES|classname are specified in the system initialization parameters), you must define the following transactions to RACF® in the appropriate class:
  • COHT
  • COIE
  • COIR
  • COI0
  • CONA
  • COND
  • CONH
  • CONL
  • CONM
  • CORT
  • COWC

Start of changeThe region user ID must be given READ access to these transactions. These transactions are in category 1 of CICS-supplied transactions, and the necessary access can be defined together with all transactions in this category. For more information about category 1 of CICS-supplied transactions, see Category 1 transactions.End of change

Users who can enter dynamic transactions in a CICSPlex SM workload management requesting region must have READ access to the COWC transaction.

Users who might invoke the debugging transactions should be given READ access to the following transactions:

CODB
COD0
COD1
COD2
COLU

The security attributes of the CONNECTION/SESSION pair defined for the link to the CMAS define which users are authorized to run these transactions. See Overview of intercommunication security for information on intercommunication security.

The COSH transaction allows a terminal user to stop agent code execution. Access to this transaction should be restricted to those users who might need to stop the agent code in this way.



dfht5mm.html | Timestamp icon Last updated: Sunday, 4 June 2017