The Collector component

You can use the Collector in real-time to detect transaction resource definitions and transaction affinities in a running CICS® region.

You can collect both dependency data and affinity data on the same region at the same time.

The Collector saves details of the dependencies or affinities in an MVS™ data space. This data is subsequently saved to storage. The details of the Command flow are saved in the CICS Journal Log Stream. The Collector consists of:

The Collector components are shown in Figure 1.
Figure 1. Collector components
The picture shows the collector components described in the preceding text.

Dependency data is collected by global user exit programs at the exit points. Affinity data is collected by the task-related and global user exit programs. Command Flow data is collected by the task-related and global user exit programs. The exit programs coexist with any other exit programs that are invoked at the same exit points.

You are recommended to place the CICS IA exit programs after any other exit programs that are invoked at the same exit points and make them the last to be enabled. This enables CICS to capture, where applicable, the correct remote SYSID associated with resources such as programs, files, TS queues, TD queues, and transactions.

Where more than one global user exit program is invoked from the same global user exit point, the order in which the programs are invoked is the order in which they are activated by EXEC CICS ENABLE commands. For more information, see "Invoking more than one exit program at a single exit" in the CICS Customization Guide.

Run the Collector in stable CICS regions only. Do not apply maintenance to application programs while the Collector is running. Such maintenance could introduce or remove dependencies or affinities, thus rendering collected data inaccurate.


Concept Concept

Feedback


Timestamp icon Last updated: Friday, 7 February 2014


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///ciuug06.html