×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
RUNJVA will create a new job on each call and therefore a new instance
of the JVM each time Brad. Using the JNI interface from RPG would
avoid that overhead so that would probably be faster becuase the JVM
startup is significant.
It occurs to me that there is possibly one other option - using
Scott's UNIXCMD (
http://www.scottklement.com/unixcmd/) would probably
work too. It should be possible to keep the JVM alive that way - it
certainly does keep the qshell or QP2Term session open until the
"file" closes. Might work if you really want to avoid a NEP.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Jun 25, 2010, at 5:36 PM, midrange-l-request@xxxxxxxxxxxx wrote:
I guess my question is, if the Java procedure is being called by the
same
job using RUNJVA from and RPG program (using QCMDEXC of course),
would this
be sped up dramatically using a NEP? My guess is no since it's all
in the
same job and the JVM doesn't start and stop each time (but it seems
like
another job is spawned.. most likely a QSH job).
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.
midrange.com
