----- Original Message -----
From: ""Mark Zelden"" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
Sent: Tuesday, January 30, 2007 5:16 PM
Subject: Why isn't ISPF APAR OA14164 PE'd?
(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.
Mark,
You should report this as a bug to IBM. I agree with you that there should
have been a PE here. I know Brian Peterson agrees with you. This is a
longstanding problem with IBM. PE's are bad, so they will avoid issuing one
if possible. They're getting better, but some still slip through the
cracks. IBM should create an AI APAR PE'ing both OA14164 and OA16455.
Good luck,
Tom
----------------------------------------------------------------------
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
