IBM Support

IT40501: DEFAULTQUEUEMANAGER IS NOT USED WHEN DESTINATIONQUEUEMANAGERNAMEIS EMPTY IN A MQENDPOINT POLICY OF CONNECTION TYPE 'SERVER'

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 MQEndpoint policy of connection type 'SERVER' is used and
    the queue manager name(destinationQueueManagerName) property
    value is not set, it is expected that the MQ nodes will use the
    default queue manager associated with the integration node or
    independent integration server. This works as expected in IIB
    V10 but the flows migrated from IIB V10 fail as
    defaultQueueManager property value is never used to override the
    queue manager when MQEndpoint policy's
    destinationQueueManagerName is empty.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 and V12.0 using
    MQEndpoint policy.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When MQEndpoint policy of connection type 'SERVER' is used and
    the queue manager name(destinationQueueManagerName) property of
    the policy is not set, it is expected that the MQ nodes will use
    the default queue manager associated with the integration node
    or independent integration server.
    
    This works as expected in IBM Integration Bus(IIB) V10.0 but the
    flows migrated from IIB will fail,  as the defaultQueueManager
    property value is never used when MQEndpoint policy's
    destinationQueueManagerName is empty.
    

Problem conclusion

  • The product has been modified such that the MQ nodes(MQInput,
    MQOutput and MQGet nodes) make use of defaultQueueManager when
    MQEndpoint policy doesn't have a <span
    style="background-color:rgb(255, 255,
    255)">destinationQueueManagerName set.</span>
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.18
    v12.0      12.0.5.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT40501

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-04

  • Closed date

    2022-07-29

  • Last modified date

    2022-09-08

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 September 2022