On Thursday, 08/31/2006 at 05:48 ZE2, "R.S." <[EMAIL PROTECTED]> wrote: > We *never* do IPLs on scheduled basis. Of course we do IPL when a need > arise.
>From our Book of Experience, volume 59, p.843, it says: What about IPLing less frequently? - Use strong Change Management procedures. The longer you go between IPLs, the more the system accretes dynamic changes and the more opportunity there is for a mismatch between the system as it is running, and the system as it is configured. - When you make configuration changes, IPL a test system to ensure that you didn't make a syntax error or some other annoying error that is only readily apparent when you IPL. (Hmmm....I seem to have forgotten to add the new member in SYS1.VTAMLST to ATCCONxx. Drats.) - Give your operators a way to practice IPLs. In an emergency situation, you don't want confusion about which icon on the HMC to use. "Use it or lose it." You know? - If more than one person can change the system configuration, then it is possible for Things To Happen that you don't know about. IPL your test image on a regular basis to catch these things. - Failure to follow the above recommendations will result in an embarrasing or costly error at the most inopportune moment. YMMV. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
