IT37409: RDQM HA queue manager cannot be created with "rdqm" as the queuemanager name

APAR status

• Closed as program error.

Error description

• When attempting to create a queue manager on the primary node of
  areplicated data queue manager (RDQM) setup with name "rdqm"
  (case insensitive), the operation will  fail with the following
  error:
  
  [mqm@host3.org ~]$ crtmqm -sx rdqm
  Creating replicated data queue manager configuration.
  Secondary queue manager created on 'host2.org'.
  Secondary queue manager created on 'host3.org'.
  IBM MQ queue manager created.
  Directory '/var/mqm/vols/rdqm/qmgr/rdqm' created.
  The queue manager is associated with installation
  'Installation1'.
  Creating or replacing default objects for queue manager 'rdqm'.
  Default objects statistics : 83 created. 0 replaced. 0 failed.
  Completing setup.
  Setup completed.
  
  Enabling replicated data queue manager.
  AMQ3817E: Replicated data subsystem call '/usr/sbin/crm
  configure load update
  /var/mqm/trace/rdqm.rdqm.config' failed with return code '1'.
  ERROR: error: unpack_colocation_tags:   Constraint
  'rdqm_with_rdqmx': Invalid reference to 'rdqm'
   error: unpack_location_tags: Constraint
  'rdqm_preferred_location': Invalid reference to 'rdqm'
   error: unpack_order_tags:    Constraint 'rdqm_after_rdqmx':
  Invalid reference to 'rdqm'
   Errors found during check: config not valid
  AMQ3813E: Failed to enable replicated data queue manager.
  

Local fix

• Customer can use alternate Queue  Manager name instead "rdqm"
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All user who try to create an RDQM HA queue manager with name
  "rdqm".
  
  
  Platforms affected:
  Linux on x86-64
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The logic used to escape and separate the queue manager name
  from other internal attributes in the RDQM configuration was
  insufficient if the queue manager was called "rdqm".
  

Problem conclusion

• The RDQM logic handling internal metadata has been updated to
  correct escape the queue manager name, permitting the use of
  "rdqm" for this purpose.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.5
  v9.x CD    9.2.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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels