IBM Support

IT35557: NPMCLASS(HIGH) not retaining non-persistent messages during QM graceful failover in RDQM HA environment.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In an RDQM HA cluster non-persistent messages on a queue defined
    with
    NPMCLASS(HIGH) may be lost after graceful failover(e.g. rdqmadm
    -p -m testqm -n host1).
    MQ trace of failover captured on the node where the QM was
    running reported an error
    when queue was closed and shutdown during QM shutdown.
    
    00:56:23.427284   1111.11     :        --------{ adiOpenFile
    00:56:23.427287   1111.11     :
    Name(/var/mqm/vols/testqm/qmgr/testqm/queues/TESTQ)
    00:56:23.427303   1111.11     :        --------} adiOpenFile
    rc=OK
    00:56:23.443567   1111.11     :        ----} aqtIdxToSpcFn rc=OK
    00:56:23.443570   1111.11     :        ---}! aqqRechainMsgs
    rc=krcE_RESOURCE_PROBLEM
    00:56:23.450340   1111.11     :        ---} aqmCloseQueue rc=OK
    00:56:23.450343   1111.11     :        --}! aqmShutdownQueue
    rc=krcE_RESOURCE_PROBLEM
    ...
    00:56:23.450355   1111.11     :    -}! aocShutdownQ
    rc=krcE_RESOURCE_PROBLEM
    

Local fix

  • Ensure necessary messages are PUT on the queue as persistent.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using NPMCLASS(HIGH) feature in RDQM HA environment
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in QM shutdown during failover in RDQM HA environment
    caused failure in
    queue shutdown and this resulted in the QM not retaining the
    non-persistent messages.
    

Problem conclusion

  • MQ code has been modified to correct the defect in QM shutdown
    during failover in RDQM HA environment.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.2
    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 number

    IT35557

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-15

  • Closed date

    2021-03-23

  • Last modified date

    2021-03-23

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
25 March 2021