IC92737: A CLUSSDR CHANNEL IS NOT STARTED WHEN PERSISTENT PUB/SUB MESSAGES ARE PUT TO CLUSTERED TOPICS

WebSphere MQ V7.5 Fix Pack 7.5.0.3

APAR status

• Closed as program error.

Error description

• When messages are put to cluster queues in syncpoint the
  cluster
  channels are not started until the application calls MQCMIT;
  the CLUSSDR channels to all the queue managers which are
  destinations for messages put in the Unit of Work are started
  during commit processing.
  This operation does not appear to be carried out when
  publications are put to remote cluster subscriber queues at the
  commit of the internal Unit of Work, that is, the cluster
  channels associated with the put of the subscriber messages are
  not started at that time. The channels are held in the queue
  manager's memory associated with the connection, and are
  started when the application is disconnected and the connection
  is closed.
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• Local Fix
  There are 4
  1. Change PMSGDLV to ALLAVAIL
  2. Change the messages to non-persistent
  3. Change the CLUSRCVR channels to DISCINT(0)
  4. Call MQDISC after putting msgs to a clustered topic
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users publishing persistent messages outside syncpoint to
  clustered topics with durable subscriptions on remote cluster
  queue managers
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  The cluster channel was not started when the internal unit of
  work was committed. The unit of work is opened to ensure all
  messages are put to durable subscriptions.
  

Problem conclusion

• If necessary start cluster channels when all messages have been
  put to subscribers.
  
  The APAR IV21703 fixed the same problem in MQ 701 and MQ 7.1 and
  the APAR IC92737 was port of IV21703 to MQ 7.5.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.3
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  WMQ BASE MULTIP

• Fixed component ID

  5724H7241

Applicable component levels

• R750 PSY

     UP