On Wed, 23 Jan 2013 13:33:51 -0800, Skip Robinson <[email protected]> wrote:
>I want to reiterate an endorsement of AUTOIPL. It costs nothing but some >configuration time. In DIAGxx you put > > AUTOIPL SADMP(dddd,SMSYSC) MVS(LAST) /* IPL SAD FROM SAD IPL vvvvvv */ > >When we first went to z/OS R13, we stumbled on an obscure memory leak >problem that took IBM a while to figure out. We came in more than once in >the morning to find that our development system had IPLed at >oh-dark-thirty and had a fresh SAD from just before IPL. The system had >run completely out of real storage, wait stated, took SAD according to the >statement in DIAGxx, and reIPLed itself. Even Ops didn't always notice. > >There's one caveat to add. Not long ago we went through a 'DASD refresh' >that moved every volume to a different address. At IPL time, z/OS checks >the specified SADMP address for validity. If he determines that it's >invalid--in our case the address was no longer genned--then the entire >statement is discarded. Not just no SADMP but no AUTOIPL. Takes another >IPL with correct values to fix it. Tough to remember, but in case it ever >happens to you... > >. It's more than just the DIAGxx definition. The MVS sysprogs and storage admins know that if the SADUMP IPL volume moves (built on secondary sysres vol or dlib vol for each OS release running) or any of the output volumes move, that SADUMP may need to be regenerated and/or the AMDSADDD utility needs to be re-run. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
