Looks like introducing knowingly a single point of failure into a system without any way out . This was my point earlier on I was caught 3 years ago despite warning the vendor of the differences in STSI and STIDP on z/990 but indeed they ignored me and no batch would run i had to call someone in Texas ( sorry guys but the Texas or Florida accent mixed with my own exasperated french accent brought some extra delays to our batch window ) It added latency like some new managers call it :-)) Bruno Bruno(dot)sugliani(at)groupemornay(dot)asso(dot)fr
On Sun, 25 Feb 2007 09:02:40 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >>In the case of a processor upgrade: if you get a hard error during production due to a bad ISV key, your testing criteria are way too lax. > >Scenario: >1. Vendor delivers key. >2. Key cannot be installed until the upgrade. >3. Upgrade cannot be done until the weekend. >4. Key fails. >5. Vendor support is only available M-F/9-5 (local time). >6. Asia Pacific Region's Monday Day Shift starts mid-day Sunday (local time). >7. Now what? And, where did my testing fail? > > >- >Too busy driving to stop for gas! > >---------------------------------------------------------------------- >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 >========================================================================= ---------------------------------------------------------------------- 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
