Welcome
CICS® IA External Interfaces
The Appendix describes available Stored Procedures and Command Flow user exit.
Db2® Stored Procedures
You can use the CICS® IA External Interfaces to directly access different types of collected data from you application.
Stored Procedures for Application Deployment
In CICS® IA 5.5, there are four new stored procedures that are currently used exclusively by the CICS IA Explorer plug-in.

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
CICS® IA security
CICS® IA External Interfaces
The Appendix describes available Stored Procedures and Command Flow user exit.
- Db2® Stored Procedures
  You can use the CICS® IA External Interfaces to directly access different types of collected data from you application.
  - CIUSPAPP Stored Procedure
    With the help of this CICS® IA External Interface, you can access saved dependency data directly from your application.
  - CIUSPAFF Stored Procedure
    With the help of this CICS® IA External Interface, you can access saved affinity data directly from your application.
  - CIUSPCFL Stored Procedure
    You can delete the command flow data from the CICS® IA command flow Db2® tables using the CIUSPCFL stored procedure.
  - CIUSPDEL Stored Procedure
    You can delete the interdependency data from the CICS® IA interdependency Db2® tables using the CIUSPDEL stored procedure.
  - CIUSPDPG Stored Procedure
    By using the CIUSPDPG stored procedure you can list and then delete records from CICS® IA Db2® tables, which might contain information about old version of programs.
  - CIUSPTSR Stored Procedure
    With the help of this CICS® IA External Interface, you can produce threadsafe reports directly from your application.
  - CIUSPAP1 Stored Procedure
    When you use the CIUSPAP1 stored procedure you can view or delete resource information for a CICS® TS application definition.
  - CIUSPPUR Stored Procedure
    When you use the CIUSPPUR stored procedure you can access saved dependency data directly from your application.
  - Stored Procedures for Application Deployment
    In CICS® IA 5.5, there are four new stored procedures that are currently used exclusively by the CICS IA Explorer plug-in.
    - CIUSPEPS Stored Procedure
      CIUSPAPP is a stored procedure that you can use to identify and group your application entry points by the resource used. The type of resource that is used can be any CICS®, Db2, MQ or IMS resource.
    - CIUSPEP2 Stored Procedure
      CIUSPEP2 is a stored procedure that you can use to identify your application entry points for a transaction, program, or web service and group them by the type of the resources they use.
    - CIUSPEP3 Stored Procedure
      CIUSPEP3 is a stored procedure that you can use to identify your application entry points for an existing platform, application, or Operation.
    - CIUSPDEP Stored Procedure
      CIUSPDEP is a stored procedure that returns a list of application dependencies, which can be added to a CICS Bundle that is then used to define a CICS Application. CIUSPDEP can be called against a PLATFORM, an APPLICATION, or an OPERATION. It returns information about your CICS, Db2, and MQ dependencies.
- The CICS® IA Command Flow user exit
  The CICS® IA Command Flow user exit provides additional options when you are saving information about the traced commands into the dataspace.
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

Stored Procedures for Application Deployment

In CICS® IA 5.5, there are four new stored procedures that are currently used exclusively by the CICS® IA Explorer plug-in.

The new stored procedures are provided to assist you to identify:

Your CICS Application entry points
Your CICS Application Dependencies

A short description is provided for these new stored procedures. You need to obtain this information when you start to deploy the new Platform and Application concepts that are introduced in CICS® IA 5.1, onwards. These stored procedures are shipped in the NATIVE format only and can be used only if your CICS® IA database is using Db2 9.1, or later.