Description: Before z/OS V1R13, exits for the DADSM pre-
and post-processing functions were loaded by DFSMSdfp, as installation
exits during initialization, as modules IGGPRE00 and IGGPOST0. Starting
with z/OS V1R13, z/OS dynamic exits services is used to define a
pre-processing dynamic exit, IGGPRE00_EXIT, and a post-processing
dynamic exit, IGGPOST0_EXIT, and associate IGGPRE00 and IGGPOST0
modules as exit routines to these respective dynamic exits. All DADSM
functions (create, extend, scratch, partial release, and rename) share
these common dynamic exits and will be called where the previous installation
exits of IGGPRE00 and IGGPOST0 were called using the same existing
interfaces. This change requires changes to DFSMSdfp operating procedures
and system automation (if any).
Element or feature: |
DFSMSdfp. |
When change was introduced: |
z/OS V1R13. |
Applies to migration from: |
z/OS V1R12. |
Timing: |
Before the first IPL of z/OS V2R1. |
Is the migration action required? |
Yes, if DADSM installation exits IGGPRE00 or
IGGPOST0 are in use. |
Target system hardware requirements: |
None. |
Target system software requirements: |
None. |
Other system (coexistence or fallback) requirements: |
None. |
Restrictions: |
None. |
System impacts: |
None. |
Related IBM Health Checker for z/OS check: |
None. |
Steps to take: Follow these steps:
- If you use the IGGPRE00 or the IGGPOST0 installation exits, you
do not need to change them in any way; just install them as you always
have. DFSMSdfp will automatically exploit the dynamic exit services
and use your IGGPRE00 or IGGPOST0 installation exit as exit routines
to the new IGGPRE00_EXIT and IGGPOST0_EXIT dynamic exits. You do
not need to change the load module names for IGGPRE00 or IGGPOST0,
however, you may change the names if desired. If you do change the
names, update the PROGxx parmlib member or issue the SETPROG command
to get the modules loaded because DFSMSdfp will not load them as exit
routines to the dynamic exits.
- You can now have multiple exit routines associated with each of
the IGGPRE00_EXIT and IGGPOST0_EXIT dynamic exits for the DADSM pre-
and post-processing exits. Other programs can use the CSVDYNEX macro
to associate their exit routines to these dynamic exits and can add
and delete exit routines from any dynamic exit routine as required.
They also can be added and deleted with the PROGxx member of
parmlib and with the SETPROG ADD operator command. All exit routines
will be called when the DADSM pre- and post-dynamic exits are called
from each DADSM function. The execution of one exit routine may then
change the behavior of a subsequent one. The order in which the exit
routines are called by the system could be in any order.
- The IGGPRE00 and IGGPOST0 module addresses in the CVAF table (CVFDPR31,
CVFDPOR31) will continue to be set. Therefore, other programs that
continue to use this interface will be unaffected. Since dynamic
exit services would not be used in this case, no other exit routine
associated with the dynamic exits will be called. These programs should
be changed to use dynamic exit services, CSVDYNEX.
Reference information: To read more about the use of dynamic
exit services and these new dynamic exits, see: