I concur with Barbara. Given ordinary due diligence, there should be no issues
w/IBM software.
In all of the 20+ years I have been in this business, I can recall 1 instance
where the compat support was compromised and that wasn't fatal, just a nuisance.
BTW, at one large former employer (44 CECS, 10 SYSplexes) full rollout took 4
months from dev 2 QC to prod.
i.e. MONTH 1 LPAR DEV1
MONTH 2 LPAR QC1, DEV2
MONTH 3 LPAR QC2, PRD1
MONTH 4 LPAR PRD2
HTH,
<snip>
> I understand that IBM provides a multi-release co-existence support policy
> for z/OS and other ServerPac products, which very adequately covers much of
> our IBM inventory, and that IBM will fix any problems discovered. But, have
> you actually encountered any problems caused by co-execution of multiple
> maintenance levels or releases of IBM software? BTW, IBM transaction and
> database software is out of the scope of this question for us, because they
> are maintained separately.
....snippage
In all, give due diligence, I don't think there are problems with phased (IBM)
maintenance. For vendors, I have seen one that uses SMP/E but has no clue what
a prereq across different fmids is. So I would never roll out *their*
maintenance phased, but then, their software is not sysplex in scope.
Barbara Nitz
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
