Stacking Application-Level library requests
Application-level REXX exec and CLIST requests can be stacked up to eight requests each. Because the application-level requests are stacked, you can activate a REXX exec or CLIST and then reissue the request for the same REXX exec or CLIST and the first request will still exist. When you stack application-level library requests for REXX execs or CLISTs, the last application level you activate becomes the current one. Only the top, or current application-level request is active.
For example, if you activate an application-level CLIST,
altlib activate application(clist) dataset('userid.ds1')
and
then unconditionally activate another application-level CLIST, altlib activate application(clist) dataset('otherid.ds5') uncond
the
second request becomes current and the first request is stacked under
it.If you entered the command, ALTLIB DISPLAY, to display the search
order, the display at your terminal will look similar to the following:
IKJ79322I Current search order (by DDNAME) is:
IKJ79326I Application-level CLIST DDNAME=SYS00027
IKJ79321I Stacked DDNAME=SYS00026
IKJ79327I System-level EXEC DDNAME=SYSEXEC
IKJ79328I System-level CLIST DDNAME=SYSPROC
Deactivate the application-level for CLIST to remove the second
request and make the first request current. Or, you can clear all
requests and reset the original library search order. For example,
to clear only the current request issue:
altlib deactivate application(clist)
To clear all stacked application-level requests and leave the user
and system levels as they are, issue:
altlib deactivate application(*)