PIE®/TSO-DynamicSteplib

With PIE/TSO-DynamicSteplib, you can change the following:

• STEPLIB
• ISPLLIB
• Any current allocation

You can add datasets before or after your current concatenation and can completely replace your STEPLIB or ISPLLIB concatenation. You can even eliminate your STEPLIB or ISPLLIB altogether.

PIE/TSO-DynamicSteplib improves performance, both for your logon and for the system as a whole. Searching the STEPLIB is a resource intensive process. So it is critical to make the STEPLIB as small as possible. Yet you have scores of applications. You certainly don't want all of them in the LPA and link list. So, to be run, the applications have to be in the STEPLIB. With TSO alone, these applications have to be added to the STEPLIB in the logon procedure. If you put the dataset for every application in the STEPLIB of the general logon procedure, it can take a long time and a lot of resources to finally find an application toward the bottom of the list.

You can alleviate this problem by creating a customized logon procedure for each user that includes only the datasets the user needs. But this is a maintenance headache most installations aren't willing to suffer.

Streamlining STEPLIBs improves performance for each user, because the search times are minimized. It also improves performance of your whole system, because these small decreases compound to a substantial savings. If you run PIE/TSO-MultiTSO, you can have different STEPLIBs for each session. As you switch from session to session, application to application, PIE/TSO-DynamicSteplib activates the appropriate STEPLIB for that environment.

Right now, with all your datasets allocated in the general logon procedure, one person is responsible for administering all datasets changes for all applications. Using PIE/TSO-DynamicSteplib, you can allocate these datasets in individual CLISTs or REXX EXECs, and delegate datasets administration to the person responsible for maintaining each application.