IT20892: Migrated clustered queue manager fails to start after upgrading from a 32-bit to 64-bit MQ version on Windows

APAR status

• Closed as program error.

Error description

• IBM MQ was upgraded from a 32-bit (prior to v8) to a 64-bit
  MQ version on a Windows server.  Attempts to start and migrate a
  clustered queue manger fails.  A summary of the FDCs after the
  queue manager fails to start are as follows:
  Probe Id          :- ZF228010
  Component         :- zfuHealthCheckECThread
  Major Errorcode   :- xecP_E_INVALID_PID
  MQM Function Stack
  zfuHealthCheckECThread
  xcsFFST
  *
  Probe Id          :- ZX152010
  Component         :- zmuHealthCheckECThread
  Major Errorcode   :- xecP_E_INVALID_PID
  MQM Function Stack
  zmuHealthCheckECThread
  xcsFFST
  *
  Probe Id          :- ZX165061
  Component         :- zmuUtilityManager
  Major Errorcode   :- xecP_E_INVALID_PID
  MQM Function Stack
  amqzmuc0
  zmuUtilityManager
  xcsFFST
  *
  Probe Id          :- ZX165131
  Component         :- zmuUtilityManager
  Major Errorcode   :- zrcE_UNEXPECTED_ERROR
  MQM Function Stack
  amqzmuc0
  zmuUtilityManager
  xcsFFST
  *
  Further examination of the FDCs shows that the invalid PID is
  reported for the Execution controller process (amqzxma0.exe).
  MQ trace of the amqzxma0.exe process ends with:
  
  ----------}  zxcRestoreObjectClqMgrExtractInf (rc=OK)
  ----------{  zxcRestoreObjectClqMgrMigration
  -----------{  xcsGetMemFn
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  32bit WebSphere  MQ server clustered queue managers migrating to
  a 64bit version of MQ, for example , WebSphere MQ prior to
  version 8 migrating to a later IBM MQ version, on Windows
  platforms.
  
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Due to a programming error in the 32 to 64 bit migration code,
  the execution controller process (amqzxma0.exe) may terminate
  with an unhandled memory access violation during the cluster
  migration process when the queue manager cluster list contains
  more than 6 entries.
  

Problem conclusion

• The MQ 32 to 64bit cluster migration code within the MQ queue
  manager has been updated to allocate sufficient memory to
  migrate the entire cluster list.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.8
  v9.0 CD    9.0.4
  v9.0 LTS   9.0.0.2
  
  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:

  XX00232

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE M/P

• Fixed component ID

  5724H7261

Applicable component levels

• R902 PSY

     UP