To install an ISPF installation-wide exit:

1. Indicate in installation tailoring that ISPF installation-wide exits are defined. When you install ISPF, you indicate that exit routines might exist by setting the ENABLE_ISPF_EXITS keyword in the ISPF Configuration table to YES. As a result, you can replace, add, or remove exit routines by simply reassembling ISPXDT and relinking ISPEXITS. Otherwise, ISPF uses the default value of NO and does not load the ISPEXITS module. In this case, you cannot invoke any exit routines and you have to repeat part of the installation process if you want to change this value. See The ISPF Configuration Table for more information.
2. Use the exit macros to assemble the exit definition table (ISPXDT). This process is discussed in detail in Exit macros. These macros reside in ISP.SISPMACS.
3. Link-edit the ISPEXITS load module. ISPXDT is the main entry point of this module. There is no need to include any other ISPF-supplied CSECTS in ISPEXITS. Figure 1 contains sample JCL to link-edit ISPEXITS.
   Figure 1. Sample JCL to Link-Edit ISPEXITS

   //LKED EXEC PGM=IEWL,REGION=1024K,
   // PARM='XREF,LET,LIST,RENT,SIZE=(512K,128K)'
   //SYSPRINT DD SYSOUT=A
   //SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,5))
   //SYSLMOD DD DISP=SHR,DSN=ISP.SISPLOAD
   //* All exit routines and ISPXDT CSECT must be in SYSLIB,
   //* but an INCLUDE SYSLIB statement is only required for
   //* ISPXDT and not for the exit routines.
   //SYSLIB DD DSN=ISP.LOCOBJ,DISP=SHR
   //SYSLIN DD *
      ORDER ISPXDT
      ENTRY ISPXDT
      INCLUDE SYSLIB(ISPXDT)
    NAME ISPEXITS(R)
   /*
   //

4. ISPXDT does not contain any executable code. If your exit routines are reentrant, ISPEXITS can be copied into the LPA library. Otherwise, it must be copied into the system link library.

Related references

• Exit macros