IBM Support

IT37111: CICSREQUEST NODES WILL REUSED THE SAME CONNECTION IF A POLICY ISSPECIFIED BUT THE POLICY IS NOT IN THE DEFAULT POLICY PROJECT

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 CICSRequest node in ACE v11 will all reuse the same
    connection if a CICSConnection policy is specified on the node
    via the CICS Server node attribute and the policy is not located
    in the default policy project. All such CICSRequest nodes within
    a single integration server will all use the same CICS
    connection. The precise connection that is used will be the one
    for the first CICSRequest node that is executed in a message
    flow.
    
    This can be seen in a service trace from the
    CICSDirector.getAdapter() method. In a failing situation, the
    same CICSAdapter object will be returned in subsequent calls
    even if different policy names or connection details are
    specified:
    
    
    { CICSDirector.getAdapter , 'CICS_POLICY_1 AAA
    tcp://localhost:3001 null null 30000'
     CICSDirector.getAdapter , 'Failed to find specified policy',
    'CICS_POLICY_1'
     CICSDirector.getAdapter , 'Lookup =', 'AAA##null##null##30000'
    } CICSDirector.getAdapter ,
    'com.ibm.broker.cics.CICSAdapter@c45af3d0'
    ...
    { CICSDirector.getAdapter , 'CICS_POLICY_2 AAA
    tcp://localhost:3002 null null 30000'
     CICSDirector.getAdapter , 'Failed to find specified policy',
    'CICS_POLICY_2'
     CICSDirector.getAdapter , 'Lookup =', 'AAA##null##null##30000'
    } CICSDirector.getAdapter ,
    'com.ibm.broker.cics.CICSAdapter@c45af3d0'
    

Local fix

  • Copy the desired policies into the default policy project or set
    the default policy project name to match the policy project that
    contains the CICSConnection policies.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the CICSRequest node in IBM App Connect Enterprise
    v11 and v12 using a CICS Connection Policy that is not in the
    default policy project.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The CICSRequest node in ACE v11 will all reuse the same
    connection if a CICSConnection policy is specified on the node
    via the CICS Server node attribute and the policy is not located
    in the default policy project. All such CICSRequest nodes within
    a single integration server will all use the same CICS
    connection. The precise connection that is used will be the one
    for the first CICSRequest node that is executed in a message
    flow.
    
    This can be seen in a service trace from the
    CICSDirector.getAdapter() method. In a failing situation, the
    same CICSAdapter object will be returned in subsequent calls
    even if different policy names or connection details are
    specified:
    
    { CICSDirector.getAdapter , 'CICS_POLICY_1 AAA
    tcp://localhost:3001 null null 30000'
      CICSDirector.getAdapter , 'Failed to find specified policy',
    'CICS_POLICY_1'
      CICSDirector.getAdapter , 'Lookup =', 'AAA##null##null##30000'
    } CICSDirector.getAdapter ,
    'com.ibm.broker.cics.CICSAdapter@c45af3d0'
    ...
    { CICSDirector.getAdapter , 'CICS_POLICY_2 AAA
    tcp://localhost:3002 null null 30000'
      CICSDirector.getAdapter , 'Failed to find specified policy',
    'CICS_POLICY_2'
      CICSDirector.getAdapter , 'Lookup =', 'AAA##null##null##30000'
    } CICSDirector.getAdapter ,
    'com.ibm.broker.cics.CICSAdapter@c45af3d0'
    

Problem conclusion

  • The CICSRequest node will now correctly find and use CICS
    Connection policies even if they are not in the default policy
    project.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.14
    v12.0      12.0.2.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

    IT37111

  • 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

    2021-06-03

  • Closed date

    2021-08-19

  • Last modified date

    2021-10-06

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
13 October 2021