IBM Support

IT32321: Intermittent hang in dltdrsecondary command when run after making the queue manager secondary on the HA 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

  • If a user attempts to delete the DR secondary instance of an
    HA/DR
    queue manager, the  command-line interface may hang while
    attempting
    to delete the  DR resources used by the Appliances and queue
    manager. This
    will result in an incomplete deletion of the DR resources for
    the queue manager
    yielding unpredictable behavior of the DR queue manager
    attempting to be deleted.
    
    The following lines may be observed in the
    /var/mqm/trace/dltdrsecondary.c-fmt file of the runmqras output:
    
    Mon Mar 23 16:24:43 EDT 2020: { Entering dltdrsecondary -m DRQM1
    ...
    Mon Mar 23 16:24:47 EDT 2020: pcs resource delete DRQM1_DR_IP
    (no entries after)
    
    and
    
     Mon Mar 23 16:52:14 EDT 2020: { Entering dltdrsecondary -m
    DRQM1
    ...
    Mon Mar 23 16:52:16 EDT 2020: pcs resource delete DRQM1_DR_ping
    Mon Mar 23 16:52:18 EDT 2020: Deleting Resource - DRQM1_DR_ping
    (no entries after)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MQ Appliance in High Availability and Disaster
    Recovery configuration.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    While deleting the cluster resources an incorrect conditional
    check in the code causes the resources to be removed forcefully,
    this leads to unexpected failures.
    

Problem conclusion

  • The code has been modified to correct the incorrect conditional
    check.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.8
    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

    IT32321

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-26

  • Closed date

    2021-01-22

  • Last modified date

    2021-01-22

  • 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 APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

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

Document Information

Modified date:
23 January 2021