IBM Support

IT27834: A cluster repository loses sight of some other queue managers after a refresh cluster is done

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 REFRESH CLUSTER(clusname) REPOS(NO) command was issued.
    Afterwards, some other queue managers in the cluster were
    unreachable from the queue manager where the REFRESH was done.
     Applications received MQRC 2085 or 2087 when attempting to send
    messages to these queue managers.
    
    The issue occurs when a cluster sender channel is active at the
    time that the refresh is issued but then goes inactive before
    the republished channel information from the Full Repositories
    has been received and processed.
    

Local fix

  • Do another REFRESH CLUSTER command or simply alter the
    description of the CLUSRCVR channel on the target queue manager
    to cause the cluster subscription to be republished.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who run REFRESH CLUSTER while channels are running.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If auto-defined cluster sender channels were running when a
    REFRESH CLUSTER command was issued, and the channel stopped
    prior to the completed handshake with the Full Repositories, the
    refreshed records for those channels might not have been
    correctly added to the local cluster cache when they were
    received from the Full Repositories and processed.
    

Problem conclusion

  • Cluster refresh and reconcile processing has been corrected, to
    ensure the republished cluster Qmgr record is added to the
    cluster cache, in the scenario described.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.14
    v9.0 LTS   9.0.0.8
    v9.1 CD    9.1.4
    v9.1 LTS   9.1.0.4
    
    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

    IT27834

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-22

  • Closed date

    2019-09-30

  • Last modified date

    2019-10-02

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

    PH03171

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

Fix information

  • Fixed component name

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 October 2019