On Wed, 5 Sep 2007 09:15:48 -0700, Skip Robinson <[EMAIL PROTECTED]> wrote:
>Paolo's procedure will handle the change with what amounts to a >sysplex-wide cold start. I always worry about 'cold start' of any stripe or >flavor. What happens if some otherwise trivial error results in no system >available? That's one point of view. Another is: Exactly the reason I like doing a sysplex wide IPL when the opportunity presents itself during a *scheduled* outage. It's a heck of a lot better to deal with during a scheduled outage then when under the gun when something very bad happens and takes out your entire sysplex. Plus it cleans up consoles :-) Case in point: While I was at SHARE there was a DASD problem that took out a small sysplex. It was the first time a sysplex wide IPL was done since at least z/OS 1.8 was implemented. A "oversight" in the implementation months prior to the outage (related to the RACF range table) rared its ugly head on the way up and delayed the recovery even further. As long as at least one system was up, RACF knew the correct configuration. The sysplex wide IPL prevented RACF from starting up and left a dead sysplex with no one able to figure out what the cause was (they thought it was still a DASD problem). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
