IT29089: MQ 9.1 queue manager migrated from MQ 7.1 generates FDC AD028008during startup

APAR status

• Closed as program error.

Error description

• The queue manager is migrated from MQ 7.1. During the startup,
  the following failure data capture (FDC) record is always
  reported. The FDC indicates open system call
  failed with error EISDIR(Is a directory) when opening a queue
  file.
  
  Probe Id          :- AD028008
  Component         :- adiOpenFile
  Program Name      :- amqzxma0
  Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
  Probe Description :- AMQ6119S: An internal IBM MQ error has
  occurred (Rc=21from open)
  Comment1        :- Rc=21 from             open
  ...
  MQM Function Stack
  amqzxma0
  zxcExecutionController
  zxcStartupLogic
  kpiStartup
  apiStartup
  aocCompleteRestart
  aqmAccessQueue
  aqqAccessQueue
  aqqAccessQHeader
  aqpReadData
  aqpOpen
  adhOpen
  aduLocateFileCtl
  adiOpenFile
  xcsFFST
  ...
  { aotLocateEntryByQid
  } aotLocateEntryByQid rc=MQRC_UNKNOWN_OBJECT_NAME
  ...
  
  FDC Summary:
  
   AMQ4366.0.FDC  2019/09/25 15:02:31.626954-7 amqzxma0  4366 1
  AD028008 adiOpenFile         xecF_E_UNEXPECTED_SYSTEM_RC
   AMQ4366.0.FDC  2019/09/25 15:02:31.670252-7 amqzxma0  4366 1
  AD004020 adhOpen             krcE_UNEXPECTED_ERROR
   AMQ4366.0.FDC  2019/09/25 15:02:31.714493-7 amqzxma0  4366 1
  AQ143008 aqqAccessQHeader    krcE_UNEXPECTED_ERROR
  

Local fix

• Move the orphaned ghost queue files which are not known to the
  queue manager and for which no corresponding model queue can be
  found out of the queues directory. The user can use the
  following command to check the queues that are known to the
  queue manager and the corresponding file names to find the
  orphaned queues.
  
  * dspmqfls -m <qmgr name> -t all '*'
  
  The filenames not listed by the dspmqfls command likely the
  orphaned queues.
  
  Note: Only the orphaned ghost queues should be moved out of the
  queues directory(or they can be deleted). Moving the ghost queue
  files that are known to the queue manager is likely to cause
  unexpected problems/failures.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users migrating queue managers from MQ 7.1 and lower MQ versions
  to MQ 9.1 with orphaned temporary/permanent dynamic queues
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  During queue manager restart the queue manager checks if there
  are any
  orphaned ghost queues which are not known to the queue manager
  and for
  which no corresponding model queue can be found. When the queue
  manager finds such a file
  it has to determine if this file is related to a temporary
  dynamic queue
  or a permanent dynamic queue. The FDC generated indicates the
  queue
  manager failed to determine the type of queue and that is due to
  an
  error in the code that is failing to account for the fact that
  queues
  are now created as flat files (queues/<queue name>), whereas in
  the past
  MQ (MQ 7.1 and older versions) used a directory per queue
  (queues/<queue directory name>/q).
  

Problem conclusion

• MQ code has been modified to consider the old queue directory
  structure when checking
  the queue file.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 CD    TBC.
  v9.1 LTS   9.1.0.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

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels