What I, personally, think would be "neat" would be some sort of R/O "page data set". It would be something like the LPA. It would be created and updated to basically contain the z/OS nucleus. NIP would simply allocate the fixed real memory for this "nucleus". It would read the data into this memory from this "page data set" . It would then create the page tables necessary to properly map the real memory into shared virtual memory. The "page data set" would actually be maintained by some z/OS "system generation" program from the contents of SYS1.NUCLEUS, plus "anything else" that NIP uses to create the z/OS nucleus. NIP would also read in the HCD infomation for the UCBs et al.
But, again, this will cost up-front money to design and implement. What we have now works; works rather well; and is reliable. What the above is based upon is vaguely based on the VM concepts of NSS or DCSS segments. On Wed, Apr 9, 2014 at 11:03 AM, Paul Gilmartin <[email protected]>wrote: > On Wed, 9 Apr 2014 10:11:46 -0500, Tom Marchant wrote: > > > >Why do YOU need PDSE support at IPL time? > >As far as I know, it makes no sense to _require_ that PDSE support be > available at IPL time. > >If you have a business case, or a requirement for your code, please state > it. > > > I suspect the objective is to eliminate PDS entirely. Simpler is better, > and > PDSE is simpler than PDSE + PDS. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
