PH68733: LIBERTY JVMSERVER REMAINS IN A DISABLING STATE AFTER DFHSJ1007 IS ISSUED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An 0Cx abend occurs on a JVM thread causing CICS to issue
  DFHSJ1007 and phaseout the Liberty JVMSERVER.  If this fails to
  disable the JVMSERVER, the CJSL system task should issue a purge
  against the JVMSERVER.  If the JVMSERVER remains in a disabling
  state, CJSL should escalate to forcepurge, then kill to ensure
  the JVMSERVER is disabled, allowing it to then be re-enabled.
  However, in a region where there are repeated LINK calls to an
  @CICSProgram within the Liberty JVMSERVER (using the
  cicsts:link-1.0 feature), this causes the internal timeout
  before the next disable action is issued to be repeatedly reset.
  This can result in the JVMSERVER remaining in a disabling state.
  
  Additional Keyword(s): Inconsistent, SJ1007
  
  KIXREVQWD
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: JVMSERVER remains in disabling state    *
  *                      after DFHSJ1007 is issued.              *
  ****************************************************************
  A Liberty JVMSERVER is enabled to process a workload that LINKs
  to a Java program using the cicsts:link-1.0 feature.
  
  A 0Cx abend occurs on a JVM thread which puts the JVMSERVER into
  an inconsistent state.  CICS issues a disable phaseout against
  the JVMSERVER.
  
  The 0Cx abend causes the thread used by the cicsts:link-1.0
  feature to hang.  As a result this thread does not terminate and
  CICS continues to send LINK requests to the
  JVM.  These repeatedly time-out causing DFHSJ1006 messages.
  
  If at least one LINK request is made every 60 seconds then CICS
  will not escalate to a disable purge of the JVMSERVER, as the
  clean up processing that occurs after a time-out repeatedly
  resets the 60 second count down.
  
  If disable purge has been issued, then at least one LINK request
  every 15 seconds (or in the interval specified by
  PURGE_ESCALATION_TIMEOUT) will prevent CICS from escalating to
  force purge and kill if these are required.
  
  As a result the JVMSERVER can remain in a disabling state
  indefinitely.
  

Problem conclusion

• CICS has been updated so that if a LINK is made to a Java
  program defined in a JVMSERVER that is not in an enabled state
  then this will fail immediately with an INVREQ response with a
  RESP2 of 52.  The DFHSJ1006 message issued will indicate that
  the JVMSERVER is not enabled.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PH69122 UO06124

Modules/Macros

• DFHSJTH
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R300 PSY UO06124

     UP25/12/11 P F512 ¢

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.