Welcome
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.
Managing the collected data
To manage the data that you have collected, you can delete your unwanted data and keep your data sources in sync.
Deleting by application ID
In CICS® Transaction Server you can deploy applications in a platform. You can define the various resources that make up a business application in CICS as a single entity and deploy these resources to CICS as a single resource.

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.
- Identifying the data that you collect
  You can reduce the amount of data you initially collect by identifying patterns in your resource names, and by using a collection ID to identify the data you load into IBM® Db2®.
- Managing the collected data
  To manage the data that you have collected, you can delete your unwanted data and keep your data sources in sync.
  - Identifying data to delete
    The CICS® IA data that you collect can change, which can lead to redundant records being stored in the database. You can delete data from the database in a number of ways. You can use SQL queries to help you to delete the unwanted data from your database tables, which improves performance.
  - Deleting by collection ID
    You can now delete CICS® IA data from all the dependency tables by using the stored procedure CIUSPDEL, and using a collection ID.
  - Deleting by Command Flow ID
    You can now delete CICS® IA command flow data from the CIU_CMDFLOW_DATA and CIU_CMDFLOW_INDEX Db2 tables by executing the CIUSPCFL stored procedure with the specified command flow ID.
  - Deleting duplicate resources
    You can now delete CICS® IA data from some dependency tables by using the stored procedure CIUSPPUR, and using a prefix of the name for TSQ or ENQ objects. This resource names should consists of a constant prefix and a variable parts.
  - Deleting by application ID
    In CICS® Transaction Server you can deploy applications in a platform. You can define the various resources that make up a business application in CICS as a single entity and deploy these resources to CICS as a single resource.
  - Deleting old versions of programs
    You can delete CICS® IA data from different dependency tables. The tables might contain many records that relate to old versions of a program. By deleting the unwanted records, you reduce the size of your tables and can improve the efficiency of your system.
  - Managing affinity data
    You can capture affinity data by CICS® region, and you can use the affinity data when you want to implement workload balancing across cloned regions.
  - Removing duplicate resources from the Collector files
    You can use the clean up batch utility to remove duplicate resources which minimizes the volume of data stored in the Collector files.
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.3

Deleting by application ID

In CICS® Transaction Server you can deploy applications in a platform. You can define the various resources that make up a business application in CICS® as a single entity and deploy these resources to CICS® as a single resource.

An application that is defined as part of the platform can be managed as a single entity throughout the lifecycle, making CICS® application management faster, easier, and less prone to error. For more information about applications, see Applications in the CICS® TS 5.2 Documentation.

The CICS® IA exits capture application information and associate them with the dependency data and the command flow data that is collected.

You can use the CICS® IA plug-in to delete the data by application and version. Right-click the name of the application for which you want to delete data, then click Delete associated data.