IBM Support

IT40337: IBM MQ full repository queue manager reported errors AMQ9435E and 2085 (MQRC_UNKNOWN_OBJECT_NAME)

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

  • An administrator removed a queue manager (QMGRA) from a cluster.
    After
    27 days, the full repository queue manager reported AMQ9435E on
    amqrrmfa program in queue manager error log:
    .
    --------------------------------------------------------
    AMQ9435E: Unable to put repository manager message.
    EXPLANATION:
    The repository manager tried to send a message to the
    SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose
    identifier is QMGRA_YYYY-MM-DD_HH.MM.SS, but the MQPUT call was
    unsuccessful. MQCC=2, MQRC=2085. Processing continues, but the
    repository information may be out of date.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Systems of Publish Subscribe Clusters with multiple auto defined
    cluster sender channels to a destination queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem was caused during name resolution processing when a
    destination is being chosen using the queue manager identifier
    of a cluster queue manager and a named cluster is used in an
    attempt to route messages only over channels shared in the same
    named cluster.
    
    The destination selection should have choose an alternative
    route where one existed, even after filtering has returned no
    eligible channels (those shared in the named cluster filter).
    

Problem conclusion

  • The problem is resolved by ensuring that where filtering based
    on a cluster name results in no destinations, that  destination
    selection is retried without the filter in place.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.15
    v9.3 LTS   9.3.0.5
    v9.x CD    9.3.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

    IT40337

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-20

  • Closed date

    2023-03-31

  • Last modified date

    2023-03-31

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 April 2023