Not nearly enough information here about what you're doing to make any recommendations.
If it was me, I'd submit the java from the CL using a QSH script. The CL would be out of the picture once the SBMJOB CMD(QSH CMD('myshellscript.sh')) was passed.
The java would camp (block) on the input from the scale (probably a socket?) when something came from the scale, the java would use jt400 classes to write to the database table or data area. Then it would loop back to camp on the input again. Once started, you'd get input from the scale to destination in sub-second time. The java could run on the i or on another machine running windows, linux or anything with a jvm.
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Fekete
Sent: Tuesday, October 16, 2012 9:25 AM
Subject: How do I keep JVM open after first call?
I have a CL calling a Java program that retrieves a weight from a scale and moves the weight to a either a database or a data area in the java program.
If it is the database option, it takes 5 to 7 seconds to write to the database file and if we use the chgdtaara command it takes 5 seconds to open
the connection to the iSeries and another to execute the command. The
programmer says he is trying to leave the connection(s) open, but it doesn't seem to be working.
What do we have to do to speed up this process?
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l
As an Amazon Associate we earn from qualifying purchases.