On Fri, 3 Mar 2006 11:42:43 -0600, Ed Gould wrote: >There is a discussion going on another list on how to identify a >*HIGH* (data base corruption possibility). >Someone suggestion a HIPER doc APAR IBM came back and said they would >not make a HIPER doc APAR, nor apparently is there a INFO APAR >allowed to be HIPER. > >Anybody have a suggestion how IBM might flag an APAR as being >extremely important and could lead to a Data base corruption if it is >not addressed at installation?
A FLASH from IBM might be more than slightly in order for such a documentation oversight. Trouble is, FLASHes are not very timely ... a lot of RACF databases can become corrupted between the idea and the implementation. Maybe the APAR should be appealed to get a code change rather than a doc change? (Oh yeah, like the RACF people are gonna let that happen!) -- Tom Schmidt Madison, WI ---------------------------------------------------------------------- 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
