Using a DSRSEXIT, TERMEXIT, or MAPTEXIT user exit

• DSRSEXIT to manage the redefinition of Db2 VSAM data sets (see Using-DSRSEXIT-to-manage-VSAM-data-set-redefinition)
• TERMEXIT to control updates to BMCHIST, BMCSTATS, real-time statistics, and UPDATEDB2STATS (see Using-TERMEXIT-to-control-BMCHIST-and-statistics-updates)
• MAPTEXIT to create mapping objects for use with DSNUTILB (see Using-MAPTEXIT-to-create-mapping-objects)

This section describes the following information common to all REXX exits that you can use with REORG PLUS:

• Requirements and restrictions
• Variables and return codes

To use a sample REXX user exit from the HQL.LLQSAMP library, copy the appropriate member as the base code for your exit; edit the code if needed, and save the modified exit in your SYSEXEC library. For additional instructions, see the section for the specific exit. 

DSRSEXIT, TERMEXIT, and MAPTEXIT common restrictions

The REXX user exits have the following restrictions:

• REORG PLUS does not permit any TSO commands, such as ALLOC, in a REXX exit.
• You cannot perform a call to another REXX program from within one of your REXX user exit programs. Doing so will cause values in your REXX variables to be lost.

DSRSEXIT, TERMEXIT, and MAPTEXIT common variables and return codes

REORG PLUS communicates with REXX exits through REXX variables. The Variables common to all REXX exits table lists the variables that are common to all REXX exits. For the list of variables unique to a particular REXX exit, see the section about variables for that exit.

Your REXX exit should always return a return code of 0 to REORG PLUS. REORG PLUS uses the REXX variables returned from the exit, not the return code, to determine the intent of the exit. If you specifically code a nonzero return code, REORG PLUS treats it as an environment failure and terminates the job. 

The following table lists the variables that REORG PLUS passes to all REXX user exits. You cannot change the value of any of these variables.