|
Thorbjorn, Thanks for the reply. I finally managed to get it to at least do something by keying it in like so: SYSTEM "CRTJVAPGM 'poi-2.5.1-final-20040804.jar' OPTIMIZE(40)" When it gets finished, I will be able to test my program and see if this will help the preformance. Thanks, Terry Anderson > message: 3 > date: Tue, 21 Feb 2006 00:17:58 +0100 > from: Thorbj?rn Ravn Andersen <thunderaxiom@xxxxxxxxx> > subject: Re: Performance when using POI to create an excel workbook. > > as400tech@xxxxxxxxxxx wrote: > > >List, > >I started this post on the Midrange-L list, but was told I may have > >better luck finding an answer here. > > > >O.K., this is what is happening. I have modified Scott Klement?s > >XLCRTDEMO program that creates an excel workbook from an RPG program > >using the Jakarta POI java routines. This works great with the exception > >of the time it takes to create the workbook. From start to finish, it is > >taking about 30 minutes. It takes about 90 seconds to build the work > >file and the rest of the time is being spent creating the workbook. > > > >It was suggested that I try to optimize the .jar file using the > >following command.: > > > > SBMJOB CMD(QSH CMD('for jar in $(find /jakarta-poi-2.5.1/ -name > > ''*.jar''); do system "CRTJVAPGM CLSF(''"$jar"'') OPTIMIZE(40)";done')) > > > >I was unable to get it to run as a submitted job, but I could get it to > >run interactively. I now get : > > > >find: 001-2187 The option db2_classes.jar is not valid. > > > > > This is the find command complaining. This might be because it somehow > gets the "*.jar" expanded - hard to tell. > > You might instead ask the invoking JAVA command to optimize to level 40, > just to see if it helps. This is not saved to disk, but it will give you > a hint if it is worth the effort. > > -- > Thorbj?rn > > >
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.