PH38250: CICS WAS NOT ABLE TO SUCCESSFULLY DISABLE AND THEN RE-ENABLE A JVMSERVER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A failure occurs within a JVM (in the reported case this was an
  0C4 in JIT code) that results in:
  
  DFHSJ1007 JVMSERVER is being disabled and restarted by CICS
  because it is in an inconsistent state.
  
  CICS starts to disable the JVMSERVER.  The task disabling the
  JVMSERVER then calls into the JVM in sjth_quiesce_wlp_threads.
  However if the task's Java stack has been corrupted by the
  earlier failure then this call may hang.  If this occurs then
  the JVMSERVER will hang in disabling state.  The hanging task
  owns the JVMSRVLK which will prevent other tasks performing
  operations on the JVMSERVER.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: JVMSERVER in disabling state            *
  *                      indefinitely after DFHSJ1007.           *
  ****************************************************************
  In the reported case a Liberty JVMSERVER was running
  successfully then an 0C4 in JVM code occurred.  CICS detected
  the 0C4, issued DFHSJ1007, and then attempted to disable and
  re-enable the JVMSERVER.  However the logic to disable the
  JVMSERVER hung.
  
  The logic to disable a JVMSERVER includes a call to CICS Java
  code which then calls Liberty to stop.  In this case CICS
  called this Java code on the TCB/thread which encountered the
  0C4.  The TCB no longer had a Java stack which caused the call
  to hang leaving the JVMSERVER in a disabling state indefinitely.
  
  The task attempting to disable the JVMSERVER correctly held
  the JVMSRVLK lock at the time of the hang which meant no other
  task could perform actions against the JVMSERVER.
  

Problem conclusion

• CICS has been changed so that when a Liberty JVMSERVER is
  disabled the call to CICS Java code to stop Liberty is made on a
  different TCB/thread from that which requested the JVMSERVER be
  disabled.
  

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:

  UI76691 UI76692 UI76693 UI76694 UI76695 UI76696 UI76697 UI76698

Modules/Macros

• DFHAPJVM DFHAXIS2 DFHCDJNI DFHSJBD  DFHSJDM  DFHSJDS  DFHSJDUF
  DFHSJIN  DFHSJIS  DFHSJIX  DFHSJJS  DFHSJL   DFHSJNA  DFHSJNR
  DFHSJNT  DFHSJRE  DFHSJRL  DFHSJRM  DFHSJRT  DFHSJSC  DFHSJSM
  DFHSJST  DFHSJT8  DFHSJTH  DFHSJTRI DFHSJXM  DFJ@H317 DFJ@H356
  DFJ@H360 DFJ@H427 DFJ@H467 DFJ@H468 DFJDTCOE DFJOUTRE DFJWLPBP
  DFJWLPPL
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI76696

     UP21/08/14 P F108 ¢

• R003 PSY UI76698

     UP21/08/14 P F108 ¢

• R00D PSY UI76697

     UP21/08/14 P F108 ¢

• R100 PSY UI76693

     UP21/08/13 P F108 ¢

• R103 PSY UI76695

     UP21/08/14 P F108 ¢

• R10D PSY UI76694

     UP21/08/14 P F108 ¢

• R200 PSY UI76692

     UP21/08/13 P F108 ¢

• R300 PSY UI76691

     UP21/08/13 P F108 ¢

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.