Welcome
Details of dependencies and affinities collected
Commands monitored for potential dependencies
This section lists the commands monitored by the Collector because they have the potential to create dependencies.
Non-CICS API commands detected
Collecting dynamic COBOL calls
CICS® IA detects dynamic COBOL calls, which are collected by the Dependency and Command Flow Data collectors.

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.
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
- Commands monitored for potential dependencies
  This section lists the commands monitored by the Collector because they have the potential to create dependencies.
  - CICS® commands detected
  - CICS® FEPI commands detected
  - Non-CICS API commands detected
    - IBM® Db2®: EXEC SQL
      The Db2® commands that the collector monitors for potential dependencies.
    - IBM MQ: MQM
      The MQ commands that the collector monitors for potential dependencies.
    - IMS® database: EXEC DLI
      The EXEC DLI commands that the collector monitors for potential dependencies.
    - IMS® database: CBLTDLI, ASMTDLI and PLITDLI calls
      The IMS macro calls that the collector monitors for potential dependencies.
    - CICSPlex SM commands
      The CICSPlex SM commands that the collector monitors for potential dependencies.
    - Natural commands
      The Software AG Natural and ADABAS commands that the collector for potential dependencies.
    - Collecting dynamic COBOL calls
      CICS® IA detects dynamic COBOL calls, which are collected by the Dependency and Command Flow Data collectors.
- Commands monitored for potential affinities
  This section lists the affinity-related EXEC CICS® commands detected by the CICS IA Collector.
- Details of what is detected
  This section describes what is detected by the Detector and Reporter for each affinity type.
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

Collecting dynamic COBOL calls

CICS® IA detects dynamic COBOL calls, which are collected by the Dependency and Command Flow Data collectors.

To support the collection of dynamic COBOL Language Environment calls, CICS® IA assumes that the Call parameter list for IBM® COBOL program conforms to the structure documented in the publication Language Environment® Vendor Interfaces for COBOL Call routine

To support the collection of dynamic VS COBOL II calls, the call must be an ID type call and not a Literal call.

If neither of the two previous statements applies, the called program name is not collected and the called name is replaced in the OBJECT field:

UNEXP-hn

where n is reserved for IBM® diagnostics,

and h is a hex digit that indicates the program attributes as shown:

0xxx: The calling program is detected as COBOL for OS/390®.
1xxy: The calling program is detected as VS COBOL II program.
x0xx: The called program is detected as COBOL for OS/390®.
x1xx: The called program is detected as VS COBOL II program.
xx0x: The calling program AMODE is detected as 31.
xx1x: The calling program AMODE is detected as 24.
xxx0: The AMODE of the called program is detected as 31 bit.
xxx1: The AMODE of the called program is detected as 24 bit.