Welcome
CICS® IA space considerations
Data space allocation
The data space consists of a number of tables, both permanent and temporary. The number and size of the tables varies depending on whether you are collecting Interdependency data or Affinities data.
Calculating the space required for interdependency collection
The interdependency collection can consist of up to eight tables depending on the options selected.
Calculating CICS® data space
Three tables are used to create CICS® data.

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.
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
- Required data
  To calculate the space allocation requirements, estimate some values for the environment in which you want to run CICS® IA.
- Data space allocation
  The data space consists of a number of tables, both permanent and temporary. The number and size of the tables varies depending on whether you are collecting Interdependency data or Affinities data.
  - Calculating the space required for interdependency collection
    The interdependency collection can consist of up to eight tables depending on the options selected.
    - Calculating CICS® data space
      Three tables are used to create CICS® data.
    - Calculating Db2® data space
      One table is used to store Db2® data.
    - Calculating IMS® data space
      Two tables are used to store IMS® data.
    - Calculating MQ data space
      Two tables are used to store MQ data.
    - Calculating Natural data space
      One table is used to store Natural data.
    - Calculating the resource data space
      There is one table used to capture the CICS® resource data.
    - Total Interdependency data space calculation for Interdependency
      Calculation for the total data space required for interdependency.
  - Calculating the space required for affinity collection
    A number of data spaces are tables used when collecting affinity information.
- VSAM data set allocation
  There are ten VSAM files associated with CICS® IA.
- Db2® space allocation
  Calculate the Db2® space allocations using these assumptions and guidance.
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

Calculating CICS® data space

Three tables are used to create CICS® data.

About this task

Collect CICS® data as described:

Estimate the number of application programs that are used in the CICS® region, using the CICS® IA scanner. Call this number NUM_CICS_PROG.
Estimate the average number of EXEC CICS® calls per program, using the CICS® IA scanner. Run the scanner against all load module data sets in the DFHRPL that make up your applications. There are three types:
1. Key less than or equal to 32 bytes. Including all EXEC CICS® calls other than those listed in step b. Call this number AVG_EXEC_SHORT.
2. Resources greater than 32 characters. Currently only EXEC CICS® ENQ or EXEC CICS® DEQ have resource names greater than 32 bytes. Call this number AVG_EXEC_LONG.
3. Resources that use DTP. These resources consist of the following commands: ALLOCATE, CONNECT, SEND, CONVERSE and FREE. Call this number AVG_DTP.
Estimate the number of transaction and program associations. In this example, the estimate is that each can be associated with five transactions. Call this number PROG_TRAN_RATIO.

Calculate CICS® data space as follows:

 (108 * NUM_CICS_PROG * AVG_EXEC_SHORT  * PROG_TRAN_RATIO) + 
 (338 * NUM_CICS_PROG * AVG_EXEC_LONG  * PROG_TRAN_RATIO) + 
 ( 16 * NUM_CICS_PROG * AVG_DTP * PROG_TRAN_RATIO)  =   CICS_DS bytes.