After you write the function and subroutine code and the directory, you must define the directory name in the function package table. The function package table contains information about the user, local, and system function packages that are available to REXX execs running in a specific language processor environment. Each environment that is initialized has its own function package table. Function package table describes the format of the table.

If you name your local function package directory IRXFLOC and your user function package directory IRXFUSER, the external functions and subroutines in your package are then available to execs that run in non-TSO/E, TSO/E, and ISPF. There is no need for you to provide a new function package table.

If you provide a system function package or several local or user packages, you must then define the directory name in a function package table. To do this, you must provide your own function package table. You must also provide your own IRXPARMS, IRXTSPRM, and/or IRXISPRM load module depending on whether you want the function package available to execs running in non-TSO/E, TSO/E, or ISPF.

You first write the code for the function package table. You must include the default entries provided by TSO/E. The IRXPARMS, IRXTSPRM, and IRXISPRM modules contain the default directory names IRXEFMVS, IRXFLOC, and IRXFUSER. In addition, the IRXTSPRM and IRXISPRM modules also contain the default IRXEFPCK directory name. Function package table describes the format of the function package table.

You must then write the code for one or more parameters modules. The module you provide depends on whether the function package should be made available to execs that run in ISPF only, TSO/E only, TSO/E and ISPF, non-TSO/E only, or any address space. Changing the default values for initializing an environment describes how to create the code for your own parameters module and which modules you should provide.