IBM Support

IT14872: MQSIMIGRATECOMPONENTS DOES NOT UPDATE THE WINDOWS SERVICE ON SECOND NODE IN MSCS ENVIRONMENT

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 performing an in-place migration for an integration node
    that is configured on Microsoft Cluster Services (MSCS), the
    mqsimigratecomponents command does not update the Windows
    Service with the new installation path on the secondary server
    node.
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s): mqsimigratecomponetnts
    MSCS, windows service
    

Local fix

  • Manually start the integration node on the secondary server
    node using the mqsistart command.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 on Windows performing an
    in-place migration for an integration node that is configured on
    Microsoft Cluster Services (MSCS).
    
    
    Platforms affected:
    Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    To perform an in-place migration for an integration node that is
    configured on Microsoft Cluster Services (MSCS), the
    mqsimigratecomponents command is run on all nodes in the
    cluster. When run on the first node, it migrates the shared
    broker configuration and updates the Windows service
    successfully.  When the command is then run on the secondary
    server node, it detects that the shared broker configuration has
    already been updated and assumes that there is nothing further
    to do. But on Windows it should update the Windows Service with
    the new installation path.
    
    
    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 mqsimigratecomponents command now updates the Windows
    service with the new installation path when the command is run
    on the second server in a high availability configuration.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.8
    
    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

    IT14872

  • 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-04-20

  • Closed date

    2017-03-15

  • Last modified date

    2017-03-15

  • 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