IBM Support

IT24778: Message "AMQ7208: The Queue Manager failed to start cluster channel 'AMQ' " is erroneously written to error logs.

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

  • The message AMQ7208 is written to the queue manager error log
    each
    time a message arrives on a transmission queue even though the
    queue manager is not configured in a cluster.
    
    This doesn't affect any applications, the messages in the
    transmission queue, xmitq, are picked up and transferred by the
    expected channel definition.
    

Local fix

  • The error message is generated because the property CLCHNAME has
    been
    (incorrectly) set on a sender channel's transmit queue.  Unset
    the property and
    the incorrect error messages will stop appearing in the queue
    manager error logs.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ V8 and later
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    An MQ administrator incorrectly configured the CLCHNAME property
    on a sender channel's transmit queue.  This caused the queue
    manager
    to treat the transmit queue as if it were a cluster transmit
    queue and
    to try to start a non-existent cluster channel.  As a
    consequence the
    following error message was written to the queue manager error
    log:
    AMQ7208: The Queue Manager failed to start cluster channel
    

Problem conclusion

  • The problem was caused by a user error, but the queue manager
    could
    have done a better job of detecting the incorrect configuration
    and ignoring
    it.  Consequently the code has been modified to stop the queue
    manager from
    attempting to start a cluster channel with an invalid cluster
    channel
    name.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.0 LTS   9.0.0.7
    v9.1 CD    9.1.2
    v9.1 LTS   9.1.0.2
    
    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

    IT24778

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-19

  • Closed date

    2019-01-21

  • Last modified date

    2019-01-21

  • 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

    5724H7251

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

Document Information

Modified date:
21 January 2019