|
Mike - I don't know if this is your problem or not, but I've seen two instances of major performance degradation after a V5R1 or V5R2 upgrade from a V4 release. Both of these involved a single service program compiled with activation group=*NEW When recompiled with activation group=*CALLER the performance straightened right out. I don't know all of the nuts and bolts details, but apparently there were some changes to the CLE compiler in V5, and the previous defaults are not optimal. I hadn't heard of this with JDE though, I saw it in WAF and a similar incident was discussed here earlier this month with some EDI sofware. We tracked this down by running performance traces and discovering that one single job was chewing up a large percentage of the CPU time. Of course it took two months to convince IBM that it was an issue.... Scott Ingvaldson AS/400 System Administrator GuideOne Insurance Group -----Original Message----- Date: Mon, 14 Apr 2003 10:08:20 -0700 From: "Mike Shaw" <mhshaw@xxxxxxxxxxxxxxxx> Subject: RE: Model 270 At V5R2 Is Dead Toad Slow Running JDE One World....... Mark, Per your suggestion I ran the STROBJCVN over the JDE libs yesterday and did see some improvement in performance as a result. I was aware and did this when we went from V4R5 to V5R1 last spring as part of my post install tasks. There was a known performance hit initially for object conversion if you did not do this. I guess it is true for V5R2 as well.............. I did a total V5R2 shake down last night to see what I really had beyond any doubt. I found that the HIPER PTF group did not apply, yet it is on the same CD as DB2 and it did apply.....Working to get that resolved right now. Slooooooowly but surely it's coming around........ Thanks! Mike Shaw
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.