IV90040: QUEUE MANAGER FAILS TO START WITH ERROR AMQ7017 FOLLOWING AN ABNORMAL TERMINATION.

APAR status

• Closed as program error.

Error description

• A queue manager fails to start with the AMQ7017 error and an
  FDC record with a probe id HL083112 following an abnormal
  termination.
  The abnormal termination was due to the failure to open a
  checkpoint file during the queue manager shut down.
  
  The FDC record will be observed:
  
  Probe Id          :- AL036002
  Application Name  :- MQM
  Component         :- alsRecordCheckPoint
  Program Name      :- amqzmuc0
  Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
  Probe Description :- AMQ6119: An internal WebSphere MQ error has
  occurred     (open())
  FDCSequenceNumber :- 0
  Arith1            :- 26 (0x1a)
  Comment1          :- open()
  
  While starting the queue manager, the following errors would be
  observed:
  AMQ7017 - Log not available will be seen in the queue manager
  error logs as well on the command line when strmqm command is
  issued.
  
  Also, the following FDC record will be observed:
  LVLS              :- 7.1.0.2
  Product Long Name :- WebSphere MQ for AIX
  Vendor            :- IBM
  Installation Path :- /usr/mqm
  Installation Name :- Installation1    (1)
  Probe Id          :- HL083112
  Application Name  :- MQM
  Component         :- mqlReadLogRecord
  Program Name      :- amqzxma0
  Addressing mode   :- 64-bit
  Major Errorcode   :- hrcE_UNEXPECTED_ERROR
  Minor Errorcode   :- OK
  Probe Type        :- INCORROUT
  Probe Severity    :- 2
  Probe Description :- AMQ6125: An internal WebSphere MQ error
  has occurred.
  
  MQM Function Stack
  ExecCtrlrMain
  zxcStartupLogic
  kpiStartup
  apiStartup
  almPerformReDoPass
  hlgScanLogBegin
  mqlReadLogRecord
  xcsFFST
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using MQ
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When the queue manager ends because of a failure in completing
  the checkpoint, there is a possibility of inconsistency between
  the checkpoint data stored in the checkpoint file and the data
  stored in the recovery logs. The queue manager did not resolve
  this
  inconsistency during subsequent startup, which resulted in
  failure during queue manager startup.
  

Problem conclusion

• MQ code has been modified to resolve the inconsistency in the
  checkpoint data to resolve the problem.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.1       7.1.0.9
  v7.5       7.5.0.8
  v8.0       8.0.0.7
  v9.0 CD    9.0.3
  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:

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

Fix information

• Fixed component name

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R710 PSY

     UP