IBM Support

IT12930: MQSIADDBROKERINSTANCE COMMAND FAILS WHEN IT CANNOT DETERMINE MQ INSTALL LOCATION.

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

  • The 'mqsiaddbrokerinstance' command fails to add a broker
    instance to standby server when it cannot determine the install
    path of
    MQ.  The following error is typically seen :
    
    BIP8050E: Unable to create WebSphere MQ Queue Manager .
    
    The utility trace of the command shows following execution
    entries leading to the error :
    ======================================
    {  ImbCmdLib::getMQInstallPath
    
      {   getMQInstallPath
          getMQInstallPath 'Could not determine WMQ install path'
      }   getMQInstallPath
    }  ImbCmdLib::getMQInstallPath
    ImbCmdLibBase::createMqQueueManager 'Could not find MQ install
                                         Path '
    ImbCmdLibBase::createMqQueueManager , 'Throwing exception',
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus 9.0 on Windows platforms
    running the command mqsiaddbrokerinstance.
    
    
    Platforms affected:
    Windows on x86 platform, Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The 'mqsiaddbrokerinstance' command fails to add a broker
    instance to standby server if it cannot determine the install
    path of WebSphere MQ.  The command throws the following error :
    
    BIP8050E: Unable to create WebSphere MQ Queue Manager .
    
    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

  • The product now provides an environment variable
    MQSI_MQ_INSTALL_PATH to allow you to specify the WebSphere MQ
    install location.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.6
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT12930

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-24

  • Closed date

    2016-06-09

  • Last modified date

    2016-06-09

  • 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

    5724J0530

Applicable component levels

  • R900 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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020