Invocation for non-CICS transaction abends

The following exits invoke Fault Analyzer for real-time analysis when an abend other than a CICS® transaction abend occurs (for example, batch and IMS™).

MVS™ IEAVTABX change options/suppress dump exit IDIXDCAP

  • This exit can be used with Language Environment®-based and non-Language Environment-based batch application programs. IDIXDCAP is installed as an IEAVTABX_EXIT dynamic exit (z/OS 2.2 or later is required) and is invoked for all abends requesting an ABDUMP, regardless of whether the job step has allocated a SYSMDUMP, SYSUDUMP, or SYSABEND DDname. Note that IMS pseudoabends that do not request an ABDUMP, will not invoke Fault Analyzer through this exit.

    The use of SLIP with ACTION=NODUMP (for example, a CANCEL command resulting in an Sx22 abend, for which most MVS™ systems have a matching SLIP TRAP) might not prevent Fault Analyzer from being invoked through the IEAVTABX_EXIT. To prevent Fault Analyzer invocation, ensure that the IDICNFxx PARMLIB configuration member includes an Exclude option specification with a list of appropriate abend codes for your installation. A sample list of standard abend codes are included in the sample IDICNFxx parmlib member provided as member IDICNF00 in data set IDI.SIDISAM1.

  • Reanalysis of faults that were captured using this exit can be performed if a minidump was written.
  • LE-enabled abends need to run with TERMTHDACT, specifying the suboption UATRACE, UADUMP, UAONLY, or UAIMM, in the LE options so that LE calls a system dump to activate this exit. All other TERMTHDACT suboption settings skip the IEAVTABX exit invocation and invoke the CEEEXTAN exit (described below) instead.
  • This exit can extract WTO console messages related to the abending job from the master trace table and include these messages in the analysis report.

For information about installing this exit, see Installing the MVS change options/suppress dump exit IDIXDCAP.

Batch Language Environment (LE) abnormal termination CEEEXTAN CSECT exit IDIXCEE and CELQXTAN CSECT exit IDIXCE64

  • These exits are effective only with Language Environment®-based batch (non-CICS) application programs.
  • There is no requirement for a JCL SYSMDUMP DD statement to be allocated for these exits to be invoked.
  • Reanalysis of faults that were captured using these exits can be performed if a minidump was written.
  • Permits instance-specific LE message inserts to be obtained and included in the analysis report.
  • These exits can extract WTO console messages related to the abending job from the master trace table and include these messages in the analysis report.
  • 64-bit LE applications: Because the MVS IEAVTABX change options/suppress dump exit is never invoked for LE-based AMODE64 batch application programs, the IDIXCE64 exit is required in that environment.
  • 31-bit LE applications: If the LE option TERMTHDACT is used with the UATRACE, UADUMP, UAONLY, or UAIMM suboption, then the MVS™ IEAVTABX change options/suppress dump exit is invoked instead of the IDIXCEE exit. In all other cases, Fault Analyzer will only be invoked for LE-based AMODE31 applications if the IDIXCEE exit is installed.
  • If you run both AMODE31 and AMODE64 LE-based applications, you must install both the IDIXCEE and IDIXCE64 exits.

For information about installing this exit, see Installing the Language Environment abnormal termination exits IDIXCEE and IDIXCE64.

Both MVS IDIXDCAP and Batch LE IDIXCEE exits are installed

If both the batch Language Environment® abnormal termination exit IDIXCEE and the MVS™ change options/suppress dump exit IDIXDCAP are installed, then the IDIXDCAP exit intercepts the abend instead of the LE exit if one of the following LE options is in effect:
  • TERMTHDACT(UATRACE)
  • TERMTHDACT(UADUMP)
  • TERMTHDACT(UAONLY)
  • TERMTHDACT(UAIMM)