Welcome
Running the Reporter
Running the Dependency Reporter
This section describes how to run the CICS® IA Dependency Reporter. The Dependency Reporter consists of a batch job, CIUJCLRP, that produces reports of the dependencies found by the Collector.
Output from the Dependency Reporter
The Dependency Reporter produces sample reports. Here are examples of CICS®, Db2®, MQ, and IMS® reports.
MQ report
The report lists all the MQ commands that were collected by the Collector.

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.3
CICS® IA Version 6.3 maintains broad functionality and provides full support for the new CICS Transaction Server 6.3. Building on previous releases, it includes updates for commands whose threadsafe status has been enhanced in CICS Transaction Server 6.3, enabling more applications to run without switching 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.
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 Dependency Reporter
  This section describes how to run the CICS® IA Dependency Reporter. The Dependency Reporter consists of a batch job, CIUJCLRP, that produces reports of the dependencies found by the Collector.
  - Modifying a Dependency Reporter Job
    Changes to make before running the CIUJCLRP job.
  - Output from the Dependency Reporter
    The Dependency Reporter produces sample reports. Here are examples of CICS®, Db2®, MQ, and IMS® reports.
    - CICS® report
      A CICS® report consists of a header page and, if the dependency data file contains interdependency records, one or more pages of interdependency records.
    - Db2® report
      The report lists all the Db2® commands that were collected by the Collector.
    - MQ report
      The report lists all the MQ commands that were collected by the Collector.
    - IMS® report
      The report lists all the IMS® commands that were collected by the Collector.
- Running the Affinities Reporter
  The CICS® IA Affinities Reporter can be used to produce reports and definitions.
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.3

MQ report

The report lists all the MQ commands that were collected by the Collector.

Example MQ report from the Dependency Reporter shows an example MQ report.

Figure 1. Example MQ report from the Dependency Reporter

2025/12/18 - CICS INTERDEPENDENCY ANALYZER (CIU) - Version 630  -  Page:  63              
                      MQ RESOURCES REPORT FOR APPLID: IYCYZC3C                            
                                                                                          
 Tran  Program  Offset    Command              Resource                                   
------------------------------------------------------------------------------------------
                           Usage  First Run            Last Run             Term  TCBmode 
------------------------------------------------------------------------------------------
 MAIL  CSQ4CVD1 00004C4E  OPEN QUEUE           CSQ4SAMP.MAILMGR.DJWHITE                   
                               1  2025-12-18 09.24.16  2025-12-18 09.24.16     Y       QR 
                                                                                          
                00004CDA  CLOSE QUEUE          CSQ4SAMP.MAILMGR.DJWHITE                   
                               1  2025-12-18 09.24.58  2025-12-18 09.24.58     Y       QR 
                                                                                          
       CSQ4CVD2 00004806  GET QUEUE            CSQ4SAMP.MAILMGR.DJWHITE                   
                              24  2025-12-18 09.24.18  2025-12-18 09.24.18     Y       QR 
                                                                                          
       CSQ4CVD3 00003BA6  GET QUEUE            CSQ4SAMP.MAILMGR.DJWHITE                   
                               2  2025-12-18 09.24.19  2025-12-18 09.24.22     Y       QR

The report fields contain the same information as the identically named fields on the CICS® report, with the following variations and deletions:

Resource: The resource against which the command was issued, causing a dependency between it and the named program. For the MQ report, this resource is the fully-qualified queue name.
Sysid: Not reported on the MQ report.