Special Monitoring Situations › Special Monitoring Situations › Monitor Programs with LE/370 Condition Handlers

Monitor Programs with LE/370 Condition Handlers

LE/370 condition handlers do not receive control in the same manner as a normal CICS COBOL program. Therefore, they must be monitored using the CA InterTest Segmented Monitoring and ABI=OFF options.

To monitor COBOL/370 programs containing calls to enable or disable LE/370 condition handlers, perform these steps:

1. Use normal monitoring.
2. Specify ABI=OFF for the main program, and if there is a composite module, for all subprograms.

   Note: Do not specify ABI=OFF for the LE/370 condition handler module if you want CA InterTest for CICS to intercept abends that occur within the LE/370 condition handler. ABI=OFF is needed for all programs except the condition handler to prevent CA InterTest for CICS from intercepting the abend before the LE/370 condition handler is invoked.

Because LE/370 condition handlers do not receive control the same way a normal CICS program does, you must start and stop monitoring for the condition handler routine or program by using the Segmented Monitoring breakpoint options (+ and ‑). For example, use the Source Listing facility to display the condition handler routine or program, and then set a start monitoring (+) breakpoint at the first statement number, which causes CA InterTest for CICS to begin monitoring when the condition handler is invoked by LE/370. Set normal breakpoints, such as unconditional, conditional and so on, in the condition handler program. For details on segmented monitoring, Segmented Monitoring to Handle Special Situations.

You must set a stop monitoring breakpoint (‑) before or at the GOBACK statement of the condition handler or unpredictable results might occur.