|
... and group PTF's are never listed on a cum, however there may be overlapping ptfs which appear on both the cum and the group. The members of a group PTF change week by week. Unlike a cum which has a listed group of PTF's at a certain time. Compare it to SF99xxx where xxx is the version of OS/400 you are on, like SF99440. This changes, not as often as a group (unless seriously defective), but it does change. Don't compare it to c99313440 which is a cum at a particular date. Some, if not all, of the groups do maintain a data area on the system so that you may check the level of the group, (just learned that this week). For example look at: Data area . . . . . . . : SF99104 Library . . . . . . . : QSYS Type . . . . . . . . . : *CHAR Length . . . . . . . . : 50 Text . . . . . . . . . : Value Offset *...+....1....+....2....+....3....+....4....+....5 0 'Group PTF#: SF99104-06 V4R4M0 11/24/1999 ' oludare@ix.netcom.com on 12/22/99 11:42:45 AM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: Fax to: Subject: Re: CUM PTF SF99200 is a VERSION 370/410/420/430/440 Y2K group PTF. Further information can be access from http://www.software.ibm.com/year2000 Oludare ----- Original Message ----- From: "Jim Langston" <jlangston@conexfreight.com> To: <MIDRANGE-L@midrange.com> Sent: Tuesday, December 21, 1999 10:42 AM Subject: Re: CUM PTF > C8314370. And the PTFs did in fact install during the > unattended IPL. It was just that I had some temporary > PTFs applied that had to be applied permanently before > certain other PTFs could be applied. > > So I did a APYPTF LICPGM(*ALL) APY(*PERM). > So now when it IPLs on Friday the rest of the PTFs should > be applied. > > I just hope there's no defective PTFs on this CUM, because > I applied them permanently after some of the new PTFs had > installed temporary. > > Question, what is this CUM SF99200 and do I need it? > > Regards, > > Jim Langston > > oludare wrote: > > > Sorry to drag you guys back but is this subject on CUM# C8314370 or SF99200? > > > > Dare > > +--- > | 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.