IT39744: SYSTEM.CLUSTER.TRANSMIT.QUEUE had USAGE(NORMAL) and, months later, queue manager failed

APAR status

• Closed as program error.

Error description

• SYSTEM.CLUSTER.TRANSMIT.QUEUE had been configured by the user
  incorrectly to have USAGE(NORMAL). The
  SYSTEM.CLUSTER.TRANSMIT.QUEUE is expected to be defined with
  USAGE(XMITQ).
  
  Following this, the Queue manager's cluster repository manager
  program (name: amqrrmfa) did not immediately write errors.  But,
  after many months with no errors, then a severe failure
  occurred, in which amqrrmfa could not put a message to the
  queue.  The internal cluster state updates were consistently
  failing.  Also, if left unattended, this failure would lead to
  the queue manager ending after a few days.
  
  When the error eventually occurred, this was written to the
  queue manager error logs:
  
  AMQ9511E: Messages cannot be put to a queue.
  EXPLANATION: The attempt to put messages to queue
  'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'xxx' failed
  with reason code 2092.
  
  Reason code 2092 means MQRC_XMIT_Q_USAGE_ERROR.
  
  Note that, even if other cluster transmission queues are used on
  the queue manager, the incorrect USAGE attribute on the
  SYSTEM.CLUSTER.TRANSMIT.QUEUE still would cause similar
  failures.  This means the same problem would affect queue
  managers using other cluster transmission queues.
  

Local fix

• Correct the SCTQ definition to specify USAGE(XMITQ).
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who have mis-configured their queue manager by setting
  USAGE(NORMAL) on the SYSTEM.CLUSTER.TRANSMIT.QUEUE.  This
  mis-configuration is likely to happen rarely, or never.
  
  Even if other cluster transmission queues are used on the queue
  manager, the MQ code still checks attributes of the
  SYSTEM.CLUSTER.TRANSMIT.QUEUE.  Therefore queue managers that
  are configured to use other cluster transmission queues are also
  susceptible to the issue.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Although setting USAGE(NORMAL) on the
  SYSTEM.CLUSTER.TRANSMIT.QUEUE is a user mistake, the queue
  manager should have detected the bad configuration and written
  an error sooner - for example, during queue manager startup - to
  alert the user to the situation.  Then the user can correct the
  configuration and not be susceptible to the unexpected failure
  described.
  

Problem conclusion

• The IBM MQ code has been altered to detect a setting of
  USAGE(NORMAL) on the SYSTEM.CLUSTER.TRANSMIT.QUEUE during queue
  manager startup, and write a AMQ9531E and AMQ9448E error
  messages, to alert the user to the situation.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.6
  v9.x CD    9.2.5
  
  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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels