RefreshExits
The RefreshExits option specifies the types and names of user exits to be invoked during the first batch reanalysis of a dump registration fault entry. Any number of exit names can be specified for a given exit type, and all exits are attempted invoked.
Multiple specifications of the RefreshExits option are cumulative.
- REXX EXECs must be specified as
and be available via the IDIEXEC DDname.REXX(exit_name_1, exit_name_2, …)
- Load module exits must be available via the standard system search path (LPA, LINKLIST, or JOBLIB/STEPLIB JCL statement).
- END
- End Processing user exit. This exit can be used to request suppression of the Fault Analyzer minidump or the update of the entire history file entry. For details, see End Processing user exit (Fault entry refresh).
- 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.
If one or more exits have been specified via the RefreshExits option,
information about the exits is written to the Options in Effect
section
of the analysis report. In this section, all specified exits are listed,
and those of each type that were invoked
(if any) are identified.
Options in Effectsection of the analysis report follows:
Exits:
The following user exits were specified via RefreshExits options.
Type Name Type Invoked
-------- -------- ---- ---------------------
END ABC1 LMOD Yes
This example indicates that a single End Processing user exit (ABC1) had been specified as a load module. This user exit was invoked.