|
You may have misunderstood me. I'm planning upgrade to V5R1M0 and researching a couple of my adapters (9162 and 6506). ----- Original Message ----- From: <rob@dekko.com> To: <midrange-l@midrange.com> Sent: Wednesday, March 20, 2002 10:00 AM Subject: Re: SQL Misbehaving > > Wait, in an earlier email you said you were running V5R1. I still have it. > Now you are telling me you are running V4R5? > > Cum vs Group > Cum's will apply to many products, including, but not limited to, the > operating system itself. > Group's may apply to more than one product but their target is a particular > issue. For example to fix a Java issue may require fixes to 999, ss1, JV1, > etc. The java group may have all of these. > Cum's don't come out as frequently as group ptf's. There may be several > releases of group ptf's in between each cum release. For example they try > to come out with a new HIPER group on a weekly basis. The other groups are > not quite as frequent as hipers but are probably more frequent than cum's. > > For V4R5. > The latest cum level may be looked up at: > http://www-912.ibm.com/s_dir/sline003.NSF/3a8f58452f9800bc862562900059e09e/2 f479b5325c019208625690c0073ba6e?OpenDocument > The latest cumulative package for Version 4 Release 5.0 is: C2050450 > > Suggested Minimal groups are: > http://www-912.ibm.com/s_dir/sline003.NSF/GroupPTFs?OpenView&view=GroupPTFs > Release Title Last Updated > SF99105: 450 DataBase 03/11/2002 > SF99096: 450 Hipers 03/19/2002 > SF99077: 450 Backup Recovery Solutions 03/11/2002 > SF99068: 450 Java 03/11/2002 > > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin > > > > "Dare @ Work" > <oludare To: <midrange-l@midrange.com> > Sent by: cc: > midrange-l-admin@mi Fax to: > drange.com Subject: Re: SQL Misbehaving > > > 03/20/2002 09:36 AM > Please respond to > midrange-l > > > > > > > Thanks Rob, > > I'm planning a cum and group PTF load next month and I'm at V4R5M0. Could > you remind me the difference between group PTF and Cum. My recollection is > that Cum is for the OS while group take care of the components that reside > on the OS. > > Dare > > ----- Original Message ----- > From: <rob@dekko.com> > To: <midrange-l@midrange.com> > Sent: Wednesday, March 20, 2002 9:29 AM > Subject: Re: SQL Misbehaving > > > > > > 1) The top cum is TL01100. That one came out in the first third of > 2001. > > There is a good and bad. It is good that you have applied a cum. Some > > people have upgraded their OS and never applied a cum. Our first AS/400 > > only support 1 file in RPG. I thought that was taking modular > programming > > to the extreme, but it turns out a ptf was needed. The next part may > sound > > too much like IBM and please forgive me. But, can you afford the time to > > get the latest cum and apply that? For the latest cum info: > > > http://www-912.ibm.com/s_dir/sline003.NSF/2d3aff1c6b4d6ce086256453000d971e/1 > > eba4d1d2f39c3f886256a57004d6f69?OpenDocument > > The latest cumulative package for Version 5 Release 1.0 is: C2071510 > > > > 2) And, since you are at V5R1M0, what appears when you type in DSPDTAARA > > SF99501? If you get the message that the data area was not found then > > you've never put on a database group ptf. > > To check out group ptf's: > > > http://www-912.ibm.com/s_dir/sline003.NSF/GroupPTFs?OpenView&view=GroupPTFs > > At a minimum I would apply: > > SF99501 - 510 DATABASE > > SF99097 - 510 HIPER > > SF99078 - 510 Backup Recovery Solutions > > SF99069 - 510 Java > > > > I've did a DSPOBJD of all objects/libs into a file. And the following > SQL > > works fine: > > SELECT ODOBNM, ODOBTP, ODOBAT, ODOBTX, ODCTIM, ODOBOW, ODCRTU, > > ODUCNT > > FROM routines/dskdtl > > WHERE ODUCNT >0 and odobnm like 'Q%' > > > > If you can think how I may be of more help, let me know. > > > > Rob Berendt > > -- > > "They that can give up essential liberty to obtain a little temporary > > safety deserve neither liberty nor safety." > > Benjamin Franklin > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.