Customizing the CICS environment

There are three exit points at which Fault Analyzer can be invoked for transaction abends under CICS®.
XPCABND
Global user exit using program IDIXCX53. This exit is the main exit provided to invoke Fault Analyzer for CICS® transaction fault analysis.
XDUREQ
Global user exit using program IDIXCX53. This exit can be used to invoke Fault Analyzer for CICS® dumps generated from an EXEC CICS® DUMP command.

The analysis performed by Fault Analyzer at this exit point is the same as for the XPCABND exit point.

LE Exit
LE abnormal termination exit using program IDIXCCEE. This exit is only effective with Language Environment®-based application programs when the CEECXTAN exit has been set.
CICS® AKCS abends can be analyzed using this exit, if both of the following are true:
  • The failing program is LE enabled.
  • An entry exists in the CICS® dump table for AKCS, specifying that a transaction dump is to be taken.

The first two of these exits are CICS® global user exit points, and Fault Analyzer is enabled and disabled at these points using CICS® calls. By default, these exit points are not enabled in a CICS® region. They are enabled either by adding an entry to the CICS® PLT (see Adding the required programs to the startup PLT), or by using the supplied CFA transaction once CICS® has initialized (see Controlling CICS transaction abend analysis).

The LE abnormal termination exit, however, requires a modification to LE (see Configuring Language Environment for CICS to invoke Fault Analyzer), and hence its effect is system wide. Fault Analyzer provides a mechanism for controlling the use of this exit at a CICS® region level, but for this mechanism to work, the LE exit must first be enabled system wide. Once enabled at a system wide level, then the initial setting in a CICS® region is enabled.

IDI.SIDIAUTH needs to be added to the DFHRPL concatenation of the CICS® JCL for any of the above exits to be successfully enabled.

To use Fault Analyzer with CICS®, you need to perform the following steps:

  1. Configure Language Environment® for CICS® to invoke Fault Analyzer

    For details, see Configuring Language Environment for CICS to invoke Fault Analyzer.

  2. Define the required programs to your CICS® system

    For details, see Defining required programs to CICS.

  3. Add the required programs to your startup PLT

    For details, see Adding the required programs to the startup PLT.

  4. Add the required programs to your shutdown PLT

    For details, see Adding the required programs to the shutdown PLT.

  5. Define a transaction for Fault Analyzer

    For details, see Enabling dynamic control of analysis of CICS transaction abends.