The APAR is currently Severity 3, and does not have the HIPER flag set. If these conditions remain the same when the fixing PTF becomes available, IBM will not assign RSU to the fixing PTF until July 2007 at the earliest when the quarterly RSU becomes available. And, that's only if the fixing PTF becomes available (COR-closes) before March 31, 2007.
Should this problem be "severity 3"? Is this problem correctly classified as not "HIPER"? If this really is a serious problem (sure sounds like it to me), adjusting the APAR severity and setting appropriate flags *now* means that customers will see the fix "recommended" in 5-9 weeks from COR-close. Otherwise, it's 4-7 MONTHS from COR-close. Brian On Tue, 2 Jan 2007 10:57:06 -0800, Edward Jaffe wrote: >We ran into the subject problem here. If you run any code that protects >and then shares storage under z/OS 1.8, watch out! > >-- >Edward E Jaffe ---------------------------------------------------------------------- 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
