IBM Support

IT21351: Deleted cluster queues may become active as a result of refreshing full repository queue managers

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

  • A Cluster queue which has been deleted from the cluster by
    setting the CLUSTER or CLUSNL attributes to (' '), can re-appear
    in the cluster configuration during a REFRESH CLUSTER operation
    issued against a full repositories for given cluster(s).
    
    This problem can be observed by its existence in the outputs of
    the MQSC display commands and seeing the 'deleted' queue
    referenced when it should not be.
    
    Due to timing windows caused by overlapping REFRESH CLUSTER
    commands (or at least, the flow of data originating from them)
    the problem may not always arise such that the deleted queue,
    remains deleted in configuration.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Queue Manager Clusters who have removed queues from the
    cluster configuration and subsequently issue refresh cluster
    against one or more full repositories in that cluster.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A timing windows caused by overlapping REFRESH CLUSTER commands
    (or at least, the flow of data originating from them) had the
    potential to cause a deleted queue to be republished as a live
    queue to other full repositories.
    

Problem conclusion

  • The MQ queue manager cluster repository manager logic has been
    updated to ensure that deleted queue records are republished
    correctly to other repositories on issuing REFRESH CLUSTER.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.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

    IT21351

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-09

  • Closed date

    2017-08-10

  • Last modified date

    2017-08-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI85738

Fix information

  • Fixed component name

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP



Document information

More support for: WebSphere MQ

Software version: 8.0.0.0

Reference #: IT21351

Modified date: 10 August 2017


Translate this page: