IBM Support

IT28799: MQ FDCS with Probe IDs RM215010 and RM220005 are written after cluster transmission queue is set to NOSHARE

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

  • Failure Data Capture (FDC) records with the following
    information are generated when a user has altered the default
    share value of a cluster transmit queue and/or its model queue
    (SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE) to NOSHARE .
    
    Probe ID: RM215010
    Component: rrmReallocMsgs
    Error Code: MQRC_OBJECT_IN_USE
    
    Probe ID: RM220005
    Component: rrmRepository
    Error Code: rrcE_MQOPEN_FAILED
    

Local fix

  • Set the cluster transmission queue to SHARE which is the
    default.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who have changed their cluster transmission queue to be
    NOSHARE.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The cluster transmission queue was given NOSHARE attribute by
    the user.
    
    This causes the reallocation of messages from the cluster
    transmission queue to fail because the reallocation routine
    (running within the queue manager's Repository Manager program)
    cannot open the transmission queue for input when the failing
    channel also has it open for input.
    
    The failure is not severe, but the queue manager's Repository
    Manager program wrote FDCs and went into a retry state
    unnecessarily.
    

Problem conclusion

  • The MQ code has been corrected so that the queue manager's
    Repository Manager program writes no FDCs, but instead writes an
    AMQ9509E error message to report what has happened.
    
    NOSHARE should not be set on cluster transmission queues, or the
    model queue SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE, because it
    prevents the cluster reallocation functionality from working.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version     Maintenance Level
    v8.0        8.0.0.16
    v9.0 LTS    9.0.0.11
    v9.1 CD     TBC
    v9.1 LTS    9.1.0.6
    
    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

    IT28799

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    911

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-15

  • Closed date

    2020-04-17

  • Last modified date

    2020-04-17

  • 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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 April 2020