Welcome
The structure of the CICS® IA database
The structure for the Detailed resource objects
This section describes the structure for the Detailed resource objects.
GLUE and TRUE exit resource table
Use the information in the CIU_EXIT_INFO tables to write your own SQL applications to query the tables; these applications must use native SQL queries.

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
- The structure of the Dependency database objects
  This section describes the tables and views defined in the Dependency database.
- The structure of the Affinity objects
  This section describes the tables and views defined in the set of Affinity database objects.
- The structure of the Load Module Scanner objects
  This section describes the tables and views defined in the Load Module Scanner database objects.
- The structure of the CSECT Scanner objects
  This section describes the tables and views defined in the CSECT Scanner database.
- The structure of the CICS® regions objects
  This section describes the structure of the CICS® regions objects.
- The structure for the Detailed resource objects
  This section describes the structure for the Detailed resource objects.
  - Connections table
    Use the information in the CIU_CONNECTIONS table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - File resource table
    Use the information in the CIU_FILE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Program resource table
    Use the information in the CIU_PROGRAM_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Transaction resource table
    Use the information in the CIU_TRANSID_DETAIL tables to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Transient Data queue resource table
    Use the information in the CIU_TDQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Temporary Storage queue resource table
    Use the information in the CIU_TSQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Web service resource table
    Use the information in the CIU_WEBSERV_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - GLUE and TRUE exit resource table
    Use the information in the CIU_EXIT_INFO tables to write your own SQL applications to query the tables; these applications must use native SQL queries.
  - Event table
    Use the information in the CIU_EVENT_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
- The structure of the CICS® IA plug-in for IBM® CICS Explorer™ resource objects
  This section describes the CIU_RESOURCE table. This table is used by the CICS® IA plug-in to improve performance and combine resource tables.
- The structure of the Version objects
  This section describes the CIU_VERSION table. This table is used by the CICS IA plug-in for CICS® Explorer to synchronize the CICS IA plug-in version being used and the base IA database objects.
- The structure of the Command Flow table objects
  This section describes the Command Flow base table that contains records for each command that is issued by the transactions. You can write your own SQL applications to query the table; these applications must use native SQL to write the queries.
- The Structure of the Program Flows table objects
  This section describes the structure of two CICS IA tables that are used only to generate the program flows report in the CICS IA plug-in for the CICS Explorer.
- Type and Function mapping for monitored commands
  Learn about the correspondence between resource type and command function for the monitored CICS® commands.
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

GLUE and TRUE exit resource table

Use the information in the CIU_EXIT_INFO tables to write your own SQL applications to query the tables; these applications must use native SQL queries.

CIU_EXIT_INFO

This table stores detailed information about every CICS® GLUE and TRUE exit that is called by at least one transaction. Exit information is stored in this table only if the Exits field on the CICS® Resources Options panel, CIU240, is set to Y.

Table 1. The CIU_EXIT_INFO table
Field Name	Type	Special restrictions
COLLECTION_ID	CHAR(16)	Collection ID.
ARCHIVE_DATE	TIMESTAMP	Time of archiving.
APPLID	CHAR(8)	CICS® region applid.
HOMESYSID	CHAR(4)	SYSID of local region.
PLATFORM	CHAR(64)	Platform name
APPL_NAME	CHAR(64)	Application name
APPL_VER1	INTEGER	Major version number
APPL_VER2	INTEGER	Minor version number
APPL_VER3	INTEGER	Micro version number
APPL_OPER	CHAR(64)	The operation associated with the task
EXIT_PROGRAM	CHAR(8)	The name of the exit program.
EXIT_NAME	CHAR(8)	The name of the exit.
EXIT_POINT	CHAR(8)	The name of the entry point associated with the exit. GLUEs only.
EXIT_TYPE	CHAR(4)	The type of exit. Values are GLUE or TRUE.
FIRST_RUN	TIMESTAMP	Time of first occurrence, in the local time format.
LAST_RUN	TIMESTAMP	Time of latest observation, in the local time format.

CIU_TRUEEXIT_INFO

Table 2. The CIU_TRUEEXIT_INFO table
Field Name	Type	Special restrictions
TRUE_NAME	CHAR(8)	The TRUE exit program name.
PRODUCT_INFO	CHAR(50)	The product name.

V_CIU_TRUEEXIT_INFO

Table 3. The V_CIU_TRUEEXIT_INFO table
Field Name	Type	Special restrictions
COLLECTION_ID	CHAR(16)	Collection ID.
ARCHIVE_DATE	TIMESTAMP	Time of archiving.
APPLID	CHAR(8)	CICS® region applid.
HOMESYSID	CHAR(4)	SYSID of local region.
TRANSID	CHAR(4)	CICS® transaction ID.
PROGRAM	CHAR(8)	Currently active CICS® program.
FUNCTION	CHAR(24)	CALL.
TYPE	CHAR(24)	EXIT.
LAST_RUN	TIMESTAMP	Time of latest observation, in the local time format.
TRUE_NAME	CHAR(8)	The TRUE exit program name.
PRODUCT_INFO	CHAR(50)	The product name.