Deciding which exits to use

The following are the SMF-supplied exits along with a summary of when each exit receives control, the information passed to each exit, and the type of return from each exit to the control program. They can link to installation-written exit routines. For complete information about these exits, see z/OS MVS Installation Exits.

The termination exit (IEFACTRT) receives control on the normal or abnormal termination of each job step and job. A return code from this exit indicates whether the system is to continue the job (for job steps only) and whether SMF termination records are to be written to the SMF data set. The parameters passed to this exit are the addresses of:
- The common exit parameter area
- The job step name
- The programmer name
- The job CPU time
- The job accounting fields
- The step CPU time
- The step accounting fields
- The completion code
- The SMF termination record
- The name of the subsystem for the job being processed.
The user account validation exit (IEFUAV) receives control during the set-up and execution of APPC/MVS transaction programs (TPs), and during the creation of a z/OS® UNIX System Services forked or spawned address space whose profiles specify TAILOR_ACCOUNT(YES). IEFUAV is used to validate the accounting information of TP users and forked and spawned address spaces. Note that IEFUAV does not receive control for local spawns, as these only create processes in the same address space as the parent. A return code from this exit routine indicates whether processing for the unit of work should continue or be cancelled.
The parameters passed to this exit are the addresses of the common exit parameter area, an area containing the programmer's name, an indication of the processing environment (Exit Function Code), accounting information, and an 80 byte area into which the exit can place a message to be issued to the APPC/MVS or z/OS UNIX System Services job log.
The job initiation exit (IEFUJI) receives control before a job on the input queue is selected for initiation. A return code from this exit indicates whether the system is to continue processing the job. The parameters passed to this exit are the addresses of the common exit parameter area, programmer name, job priority, job accounting fields, and the name of the subsystem for the job being processed.
The job purge exit (IEFUJP) receives control when a job is ready to be purged from the system (after the job has terminated and all SYSOUT output that pertains to the job has been written). A return code from this exit indicates whether the SMF job purge record (type 26) is to be written to the SMF data set. The parameters passed to this exit are the addresses of the common exit parameter area, and SMF job purge record.
The job validation exit (IEFUJV) receives control before each job control statement in the input stream or cataloged procedure is converted. This exit receives control after all the JCL is converted and again after all the JCL is interpreted. IEFUJV is not invoked for JCL comment statements or null statements. A return code from this exit indicates whether the system is to continue processing the job. For an alternative to IEFUJV, examine JES exits in z/OS JES2 Installation Exits and z/OS JES3 Customization.
The parameters passed to this exit are the addresses of:
- The common exit parameter area
- The JCL statement image (this address is zero for entry codes 16 and 32)
- The entry code (type of JCL statement for all entry codes except 16 and 32)
- The converter parameter
- The name of the subsystem for the job being processed
- The environment indicator associated with the subsystem for the job being processed
The step initiation exit (IEFUSI) receives control before each job step is started (before allocation). A return code from this exit indicates whether the system is to continue processing the job step, or whether the job is to be cancelled. The parameters passed to this exit are the addresses of:
- The common exit parameter area
- The job step name
- The program name
- The step accounting fields
- An area which the exit can use to communicate to MVS™ the region size and region limit it desires for the job step
- A flag indicating whether the job is running V=R
- IBM-supplied default values for data spaces, hiperspaces, and data sharing (through the IARVSERV macro)
- The name of the subsystem for the job being processed
- MEMLIMIT information.
The SYSOUT limit exit (IEFUSO) receives control when the number of records written to an output data set exceeds the output limit for that data set. A return code from this exit indicates whether the system is to continue processing the job with a new output limit or to cancel the job. The parameter passed to this exit is the address of the common exit parameter area.
The time limit exit (IEFUTL) receives control when one of the following time limits expires:
- The job CPU time limit (from the JOB statement).
- The step CPU time limit (from the EXEC statement, the default from the job entry subsystem).
- The continuous wait time limit for the job (from the SMFPRMxx JWT, SWT, or TWT parameters). Continuous wait time is defined as time spent waiting while the application program is in control. For example, for data sets allocated dynamically (while the application program is running, for example) either or both of the following count toward a job's continuous wait time:
  - The time required to recall a data set from HSM Migration Levels 1 or 2
  - The time required to mount a tape
  If a data set was allocated statically (that is, for a DD statement) only the second of these activities will be counted towards the job's continuous wait time.
A return code from this exit indicates whether the system is to continue processing the job step with a new time limit or cancel the job. The parameters passed to this exit are the type of time limit that expired, and the addresses of the common exit parameter area, and the name of the subsystem being processed.
The SMF dump exit (IEFU29) receives control when an SMF data set becomes full. A return code from this exit indicates whether the dump message (IEE362I or IEE362A) is to be issued. The parameter passed to this exit is the address of SMF data set name.
The SMF log stream dump exit (IEFU29L) allows you to archive SMF from a log stream. This exit is invoked using the SWITCH SMF command. The parameter passed to this exit is the address of a 44-character field that contains the name of the SMF log stream to be dumped. This field is left-justified and padded on the right with blanks.
The SMF record exit (IEFU83) receives control before each record is written to the SMF data set. A return code from this exit indicates whether the system is to suppress the current SMF record. The parameter passed to this exit is the address of the SMF record to be written.
The SMF record exit (IEFU84) receives control when the SMF writer routine is branch-entered and is not entered in cross-memory mode. A return code from this exit indicates whether the system is to suppress the current SMF record. The parameter passed to this exit is the address of the SMF record to be written.
The SMF record exit (IEFU85) receives control when the SMF writer routine is branch-entered and is entered in cross-memory mode. A return code from this exit indicates whether the system is to suppress the current SMF record. The parameter passed to this exit is the address of the SMF record to be written.