IBM Support

IT25059: After REFRESH CLUSTER, FDCs with probe RM702021 component rrmCheckSubsForQMgr appear

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

  • After the REFRESH CLUSTER command has been processed, an
    incorrect state occurs in the cluster cache.
    
    The following failure data capture (FDC) record is generated
    possibly several times, once per hour:
    
    Probe Id :- RM702021
    Component :- rrmCheckSubsForQMgr
    Program Name :- amqrrmfa
    Comment1 :- Missing subscription
    
    MQM Function Stack ends with:
    rrmMaintainClqMgr
    rrmCheckSubsForQMgr
    xcsFFST
    
    This does no known harm to product functionality, but the
    repeated FDC reporting uses unwanted quantities of disk space
    under /var/mqm/errors.
    
    The "Missing subscription" text refers to an internal mechanism
    in the cluster cache code, and does not refer to
    publish/subscribe messaging by applications.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who run REFRESH CLUSTER, where running cluster channels
    could not be stopped.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The refresh-cluster processing includes re-subscribing for any
    remote queue managers whose records could not be deleted because
    their channels could not be stopped during the refresh-cluster
    processing.
    
    The new subscriptions were being created with "refresh" flags
    inconsistent with the internal object representing the remote
    queue manager.  This made the subscriptions susceptible to being
    deleted too soon.  This is incorrect, and caused the FDC that
    was seen.
    
    These faulty subscriptions were deleted 30 days after the
    running of REFRESH CLUSTER, and the FDCs started to be written
    immediately after that.
    

Problem conclusion

  • The MQ code has been corrected.  In this scenario, the new
    subscriptions are created with "refresh" flags consistent with
    the internal object representing the remote queue manager
    
    ---------------------------------------------------------------
    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

    IT25059

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-24

  • Closed date

    2019-09-24

  • Last modified date

    2019-10-02

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

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

    PH17275

Fix information

  • Fixed component name

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 October 2019