Welcome
Configuring CICS® IA
This section describes what you need to do before you can use CICS® IA.
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.
CICS® considerations
Before you run the installation jobs that enable your CICS® regions to collect CICS IA data, you must consider and resolve the following questions.
Share VSAM files
To control the operation of multiple instances of the Collector running on different CICS® regions, from a single CICS terminal, you must share the dependency and affinity data files, and the control record file across all the regions that are monitored.

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.
- 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.
  - CICS® considerations
    Before you run the installation jobs that enable your CICS® regions to collect CICS IA data, you must consider and resolve the following questions.
    - CICS® IA controlling region
      CICS® IA stores all the information about which collections and what data you want to collect, and so on, in a VSAM file. This file is known as the CONTROL file.
    - Share VSAM files
      To control the operation of multiple instances of the Collector running on different CICS® regions, from a single CICS terminal, you must share the dependency and affinity data files, and the control record file across all the regions that are monitored.
    - Controlling CICS® IA from the CICS® IA plug-in
      You can administer and operate the CICS® IA collectors from the CICS IA plug-in for Explorer.
    - Collecting Db2® commands
      You can collect data about the Db2® commands and resources that are used by your transaction and program in a CICS® region with the CICS IA dependency collector.
    - Command flow collector
      The CICS® IA command flow collector uses CICS user journals or logstreams, to store captured data. The logstreams can be created as coupling facility logstreams or DASD only logstreams.
  - Configuring a new collection environment
    To create a new collection configuration, select option 3 from the configuration menu.
  - Creating a new collection environment
    The steps that are required to define the resources that are required to enable CICS® IA collection in your CICS regions. Review and submit the sample jobs that are configured.
  - Run the IVP transaction to verify the installation
    Use the CICS® IA installation verification program (IVP) to verify that CICS IA is installed correctly in your CICS region. You are recommended to fix any errors reported by the IVP before you run any other CICS IA program.
- 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

Share VSAM files

To control the operation of multiple instances of the Collector running on different CICS® regions, from a single CICS® terminal, you must share the dependency and affinity data files, and the control record file across all the regions that are monitored.

To share the files, you can use either:

VSAM record-level sharing (RLS). For more information about using VSAM RLS in CICS®, see the CICS® Installation Guide.
Function shipping to a file-owning region (FOR). For more information about CICS® function shipping, see the CICS® Intercommunication Guide. If you use function shipping, it is recommended that, for performance reasons, you define the files as local to the controlling region or in a file owning region and remote in all the other regions to be monitored.

You can select your preferred sharing method and customize the required samples according to your selection, with the customization exec.