Data areas

The following provides descriptions of data areas available to user exits. For information about user exits, refer to Customizing Fault Analyzer by using user exits.

Softcopy versions of the following data areas are available in the softcopy samples data set (IDI.SIDISAMP) for Assembler, COBOL, C, and PL/I as members IDISXPLA, IDISXPLB, IDISXPLC, and IDISXPLP respectively.

Notes relating to the following data areas:
  • The 'Access' column provides information about a user exit's ability to update individual fields as follows:
    Read/write. These fields can be updated by the user exit.
    Read only.
  • Numerical fields are identified by '(nnn)' and are, on input to the user exit, always padded on the left with zeroes to the total width of the field.
    Note: Leading zeroes are generally not included in data area fields provided to REXX user exits.
  • All fields for which Fault Analyzer does not provide an initial value are initialized to blanks.
    Note: Blank-padding is generally not included in character-format data area fields provided to REXX user exits, unless the fields might contain hexadecimal characters.
  • Unless otherwise indicated, all fields are translated to upper case by Fault Analyzer.
  • Unless otherwise indicated, all R/W fields can be truncated using a null character (X'00') as delimiter. Truncation is never used by Fault Analyzer when initializing the parameter lists.
  • For COBOL, substitute all underscores ('_') with dashes ('-').
To see the initial values of any of these fields for an abending job, add the following JCL statements to produce an exit trace:
where exit_type is either CONTROL, LISTING, FORMAT, REPORT, MSGXPL, END, or NOTIFY, depending on the data area that you are interested in. For more information about tracing, see Diagnostic tracing. For more information about the Exits option, see Exits.