Identifying dependencies by application or operation
The CICS® IA plug-in provides a wizard to identify the resource dependencies for an application or an operation.
Before you begin
You must have already deployed an application and then used CICS IA to collect the application data. Alternatively, you must have collected dummy data by setting the operation field on a CICS program. For more information, see Assigning an operation value to a program.
Also, ensure that your CICS IA Collector gathered detailed data for transactions, programs, and web services.
About this task
- ATOMSERVICE
- DB2CONN
- DB2ENTRY
- DB2TRAN
- DOCTEMPLATE
- ENQMODEL
- EVENTBINDING
- EPADAPTER
- EPADAPTERSET
- EPASDAPTER
- EVENTBINDING
- FILE
- JOURNALMODEL
- JSONTRANSFRM
- JVMSERVER
- LIBRARY
- MAPSET
- MQCONN
- PARTITIONSET
- PIPELINE
- PROCESSTYPE
- PROGRAM
- SCACOMPOSITE
- TCPIPSERVICE
- TDQUEUE
- TRANSACTION
- TRANSID
- TSQMODEL
- URIMAP
- WEBSERVICE
- XMLTRANSFORM
CICS IA also reports if there is a dependency on a DB2® connection or a WebSphere® MQ connection.
Complete the following steps to identify dependencies by application or operation.
Procedure
What to do next
The new CICS bundle that contains the dependencies, can be included in a CICS application bundle.
The bundle, which is created is stored in the Explorer Eclipse workspace and is available to CICS bundle applications that are created in the same workspace. The bundles are also available to the CICS platform bundle and the CICS application binding bundle. Some of the dependencies might relate to a specific platform.