ENV - Common exit environment information

Parameter list version (currently 0005).

Summary of changes:

0003

Support for 6-digit CICS® system abend codes.

0004

Change of LOCK_FLAG from 1 to 2 characters to support fault entry expiration control.

Fault ID.

For an End Processing user exit, and for a Notification user exit when a fault is a duplicate (NFY.NFYTYPE='N' or 'F'), this field contains the duplicate fault ID.

For a Notification user exit when a fault is not a duplicate (NFY.NFYTYPE='C' or 'R'), this field contains the assigned fault ID.

For all other exits, this field is not initialized.

Date of abend in the format YYYY/MM/DD.

Time of abend in the format HH:MM:SS (24-hour clock value).

Real-time execution (Y/N).

Job/started task name.

EXEC program name.

User ID.

ABEND module name. This value identifies the module name where the initial (if more than one) abend occurred.

CICS® transaction ID.

CICS® task number.

Job execution class.

Number of job accounting fields (nnn) (from JCT ACTJNFLD).

Job accounting information (from JCT ACTACCNT).

For job accounting, this field contains a one-byte length field, followed by the content of the field (repeated as many times as the number of fields shown in ENV.ACCOUNTING_FIELDS).

Any non-printable characters (such as the binary field length value) are shown as periods.

User field 1. This field can be used to pass information from one user exit to another. Fault Analyzer does not reinitialize this field between calls to user exits and no upper case translation is performed. Truncation by null character (X'00') of this field is not permitted.

User field 2. Same as USER_1.

Refer to LoopProtection for more information about this option.

This option can be modified by any user exit.

Write routine entry-point address.

Job/started task step name.

JES job ID.

IMS™ program name. This name is available if the environment has a DFSPRPX0 module loaded.

User name field.

User title field.

Application ID. Only applicable to CICS® transaction faults (ENV.JOB_TYPE = C) and when ENV.VERSION is greater than 1, in which case it contains the associated CICS® APPLID.

CICS® terminal ID.

CICS® terminal netname.

CICS® CSA address.

This field is only available for CICS® transaction abend or CICS® system dump analysis.

CICS® TCA address.

This field is only available for CICS® transaction abend analysis.

Fault history file name.

This field is not used for any IDIUTIL batch utility user exits. For all other user exit types, this field is initialized by Fault Analyzer to the history file name provided via the IDIHIST DDname (either preallocated or via the DataSets option).

During real-time processing, an Analysis Control or End Processing user exit might choose to change this data set name to that of another history file, which is subsequently used instead. For all other user exit types or processing modes, this field is read-only.

For a Notification user exit invoked for a duplicate fault (NFY.NFYTYPE='N' or 'F'), this name is the name of the history file in which the duplicate fault identified by ENV.FAULT_ID was found.

Total CPU time used by Fault Analyzer in 1/100s of a second at the end of generating the analysis report.

CICS® release level in VnnRnnMnn format

DB2® release level in VnnRnnMnn format

IMS™ release level in VnnRnnMnn format

z/OS® release level in VnnRnnMnn format

Fault entry lock flag. The purpose of this flag is to provide a mechanism that prevents accidental deletion of the current fault entry. For more information about this flag, including specification of fault entry expiration control, see Viewing fault entry information.

Changes to this field are only reflected in the history file fault entry when an Analysis Control user exit is invoked during real-time analysis processing, or when creating a new fault entry from interactive reanalysis of an MVS dump data set.

By default, the lock flag is set to a blank, which does not prevent deletion of the fault entry.

The final value of the lock flag is subject to any changes made by the IDIXLOCK lock flag control exit. See Controlling fault entry lock flag values.

Total number of duplicates, not including the current fault.

This total is determined by accumulating all instances of duplicate recorded faults, in the same history file, going back as far as the NoDup(Normal(…)) time period in effect. Any recorded faults encountered whose duplicate criteria match the current fault account for one instance, and if duplicates have been recorded against the fault, the duplicate count of that fault are also added.

Point-of-failure module name.

Point-of-failure module link-edit date in the format YYYY/MM/DD.

Point-of-failure module link-edit time in the format HH:MM:SS.

Point-of-failure CSECT name.

Point-of-failure entry-point, program/CSECT or load module offset (decimal).

Data set name from where the point-of-failure program was loaded.

Data set name from where the EXEC program was loaded.

Date of most recent duplicate fault in the format YYYY/MM/DD.

Time of most recent duplicate fault in the format HH:MM:SS (24-hour clock value).

Security server default group ID.

Number of minidump pages (nnnnnnnnnn).

The IDIRLOAD DDname. During initial RFR fault entry reanalysis initiated by an I or B line command on the Fault Entry List display, if the STEPLIB or JOBLIB data set concatenation was saved, then Fault Analyzer allocates the STEPLIB or JOBLIB concatenation to a system-generated DDname (SYSnnnnn) and initializes this field with that DDname. The purpose of this is to automatically facilitate the Binder CSECT mapping that could not be performed during the real-time analysis.

In all other cases, this field is initialized by default to IDIRLOAD.

Upon return from the Analysis Control user exit, Fault Analyzer will use any data sets that are allocated to the DDname specified in this field as the IDIRLOAD allocation. For more information, see Using the IDIRLOAD DDname for CSECT mapping.

Changes made to this field by user exit types other than Analysis Control are ignored.

The specified DDname is not case sensitive.

Hexadecimal reason code that is associated with ENV.ABEND_CODE.

Available to all user exits that run following "Analysis" processing as per Fault Analyzer analysis exit points (IDIDA).

The user ID who last changed the ENV.LOCK_FLAG field.

Date of original fault in the format YYYY/MM/DD.

Time of original fault in the format HH:MM:SS (24-hour clock value).

The type of dump data set associated with this fault entry, as one of the following:

P

SLIP dump

S

SDUMP (SVC dump)

T

TDUMP (transaction dump)

X

XDUMP (extended dump)

The name of the dump data set associated with this fault entry.