PI05508: REMOTE SUBSCRIBERS STOPPED RECEIVING PUBLICATIONS FROM THE WEBSPHERE MQ V7.1.0 QUEUE MANAGER.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Although publishers were able to successfully connect to a
  WebSphere queue manager and publish messages for a given
  topic, publications were not reaching the subscribers
  registered with remote queue managers in the Pub/Sub cluster.
  No Publish and Subscribe related error messages were written to
  the queue manager error logs. However, MQ Clustering related
  errors were written to the queue manager error log of the full
  repository, along with an FDC.
  .
  Queue Manager Error Log:
  AMQ9469 Update not received for ...
  .
  FDC:
  Component :- rrmMaintainClqMgr
  Program Name :- amqrrmfa
  Major Errorcode :- rrcW_CLUS_NO_QMGR_UPDATE
  Probe Description :- AMQ9469: Update not received for ...
  

Local fix

• Remove the topic(s) associated with the loss of subscriptions
  from the cluster and then place it back into the same cluster
  This will subsequently force the recreation of proxy
  subscriptions to be made and sent to other queue managers in the
  publish subscribe cluster
  

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: Remote subscribers not receiving        *
  *                      publications after a CLUSRCVR is        *
  *                      removed from the cluster.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A queue manager in a pubsub cluster has two CLUSRCVRs defined
  (both for the same cluster). When one of these CLUSRCVRs is
  deleted the queue manager stops receiving publications made on
  other queue managers in the cluster.
  The reason for this is that rfxDeleteClqMgr runs on all the
  other queue managers in the cluster. On finding it is in a
  pubsub cluster it deletes proxy subscriptions for the QMName, on
  the assumption that the queue manager has now left the cluster.
  In this case however, a clusrcvr remains, the queue manager has
  not left the cluster and proxy subscriptions for it should
  therefore not be deleted.
  

Problem conclusion

• rfxDeleteClqMgr has been changed to check if the CLQMGR being
  removed from the cluster is the last remaining CLQMGR for that
  queue manager, and if so deletes proxy subscriptions for that
  destination.
  010Y
  100Y
  CSQXRFXC
  CSQXTRTB
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

  IC96426

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

  UI13779 UI13780

Modules/Macros

• CSQXRFXC CSQXTRTB
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UI13779

     UP14/02/05 P F402 Ž

• R100 PSY UI13780

     UP14/02/05 P F402 Ž

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.