Controlling which jobs are analyzed with Exclude processing

The term "work unit" is used in this section to refer to either a batch job, a started task, or a TSO user.

The Exclude and Include options (Exclude/Include) can be used to select which work unit abends you want analyzed.

If neither option is specified, the default is to include all work units.

It is possible to specify each of these options any number of times to achieve the desired inclusion or exclusion of specific work units. For example, all jobs can be excluded and then only certain jobs included, or if the opposite is desired, all jobs included (the default) and only some jobs excluded.

The selection process is as follows:
  • The initial "state" of work unit selection is to include everything.
  • Each specification of an Include or Exclude option is tested against the abending work unit:
    • If the criteria matches the abending work unit characteristics, then the current state is set to 'include' (if an Include option matched) or 'exclude' (if an Exclude option matched).
    • If the criteria does not match, then the state remains unchanged.
  • If the final state after processing of all Include and Exclude options is 'exclude', then the abending work unit is excluded from analysis. In this case, you get no analysis report, and no fault entry is written to the history file.
    Note:
    1. If you have excluded the real-time analysis, then you cannot later reanalyze, since there is no history file entry.
    2. To make exclusion of analysis 'transparent' to the abending work unit, you might want to consider using the Quiet option. Otherwise, a message is issued to indicate that exclusion has occurred.
It follows from the above that the order in which Include and Exclude options are specified is significant. For example, if the following were specified, all batch jobs executing under the user ID FRED would be included for analysis, regardless of job name or execution class:
Exclude(TYPE(JOB) NAME(TEST*))   /* Exclude all batch jobs with names
                                    starting with TEST */
Exclude(CLASS(Z))                /* Exclude all batch jobs in class Z */
Include(TYPE(JOB) USERID(FRED))  /* Include batch jobs belonging to FRED */
However, if the last two options were reversed as shown, FRED's batch jobs would be excluded if they were executing in class Z:
Exclude(TYPE(JOB) NAME(TEST*))   /* Exclude all batch jobs with names
                                    starting with TEST */
Include(TYPE(JOB) USERID(FRED))  /* Include batch jobs belonging to FRED */
Exclude(CLASS(Z))                /* Exclude all batch jobs in class Z */
Note: Final exclude/include status can be controlled by an Analysis Control user exit (including dump registration) by setting the ENV.EXCLUDE value to "Y" or "N".