Welcome
Configuring CICS® IA
This section describes what you need to do before you can use CICS® IA.
New Db2® configuration
The data collected from the Dependency, Affinity and Command Flow collectors are stored in the CICS® IA database. Data collected from the CICS IA scanners are also stored in this database.
Configure a new Db2® environment
To create a new Db2® configuration, select option 1 from the configuration menu.
Output data set variables
The values that are required to allocate the output data sets.

Preface
This information describes the IBM® CICS® Interdependency Analyzer for z/OS®. It explains what the program does and how to set up and run its various components.
What's new in CICS® IA Version 6.1
CICS® IA Version 6.1 continues to support a wide range of capabilities and fully supports new CICS Transaction Server 6.3. Building on previous releases, CICS IA Version 6.1 contains updates to reflect those commands for which CICS Transaction Server 6.3 has updated the threadsafe status allowing more applications to run without requiring a switch to QR TCB mode.
Overview of the CICS® Interdependency Analyzer
This section gives an overview of the CICS® Interdependency Analyzer (CICS IA), and describes its components.
Getting Started with the CICS® IA plug-in for CICS Explorer®
The CICS® Interdependency Analyzer plug-in for CICS Explorer® provides an Eclipse-based interface to analyze your CICS IA data. It also provides cheat sheets that guide you through the steps required to configure and install CICS IA. It is recommended that you download the CICS IA plug-in and follow the steps in the cheat sheets.
Configuring CICS® IA
This section describes what you need to do before you can use CICS® IA.
- Prepare your CICS® IA configuration environment
  CICS® IA uses an ISPF dialog that runs REXX execs to assist you in configuring your CICS IA environments.
- New Db2® configuration
  The data collected from the Dependency, Affinity and Command Flow collectors are stored in the CICS® IA database. Data collected from the CICS IA scanners are also stored in this database.
  - Db2® considerations
    Before you run the installation jobs to create the IBM® Db2® environment, you must consider and decide the following questions.
  - Configure a new Db2® environment
    To create a new Db2® configuration, select option 1 from the configuration menu.
    - Output data set variables
      The values that are required to allocate the output data sets.
    - Db2® variables
      The Db2® variables that are required to define the CICS® IA Db2 databse
    - General variables
      The variables required to allocate the QSAM data sets that are used by CICS IA batch jobs.
  - Create a new Db2® environment
    This section describes the steps that are required to define your CICS® IA Db2® database, and how to review and submit the sample jobs that you configured in the previous section.
  - Loading the IVP data and connect to the CICS® IA plug-in
    CICS® IA provides sample data that you can load into your new IA Db2® database. You can then connect to the database with the CICS IA plug-in for CICS Explorer® and verify that your Db2 database is created successfully.
- New collection configuration
  CICS® IA provides a number of real-time collectors. To enable the collectors, you must complete a number of tasks to create the resources that are required to facilitate the collection and to define these resources to the CICS regions where the collectors run.
- Upgrading an existing Db2® configuration
  Before you begin upgrading your Db2® configuration, ensure that you have read and followed the instructions to prepare your CICS® IA environment and the Db2 considerations.
- Upgrading your collection configuration
  How to configure an existing collection environment for upgrade, upgrade an existing collection environment, and run the IVP transaction to verify the installation.
- Post configuration tasks
  This section describes some optional tasks that you might be required to be perform.
Running the Collector
You run the CICS® IA Collector to look for instances of program commands that might cause resource dependencies or transaction affinities.
Updating the Dependency and Affinity database objects
The Dependency database objects contain accumulated data about your applications and the resources that they use. Update the database objects regularly to add new information recorded by the Collector in the VSAM dependency files.
Managing your CICS® IA data
With each new release CICS® IA captures more data. In volatile development environments this data can soon become out of date. If you have out of date data, the CICS IA plug-in might retrieve more data than you need. The presence of unwanted data might impede your analysis and provide confusing results.
The CICS® IA UDB database
CICS® IA provides jobs to unload CICS IA data into CSV files. These files can be used to populate the IBM® supported UDB databases.
Running the Reporter
Running the Program Threadsafe report
The threadsafe report can be run from the CICS IA Explorer plug-in or as a batch job using the sample CIUJTSQ2 that can be found in SCIUSAMP.CICS. The report runs the Db2® stored procedure CIUSPTSR.
Running the Load Module Scanner
The Load Module Scanner scans load modules for instances of program commands that could cause resource dependencies or transaction affinities.
Running the CSECT Scanner
The CICS® IA CSECT Scanner scans load modules for information that can be used to identify the version of each CSECT.
Running the Builder
The CICS® IA Builder runs as a batch job to build affinity-transaction-group definitions suitable for input to the CICS system management product, CICSPlex SM.
Running the sample Db2® query
This section describes how to run the sample CICS® IA batch query job CIUJSAMP.
Solving problems
This section helps you to isolate and determine the cause of CICS® IA problems.
Details of dependencies and affinities collected
Correlating Load Module Scanner and Dependency Reporter output to source
The structure of the CICS® IA database
Messages and codes
This section describes the messages that the Collector, Query interface, Dependency Reporter, Affinities Reporter, Load Module Scanner, CSECT Scanner, and Builder can issue, and the transaction abend codes that the Collector can produce.
CICS® IA space considerations
CICS® IA security
CICS® IA External Interfaces
The Appendix describes available Stored Procedures and Command Flow user exit.
Collecting dynamic COBOL calls
CICS® IA detects dynamic COBOL calls, which are collected by the Dependency and Command Flow Data collectors.
Accessibility
Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully
Download PDF
Download the PDF format documentation for CICS Interdependency Analyzer for z/OS 6.1

Output data set variables

The values that are required to allocate the output data sets.

OUTPUT DSN FOR Db2® SCIUSAMP: The output data set that contains the modified SCIUSAMP members to configure the Db2® database. This field defaults to @hlq.SCIUSAMP.Db2.
REQUIRED.

OUTPUT DSN FOR Db2® SCIUSQL: The output data set that contains the modified SCIUSQL members to configure the Db2® database. This field defaults to @hlq.SCIUSQL.Db2.
REQUIRED.

OUTPUT DSN FOR Db2® SCIUDAT1: The output data set that contains the modified SCIUDAT1 members to configure the Db2® database. This field defaults to @hlq.SCIUDAT1.Db2.
REQUIRED.

OUTPUT DSN FOR Db2® SCIUDAT2: The output data set that contains the modified SCIUDAT2 members to configure the Db2® database. This field defaults to @hlq.SCIUDAT2.Db2.
REQUIRED.

OUTPUT DEVICE TYPE: The data set device type that is used to allocate the output data sets. This field defaults to SYSDA.
REQUIRED for a Full configuration. For a Short configuration, this field is not displayed.

OUTPUT VOLUME SERIAL: The volume serial where CICS IA configuration data sets are allocated. Specify a valid volume serial number if you want to allocate your data sets on a specific non-SMS controlled volume. Specify SMS as the volume serial number to let SMS pick a volume. This field is defaults to SMS.
REQUIRED for a Full configuration. For a Short configuration, this field is not displayed.

DATA SET VERIFICATION: Defines whether it is necessary to verify the existence of the data sets required to configure and create the CICS® IA database. For example, the Db2® load library data set SDSNLOAD. This field defaults to YES.
REQUIRED for a Full configuration. For a Short configuration, this field is not displayed.

HLQ for CICS® IA output data sets

This field is displayed on the panel for a Short configuration only. It is required and specifies the common value for both the Db2 LOAD TEMPLATE QUALIFIER and the QSAM FILE QUALIFIER variables. For more information, see Db2 variables.