I had an interesting meeting this afternoon with a client that is 
migrating from Lawson version 7 to version 8. According to the client, 7 
was basically RPGIII or IV code that may have had the CVT to ILE cmd run 
against the code but not much other ILE stuff was done. This new code uses 
a stored procedures does the bulk of its I/O via SQL. We also know disk 
requirements were increased by 35+ percent. This is a 820 dual CPU at 2385 
CPW(think that's right) with something like 32gb memory. Now the kicker... 
they are running "26" separate Lawson Environments. These all existed on 
V7 but about 1/2 are now using the V8 code. Also when on V7 code only the 
system usually had approx 1100 active jobs (WRKACTJOB #), now it's closer 
to 2600 Active jobs. Processes that used to take say 5 minutes to run are 
now taking 20 minutes or longer. CPU time used has increased but not 4 
times. Plenty of Disk arms on new 2780 IOAs.

I'm going in on Friday with some of their staff to start looking for what 
might be the bottle neck. Basically a system performance audit and job 
traces to see what PEX will show.

So the questions I have are

#1 Anyone running Lawson V8?
#2 Anyone that is running V8 and more than 1 or 2 environments?
#3 Anyone else seen this type of performance hit?
#4 If #3 how I did you fix it?
#5 Any suggestions in general?

Thanks in advance
_____________________
Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified iSeries Solutions Expert
IBM Certified iSeries e-Business Infrastructure
IBM Certified Designing IBM e-business Solutions 
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx      www.manageinc.com

There are 10 types of people in the world:
Those that understand binary, and those that don't.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.