Well, maybe we should have tried to define 2 new levels of HIPER (and this 
is NOT an official statement from IBM on the subject) :

Halfway HIPER (H2 APAR's)
These are HIPER APAR's that are not a concern to every z/VM user (HIPER 
only if you meet some certain condition), and in that case they will not 
be flagged for the RSU.

HIPER Have to Have (H3 APAR's)
You want it on your system no matter what, and it will be flagged for the 
RSU.

Why do I suddenly feel like a little duck, slowly traveling along the top 
edge of a piece of plywood?  Darn, clicking heels together did not change 
feeling!  Scottie, if you can hear me, beam me up...

Kurt Acker 




Mike Walter <[EMAIL PROTECTED]> 
Sent by: The IBM z/VM Operating System <[email protected]>
04/27/2007 06:22 PM
Please respond to
The IBM z/VM Operating System <[email protected]>


To
[email protected]
cc

Subject
Re: FYI APAR HIPER flag change (cross posted)







> 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. 
 
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. 

Reply via email to