The resource signature, the combination of the definition
and the installation signatures, can be used to audit and manage resources
by capturing details when the resource is defined, installed, and
last changed.
Being able to display information about when the resource was defined,
installed, and last changed helps with problem determination. The
details improve the auditing and tracing of resources and can be displayed
in the CICS Explorer® views, CICSPlex® SM views, CEDA panels,
using
EXEC CICS INQUIRE SPI commands and
CEMT
INQUIRE commands. The following resource types support the
resource signature:
- ATOMSERVICE
- BUNDLE
- CONNECTION
- DB2CONN
- DB2ENTRY
- DB2TRAN
- DOCTEMPLATE
- ENQMODEL
- EPADAPTER
- EPADAPTERSET
- EVENTBINDING
- FILE
- IPCONN
- JOURNALMODEL
- JVMSERVER
- LIBRARY
- MQCONN
- MQINI
- OSGIBUNDLE
- PIPELINE
- PROFILE
- PROCESSTYPE
- PROGRAM
- TCPIPSERVICE
- TDQUEUE
- TRANCLASS
- TRANSACTION
- TSMODEL
- URIMAP
- WEBSERVICE
- XMLTRANSFORM
For these resources, their definition and installation signatures
can be compared to identify their origin. For more information, see
the following topics.