Study the figures to help you understand how the affinity-related
components of CICS® IA relate
to each other.
Refer to
Figure 1 for
the Collector structure.
Figure 1. The reporting
structure of the CICS IA affinity-related
components
CICS IA includes
these affinity-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 potential affinities created by the commands
- The resources used 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 Affinity database objects
- The Affinity database objects contain data extracted from the
VSAM affinity files 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 provides
a graphical front end to CICS IA. For
more information about the CICS IA
plug-in, see
the Analyzing CICS IA data using the CICS IA plug-in for CICS Explorer section in the IBM® CICS Explorer® User Guide
.
- The Affinities Reporter
- The
Affinities Reporter is
a batch utility that you can use to do any of the following:
- Convert the affinity data in the Affinity database objects into
reports in a readable format.
- Convert the affinity data in the VSAM files into reports in a
readable format. You might use this function if, for example, you
do not have DB2®.
- From the affinity data, in the Affinity database objects, create
a file of affinity-transaction-group definitions in a syntax approximating
to the batch API of CICSPlex® SM.
This file is intended as input to the Builder component.
- The Builder
- The
Builder is a batch utility that takes as input the file of basic affinity-transaction-group
definitions created by the Affinities Reporter. It
produces a file of "combined" affinity-transaction-group definitions
suitable for input to CICSPlex SM,
which requires that a specific CICS transaction
ID (TRANSID) is in only one transaction group.