IT30391: MQ Appliance Queue Manager did not failover to secondary node after resolving partitioned state

APAR status

• Closed as program error.

Error description

• When trying to failover an HA QMgr after an HA partitioned
  state was resolved with the makehaprimary command, the queue
  manager fails to start on the secondary appliance.
  
  After executing sethagrp -s on preferred location, the queue
  manager status is Ended normally.
  
  mqa(mqcli)# dspmq
  QMNAME(QM1)                                        STATUS(Ended
  normally)
  
  HA queue managers migrated from 9.0.x to 9.1 are susceptible to
  this issue.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  MQ Appliance users who use HA queue managers that were migrated
  from version 90x.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The makehaprimary command run to resolve the Partitioned state
  of the queue manager puts the queue manager in banned state on
  the secondary appliance.  As a result the queue manager wouldn't
  start on the HA partner machine during subsequent failover.
  This problem is observed only on queue managers that were
  migrated from version 90x.
  

Problem conclusion

• The code was modified to clear the banned state.
  

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 APPLIANCE M2

• Fixed component ID

  5737H4700

Applicable component levels