PM79483: CHIN TASK DOES NOT TERMINATE DUE TO LOOP CONDITION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After an external failure the queue manager initiated
  termination after which the CHIN address space generated
  recursive snap dumps for XFFSrstConsumer ; meanwhile the CHIN
  itself was discovered to be looping and never terminated.
  As determined by Level 3 the CHINIT posted an async-consumer
  call back. Before the call back thread was able to issue the
  CSQMGETM call to get the message from the queue, the QMGR
  terminated. Thus, when reaching the code where the call is
  done, the thread detected the QMGR had gone and updated its
  return code to 2162 (QMGR stopping). However this return
  code does not cause the async-consume thread to stop
  processing, and it is stuck in an infinite loop waiting for
  the control thread to tell it to terminate. The control
  thread cannot do this as it needs the async-consume thread
  to un-dispatch itself and allow other units of execution
  in the CHINIT (that are using the same dispatching) to do
  some processing. This causes the CHINIT to be stuck and
  not shut down correctly
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and Release 1       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The CHINIT hangs during QMGR shutdown   *
  *                      when using client async consume or      *
  *                      server conn channels with SHRCNV        *
  *                      greater than 1.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The async consume call back thread in the CHINIT is kicked off,
  but the QMGR is shutting down before the lpiSPIMQGETM call can
  be issued. This causes the async consume thread to go into an
  infinite loop, causing the CHINIT to hang.
  

Problem conclusion

• The code was changed to successfully terminate the async consume
  thread if the QMGR goes away.
  010Y
  100Y
  CSQXRSTM
  

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:

  UK92043 UK92044

Modules/Macros

• CSQXRSTM
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK92043

     UP13/04/05 P F304

• R100 PSY UK92044

     UP13/04/04 P F304

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.