Welcome
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.
Output from the Builder
The Builder produces a file containing a set of definitions of combined affinity transaction groups and a report listing the combinations that occurred.
Empty transaction groups report
The empty transaction groups report gives all basic transaction groups (Trangroups) that were defined, but contained no transactions.

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 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.
- Editing the CIUAFFBL job
  To run the Builder, edit and run the CIUAFFBL job.
- Syntax for input to the Builder
  The syntax in the sequential data sets used as input for the Builder is similar, but not identical, to that allowed by CICSPlex SM.
- Output from the Builder
  The Builder produces a file containing a set of definitions of combined affinity transaction groups and a report listing the combinations that occurred.
  - Combined affinity-transaction-group definitions
    Before each definition of a combined group in the output file, the Builder adds a commented-out REMOVE command for that group. If you already have combined groups of the same name, check that it is appropriate to delete them before you uncomment the REMOVE command.
  - Data sets processed report
    The data sets processed report gives the names of all the input data sets, specified on the REPGRPS DD statement, that were read.
  - Empty transaction groups report
    The empty transaction groups report gives all basic transaction groups (Trangroups) that were defined, but contained no transactions.
  - Group merge report
    For each combined group, the group merge report gives the constituent transactions and basic groups that comprise the combined group and provides a type of audit trail.
  - Error report
    The error report gives the syntax or logic of any errors that were detected in the processing of the input files.
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

Empty transaction groups report

The empty transaction groups report gives all basic transaction groups (Trangroups) that were defined, but contained no transactions.

It is produced only if the input data sets have no errors. An empty Trangroup probably indicates that you have made a mistake. The Reporter cannot produce empty Trangroups, so you must have created the input by hand, and probably omitted some corresponding CREATE DTRINGRP statements.

Figure 1. Example empty Trangroups report

CICS INTERDEPENDENCY ANALYZER                                                2007/09/19    Page    2
BUILDER EMPTY TRANGROUP DEFINITIONS
      CICSPDN1.TRANGRPS.EMPTY1
        G1           (GLOBAL SYSTEM   )     G2           (GLOBAL PERMANENT)     G3      (GLOBAL SYSTEM   )
      CICSPDN1.TRANGRPS.EMPTY2
        L2           (LUNAME PERMANENT)     L3           (LUNAME LOGON    )     L4      (LUNAME PCONV    )