RESID values

In all cases (except for the SPCOMMAND resource type), the resource identifiers (RESID values) are defined by your installation.

When defining RESID values, be aware of the effects of using blanks (X'40') in resource identifiers. For example, in: 
QUERY SECURITY RESTYPE('PSB') RESID('A B')
the blank delimits the RESID and causes RACF® to use a resource name of A.

For SPCOMMAND, the identifiers are predetermined by CICS®. The list of possible RESID values for SPCOMMAND is as follows:

  • ASSOCIATION
  • ATOMSERVICE
  • AUTINSTMODEL
  • AUTOINSTALL
  • BRFACILITY
  • BUNDLE
  • BUNDLEPART
  • CAPDATAPRED
  • CAPINFOSRCE
  • CAPOPTPRED
  • CAPTURESPEC
  • CFDTPOOL
  • CONNECTION
  • CSD
  • DB2CONN
  • DB2ENTRY
  • DB2TRAN
  • DISPATCHER
  • DOCTEMPLATE
  • DSNAME
  • DUMP
  • DUMPDS
  • ENQUEUE
  • EPADAPTER
  • EPADAPTERSET
  • EPADAPTINSET
  • EVENTBINDING
  • EVENTPROCESS
  • EXCI
  • EXITPROGRAM
  • FEPIRESOURCE
  • FILE
  • HOST
  • IPCONN
  • IRC
  • JOURNALMODEL
  • JOURNALNAME
  • JVMSERVER
  • LIBRARY
  • MODENAME
  • MONITOR
  • MQCONN
  • MQINI
  • MVSTCB
  • OSGIBUNDLE
  • OSGISERVICE
  • PARTNER
  • PIPELINE
  • PROCESS
  • PROFILE
  • PROGRAM
  • REQID
  • REQUEST
  • RESETTIME
  • RRMS
  • SECURITY
  • SHUTDOWN
  • STATISTICS
  • STORAGE
  • SUBPOOL
  • SYSDUMPCODE
  • SYSTEM
  • TASK
  • TCLASS
  • TCPIP
  • TCPIPSERVICE
  • TDQUEUE
  • TEMPSTORAGE
  • TERMINAL
  • TRACEDEST
  • TRACEFLAG
  • TRACETYPE
  • TRANDUMPCODE
  • TRANSACTION
  • TSQUEUE
  • TSMODEL
  • TSPOOL
  • TYPETERM
  • UOW
  • UOWDSNFAIL
  • UOWENQ
  • UOWLINK
  • URIMAP
  • VOLUME
  • VTAM®
  • WEB
  • WEBSERVICE
  • XMLTRANSFORM
Note: VTAM is now the z/OS® Communications Server.

QUERY SECURITY RESTYPE enables an application program to request from RACF the level of access a terminal user has to the specified resource for the environment in which the transaction is running.

Before calling RACF, CICS checks that the resource is installed. If the resource does not exist, CICS does not call RACF and returns the NOTFND condition. However, note that this check is not made for PSBs.

When the RESTYPE is TRANSATTACH and the transaction specified on the RESID parameter is unknown in the local region, a NOTFND condition is returned. However, if dynamic transaction routing is being used, there is no need for the transaction to be installed in the terminal-owning region. The transaction specified on the DTRTRAN system initialization parameter is attached if an unknown transaction identifier is entered.

Application programmers should be aware that the NOTFND condition does not necessarily indicate that a terminal user will be unable to enter a transaction identifier, because the transaction may be routed dynamically.