IBM Support

SE42046: QUEUE MANAGER MAY NOT START AFTER UPGRADE V6 TO V7.0.1.1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The queue manager fails to start at V7.0.1.1 on OS V6R1M0,
    and V5R4M0.  This problem may or may not occur after upgrading
    from V6.0.  A cold start does not resolve the problem. The
    following probe ids result from the failure to start AO127000,
    AO028002, and AL038229.
    .
     WebSphere MQ First Failure Symptom Report
     =========================================
    
    Date/Time         :- Monday June 21 2010 13:58:05
    UTC Time          :- 1277128685.444584
    UTC Time Offset   :- 0 (UNKNOWN)
    Host Name         :- MQAS07.RTP.RALEIGH.IBM.COM
    Operating System  :- OS400 V6R1M0
    PIDS              :- 5724H7226
    LVLS              :- 7.0.1.1
    Product Long Name :- WebSphere MQ for i5/OS
    Vendor            :- IBM
    Probe Id          :- AO127000
    Application Name  :- MQM
    Component         :- aotLocateEntryByQid
    SCCS Info         :- lib/lqm/amqaotfa.c, 1.22.2.1
    Line Number       :- 288
    Build Date        :- Dec 22 2009
    CMVC level        :- p701-101-091221
    UserID            :- 00000137 (QMQM)
    Job Name          :- 067941/QMQM/AMQZXMA0
    Job Description   :- QMQM/AMQZXMA0
    Submitted By      :- 067940/ADMIN/STRMQM_R
    Activation Group  :- 19 (QMQM) (QMQM/AMQZXMA0)
    Max File Handles  :- 2048
    Process           :- 00000440
    Thread            :- 00000001
    QueueManager      :- TEST.MQM
    UserApp           :- FALSE
    ConnId[1] IPCC    :- 2
    ConnId[2] QM      :- 2
    ConnId[3] QM-P    :- 2
    ConnId[4] App     :- 2
    Major Errorcode   :- STOP_ALL
    Minor Errorcode   :- OK
    Probe Type        :- HALT6110
    Probe Severity    :- 1
    Probe Description :- AMQ6110: An internal WebSphere MQ error has
    occurred.
    FDCSequenceNumber :- 0
    Arith1            :- 0
    Arith2            :- 0
    .
    MQM Function Stack
    ExecCtrlrMain
    zxcStartupLogic
    kpiStartup
    apiStartup
    almPerformReDoPass
    apiReplayLogRecord
    aocReplayLogRecord
    aomReplayMediaLSNs
    aotLocateEntryByQid
    xcsFFST
    .
    WebSphere MQ First Failure Symptom Report
    =========================================
    
    Date/Time         :- Monday June 21 2010 13:59:51
    UTC Time          :- 1277128791.270200
    UTC Time Offset   :- 0 (UNKNOWN)
    Host Name         :- MQAS07.RTP.RALEIGH.IBM.COM
    Operating System  :- OS400 V6R1M0
    PIDS              :- 5724H7226
    LVLS              :- 7.0.1.1
    Product Long Name :- WebSphere MQ for i5/OS
    Vendor            :- IBM
    Probe Id          :- AO028002
    Application Name  :- MQM
    Component         :- apiReplayLogRecord
    SCCS Info         :- lib/lqm/amqapija.c, 1.33.2.1
    Line Number       :- 278
    Build Date        :- Dec 22 2009
    CMVC level        :- p701-101-091221
    UserID            :- 00000137 (QMQM)
    Job Name          :- 067941/QMQM/AMQZXMA0
    Job Description   :- QMQM/AMQZXMA0
    Submitted By      :- 067940/ADMIN/STRMQM_R
    Activation Group  :- 19 (QMQM) (QMQM/AMQZXMA0)
    Max File Handles  :- 2048
    Process           :- 00000440
    Thread            :- 00000001
    QueueManager      :- TEST.MQM
    UserApp           :- FALSE
    ConnId[1] IPCC    :- 2
    ConnId[2] QM      :- 2
    ConnId[3] QM-P    :- 2
    ConnId[4] App     :- 2
    Major Errorcode   :- STOP_ALL
    Minor Errorcode   :- OK
    Probe Type        :- HALT6110
    Probe Severity    :- 1
    Probe Description :- AMQ6110: An internal WebSphere MQ error has
    occurred.
    FDCSequenceNumber :- 18
    Arith1            :- 0
    Arith2            :- 0
    .
    
    MQM Function Stack
    ExecCtrlrMain
    zxcStartupLogic
    kpiStartup
    apiStartup
    almPerformReDoPass
    apiReplayLogRecord
    xcsFFST
    .
    WebSphere MQ First Failure Symptom Report
    =========================================
    
    Date/Time         :- Sunday June 13 2010 12:32:36
    UTC Time          :- 1276450356.518304
    UTC Time Offset   :- -300 (UNKNOWN)
    Host Name         :- MQAS07.RTP.RALEIGH.IBM.COM
    Operating System  :- OS400 V6R1M0
    PIDS              :- 5724H7226
    LVLS              :- 7.0.1.1
    Product Long Name :- WebSphere MQ for i5/OS
    Vendor            :- IBM
    Probe Id          :- AL038229
    Application Name  :- MQM
    Component         :- alsLocateReplayJSN
    SCCS Info         :- lib/lqm/unix/as400/amqalccx.c, 1.75.1.1
    Line Number       :- 803
    Build Date        :- Dec 22 2009
    CMVC level        :- p701-101-091221
    UserID            :- 00000107 (QMQM)
    Job Name          :- 377725/QMQM/AMQZXMA0
    Job Description   :- QMQM/AMQZXMA0
    Submitted By      :- 377724/ADMIN/STRMQM_R
    Activation Group  :- 17 (QMQM) (QMQM/AMQZXMA0)
    Max File Handles  :- 2048
    Process           :- 00000101
    Thread            :- 00000001
    QueueManager      :- TEST.MQM
    UserApp           :- FALSE
    ConnId[1] IPCC    :- 2
    ConnId[2] QM      :- 2
    ConnId[3] QM-P    :- 2
    ConnId[4] App     :- 2
    Major Errorcode   :- arcW_NO_CHECKPT_DATA
    Minor Errorcode   :- OK
    Probe Type        :- INCORROUT
    Probe Severity    :- 3
    Probe Description :- AMQ6125: An internal WebSphere MQ error has
    occurred.
    FDCSequenceNumber :- 0
    Arith1            :- 248 0x'f8'
    Arith2            :- 72 0x'48'
    .
    
    MQM Function Stack
    ExecCtrlrMain
    zxcStartupLogic
    kpiStartup
    apiStartup
    almPerformReDoPass
    alsLocateReplayJSN
    xcsFFST
    .
    

Local fix

  • No other way found to start the queue manager short of deleting
    it and creating it manually.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    WMQ users attempting to start a queue manager either normally or
    after a cold start
    
    Platforms affected:
    iSeries
    
    ****************************************************************
    PROBLEM SUMMARY:
    There was a code path in WMQ where journal replay could be
    attempted even when no checkpoint data had been found. This
    would prevent the queue manager from starting, even when a
    cold start was performed.
    

Problem conclusion

  • WMQ code has been modified to allow startup of the queue manager
    if no checkpoint data was encountered without incorrectly
    attempting to replay the journal
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    iSeries            tbc_p700_0_1_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 number

    SE42046

  • Reported component name

    WMQ ISERIES V7

  • Reported component ID

    5724H7226

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-03-08

  • Closed date

    2010-03-12

  • Last modified date

    2010-06-22

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

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

Modules/Macros

  • RCHMGR
    

Fix information

  • Fixed component name

    WMQ ISERIES V7

  • Fixed component ID

    5724H7226

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2020