DFHSJ1109 date time applid An attempt to determine the highest semantic version of the bundletype bundle with symbolic name symbolicname referenced by bundle part bundlepartname of BUNDLE bundlename to install into JVMSERVER jvmserver has failed with reason code {JVMSERVER_NOT_FOUND | JVMSERVER_NOT_ENABLED | NO_BUNDLE_IN_VERSION_RANGE | EXCEPTION_FROM_JVMSERVER | INTERNAL_ERROR}.
Explanation
An attempt to determine the highest semantic version of the OSGi bundle with a symbolic name of symbolicname which is referenced by bundle part bundlename of CICS BUNDLE resource bundlename has failed. This error can occur when either installing a CICS BUNDLE resource that contains one or more OSGi bundles or after issuing a SET BUNDLE PHASEIN command. The reason code provides further information about why the bundle installation failed.
- JVMSERVER_NOT_FOUND
-
The target JVMSERVER is not available.
- JVMSERVER_NOT_ENABLED
-
The target JVMSERVER is not enabled.
- NO_BUNDLE_IN_VERSION_RANGE
-
No version of the OSGi bundle with a symbolic name of symbolicname found in the version range defined by the versionRange= attribute of its associated OSGi Bundle Project Reference.
- EXCEPTION_FROM_JVMSERVER
-
The JVM has thrown an exception while reading a JAR file to determine the highest semantic version of the OSGi bundle with a symbolic name of symbolicname.
- INTERNAL_ERROR
-
An internal system error occurred.
System action
CICS was unable to install the OSGi bundle into the OSGi framework. The OSGi Bundle Project Reference bundlepartname of the CICS BUNDLE resource bundlename is placed in an UNUSABLE state, and the CICS BUNDLE resource is disabled.
User response
Examine the reason code to determine why the OSGi bundle installation failed. If required, perform one of the following actions:
- JVMSERVER_NOT_FOUND
-
Check that the target JVM server jvmserver specified on the jvmserver= attribute in the OSGi Bundle Project Reference bundlepartname in CICS BUNDLE bundlename is correct. If not, specify the correct JVM server using the CICS Explorer SDK. If the correct JVM server is specified, ensure it is installed and enabled.
- JVMSERVER_NOT_ENABLED
-
Enable the target JVMSERVER jvmserver.
- NO_BUNDLE_IN_VERSION_RANGE
-
Check that the version range specified on the versionRange= attribute in the OSGi Bundle Project Reference bundlepartname in CICS BUNDLE bundlename is correct and/or the jar for the OSGi bundle has been exported to the same directory as its associated .osgibundle bundle part.
- EXCEPTION_FROM_JVMSERVER
-
Check the system log for other DFHSJ messages and the JVM server diagnostic information on zFS to determine the cause of the exception.
- INTERNAL_ERROR
-
Contact IBM Support
When you have corrected the problem, discard and reinstall the CICS BUNDLE resource bundlename.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- bundletype
- symbolicname
- bundlepartname
- bundlename
- jvmserver
- Value chosen from the following options:
1=JVMSERVER_NOT_FOUND, 2=JVMSERVER_NOT_ENABLED, 3=NO_BUNDLE_IN_VERSION_RANGE, 4=EXCEPTION_FROM_JVMSERVER, 5=INTERNAL_ERROR
Destination
CSMT