IBM Support

IT38347: Queue Managers will not run on the preferred node after MQ Appliance reloads.

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

  • A clean shutdown of the cluster process did not occur after the
    HA primary MQ appliance reloaded.  As a result, some of the
    resource attributes were left behind.  When the cluster
    processes restarted, they prevented some of
    the queue managers to return back to its preferred node.
    
    The status for the queue manager will show the following:
    
    QM(QUEUE_MANAGER)                        Status(Running
    elsewhere)
    HA role:                                 Secondary
    HA status:                               Normal
    HA control:                              Enabled
    HA preferred location:                   This appliance
    DR role:                                 Primary
    DR replication type:                     Asynchronous
    

Local fix

  • Contact IBM MQ Support to receive a service console key to
    remove the files that were left behind.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All MQ Appliance users using it for High Availablity(HA) and
    Disaster Recovery(DR).
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When MQ Appliance reloads, if a clean HA shutdown does not
    happen then it leaves behind some  HA transitory files. These
    files were not removed when the cluster restarted, and as a
    result queue manager was unable to move back to the original
    node where it was running.
    

Problem conclusion

  • The code has been modified to ensure the transitory files used
    for the cluster management are removed when the cluster
    restarts.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.4
    
    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

    IT38347

  • Reported component name

    MQ APPL M2002 V

  • Reported component ID

    5737H4701

  • Reported release

    921

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-13

  • Closed date

    2021-12-21

  • Last modified date

    2022-01-27

  • 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 APPL M2002 V

  • Fixed component ID

    5737H4701

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"921"}]

Document Information

Modified date:
28 January 2022