Installing Resource Processors

You must write and install whatever unauthorized resource processors you require; they are not supplied by TSO/E nor do they have pre-determined names. You pass the name of the resource processor in parameter 2 when your application invokes the IKJURPS service.

You can link-edit all resource processors in a separate load library that is exclusively for TSO/E resource processors or in an existing library that contains other routines. Resource processors can reside in:

STEPLIB: A step library is helpful for limited use and for testing the exit before you integrate it into your system. In this case, you can easily change the exit. However, the use of a STEPLIB is not suggested for all of your users because of the extra search time required to locate and invoke the exit.
LPA: The link pack area makes the resource processors available to all of your users. However, if you need to change the processor and make the changes available in LPA for all of your users, you must re-IPL your system.
LNKLST: The linklist concatenation makes the resource processors available to all of your users while maintaining the ability to easily change the processor if required.

The search order is STEPLIB, LPA, and then LNKLST. For more information about STEPLIB, LPA, and LNKLST, refer to z/OS MVS Initialization and Tuning Guide.

You might also consider using System Modification Program Extended (SMP/E) when installing unauthorized resource processors. SMP/E allows you to maintain a record of the resource processors you have installed. To use SMP/E you must generate your own functional module ID (FMID) and be certain that is does not duplicate any IBM-defined FMID. For more information about SMP/E, refer to SMP/E for z/OS Commands or SMP/E for z/OS User's Guide.