IT44767: Retrying or running CLUSSDR channels not restarted immediately on queue manager restart

APAR status

• Closed as program error.

Error description

• When a queue manager is started, the queue manager is expected
  to immediately restart the channels
  that were in running or retrying state when the queue ended.
  However the CLUSSDR channels were
  restarted after 30 to 60 seconds delay. The behavior is same
  even after a new message is put to the
  SYSTEM.CLUSTER.TRANSMIT.QUEUE.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of MQ clustering
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A defect in updating the channel status during QM restart caused
  the delay in starting the cluster sender channels
  

Problem conclusion

• MQ code has been modified to resolve the delay in channel
  startup during QM restart
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.25
  v9.3 LTS   9.3.0.20
  v9.x CD    9.3.6
  
  The latest available maintenance can be obtained from
  'IBM MQ Recommended Fixes'
  https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'IBM MQ
  Planned Maintenance Release Dates'
  https://ibm.biz/mqplannedmaintenance
  
  ---------------------------------------------------------------
  

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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels