IC87524: MIGRATION DOES NOT UPDATE THE MQ SERVICE DEFINITION FOR BROKER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A WebSphere Message Broker at V7.0 is configured to run as an MQ
    Service. The command mqsimigratecomponents is used to migrate
    the broker to V8.0, and this completes successfully. When the
    migrated broker is requested to start using the mqsistart
    command, the command completes successfully but the broker
    does not start.
    

Local fix

  • The MQ Service definition called "MQSI_<brokerName>" can be
    updated
    manually to point at the new V8.0 broker installation.
    Alternatively, run the following commands to delete and then
    recreate
    the MQ Service definition:
    - mqsichangebroker <brokerName> -d undefined
    - mqsichangebroker <brokerName> -d defined
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker who start the broker as
    a WebSphere MQ Service.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    If the command mqsimigratecomponents is used to migrate a broker
    that has been defined to start as a WebSphere MQ service from
    V7.0 to V8.0, the migration completes successfully but the
    broker may not start. This is because the
    mqsimigratecomponents command does not update the WebSphere MQ
    Service definition. If V8.0 has been installed in a different
    location to V7.0, the MQ Service definition will still be
    referring to the old V7.0 install path.
    

Problem conclusion

  • WebSphere Message Broker has been modified to update the
    WebSphere MQ Service definition when performing a forward
    migration using the mqsimigratecomponents command. For backwards
    migration, the WebSphere MQ Service is removed and the user will
    need to recreate it if required using the command:
    mqsichangebroker MyBroker -d defined.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v8.0
    --------           --------------------
    Multiplatforms     8.0.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere Message Broker Recommended Fixes'
    http://www.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 in 'WebSphere Message
    Broker Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87524

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-26

  • Closed date

    2013-04-30

  • Last modified date

    2013-04-30

  • 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

    WEB MESSAGE BRO

  • Fixed component ID

    5724J0520

Applicable component levels

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Message Broker

Software version:

8.0

Reference #:

IC87524

Modified date:

2013-04-30

Translate my page

Machine Translation

Content navigation