Real-time exclusion processing

While real-time analysis is never performed if the primary subsystem (JES) is unavailable, there are a number of ways to selectively exclude various elements of the Fault Analyzer processing, as illustrated in Real-time exclusion processing overview.

Notes:

❶

By providing an allocation of DDname IDIOFF to the abending job step, Fault Analyzer processing is immediately terminated without producing an analysis report or writing a history file fault entry. You can do this, for example, adding the following JCL statement in your JCL:

//IDIOFF   DD      DUMMY

Allocating IDIOFF is the quickest way to prevent Fault Analyzer from running for a particular job step, and the one which is recognized with the least amount of overhead.

Note: In the z/OS Unix System Services environment, setting the environment variable _IDI_OFF to "Y" is equivalent to using the IDIOFF DDname switch. For more information, see Turning off Fault Analyzer using an environment variable (_IDI_OFF).

❷

If calling IDISNAP from within your application (see Using the program SNAP interface (IDISNAP)), then no further exclusions are available prior to options processing being performed.

❸

If fast Exclude options processing is enabled, and the job is eligible (see Fast Exclude options processing), then a matching Exclude option (see Exclude/Include) can be used to terminate Fault Analyzer processing early.

❹

Additional invocation exit exclusions are provided for CICS® transaction abends only.

❺

If the CICSDumpTableExclude option is in effect (see CICSDumpTableExclude), and the CICS® transaction abend that is associated with the fault is specified in the CICS® transaction dump code table to not require a CICS® dump, no further processing is performed. That is, no analysis report is produced and no fault entry is written.

❻

If either of the following is true, processing terminates for the current fault:

The NODUP(CICSFAST(…)) option specifies a non-zero number of minutes, and the criteria used for determination of duplicate CICS® transaction abend fault entries match.
The NODUP(IMAGEFAST(…)) option specifies a non-zero number of minutes, and the criteria used for determination of duplicate IMS™ transaction abend fault entries match.

Although no analysis report is produced and no history file fault entry is written, the duplicate count is still updated in the history file cache against the fault entry when the next non-duplicate fault entry is written.

For details about these fast duplicate detection options, see NoDup.

❼

The EXCLUDE option (see Exclude/Include) can be used to terminate Fault Analyzer processing once the options have been read in the mainline code.

❽

Prior to writing the history file fault entry, the NODUP(NORMAL(…)) option is checked. If the option specifies a non-zero number of hours and the criteria used for determination of duplicate fault entries match (see NoDup), then processing terminates for the current fault. The real-time report is written to IDIREPRT, but no history file fault entry is created.

Note that the NODUP(NORMAL(…)) option applies to all fault entries, including CICS® transaction abend faults.

Unless Fault Analyzer processing is excluded using the IDIOFF DDname switch, then an SMF type 89 record is written to indicate Fault Analyzer usage.