On Fri, 4 Nov 2005 07:12:08 +0100, Barbara Nitz <[EMAIL PROTECTED]> wrote:
>OA08692 has cost us a 1.4 system when a 1.6 system was IPL'd. It is not >marked hiper and my colleagues tell me that it is not on the list of >toleration maintenance for 1.6 >IBM has confirmed a correlation between the 0C4 described in there and the >tight loop in memterm tasks in master (RRS memterm resource manager) on the >1.4 system. It died not doing signalling anymore, so the 1.6 system spit out >IXC402D. >And you call me paranoid - we always hit the worst case scenarios... >Regards, Barbara Nitz > I thought it was our shop that did that. :-) Kidding aside, don't you have a preventive maintenance philosophy there? We've had that fix on since April this year. According to the APAR text the fix has been available since October of 2004 (a year ago) and was on RSU0503. We usually try to do RSU maintenance on a quarterly basis. PTF List: Release 706 : UA14015 available 04/10/13 (F410 ) Release 707 : UA14016 available 04/10/13 (F410 ) Release 708 : UA14017 available 04/10/13 (F410 ) Release 709 : UA14018 available 04/10/13 (F410 ) I know if took an outage on that error and the management above our level found out an RSU fix was available 6 months ago, we would be the ones in the hot seat. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ 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
