IBM Support

DFHSJ0918 JVMSERVER disabled due to PHASEOUT request during CICS startup

Question & Answer


Question

Why would I receive message DFHSJ0918 indicating the Liberty JVM server failed to start due to a PHASEOUT request?

The CICS messages I receive are

 DFHSJ0910 date time applid userid JVMSERVER jvmserver has been created.
 DFHSJ0207 date time applid JVMSERVER jvmserver is running Java version 1.8.0.
 DFHSJ0919 I date time applid userid JVMSERVER jvmserver is processing any queued bundles.
 DFHSJ0915 date time applid userid JVMSERVER jvmserver is now enabled and is ready for use.
 DFHSJ0918 date time applid userid JVMSERVER jvmserver is being disabled due to a PHASEOUT request.
 DFHSJ0917 date time applid userid JVMSERVER jvmserver is disabled.
 DFHSJ1006 E date time applid userid An attempt to attach to JVMSERVER jvmserver has failed because the JVMSERVER is not enabled.

Answer

The STDERR output (DFHJVMERR) shows the following exception is occurring:

 org.osgi.framework.BundleException: Could not resolve module: com.ibm.cics.osgi.impl [10]
   Unresolved requirement: Import-Package: com.ibm.cics.wlp.link; version="[1.100.0,2.0.0)"
     at org.eclipse.osgi.container.Module.start(Module.java:434)
     at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
     at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
     at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
     at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242)
     at org.eclipse.osgi.container.Module.doStart(Module.java:571)
     at org.eclipse.osgi.container.Module.start(Module.java:439)
     at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172)
     at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
     at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
     at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115)
     at com.ibm.cics.router.Router.initStandardOSGI(Router.java:638)
     at com.ibm.cics.router.Router.initOSGi(Router.java:365)
     at com.ibm.cics.router.Router.main(Router.java:1326)

This exception indicates that it is unable to resolve the jar file com.ibm.cics.wlp.link.jar. This jar was introduced by CICS APAR PI58375 to support Liberty Java EE 7 Full Platform in Standard Mode running in CICS. It became available 22 July 2016. The PTFs for this APAR need to be applied to both CICS TS for z/OS and zFS. So, the problem is that either DFHSJSC was not updated with this PTF or the zFS contents used by CICS at runtime have not been updated.

You need to verify the level of DFHSJSC is at PTF UI39576 or higher. You also need to verify in USSHOME/lib the timestamp for com.ibm.cics.wlp.link.jar is at the same level. They both should be dated July 22, 2016 or later.

Once the CICS datasets and USSHOME directories are at the correct level then everything will work successfully.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Java","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
05 October 2016

UID

dwa1307407