DumpRegistrationExits

Figure 1. Syntax

Exit name specification

The DumpRegistrationExits option specifies the types and names of user exits to be invoked during the IDIXTSEL MVS™ post-dump exit processing.

The dump registration Analysis Control and Notification user exits are driven as the SVC dump data set name is recorded in a history file fault entry for later analysis by the end user. The SVC dumps might have been triggered by abends or Fault Analyzer recovery fault recording (RFR) processing; however, the dump registration exits are not driven for RFR processing. The IDIXTSEL process requires the IDI.SIDISAM1(IDIWTSEL) sample ++USERMOD to be installed (for details, see Installing the MVS post-dump exit IDIXTSEL).

The MVS™ SVC dump registration Analysis Control and Notification user exits run from the Fault Analyzer IDIS subsystem. Therefore, the DumpRegistrationExits option must be specified in the IDICNFxx parmlib member, or via an IDIOPTS DD statement in the IDIS subsystem JCL. The DumpRegistrationExits option is ignored if specified via an IDIOPTS DD statement anywhere else, such as in a CICS® region or batch job.

Multiple specifications of the DumpRegistrationExits option are cumulative.

Exits can be either REXX EXECs or load modules:

REXX EXECs must be specified as
```
REXX(exit_name_1, exit_name_2, …)
```
and be available via the IDIEXEC DDname.
Load module exits must be available via the standard system search path (LPA, LINKLIST, or JOBLIB/STEPLIB JCL statement).

The possible exit types are:

CONTROL: Analysis Control user exit. This exit can be used to modify options in effect. For details, see Analysis Control user exit (MVS SVC Dump registration).
NOTIFY: Notification user exit. This exit can, for example, be used to provide installation-specific notification of recorded faults. For details, see Notification user exit (MVS SVC Dump registration).

The exit name that is specified as exit_name can be any valid TSO/E REXX EXEC or load module name. However, certain names are reserved for special purposes:

NONE: The special name 'NONE' represents a 'null' exit that is not invoked and causes further attempts to invoke exits of the specified type to be terminated.
-DROPCNF-: The special name '-DROPCNF-' is used to drop exit specifications from the IDICNF00 parmlib member. For details, see Dropping IDICNF00 parmlib member user exit specifications.

Any number of exit names can be specified for a given exit type, and all exits are attempted invoked.