Welcome
Configuring CICS® IA
This section describes what you need to do before you can use CICS® IA.
Post configuration tasks
This section describes some optional tasks that you might be required to be perform.
CICS® IA Natural support
With CICS® IA, you can gather CICS resource information for COBOL, PL/I, and Assembler language programs called from within a Software AG Natural program.
Installing Natural support
CICS® IA Natural support runs as an exit to the Natural Review Data Collector. The Natural Review Data Collector and the CICS IA Natural support exit must be link-edited into an NSN.

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.
- 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.
  - Creating your own program exclude, transaction exclude, and resource compression list
    You can use program exclude lists, transaction exclude lists, command exclude lists, and resource compression list to limit the volume of information collected by the Collector. In this section the term, Collector, refers to the Affinity and Dependency collector functions but for command exclude list the term, Collector, refers only to the Dependency collector functions.
  - Grouping transactions and programs into applications
    CICS® IA 5.1 and later provides utilities so that you can use CICS IA 3.2 Application definitions in your CICS IA 5.1 or later environment. However, CICS Transaction Server 5.1 and later provides the capability to define applications as part of the platform capabilities, and it is now advisable to define applications in this way.
  - CICS® IA Natural support
    With CICS® IA, you can gather CICS resource information for COBOL, PL/I, and Assembler language programs called from within a Software AG Natural program.
    - Installing Natural support
      CICS® IA Natural support runs as an exit to the Natural Review Data Collector. The Natural Review Data Collector and the CICS IA Natural support exit must be link-edited into an NSN.
    - Customizing the CICS® IA Natural Interface
      Customizing the CICS® IA Natural Interface includes one task: Modifying the Exclusive Work Area (EWA) size.
  - Starting and stopping CICS® IA from the PLT
    You can start CICS® IA from a program list table (PLT) program that is initiated during the third stage of CICS initialization; that is, a program that is specified in the second part of the program list table post initialization (PLTPI) list for the CICS region.
  - CICS® IA supplied modules required in the MVS link list
    If you use the MVS interactive problem control system (IPCS) to format and analyze CICS® system dumps, you can use the CICS IA system dump formatting routines, CIUIADUF and CIUICDUF, to format the CICS IA collector data areas.
  - Creating your translation table
    CICS® IA uses a translation table to translate the resource name of the CICS IA dependency data before it is loaded to the Db2® CIU_CICS_DATA table or it creates the hlqc.CICS.CSV file.
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

Installing Natural support

CICS® IA Natural support runs as an exit to the Natural Review Data Collector. The Natural Review Data Collector and the CICS® IA Natural support exit must be link-edited into an NSN.

Before you begin

Follow these steps to install Natural Support:

Procedure

Verify that the CICS® IA Natural exit is available, using program CIURDCX1 found in the hlq.SCIULOAD library
Follow the instructions for link-editing the Natural Review Data Collector, (NATRDC) into an NSN as provided by the vendor. The exit can be linked into one of three places:
- The Independent (shared) nucleus NATvvvSH.
- The CICS® dependent nucleus NCvvvRE.
- A dynamically loaded CICS® parameter module.
Link the exit into the CICS® dependent nucleus, NCvvvRE:
1. Specify the RCA , RDCEXIT and RDCSIZE parameters in the Natural/CICS parameter module. These parameters are options on the NTPRM macro. Set the parameters as follows:
  - RCA=(CIURDCX1)
  - RDCSIZE=2
  - RDCEXIT=(CIURDCX1,400)
  Later versions of Natural do not support the use of RDCEXIT as a parameter on the NTPRM macro. Instead you must use the NTRDC macro as shown:
  - NTRDC EXIT=(CIURDCX1,400)
  You can also specify the RDCSIZE using the NTDS macro as shown:
  - NTDS RDCSIZE,2 DATA Collector Buffer
Add the following DD statement for the CICS® IA load library to the job used to link-edit the NSN:
```
//ACIUMOD DD DISP=SHR,DSN=hlq.ACIUMOD
```
Add the following linkage-editor control statement to the linkage-editor input stream:
```
INCLUDE ACIUMOD(CIURDCX1)
```
If you are linking into the Independent (shared) nucleus add the following into the job stream:
```
//SCIULOAD DD DISP=SHR,DSN=hlq.SCIULOAD          

INCLUDE SCIULOAD(CIURDCX1)
```

What to do next

When these steps are complete the CICS® IA collection of interdependency data will record the names of the Natural programs involved in place of the name of the Natural nucleus.