RACF classes for CICS resources

To protect a CICS® resource, you must create a general resource profile for the resource in a suitable class or resource grouping class. RACF® provides several classes for CICS resources. You can also define your own resource classes.

Notes:

  1. The initial character of the class names is significant when you define your own classes. For example, if you define your own classes for CICS programs, the names you choose must start with M and N for the member class and the resource grouping class respectively.
  2. There are no default resource class names for DB2ENTRY resources. You must define your own resource classes for these resources. See Resource classes for DB2ENTRY resources for more information.
  3. Profile names in the RCICSRES class must contain a prefix that specifies the CICS resource type to which they apply: ATOMSERVICE.name for ATOMSERVICE definitions, BUNDLE.name for bundles, DOCTEMPLATE.name for CICS document templates, EPADAPTER.name for EP adapters, EPADAPTERSET.epadapterset_resource_name for EP adapter sets, EVENTBINDING.name for event bindings, or XMLTRANSFORM.name for XML transforms.
Table 1. RACF-provided resource classes for CICS resources
Member class Resource grouping class Description
TCICSTRN GCICSTRN CICS transactions, normal attach security
PCICSPSB QCICSPSB CICS PSBs
ACICSPCT BCICSPCT CICS-started transactions and the following EXEC CICS commands:
  • COLLECT STATISTICS TRANSACTION
  • DISCARD TRANSACTION
  • INQUIRE TRANSACTION
  • SET TRANSACTION
DCICSDCT ECICSDCT CICS transient data queues
FCICSFCT HCICSFCT CICS files
JCICSJCT KCICSJCT CICS journals
MCICSPPT NCICSPPT CICS programs
SCICSTST UCICSTST CICS temporary storage queues
CCICSCMD VCICSCMD EXEC CICS SYSTEM commands and EXEC CICS FEPI system commands
RCICSRES WCICSRES Document templates, bundles, EP adapters, EP adapter sets, event bindings, ATOMSERVICE definitions, and XML transforms