(cross posted to IBM-MAIN and ISPF-L) This past weekend we rolled out maintenance up to RSU0606 in one of our environments. We usually do quarterly RSU - 1 quarter plus hipers which would mean RSU0609, but some local issues and EOY put us behind in this environment - hence RSU0606.
Anyway... we ran into the problem described by APAR OA16455. The fix is on RSU0609, but right in the APAR text it says the problem was caused by OA14164. We go to great pains to keep very current on holddata running / reviewing reports on Friday prior to a weekend rollout of a new RSU level just to make sure no PEs are rolling in (also the reason we do quarterly RSU - 1 quarter). Since the new APAR PTFs sup OA14164, why wouldn't OA14164 get marked PE? It it had been - we could have avoided the problem. BTW, the APAR Vanguard's VRA tool, but our problem was with a home grown application. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
