Question & Answer
Question
Why would I receive message DFHSJ0210 indicating the JVM server start failed due to a JVMPROFILE_ERROR after upgrading to CICS Transaction Server for z/OS (CICS TS) V5.2? I receive message:
DFHSJ0210 date time applid An attempt to start a JVM for the JVMSERVER resource jvmserver has failed. Reason code: JVMPROFILE_ERROR.
If I look at the SYSPRINT output I see the following exception was also issued indicating it could not find the file or directory:
date time MYLIBSRV *Exc*: Attempt to open JVM profile DFHOSGI.jvmprofile has failed. Runtime error message = EDC5129I No such file or directory.
I am running CICS TS V5.2 with a supported level of Java V7.1 and have verified that the JVMPROFILEDIR in the system initialization parameter (SIT) points to my CICS TS V5.2 JVMProfiles directory (/u/cicsts52/JVMProfiles)
Answer
The naming convention for JVM profiles has changed in CICS TSV 5.2. As documented under Changes to options in JVM profiles in the CICS TS V5.2 documentation, JVM profiles must have a file extension of .jvmprofile otherwise the JVM server will fail to enable.
In CICS TS for z/OS, Version 5.2, JVM servers can be defined in CICS bundles. For these JVM servers, the JVM profile is packaged in the CICS bundle with the JVMSERVER resource definition. CICS does not load these JVM profiles from the directory that is specified by the SIT JVMPROFILEDIR parameter. Instead, they are stored in a suitable directory for the CICS bundle, and the location is specified by the CICS bundle.
The sample JVM profiles that are shipped with CICS TS for z/OS, Version 5.2 have this file extension. Please note that you must run the DFHIJVMJ installation job to create the sample JVM profiles with the .jvmprofile suffix.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
09 December 2016
UID
dwa1182291