So you're starting a separate JVM for every call. Then you can certainly use whatever Java properties you want. You'll also have to suffer thru the JVM startup everytime.
-----Original Message-----
From: Richard Schoen [mailto:Richard.Schoen@xxxxxxxxxxxxxxx]
Sent: Monday, January 22, 2018 1:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Java extensions directory vs Excel generation
Yep, except I don't recommend RUNJAVA. Use QSHELL because you can capture and process STDOUT and return data from the Java call.
IE: Simulating call parm across process boundaries when calling Java.
To answer Justin's question, a single CL job stream can make multiple QSH calls to different JVM versions with different classpaths for each call.
In practice I don't usually recommend this, but it demonstrates the relative flexibility of writing simple Java programs and the possibility of actually making calls to multiple JVM versions in the same CL job.
Also performance mileage will vary depending on the number of Jar files you're using andn 32 vs 64-bit, etc., etc....
Always test as with any app 😊
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Java extensions directory vs Excel generation, (continued)
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.