Question & Answer
Question
Why would I receivie an abend ASJJ and message DFHSJ099 indicating the Java version is incorrect. when trying to run the JHE2 transaction in CICS Transaction Server for z/OS (CICS TS)? I receive message: DFHSJ0900 date time applid Illegal Java version. CICS requires Java version 6.0.1 but has found Java version 1.7.0 .
I am running CICS TS 4.2 with the required level of Java 6.0.1 and have verified the following:
the JVMPROFILEDIR in the system initialization parameter (SIT) points to your CICS 4.2 JVMProfiles (/u/cicsts42/JVMProfiles) directory
the JAVA_HOME option in the DFHJVMPR profile points to the Java 6.0.1 installation directory (/usr/lpp/java/J6.0.1_64)
the JAVA_INSTALL_OK file contains the value 6.0.1 as expected
When I enter the 'java -version' command, the output indicates that I am running Java 6.0.1 SR8:
java version "1.6.0"
Java(TM) SE Runtime Environment (build pmz6460_26sr8-20140411_01 (SR8))
IBM J9 VM (build 2.6, JRE 1.6.0 z/OS s390x-64 20140409_195736 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20140409_1526_B195736
JIT - r11.b06_20140409_61252
GC - R26_Java626_SR8_20140409_1526_B195736
J9CL - 20140409_195736)
Answer
This problem can occur if the DFHJVMCD profile JAVA_HOME option specifies the Java 7 installation directory instead of the Java 6.0.1 path.
Although you are not using the DFHJVMCD profile directly, it is causing this problem because the DFHJVMPR profile specified CLASSCACHE=YES. This causes CICS to use a "system" JVM to create the cache. This "system" JVM uses the DFHJVMCD profile.
Once the DFHJVMCD profile has been updated to point to the Java 6.0.1 installation directory in the JAVA_HOME parameter, the problem will no longer occur.
As an alternative, DFHJVMPR could specify CLASSCACHE=NO to not use the classcache and avoid this issue as well.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
30 October 2014
UID
dwa1162411