Welcome
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.

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
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.
- 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.3

Required data

To calculate the space allocation requirements, estimate some values for the environment in which you want to run CICS® IA.

Refer to the worksheet supplied in Values required for each CICS region and Values required for VSAM and Db2 calculations. These values are used in later calculations.

Table 1. Values required for each CICS® region
Required Data	Description	Value
PROG_TRAN_RATIO	Estimate of the number of transactions and program associations. For example, program PROGA can be associated with more than one transaction.
NUM_CICS_PROG	Number of programs that contain EXEC CICS® commands.
AVG_EXEC_LONG	Average number of EXEC CICS® calls, per program, that have a data space key greater than 32. These commands are the EXEC CICS® ENQ and EXEC CICS® DEQ.
AVG_EXEC_SHORT	Average number of EXEC CICS® calls, per program, that have a data space key less than or equal to 32. These commands are all EXEC CICS® commands apart from EXEC CICS® ENQ and EXEC CICS® DEQ commands.
AVG_DTP	Average number of EXEC CICS® DTP calls, ALLOCATE, CONNECT, SEND, CONVERSE, and FREE commands.
NUM_DB2_PROG	Number of programs that contain EXEC SQL commands.
AVG_Db2	Average number of EXEC SQL calls per program.
NUM_IMS_PROG	Number of programs that contain EXEC IMS® commands.
AVG_IMS	Average number of EXEC IMS® calls per program.
NUM_MQ_PROG	Number of programs that contain EXEC MQ commands.
AVG_MQ	Average number of EXEC MQ calls per program.
NUM_AFF_PROG	Number of programs that contain EXEC AFF commands.
AVG_AFF	Average number of EXEC AFF calls per program.
NUM_NATURAL_PROG	Number of Natural programs that contain ADABAS or PROGRAM calls.
AVG_NATURAL	Average number of ADABAS or PROGRAM calls per Natural program.

Table 2. Values required for VSAM and Db2® calculations
Required Data	Description	Value
NUM_REGION_V	Number of CICS® regions sharing the VSAM file. This value is required to calculate the VSAM file space allocation.
NUM_REGION_D	Total number of CICS® regions in which CICS® IA is collecting. This value is required to calculate the Db2® table and index sizes. The CICS® IA Db2® database can contain data from more than one set of VSAM files.