IBM Support

IT36630: RDQM may show status as 'Ended Unexpectedly' instead of 'RunningElsewhere' on the Secondary node

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

  • When the 'dspmq' or 'rdqmstatus' commands are issued on a
    working replicated data queue manager (RDQM), the status on the
    secondary nodes
    might show as 'Ended Unexpectedly' instead of 'Running
    elsewhere'.
    
    Example of 'rdqmstatus' issued in a secondary node:
    Queue manager name:                     RDQMQMGR
    Queue manager status:                   Ended unexpectedly
    HA current location:                    hostname
    

Local fix

  • Workaround:
    Trigger a manual failover of the RDQM by changing the
    preferred node. Verify the queue manager status on all the
    nodes is as expected, then set the preferred node back to its
    original preferred.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All IBM MQ users using RDQM feature
    
    
    Platforms affected:
    Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Running crm_resource --cleanup command to clear the failed
    actions might have resulted in incorrect status being displayed
    when queue manager status is queried on the Secondary node.  The
    status of the queue manager on the Secondary might have shown as
    'Ended' instead of 'Running Elsewhere'.
    

Problem conclusion

  • The code has been modified to correct this problem.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.4
    v9.x CD    9.2.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 number

    IT36630

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-20

  • Closed date

    2021-10-19

  • Last modified date

    2022-02-01

  • 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":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
02 February 2022