...well not be be a broken record, but one of the major selling features of sysplex is not making IPL-ing an image any less necessary (they are what they are) but in making them invisible (or nearly invisible) to the business. With proper configuration you can take down an image, apply maintenance and restart the image while work continues merrily along on the other images in the plex. ...and of course you can't do that if you are still operating in 1989-compatibility mode and have applications bound to specific images in the plex and/or if you don't have enough headroom to allow the remaining images to pick up the load. The really really embarrassing part about this is, z/OS on its own is not even CLOSE to a high availability system. Sorry if that bursts anybody's bubble but it isn't. So if you are still operating in 1989-compatibility mode and IPL-ing weekly or bi-weekly, then even without incurring down time or poor service from application issues the business applications on those systems are only getting something like 99.5% availability (do the math, it's easy) which is a far cry from the "five nines" that parallel sysplex is designed to allow.
Yeah, yeah I know. I know. There will be spluttering replies about "software bills, yada yada" - trust me I've heard it all. My question back is, if you're paying for a high availability platform and not leveraging it, what was the point? -- This email might be from the artist formerly known as CC (or not) You be the judge. ---------------------------------------------------------------------- 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
