DFHSJ0210 date time applid An attempt to start a JVM for the JVMSERVER resource jvmserver has failed. Reason code: {JVMPROFILE_ERROR | OPEN_JVM_ERROR | JNI_CREATE_NOT_FOUND | SETUP_CLASS_NOT_FOUND | TERMINATION_CLASS_NOT_FOUND | CREATE_JVM_FAILED | CHANGE_DIRECTORY_CALL_FAILED | STDOUT/STDERR_ACCESS_FAILED | ERROR_LOCATING_MAIN_METHOD | ATTACH_JNI_THREAD_FAILED | SETUP_CLASS_TIMEDOUT | ENCLAVE_INIT_FAILED | USS_VOLUME_CHECK_FAILED | REDIRECT_IO_FAILED | ANGEL_UNAVAILABLE | ERROR_CODE_UNRECOGNIZED}.
Explanation
An attempt to start a JVM for the JVMSERVER resource jvmserver has failed. The reason code provides further information about why the JVM failed to start:
- ANGEL_UNAVAILABLE
-
The Liberty angel process is unavailable.
- ATTACH_JNI_THREAD_FAILED
-
An attempt to attach a thread and run setup or termination classes in the JVM server has failed.
- CHANGE_DIRECTORY_CALL_FAILED
-
An attempt to change the zFS working directory has failed.
- CREATE_JVM_FAILED
-
An attempt to create a JVM has failed. Additional diagnostic messages have been output to the standard error stream.
- ENCLAVE_INIT_FAILED
-
The Language Environment enclave failed to initialize successfully. Check that the SDFJAUTH library is in the STEPLIB concatenation of the CICS region.
- ERROR_CODE_UNRECOGNIZED
-
START_JVM returned an error that was not handled.
- ERROR_LOCATING_MAIN_METHOD
-
An attempt to locate the main method within a setup or termination class has failed. An exception has been output to the standard error stream.
- JNI_CREATE_NOT_FOUND
-
JNI Create has not been found. This error might occur because the JAVA_HOME value in the JVM profile does not specify the correct Java installation location.
- JVMPROFILE_ERROR
-
An error occurred when processing the JVM profile. Additional diagnostic messages have been output to the standard error stream. The standard error stream is usually redirected to the location on zFS specified by the WORK_DIR parameter of the JVM profile. However, for early failures prior to redirection, the standard error stream might be located in SYSPRINT, or in the CICS log as a dynamically generated DD name.
- OPEN_JVM_ERROR
-
An error occurred when opening the JVM DLL. This error might occur because the JAVA_HOME value in the JVM profile does not specify the correct Java installation location.
- REDIRECT_IO_FAILED
-
An attempt to redirect stdout, stderr, or jvmtrace output for the JVM has failed. Additional diagnostic messages have been output to the standard error stream either on zFS, in SYSPRINT, or in the CICS log as a dynamically generated DD name.
- SETUP_CLASS_NOT_FOUND
-
A setup class specified in the JVM profile cannot be found. An exception has been output to the standard error stream.
- SETUP_CLASS_TIMEDOUT
-
A setup class did not return in a reasonable amount of time and was therefore canceled.
- STDOUT/STDERR_ACCESS_FAILED
-
An attempt to open the stdout or stderr stream for output has failed. The most likely reason is that the CICS job has read access only to the directory specified by WORK_DIR in the JVM profile.
- TERMINATION_CLASS_NOT_FOUND
-
A termination class specified in the JVM profile cannot be found. An exception has been output to the standard error stream.
- USS_VOLUME_CHECK_FAILED
-
An attempt to create stdout and stderr files for the JVM has failed because the USS file system is full.
System action
CICS was unable to create the JVM and returns an error to the calling module.
User response
Examine reason code msg_reason to determine why the JVM creation failed and, if required, perform one of the following user actions:
- JVMPROFILE_ERROR
-
Use the additional messages in the standard error stream to determine the cause of the problem. The messages that are output prior to the redirection can be found either in SYSPRINT or in a dynamically generated DD name in the CICS log.
- OPEN_JVM_ERROR
-
Check that the JAVA_HOME value in the JVM profile specifies the correct Java installation location.
- JNI_CREATE_NOT_FOUND
-
Check that the JAVA_HOME value in the JVM profile specifies the correct Java installation location.
- SETUP_CLASS_NOT_FOUND
-
Check the following:
-
The directory or archive containing the setup class is added to the classpath using the CLASSPATH_SUFFIX JVM Profile option.
-
The setup class is fully qualified.
Use the exception output to the standard error stream, to determine the cause of the problem.
-
- TERMINATION_CLASS_NOT_FOUND
-
Check the following:
-
The directory or archive containing the termination class is added to the classpath using the CLASSPATH_SUFFIX JVM Profile option.
-
The termination class is fully qualified.
Use the exception output to the standard error stream, to determine the cause of the problem.
-
- CREATE_JVM_FAILED
-
Use the diagnostic messages output to the standard error stream to determine the cause of the problem.
- CHANGE_DIRECTORY_CALL_FAILED
-
Check that the CICS job has read, write and execute access to the directory specified by WORK_DIR in the JVM profile.
- STDOUT/STDERR_ACCESS_FAILED
-
Check that the CICS job has read and write access to the directory specified by WORK_DIR in the JVM profile.
- ERROR_LOCATING_MAIN_METHOD
-
Use the exception in the standard error stream to determine the cause of the problem.
- ATTACH_JNI_THREAD_FAILED
-
Contact IBM Support.
- SETUP_CLASS_TIMEDOUT
-
Ensure your setup classes are not long running and return from the JVM within a reasonable time limit.
- ENCLAVE_INIT_FAILED
-
To determine the cause of the problem check SYSPRINT, or the CICS log, for error messages that are output by the Language Environment. It is likely that either the SDFJAUTH PDSE has not been included in the APF authorized STEPLIB concatenation, or there is not enough storage available to Language Environment. Additional information may be available in message DFHSJ0216.
- USS_VOLUME_CHECK_FAILED
-
Allocate more space to the file system used for stdout and stderr. Consider removing files that are no longer needed.
- ANGEL_UNAVAILABLE
-
Review the actions of the accompanying DFHSJ1400E, DFHSJ1401E, DFHSJ1402W, DFHSJ1403W or DFHSJ1404D message.
- REDIRECT_IO_FAILED
-
Use the exception in the standard error stream to determine the cause of the problem.
- ERROR_CODE_UNRECOGNIZED
-
Contact IBM Support.
Module
DFHSJINXMEOUT parameters/Message inserts
- date
- time
- applid
- jvmserver
- Value chosen from the following options:
1=JVMPROFILE_ERROR, 2=OPEN_JVM_ERROR, 3=JNI_CREATE_NOT_FOUND, 4=SETUP_CLASS_NOT_FOUND, 5=TERMINATION_CLASS_NOT_FOUND, 6=CREATE_JVM_FAILED, 7=CHANGE_DIRECTORY_CALL_FAILED, 8=STDOUT/STDERR_ACCESS_FAILED, 9=ERROR_LOCATING_MAIN_METHOD, 10=ATTACH_JNI_THREAD_FAILED, 11=SETUP_CLASS_TIMEDOUT, 12=ENCLAVE_INIT_FAILED, 13=USS_VOLUME_CHECK_FAILED, 14=REDIRECT_IO_FAILED, 15=ANGEL_UNAVAILABLE, 20=ERROR_CODE_UNRECOGNIZED
Destination
CSMT