Re: Defective PTF

["Jim Franz" <franz400@xxxxxxxxxxxx>]

i loaded cume 5102 on Monday, and hiper level 49 yesterday.
5722999 MF34850 not on my system
This is a small i5 with twinax console, no lpars.
For some reason if it is in hiper, it did not load.
jim

----- Original Message ----- 
From: "phil Kestenbaum" <pkestenbaum@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, May 12, 2005 2:45 PM
Subject: RE: Defective PTF


> What to do if is loaded but IPL is schedueled for Monday AM, Should I
remove it?
>
> -----Original Message-----
> From: Neil Palmer/DPS [mailto:neilp@xxxxxxxxxxx]
> Sent: Thursday, May 12, 2005 2:38 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Defective PTF
>
>
> Thanks for the heads up Jerry.  They haven't flagged it as defective yet:
>
>
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/93a322ccfb6ed0e486256ff700479425
>
>
>
>
> Jerry Adams <jerry@xxxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces+neilp=dpslink.com@xxxxxxxxxxxx
> 2005/05/12 13:40
>
>
>
> To
> Midrange-L <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Defective PTF
>
>
>
>
>
>
> I just finished applying the latest CUM (V5R3) and the HIPERs,
>
> The IPL after the install froze with SRC B2003200 LP=001.
>
> Anyway, with the help of a nice lady in Rochester I got over it.  To the
> point MF34850 (which was on the HIPERs) is a defective PTF.  I subscribe
> to the tech bulletin for defects, but never got anything on this one.
> In fact, the accompanying list indicated several PTFs that were
> superseded by this one.
>
> This was the 3 May HIPER, btw.  Unless there's something really critical
> for me, I usually delay a week just to avoid something like this.  I've
> gotten several notices in the past (calls, even, in one case) after I
> might normally have applied the PTFs.  This one must have slipped
> through the cracks.
>
> Just a heads up for everyone.
>
> -- 
> Jerry C. Adams
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --------------------------------------------------------
>
> This message contains confidential information and is intended intended
only for the individual named. If you are not the named addressee you should
not disseminate, distribute or copy this e-mail. Please notify the sender
immediately if you have received this e-mail by mistake and delete this
e-mail from your system. Finally, the recipient should check this email and
any attachments for the presence of viruses. The company accepts no
liability for any damage caused by any virus transmitted by this email.
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>