IBM Mainframe Discussion List <[email protected]> wrote on 04/19/2006
02:44:28 PM:
>
> Thoughts to mitigate, but not all prevent the problem include:
> 1) Overallocation of PDSEs.
> 2) Allowing secondary allocation (and the LNKLST can of worms that
opens).
> 3) Converting IBM PDSEs back to PDS (with each version - annually
here).
You cannot do this. IBM PDSEs may contain members which use program
object functions that are not available in a PDS.
> 4) Removing PDSE's from IPL LNKLST, then adding dynamically. The APARs
> mentioned indicate theses PDSEs would be deletable. What if
> something required early in IPL (SYS1.LINKLIB) becomes PDSE???
SYS1.LINKLIB will not become a PDSE. When linklib module wants or
needs to be a program object, to goes into PDSE SYS1.SIEALNKE.
But we expect SYS1.SIEALNKE to be in the IPL time LNKLST.
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
