Re: How to specify which JVM to use?

I guess that's kind of where I was trying to go. Basically the CL
would just execute a unknown command. The user would have to know
which command to use in order to set their classpath.

So if I want to use the the classic JVM, but using Java 5 I would need
to know I have to use this command:
ADDENVVAR VAR(QIBM_RPG_JAVA_PROPERTIES) VALUE('-Djava.version-1.5')

and if Bob wants to use the 32-bit version he needs to use this command
ADDENVVAR VAR(JAVA_HOME) VALUE('/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit')

You could have them add that to a table based on their user id or a
stream file maybe even data area.

The CL would then retrieve the command and execute it. No need to know
which command it's using, just that it's executing a command.

--
James R. Perkins



On Tue, Feb 2, 2010 at 09:59, David Gibbs <david@xxxxxxxxxxxx> wrote:

On 2/2/2010 11:29 AM, James Perkins wrote:

You can add an environment variable for the Java version too,
QIBM_RPG_JAVA_PROPERTIES. The value would be "-Djava.version=1.5".

That only works in the classic JVM.  It doesn't work with the PASE based JVM's.

There is also an environment variable to that you can specify the path
to the SystemDefaults.properties file too.

Specifying the java.home value in SystemDefaults.properties doesn't appear to work.  I ether get an error or the value is ignored.

So I guess I would probably just store the ADDENVVAR command with the
appropriate value in a table or a stream file and use a native program
to execute the command. I generally us a CL to set-up the classpath
anyway, but I'm not sure if you are doing that or not.

Yes, but my objective is to remove awareness of which JVM is being used from the CL driver program.

david

--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.