PM65400: WMQ Z/OS 7.0.1:A HANG SITUATION FOR CHANNELS TRYING TO START/STOP 12/11/13 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• After Queue manager restarted, cluster channels started
  automatically, however, most of cluster sender channels looks
  hung during starting or stopping process. Messages failed to
  send and receive.Issued STOP command to CHINIT, however, it did
  not terminate, then cancelled CHINIT, and restarted queue
  manager for recovery.
  
  Simillar messages were found in syslog:
  
  06:12:35.80 +CSQX500I +CSQ1 CSQXRCTL Channel TO.QMGR1 started
  
  06:12:35.80 +CSQX500I +CSQ1 CSQXRCTL Channel TO.QMGR2 started
  ...
  07:35:10.02 CSQM201I +CSQ1 CSQMDRTC  DIS CHSTATUS DETAILS
  
              CHSTATUS(TO.QMGR1)
  
              CHLDISP(PRIVATE)
  
              XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
  
              CONNAME(IP#1)
  
              CURRENT
  
              CHLTYPE(CLUSSDR)
  
              STATUS(STOPPING)
  
              SUBSTATE( )
  
              STOPREQ(NO)
  
              RQMNAME(QMGR1)
  
              END CHSTATUS DETAILS
  
  07:35:10.02 CSQM201I +CSQ1 CSQMDRTC  DIS CHSTATUS DETAILS
  
              CHSTATUS(TO.QMGR2)
  
              CHLDISP(PRIVATE)
  
              XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
  
              CONNAME(IP#2)
  
              CURRENT
  
              CHLTYPE(CLUSSDR)
  
              STATUS(RUNNING)
  
              SUBSTATE( )
  
              STOPREQ(NO)
  
              RQMNAME(QMGR2)
  
              END CHSTATUS DETAILS
  
  Actually TO.QMGR1 had been taken STOP action while TO.QMGR2 had
  been disconnected from  remote queue manager for time out.
  
  A deadly embrace  causes a hang  situation for channels trying
  to start/stop.
  

Local fix

• Cancel CHINIT and restart queue manager for recovery.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Deadlock occurs between supervisor TCB  *
  *                      and dispatcher TCB. Channel initiator   *
  *                      commands are not processed and channels *
  *                      on the affected dispatcher will hang.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The PTF for APAR PM53107 addressed an issue where a timing
  window existed when loading data conversion tables.
  
  The fix did not address the problem in all possible
  environments, specifically when conversion occurs as a
  result of specifying CONVERT(YES) on a Sender Channel.
  

Problem conclusion

Temporary fix

Comments

• Processing has been amended to address the problem
  in the relevant environment.
  ×**** PE13/03/15 FIX IN ERROR. SEE APAR PM84022  FOR DESCRIPTION
  

APAR Information

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

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

  UK81777

Modules/Macros

• CSQACCF  CSQACSTR CSQACS64 CSQALOCT CSQAVICD
  CSQXADPM CSQXLOCT HMS7010J
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK81777

     UP12/10/17 P F210 Ž

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.