On Fri, 15 Sep 2006 20:01:07 -0500, Patrick O'Keefe <[EMAIL PROTECTED]> wrote:
>On Fri, 15 Sep 2006 13:18:24 -0700, Edward Jaffe ><[EMAIL PROTECTED]> wrote: > >>... The start of my LNKLST >>definition (in PROGxx) look like this: >> >>LNKLST DEFINE NAME(IPLTIME) >>LNKLST ADD NAME(IPLTIME) DSN(SYS1.SHASLNKE) VOLUME(&SYSR1) >>LNKLST ADD NAME(IPLTIME) DSN(SYS1.SIEAMIGE) VOLUME(&SYSR1) >>... >>These libraries, as well as those automatically prepended by the system >>(i.e., SYS1.LINKLIB, SYS1.MIGLIB, and SYS1.CSSLIB) are all target >>libraries. Aren't they? You don't have DDDEFs for them in your SMP/E zones? >>... > >For them? No. Same names, certainly, but the volsers in the DDDEFs >point to our maintenance packs. IPL our maintenance packs? No, never! >Well, hardly ever. (Yes, one of our system programming test LPARs often >is IPLed from the maintenance packs.) But when we are running maintenance >those PDSEs in question aren't allocated to anything but SMP so I assume >space reclamation takes place before the maintenance packs are clones. There are many ways to handle maintenance and cloning. My methodology is at the opposite extreme from yours. I don't like to be restricted to a single maintenance zone, but prefer to clone the entire target and DLIB environment whenever I need to do something new. The resultant target libraries are IPLed at the appropriate time, and the target zone is still known to SMP. As Ed pointed out, these days there is often HOLDDATA that tells how to apply a PTF to the running system in order to avoidan IPL. Granted, it doesn't happen often. Tom Marchant ---------------------------------------------------------------------- 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
