|
All valid points. Don't know exactly who you would contact at IBM regarding this concern. Do you have that old defect email that came out a week or two ago? If so, does it have a contact person? What about contacting the person who worked with you on this pmr and have them see what they can do? Have you tried the feedback form on the website for the ptf cover letter? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Jerry Adams <jerry@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/13/2005 06:34 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: Defective PTF I did a little more searching after reading Rob' and Jim's notes. I actually had two [2] HIPERs. Level 47 was shipped with the CUM (remember last week's discussion about HIPERs and CUMs?). Before I installed I downloaded Level 49 from the FTP site. I would have omitted 47, except that the DB Group is included on the same CD. So perhaps, as Jim says, the PTF was removed from 49, but I caught it on 47. All of which sort of begs the questions: If IBM knew it was defective (and removing it from 49 indicates they did), a) Why is it not listed as defective, and b) Why was no notice sent out? I know that IBM can do both of those things because they have in the past. I've even gotten phone calls (from a real person!) saying, "Noticed you downloaded PTF so-and-so. It's a bummer, don't install it." At the very least there is a subscription list (to which I below, as most of you probably do, too) that sends out defect notices. And, finally, as Neil's post shows, there is no defect notice on the PTF's page. Jerry C. Adams Jim Franz wrote: >Jerry mentioned he thought it was hiper level 47. >Rob - you & I have 49. >Jim > >----- Original Message ----- >From: <rob@xxxxxxxxx> >To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> >Sent: Thursday, May 12, 2005 4:35 PM >Subject: Re: Defective PTF > > > > >>I have a couple of V5R3 machines. Some i5's, some iSeries. Some with >>lpar's, some without. They are all at: >>PTF Group Level >>SF99530 5102 >>SF99529 49 >>SF99503 4 >>and none of them have this ptf. >>I wonder if you do a WRKPTFGRP, and, if you are not at level 49, put a 5 >>in front of SF99529 if you see it there. Perhaps that had it on an >>earlier hiper level, but removed it? >> >>Rob Berendt >>-- >>Group Dekko Services, LLC >>Dept 01.073 >>PO Box 2000 >>Dock 108 >>6928N 400E >>Kendallville, IN 46755 >>http://www.dekko.com >> >> >> >> >> >>Jerry Adams <jerry@xxxxxxxxxxxxxxx> >>Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx >>05/12/2005 12:40 PM >>Please respond to >>Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> >> >> >>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 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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
