> All HIPER APARs are not necessarily "PERVASIVE" and as such may not be put on the RSU.
Not to shoot the messenger... but doesn't HIPER specifically stand for HIghly PERvasive? Now we (and new-to-IBM Linux customers) are expected to understand in IBM-speak that not only are Program Temporary Fixes not really temporary, but that HIghly PERvasive APARs are no longer PERvasive? <sigh> Maybe IBM needs HIPERS (which by definition are highly pervasive and belong on RSUs - status unchanged), and NOPERs, which are NOt PERvasive APARs? Or LOPERS (LOwly PERvasive)? Or just HISUG (HIghly SUGGested), but not pervasive!? Or USSUS (USual SUSpects) APARs. Have fun. This is going to be an interesting thread. Glad I didn't leave for the weekend yet! :-) We're not in Kansas any more, Toto! We may be leaving a country where the English is the native language. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Kurt Acker" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 04/27/2007 04:55 PM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject FYI APAR HIPER flag change (cross posted) Greetings, If you follow HIPER APAR's, please do not be alarmed. This note explains some changes that caused us to review all active APAR's, and change the HIPER flag when needed. System z, z/VM APAR HIPER and RSU process changes: IBM's current service guidelines requires all APARs that result in system outage be marked 'HIPER'. In z/VM's case, this also applies to APARs that correct virtual machine outages. This same APAR may or may not also be marked "PERVASIVE". The previous guideline required any system or subsystem outage APAR to be marked 'PERVASIVE' in order to have been marked "HIPER". As you can see this is a switch. To adhere to the current guideline, system outage APARs that were not marked HIPER have now been marked HIPER. zVM's RSU philosophy has been to put all HIPER APARs on the RSU. This has been changed. Now, APARs designated "HIPER" and "PERVASIVE" are automatically included on the RSU. All HIPER APARs are not necessarily "PERVASIVE" and as such may not be put on the RSU. The HIPER designation is for customer awareness that these problems exist, they cause a system or subsystem outage, and may or may not be on the RSU. Here are the newly designated HIPER APARs, currently in supported releases R510 and R520: VM56702 VM63454 VM63502 VM63540 VM63553 VM63558 VM63565 VM63567 VM63579 VM63590 VM63604 VM63619 VM63640 VM63650 VM63654 VM63655 VM63666 VM63667 VM63676 VM63694 VM63696 VM63717 VM63719 VM63720 VM63723 VM63769 VM63771 VM63772 VM63777 VM63785 VM63806 VM63807 VM63827 VM63828 VM63831 VM63832 VM63838 VM63840 VM63842 VM63843 VM63847 VM63858 VM63859 VM63860 VM63866 VM63871 VM63887 VM63888 VM63900 VM63903 VM63906 VM63907 VM63911 VM63913 VM63917 VM63924 VM63925 VM63930 VM63943 VM63954 VM63955 VM63956 VM63957 VM63962 VM63965 VM63970 VM63971 VM63973 VM63980 VM63986 VM63987 VM63988 VM63990 VM63991 VM63992 VM63994 VM63997 VM63998 VM64012 VM64013 VM64014 VM64015 VM64023 VM64029 VM64033 VM64036 VM64037 VM64042 VM64049 VM64052 VM64060 VM64075 VM64076 VM64083 VM64084 VM64099 VM64100 VM64103 VM64105 VM64115 VM64121 VM64125 VM64129 VM64141 VM64143 VM64144 VM64145 VM64154 VM64165 VM64173 VM64174 VM64183 Thanks and Best Regards, Kurt Acker The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
