IBM Support

IT13060: MQSILIST COMMAND HANGS ON STANDBY INSTANCE OF INTEGRATION NODE WHEN IT IS RUNNING.

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

  • On a HA standby node mqsilist works as expected when the standby
    node is stopped, but hangs or takes long time to return when the
    standby node is running.
    
    Other mqsi commands fail on a running standby node, e.g.
    mqsimode, whilst others run as expected on a running standby
    node, e.g mqsireportbroker.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 using multi-instance
    broker.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In a multi-instance broker setup, the mqsilist command on a
    standby node hangs or takes long time to return if the standby
    instance of integration node is running.   If the integration
    node is stopped, the mqsilist command returns promptly.
    
    Other commands like mqsimode, mqsireportbroker or
    mqsireportproperties  may also show odd behaviour when run on
    the standby node.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT13060

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-07

  • Closed date

    2016-05-25

  • Last modified date

    2016-05-25

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020