IBM Support

IT32558: DEFCLXQ(CHANNEL) is not honored if the CLUSSDR has multiple hostnames in the CONNAME attribute

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

  • User is using a comma separated CONNAME in a CLUSSDR channel and
    attempting to reconnect after changing DEFCLXQ to CHANNEL at the
    qmgr level. Displaying the channel status shows that it is still
    using SYSTEM.CLUSTER.TRANSMIT.QUEUE for the transmission queue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of cluster channel definitions with
    multiple values in the CONNAME field, who wish to use multiple
    cluster transmission queues.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error within the cluster channel logic meant that if a
    CLUSSDR channel failed to connect to the first entry specified
    in its CONNAME field and it retried using a different entry from
    the CONNAME field, then the internal metadata that controls the
    use of split cluster transmission queues was incorrectly
    discarded from the channel instance, reverting the channel
    instance to use the SYSTEM.CLUSTER.TRANSMIT.QUEUE.
    

Problem conclusion

  • The IBM MQ channel clustering logic has been carried out to
    preserve the metadata which determines the cluster transmit
    queue configuration for the CLUSSDR channel configuration in
    this scenario.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.11
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.5
    
    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

    IT32558

  • 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

    2020-04-15

  • Closed date

    2021-12-22

  • Last modified date

    2022-02-03

  • 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

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

Document Information

Modified date:
04 February 2022