IBM Support

IT43646: Clustering recovery and diagnostic improvements

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

  • There is a lack of error information where potential queue
    manager cluster disaster recovery steps have been taken and
    perhaps not completed in a test scenario.
    IBM MQ is able to determine that updates for cluster objects may
    not have originated by the "production" / original version of a
    given queue manager.
    
    The problem being addressed is to provide additional information
    to customers to warn about such updates and to where
    appropriate, use updates from the originating queue managers,
    should they be put back into the configuration, out of sequence
    and after an unsuccessful disaster recovery test.
    
    Additional tracing is also provided should recreation of
    scenarios be required to be performed for root cause analysis.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Queue Manager Clusters performing disaster recovery
    testing and experience subsequent and unexpected missing cluster
    objects resulting in application errors
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Though MQ attempts to warn users about objects being removed
    from their configurations, they are not always regarded as
    important by users.
    Should a valid but potentially out of date object be received
    after an incomplete disaster recovery test, MQ will when
    appropriate use the version of the object received in order to
    mitiagte object loss and will warn users of such activity.
    

Problem conclusion

  • MQ will provide additional error messages to users and may use
    objects previously deemed to be out of date, where they have
    originated by the appropriate queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.20
    v9.3 LTS   9.3.0.10
    v9.x CD    9.3.3
    
    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

    IT43646

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-04-27

  • Closed date

    2023-09-01

  • Last modified date

    2023-10-06

  • 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 BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 October 2023