************Beginning of data**************
java.version=1.4
java.awt.headless=true
************End of Data********************
And you can change the java.version string that will do it. That will be
global for everyone since it's a systemdefault. You'll need to make sure you
have the option for each version of the JDK installed in order to use it.
I'm not sure what will happen if you set it to a version number that isn't
installed, but its probably not good! :)
You can then run RUNJVA CLASS(*VERSION) from a command line to see what the
JVM version is, mine shows JVM V5R1M0 JDK 1.4.2 when its set to 1.4, and
when i set it to 1.3 it comes up JVM V5R1M0 JDK 1.3.1.
Leonard
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of darren@xxxxxxxxx
Sent: Wednesday, March 24, 2010 4:20 PM
To: midrange-l
Subject: Setting default JDK and level
Our development system starts the JVM at JDK 6 level 1.6. Our production
machine starts JDK 5. Everything is identical installation wise, so the
production machine is capable of running JDK 6. Does anyone know where
this is set at? It seems to be JAVA_HOME variable, but where is that set
at?
For example, in the job log I see:
Development:
Cause . . . . . : JAVA_HOME environment variable is
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit
Production:
Cause . . . . . : JAVA_HOME environment variable is
/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit
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.