Re: Error launching java ... unable to open jars.cfg

hmm. Which JAVA_HOME did you tried? Following options of 5761JV1 are for
J9.
Option 8: Java 50 32bit. JAVA_HOME=
/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit
Option 9: Java 50 64bit, JAVA_HOME=
/QOpenSys/QIBM/ProdData/JavaVM/jdk50/64bit
Option 11: Java 60 32bit, JAVA_HOME=
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit
OPtion 12: Java 60 64bit. JAVA_HOME=
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit

You can double check those options on your system. Please refer
http://www.ibm.com/developerworks/ibmi/techupdates/java for more
information about J9 on i.


Best regards.
____________________________________________________________________________________________

Gavin, Zhang Gan --
https://w3-connections.ibm.com/profiles/html/profileView.do?key=d77158d7-c5cd-4e6e-a90d-23dddc9cbaba&lang=en

IBM i J9 Team Lead,
Email: zhanggan@xxxxxxxxxx
Phone: +86-10-82452719
Address: 1/F, 28, ZhongGuanCun Software Park, No.8 Dong Bei Wang West
Road, Haidian District, Beijing P.R.China 100193
J9 on i: http://www.ibm.com/developerworks/ibmi/techupdates/java



David Gibbs <david@xxxxxxxxxxxx>
Sent by: java400-l-bounces@xxxxxxxxxxxx
11/24/2013 08:59 AM
Please respond to
Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>


To
Java Programming on and around the iSeries / AS400
<java400-l@xxxxxxxxxxxx>,
cc

Subject
Error launching java ... unable to open jars.cfg






Has anyone ever seen this before?

I just installed Java6 (classic, 32bit & 64 bit options) on a 6.1 system.
I also applied the latest Java group PTF.

When I try to verify the java version, I get this output...

----------
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/bin/java -version
getBootClasspath failed to open file
java.home=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/lib/jars.cfg - A file
or directory in the path name does not exist.
JVMJ9VM015W Initialization error for library jclscar_24(2):
getBootClasspath returned NULL
Unable to create Java Virtual Machine.
----------

At this point I can't get ANY JVM's to run. I get similar errors
regardless of what JAVA_HOME value I use.

david