On Mon, 30 Apr 2007 08:30:21 -0700
David Stuart <[EMAIL PROTECTED]> wrote:
> Back in a previous life, working for IBM Software Support, HIPER meant
> High Impact *or* PERvasive, not both.
"Hopefully It Puts Everything Right"
-
Back in a previous life, working for IBM Software Support, HIPER meant
High Impact *or* PERvasive, not both.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 4/28/2007 9:41 AM >>>
>>> On Fri, Apr 27, 2007 at 5:56
> -Original Message-
> From: Linux on 390 Port On Behalf Of Kurt Acker
>
> 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
> Watch your language ;-)
Sorry, too much feeling at seeing what is (to me at least) a doubtfull approach.
> you read the APAR text (and probably the source
>update of the PTF where possible) and make your own assessment.
Quite, and I hope everybody would do the same. But you are probably right,
On 4/29/07, Pieter Harder <[EMAIL PROTECTED]> wrote:
>I hope someone with better access to RETAIN will have done
>an estimate on how frequent a PTF for a HIPER is expected to be
>published, and how many outages folks will have when they want to
>install that within 2 weeks or so...
I think th
>I hope someone with better access to RETAIN will have done
>an estimate on how frequent a PTF for a HIPER is expected to be
>published, and how many outages folks will have when they want to
>install that within 2 weeks or so...
I think that is utter rubbish. Why take an outage to avoid an outage
On 4/28/07, Mark Post <[EMAIL PROTECTED]> wrote:
How did we get into a situation where HIPER (which stands for High Impact and
PERvasive) doesn't also mean pervasive?
I suppose some significant customer got bitten because a non-HIPER
APAR also affected them while they thought *they* would onl
On Apr 28, 2007, at 11:41 AM, Mark Post wrote:
How did we get into a situation where HIPER (which stands for High
Impact and PERvasive) doesn't also mean pervasive?
I blame Chucky.
Adam
--
For LINUX-390 subscribe / signoff /
>>> On Fri, Apr 27, 2007 at 5:56 PM, in message
<[EMAIL PROTECTED]>, Kurt
Acker <[EMAIL PROTECTED]> wrote:
-snip-
> 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.
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
10 matches
Mail list logo
