Two separate user exits can be used to alter routing. These
are referred to as
routing exits. They substitute for the
routing file or the options file or both.
- General routing exit
This user exit is named EZAPPGPR. It changes
JES or VTAM® input parameters
and is invoked before the routing or options data is
read (routing data areas are created.) It can replace the functions
of the routing or options files because you can use it to create the
RDA itself or change the key used to access the files. To invoke EZAPPGPR,
it must be in a library specified by a JOBLIB, STEPLIB, or in the
LNKLIST.
- Specific routing exit
This user exit is user-named and is invoked in one of two ways:
- After the general routing exit completes
- After the Network Print Facility creates
the routing data area
It can modify the RDA or change or augment the data obtained
from those sources. To invoke the specific routing exit, it must be
a LINKLST member of MVS™ PARMLIB
or specified on either the JOBLIB or STEPLIB DD statements.
The name of this exit is user-dependent. It must follow MVS module naming standards, can be up to an
8-byte alphanumeric name and can be defined in the:
- RTDASREX field of the routing data area, via the general routing
exit.
- SREXIT parameter in EZAPPFL TYPE=ROUTING.
- ROUTING EXIT field, as illustrated in Figure 2.
Input record exit
This user exit performs two functions:
- Allows modification of the RDA.
- Allows the alteration of the contents of data to be printed. This
can be used to insert, modify, or delete application data as needed to accommodate output to destined printers.
This exit is invoked for all data-related functions in NPF
processing.
The name of this exit is user-dependent. It must
follow MVS module naming standards,
can be up to an 8-byte alphanumeric name and can be defined in the:
See Using the EZAPPFCD macro to produce the DSECTS
needed for the exits.