|
Mike, The problem in question has been developed into APAR MA31334 and we are waiting on a coding fix. Usually we only run into these when we change releases and not with cums. I will say that we had probably not PTF'd the system in almost 12 months. This is not my usual approach but we went a long time at V5R2 without a changed CUM and I usually wait for that. Then they put out two of them pretty quickly but I kept on delaying things thinking we would be going to V5R3. However, with my DR test coming up I decide to take the plunge. Michael Crump Manager, Computing Services Saint-Gobain Containers 1509 S. Macedonia Ave. Muncie, IN 47302 (765)741-7696 (765)741-7012 f (800)428-8642 "The probability that we may fail in the struggle ought not to deter us from the support of a cause we believe to be just" Abraham Lincoln mshaw2456@comcast .net To 06/23/2005 03:18 midrange-l@xxxxxxxxxxxx PM cc Subject Please respond to Re: OS/400 V5R2 CUME C5123520 Midrange Systems Technical Discussion <midrange-l@midra nge.com> Mike, Thanks for the info. We too are a JDE OneWorld shop. The last CUME package I applied had an SQL problem as well. IBM had to come up with a fix which took about a week. Can you provide some more detail on the SQL problem that you found on the latest CUME package? Is it JDE package related? Any and all info on that would be appreciated! We are not using any AFP so I should be good there. Regards, Mike Shaw > Mike, > > We just did the cum 05123 with HIPER 134 and DB2 19. No real issues. I > have 1 SQL statement that was supposedly 'working' before that I'm trying > to work with IBM on and some intermittent AFP printer writer problems. > There are some AFP PTF's that I have not put on. Nothing major with the > writers though. > > We run WAS 4.5, 5.0, Domino 6.5.2, Sametime, QuickPlace, WPS, JD Edwards > (never ever say Oracle) and a fair amount of SQL processing. Hopefully > that means we run a fairly wide sample....... > I've been told to make sure to have ptf SI16368 on to ensure faster > recoveries (this is from the disaster recovery people). -- 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-2025 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.