CICS resources subject to command security checking
For transaction and resource security checking, you identify the resources to RACF® using the identifiers that you have assigned to them; for example, file names, queue names, and transaction names. However, in the case of command security, the resource identifiers are all predefined by CICS®, and you use these predefined names when defining resource profiles to RACF.
The full list of resource identifiers that are subject to command security checking with the associated commands is shown in Table 1. Most of these commands are common to both the CEMT and EXEC CICS interfaces; commands that are specific to CEMT have the CEMT preface.
| Resource identifier 1 | Related CICS commands |
|---|---|
| ASSOCIATION | INQUIRE ASSOCIATION |
| ATOMSERVICE | CREATE ATOMSERVICE |
| AUTINSTMODEL | DISCARD AUTINSTMODEL |
| AUTOINSTALL | INQUIRE AUTOINSTALL |
| BRFACILITY | INQUIRE BRFACILITY |
| BUNDLE | CREATE BUNDLE |
| BUNDLEPART | INQUIRE BUNDLEPART |
| CAPDATAPRED | INQUIRE CAPDATAPRED |
| CAPINFOSRCE | INQUIRE CAPINFOSRCE |
| CAPOPTPRED | INQUIRE CAPOPTPRED |
| CAPTURESPEC | INQUIRE CAPTURESPEC |
| CFDTPOOL | INQUIRE CFDTPOOL |
| CONNECTION | CREATE CONNECTION |
| CSD | CSD ADD |
| DB2CONN | CREATE DB2CONN |
| DB2ENTRY | CREATE DB2ENTRY |
| DB2TRAN | CREATE DB2TRAN |
| DELETSHIPPED | INQUIRE DELETSHIPPED |
| DISPATCHER | INQUIRE DISPATCHER |
| DOCTEMPLATE | CREATE DOCTEMPLATE |
| DSNAME | INQUIRE DSNAME |
| DUMP | CEMT PERFORM SNAP |
| DUMPDS | INQUIRE DUMPDS |
| ENQMODEL | CREATE ENQMODEL |
| EPADAPTER | INQUIRE EPADAPTER 4 |
| EPADAPTERSET | INQUIRE EPADAPTERSET 4 |
| EPADAPTINSET | INQUIRE EPADAPTINSET 4 |
| EVENTBINDING | INQUIRE EVENTBINDING 4 |
| EVENTPROCESS | INQUIRE EVENTPROCESS |
| EXCI | INQUIRE EXCI |
| EXITPROGRAM | DISABLE PROGRAM |
| FEPIRESOURCE | Certain FEPI commands |
| FILE | CREATE FILE |
| HOST | INQUIRE HOST |
| IPCONN | CREATE IPCONN |
| IRC | INQUIRE IRC |
| JOURNALMODEL | CEMT INQUIRE JMODEL |
| JOURNALNAME | INQUIRE JOURNALNAME |
| JVMSERVER | CREATE JVMSERVER |
| LIBRARY | CREATE LIBRARY 4 |
| LINE | CEMT INQUIRE LINE |
| LSRPOOL | CREATE LSRPOOL |
| MAPSET | CREATE MAPSET |
| MODENAME | INQUIRE MODENAME |
| MONITOR | INQUIRE MONITOR |
| MQCONN | CREATE MQCONN |
MQMON![]() |
![]() CREATE MQMONITOR ![]() |
| MVSTCB | COLLECT STATISTICS |
| OSGIBUNDLE | INQUIRE OSGIBUNDLE 4 |
| OSGISERVICE | INQUIRE OSGISERVICE 4 |
| PARTITIONSET | CREATE PARTITIONSET |
| PARTNER | CREATE PARTNER |
| PIPELINE | CREATE PIPELINE |
| PROCESSTYPE | CEMT INQUIRE PROCESSTYPE |
| PROFILE | CREATE PROFILE |
| PROGRAM | CREATE PROGRAM 4 |
| REQID | INQUIRE REQID |
| RESETTIME | PERFORM RESETTIME 3 |
| RRMS | INQUIRE RRMS |
| SECURITY | PERFORM SECURITY REBUILD |
| SESSIONS | CREATE SESSIONS |
| SHUTDOWN | PERFORM SHUTDOWN 2 |
| STATISTICS | COLLECT STATISTICS |
| STORAGE | INQUIRE STORAGE |
| STREAMNAME | INQUIRE STREAMNAME |
| SUBPOOL | INQUIRE SUBPOOL |
| SYSDUMPCODE | INQUIRE SYSDUMPCODE 3 |
| SYSTEM | INQUIRE SYSTEM |
| TASK | INQUIRE TASK |
| TCLASS | CREATE TRANCLASS |
| TCPIP | INQUIRE TCPIP |
| TCPIPSERVICE | CREATE TCPIPSERVICE |
| TDQUEUE | CREATE TDQUEUE |
| TEMPSTORAGE | INQUIRE TEMPSTORAGE |
| TERMINAL | INQUIRE NETNAME |
| TRACEDEST | INQUIRE TRACEDEST |
| TRACEFLAG | INQUIRE TRACEFLAG |
| TRACETYPE | INQUIRE TRACETYPE |
| TRANDUMPCODE | INQUIRE TRANDUMPCODE 3 |
| TRANSACTION | CREATE TRANSACTION 4 |
| TSMODEL | CREATE TSMODEL |
| TSPOOL | INQUIRE TSPOOL |
| TSQUEUE | INQUIRE TSQUEUE |
| TSQNAME | INQUIRE TSQNAME |
| TYPETERM | CREATE TYPETERM |
| UOW | INQUIRE UOW |
| UOWDSNFAIL | INQUIRE UOWDSNFAIL |
| UOWENQ | INQUIRE UOWENQ |
| UOWLINK | SET UOWLINK |
| URIMAP | CREATE URIMAP 4 |
| VTAM | INQUIRE VTAM |
| WEB | INQUIRE WEB |
| WEBSERVICE | CREATE WEBSERVICE |
| XMLTRANSFORM | INQUIRE XMLTRANSFORM |
- If you are using prefixing, the value specified by the SECPRFX parameter must be prefixed to the command resource name.
- Be particularly cautious when authorizing access to these and any other CICS commands that include a SHUTDOWN option.
- See CEMT considerations.
- Bundle command security applies when you use SPI commands to perform an action on a BUNDLE resource, and in that process you install, enable, disable, or discard a dynamically generated resource of this type that was defined in the CICS bundle. No CICS command security applies when you install, enable, disable, or discard a dynamically generated resource of this type through an application or platform. For more information, see Security for bundles.
SET PROGRAM REPLICATION has an additional command security checking
beyond SET PROGRAM. For more information, see Resource and command check cross-reference.
Resource profile examples
If you are running CICS with command security, define resource profiles to RACF, with access lists as appropriate, using the resource names in Table 1 as the profile names. Alternatively, you can create resource group profiles in the VCICSCMD class.
RDEFINE VCICSCMD CMDSAMP UACC(NONE)
NOTIFY(sys_admin_userid)
ADDMEM(AUTINSTMODEL, AUTOINSTALL, CONNECTION,
DSNAME, TRANSACTION, TRANDUMPCODE, VTAM)
PERMIT CMDSAMP CLASS(VCICSCMD) ID(operator_group) ACCESS(READ)
RDEFINE VCICSCMD CMDSAMP1 UACC(NONE)
NOTIFY(sys_admin_userid)
ADDMEM(AUTINSTMODEL, AUTOINSTALL, CONNECTION,
DSNAME, TRANSACTION, TRANDUMPCODE, VTAM)
PERMIT CMDSAMP1 CLASS(VCICSCMD) ID(op_group_2) ACCESS(UPDATE)
If you are running CICS with SEC=YES, users require the access levels shown in Resource and command check cross-reference.