Title: Rw100 Performance Experiences
shane pennington - January 21, 2008 03:09 PM (GMT)
I have been asked to reach out to the Lawson community relative to
experiences running RW100 and what type of performance should be
reasonably expected. I realize that reasonable expectations are
something which should be managed, however, my client is adamant that
RW100 should run much faster than it currently is.
The long and short of it is that the client is running RW100 using the
chart option (all AU's --- all Accounts). They have approximately
2500-3000 AU's and a fair number of accounts. When running RW100 wide
open for all transactions, the job takes approximately 4 hours to
complete. It produces an xml report file in the print directory which
is approximately 500-Mb. The client thinks this is too long to run.
Please, if you have experience running RW100 for a large amount of data,
please share your experience. How long does it take to run, how large
is the output file, etc...
TIA,
~Shane
area51 - January 21, 2008 06:27 PM (GMT)
Oh, yeah turn that XML off. It fubars the amount of time a report should run.
Stop lawson.
Edit lajs.cfg and change "XMLREPORTS" from "ON" to "OFF".
Start lawson. Rerun the same RW100 report. You will notice the time difference.
With LBI you can selective do this because the updated version of WF01 has an option to have both regular reports and XML. But the XML will created from XTRA.EXE in the IOS system.
shane pennington - January 21, 2008 07:58 PM (GMT)
My client want to use RW100 as a datasource for Crystal. Are you saying that someone can run an RW100 with the xml flag set to "No" and still somehow use it as a datasource for Crystal?
If so, please provide me more details. My understanding is that the xml flag must be set to yes on the report parms if you want to use RW100 as a datasource for Crystal.
moesplace - January 21, 2008 09:19 PM (GMT)
We are "sort-of" doing that here. The key is bldxffiles Lawson program...
If you are running out of a Unix script, you can automate this to complete the job, and then run:
${GENDIR}/bin/bldxffiles -SA ${USER} ${PRINTDIR} ${RPTFILE}
Where ${USER} is the job owner's login id
${PRINTDIR} is the path to the print file, but not including it - ie ${LAWDIR}/print/${USER}/<jobname>/1 and
${RPTFILE} is the report file that the user is basing the RW100 report off of.
area51 - January 21, 2008 11:22 PM (GMT)
I don't see the bldxffiles in 8.0.3.7 Is that a LSF9 program?
moesplace - January 22, 2008 04:10 PM (GMT)
I'm sorry, I don't have any way to check if it existed in 8 anymore... all of that data has been dismounted and reclaimed by the SAN gods. It does exist in LSF9 though.
Milo - January 28, 2008 09:59 PM (GMT)
Don't know about the XML part, but when I was working with a Lawson 8 environment, RW100 reports ran in minutes .... bringing the entire system to its knees while they were running. None ran more than 15 minutes or so, most completing within 3 minutes.... IBM X-series server running under Win2K3, Env. 8, Apps 8.0.3. During the time the reports were running, we got calls about the system "not working" or "frozen" or "very slow" ... we thought there was a problem but found that for some reason the RW100 reports were taking almost 100% of all system resources. They sure ran fast, though, hoo-boy! B)
The reason I mention this is, if your reports are not taking all systems resources while running, they will probably be running much slower. If there is some way to increase their priority while running, you may find that they run faster. Of course, then you have to put up with the system being slow for everything else but that's what they call a tradeoff ... good luck!