What the Collector can monitor
The commands or calls that the Collector can monitor are listed. The commands or calls that the Collector actually monitors depend on how it is configured.
For more information about configuring the Collector, see Controlling the Collector and What the Collector does not monitor.
- The EXEC CICS API commands, listed in CICS API commands, that can cause transaction dependencies
- The EXEC CICS SPI commands, listed in CICS SPI commands, that can cause transaction dependencies
- The CICS Front End Programming Interface (FEPI) API commands, listed in CICS FEPI API commands, that can cause transaction dependencies
- The CICS FEPI SPI commands, listed in CICS FEPI SPI commands, that can cause transaction dependencies
- The non-CICS API commands, listed in Non-CICS API commands detected, that can cause transaction dependencies
- The EXEC CICS API and SPI commands, listed in Table 1, that can cause transaction affinities
- The dynamic COBOL calls that are detected by the Dependency
and Command Flow Data collectors for the IBM COBOL for OS/390 and
IBM VS COBOL II programs if the CBLPSHPOP Language Environment® option
is active. The Language Environment option ALL31(ON/OFF) is supported
for dynamic calls from IBM COBOL for OS/390 programs.
For more information about the CBLPSHPOP option, see Language Environment CBLPSHPOP option in the CICS TS 5.2 Knowledge Center.
For information about the detection of dynamic COBOL calls, see Collecting dynamic COBOL calls.
For information about what the Collector reports for each monitored command, see Details of dependencies and affinities collected.
As well as monitoring program commands, the Collector also collects information about the CICS regions on which it runs and stores that information in the CIU_REGION_INFO database table. For example, for each collection of dependency or affinity data, the table contains the names of the CICS System Definition data set (CSD) and the first four resource group lists in the CSD.