CICS IA dependency-related components
CICS® IA comprises a number of components, which divide into collecting and reporting parts. The figures show how the dependency-related components of CICS IA relate to each other.
Figure 1. The Collector
structure of CICS IA components 

Figure 2. The reporting structure of CICS IA dependency-related
components

CICS IA contains
the following dependency-related components:
- The Collector
- The Collector is
a CICS transaction that runs
in your CICS region and intercepts
selected CICS and non-CICS
programming commands. Depending on what you have specified, it records,
in an MVS™ data space, details
of either of the following:
- The resources used by the commands
- The potential affinities created by the commands
You can collect both dependency data and affinity data on the same region at the same time. The dependency data, affinity data, or both are saved to VSAM files.
- The Dependency database objects
- The Dependency database objects contain data extracted from the VSAM dependency file created by the Collector. It is updated periodically to add data from new or infrequently run applications.
- The CICS IA plug-in for CICS Explorer®
- The CICS IA plug-in for CICS Explorer provides a graphical front end to CICS IA. For more information, see the IBM® CICS IA plug-in for CICS Explorer User Guide.
- The Dependency Reporter
- The Dependency reporter is a batch utility that you can use to convert the dependency data in the VSAM files into reports in a readable format. You might use this function if, for example, you do not have DB2®.
- The Load Module Scanner
- The Load Module Scanner is
a batch utility that scans a load module library to detect those programs
in the library that issue commands that might cause either of the
following:
- Transaction resource dependencies
- Transaction affinities