On Thu, Jul 20, 2023 at 02:26:39AM -0500, Willy Jensen wrote: > I for one would be sorry to see the STEPLIB program from CBT file 452 go > away. I find it very useful for packaging applications in separate set of > libraries and then use ISPF LIBDEFs, TSO ALTLIB and the STEPLIB program > to make the neccessary allocations. Sadly ISPLLIB has severe limitations > and TSOLIB cannot be used inside ISPF, unless something has changed since > I last checked. I sure would welcome a built-in TSO STEPLIB equivalent.
What does happen if an open DCB in use as a TASKLIB is closed and reopened (possibly after reallocation)? Could a general completely non-APF command which attached things with a TASKLIB and be able to close/reallocate/open the TASKLIB while the subtask tree was still around? That leaves 2 problems: 1. This leaves the problem of task module fetch requests having to search the TASKLIB for "normal" modules. Perhaps some of the most used modules, if RENT, could be preloaded via LOAD. This doesn't even take extra memory if the module is in LPA... 2. There's still the problem of being unable to execute APF programs (or at least not have the TASKLIB apply to them). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
