Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Installing the exits z/OS TSO/E Customization SA32-0976-00 |
|
Naming requirements for the exits depend on how you link-edit the
exits. You can link-edit any or all of the exits into the ADFMDF01
load module. If you link-edit the exits into ADFMDF01, you must name
the exits as follows:
You can link-edit any or all of the exits into any default environment module. The default environment module that TSO/E provides is named ADFMDFLT. Your installation may create different default environment modules for different users. You can also link-edit the exits into any of these modules. For information about creating your own environment modules, see Providing multiple default environments. If you link-edit the exits into a default environment module, there
is no restriction on the names of the exits or on the name of the
default environment module. However, offsets into the default CSECT
must contain the addresses of the exits as follows:
Any initialization, stream monitoring, or termination exit you provide within the default environment module overrides the corresponding exit named ADFEXIT1, ADFEXIT2, or ADFEXIT3 in the ADFMDF01 load module. Note: To have a stream monitoring exit, you must have an
initialization exit. A termination exit is not required.
You can place the exits in the same or different load modules, however, all exits in the same load module must have the same AMODE. No other restrictions pertain to where you can place the exits. You can provide ADFEXIT1, ADFEXIT2, and ADFEXIT3 in ADFMDF01, then, for some default environments, you can override any or all of these exits with different exits to customize the monitoring of certain classes of users. For an example of monitoring certain classes of users differently, see Possible uses. Figure 1 shows how Session Manager locates the addresses of the exits during initialization. Figure 1. Overview
of how Session Manager determines which exit to use
|
Copyright IBM Corporation 1990, 2014
|