IBM Support

IT25846: Queue manager writes FDC with Probe RN194031 rrmCheckSubs when Full Repositories are both demoted

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

  • When all Full Repositories for a given cluster name were
    demoted, other queue managers began to write failure data
    capture (FDC) records, mentioning queues in that cluster.
    
    The FDC records contain the following: RN194031 rrmCheckSubs
    "Missing subscription"
    
    Apart from the FDC files, which consume disk space, there is no
    impact to the function of the queue manager.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who remove all Full Repositories for a given cluster name,
    by demoting them.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In this case, the FDC records were written by code running on an
    internal schedule in the cluster repository manager process.
    The code that is checking that proper subscription records exist
    internally within the clustering component of the queue manager.
    
    The FDC is a "false positive".  That is, there is no problem.
    
    The reason the FDC appears is that no subscriptions exist for a
    particular queue or queue manager object, in the particular
    cluster for which there are now no Full Repositories.
    
    However, the fact there are no Full Repositories for that
    cluster means it is valid that there are no subscriptions.
    

Problem conclusion

  • The MQ code has been corrected so that the subscriptions
    validity check on a  Partial Repository is only performed for a
    cluster in which there is at least one Full Repository known.
    This then means that, in the scenario described in this APAR,
    the FDCs are no longer written.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IT25846

  • 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

    2018-07-30

  • Closed date

    2019-09-24

  • Last modified date

    2019-09-24

  • 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

    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:
24 September 2019