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

CICS IA can report the following CICS Transaction Server dependencies:
  • 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
You can also identify dependencies for a platform.
Note: CICS IA currently does not collect information on many of these resource types unless they are used in an SPI command such as INQUIRE TSMODEL.

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

  1. In any of the CICS IA views, right-click the specific application or operation.
  2. Depending on whether you selected an application or operation, choose one of the following options:
    • Application dependencies by Application
    • Application dependencies by Operation
    Screen capture that shows the Application dependencies by Application option.
    The New Dependencies wizard opens. All possible dependencies from the data collected that can be defined in a CICS bundle project as a dependency are listed.
    The New Dependencies wizard.
  3. Select the type of CICS dependency.
    Note: If the Type is DB2CONN or MQCONN, you can edit the dependency name. Override the generated name in the Name field by entering the name that you want to use.
    The wizard is populated with all of the possible entry points.
  4. To create a new CICS Bundle, select New project in the Select or create a new project field. Otherwise, select an existing CICS bundle project to update. The CICS Explorer® CICS Bundle Project wizard opens.
    Screen capture that shows the CICS Bundle Project page.
  5. If you are creating a new project, enter a relevant Project name and click Finish. The Bundle Overview page opens.
  6. In the New Entry Points wizard, click Finish The entry points are added to your project.

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.