|
I just received the CUM package for V3R7M0 about 4 days ago on 2 CDs. The CUM package for V3R7M0 is not this way. I, also, had only had to put in the first CD. Just now I tested by putting in the second CD and GO PTF and 8 Install Package, and a message on QSYSOPR told me to stick in the first CD. So the last CUM for V3R7M0 is a "normal" PTF type. Regards, Jim Langston Chuck Lewis wrote: > Yep, I was told this by support when I talked with them Monday. They >SPECIFICALLY > mentioned this (I was getting a cum tape, hiper and the Y2K stuff for V4R1...) > and I started to ask WHY they did that with this one but got sidetracked. I do > seem to remember someone else posting that to Midrange-L earlier this month >or I > got an alert from SOMEWHERE else. > > Chuck > > franz99@attglobal.net wrote: > > > IBM has been updating the Group PTF for Y2K recently, and recently > > the shipment has been 2 cd's. Weeks ago I loaded the ptfs on 10 AS/400s. > > > > Each machine, some at V3R7, some V4R2 only asked for the 1st cd. Assumed > > > > no ptfs on the 2nd cd related to my machines. Today I checked the IBM > > site for > > new changes, and found the following text in the PSP "Both media volumes > > included > > in this order should be treated as separate single PTF orders. There is > > not a prompt > > to load the second volume." I must have missed that in the PSP several > > weeks ago > > (I did lose my glasses a while ago), or it just wasn't there. > > Today I updated several machines with the 2nd cd, and indeed, more ptfs > > were loaded. > > I would recommend that anyone who has not loaded the Y2K Group PTFs > > recently > > do so. There seems to be a number of recent additions. The label on the > > 2nd cd, > > labelled "2 of 2" will not automatically load after the 1st cd (like > > every other ptf > > process I have ever seen from IBM). See the site AS400service.ibm.com > > for > > Info Apars & PSP. The Group PTF SF99200 is for V3R7, V4R1,2,3,4. SF99201 > > is > > for V3R2. > > Jim Franz > > Systematic Control, Inc > > jfranz@sysctl.com > > > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: >david@midrange.com > > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.