well, for one, if company x is a year+ behind on maintenance as you indicate
below,
hmmm, well, that's the company's own stupidity and no one but theirs. .
It is prudent to stay a couple of months behind. 3 or so is normally
considered "about right".
IBM has their CST report, their parallel sysplex test report, etc.
describing their environment,
maintenance level, etc. Oh sure, they don't have all of the software
packages "we" might, but there
is still no reason on this planet to ever be a year+ behind (or more) on
maintenance.
That's absurd, you're just asking for trouble.
We stay reasonably current and that includes the time to roll it across our
multiple sysplexes and
multiple lpars.
There is absolutely no valid excuse for not staying reasonably current on
maintenance, operating systems
and hardware.
Amazingly, by staying somewhat current, (but not quite bleeding edge)
I can't say I've ever really run into any of these issues that are in this
thread.
OW50900 made life interesting for a brief period, but that's about it.
I started with MVS/ESA V3 and now at "present" day at z/OS 1.6
----------------------------------------------------------------------
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
