What the Collector does not monitor
The program commands or calls that the Collector does not monitor are listed.
- The Collector is not running.
- The issuing program was translated with the SYSEIB option. An
exception is the EXEC CICS® PUSH HANDLE command. Monitoring these commands enables CICS IA to
capture dynamic COBOL calls. When it captures dynamic COBOL calls, the Collector can record the name of the enclave program and an undefined command offset under one of the following conditions:
- The called program does not conform to the LE prolog and LE linkage conventions.
- The ADABAS or Natural program request is received.
- The DBCTL request that relates to the recorded EXEC DLI command is received.
For more information about the detection of dynamic COBOL calls, see Collecting dynamic COBOL calls.
- The CICS IA Collector does not capture dynamic calls to PL/I and Assembler programs.
- The CICS IA Collector does not capture dynamic calls from PL/I and Assembler, including calls to COBOL programs.
- The CICS IA Collector correctly captures the EXEC CICS commands in the called programs.
You are collecting interdependency data and the CICS command is not a command that is specified in the command exclude list. See Creating a command exclude list.
- You are collecting interdependency data and the command is not one that can cause transaction resource dependency.
- You are collecting affinity data and the command is not one that can cause transaction affinities.
- The program is a DB2® or DBCTL task-related user exit.
- The program is a CICS user-replaceable program.
- The program issues a CALL to named COUNTERS.
- The transaction identifier does not match the prefix, if specified, for transactions to be monitored. See Specifying region-specific options: General.
- The command is not in the relevant subset of command
types that is specified to be monitored. These subsets are as follows:
- Dependency-related CICS commands. See Specifying region-specific options: API and SPI commands to be monitored.
- Dependency-related CICSPlex® SM, DB2, IMS™, and MQ commands. See Specifying which dependency-related CICSPlex SM, DB2, IMS, and MQ commands are to be monitored.
- Affinity-related CICS commands. See Specifying which affinity-related CICS commands are to be monitored.
- The first few letters of the program name match a prefix
in the list of "excluded" program prefixes, which identify programs
for which data is not to be collected. See Creating a program exclude list.
The default program exclude list excludes programs with names that start with ABL, CAU, CBM, CEE, CIU, CME, CPA, CSQ, DFH, DSN2, DSNC, DWW, EDC, EQA, EYU, IBM®, IN25, IGZ, ISZ, or VID.
- The first few letters of the transaction name match a prefix in the list of "excluded" transaction prefixes, which identify transactions for which data is not to be collected: see Creating a transaction exclude list.
- The command causes an unhandled abend.
The Collector does not monitor pseudoconversations in which you continue a pseudoconversation by setting a transid in the TIOA rather than by using RETURN TRANSID.
Ideally, CICS IA will ignore commands issued by task related user exits and global user exits because they are not part of applications. However, it cannot distinguish such commands from others, and does monitor them. If your user exits use commands that can cause transaction dependencies, the commands are monitored, perhaps making any dependency problem seem worse than it actually is.