EXITS control statement

The EXITS control statement follows the same format as the Exits keyword for real-time analysis and reanalysis. The difference is that the exit points are for LISTHF, DELETE, and IMPORT.

Figure 1. Syntax

1  EXIts ( + , 
1 (
1 exit name specification
1 ) )
exit name specification

1+ ,
2.1 exit_name
2.1  REXX ( + , exit_name )


The exit is driven for every fault entry in the LISTHF or DELETE target data sets that match the specified selection qualifiers, and for the members found in the 'from' data set for IMPORT. In all cases, the UTL.PERFORM_ACTION flag is set to 'Y' by default, except when an HFZUTIL Delete user exit is called for a locked fault entry. In this case, when ENV.LOCK_FLAG is not blank, the UTL.PERFORM_ACTION flag is set to 'N' before passing control to the user exit.

The EXITS control statement remains in effect for any LISTHF, DELETE, or IMPORT control statements that follow, or until a new EXITS control statement is encountered for this run of the utility. The effect of multiple EXITS control statements is not cumulative; the previous exits are cleared on encountering a new EXITS control statement. There are no initial user exits active at the start of HFZUTIL execution and the LISTHF, DELETE, and IMPORT exit points are not recognized in or read from the configuration files used by Z Abend Investigator real time analysis and reanalysis.

A detailed description of each exit type is provided in Customizing Z Abend Investigator by using user exits.

An example showing the use of the EXITS control statement is provided in Example 6. Importing history file entries.