IBM Support

IT13582: MSGFLOW WITH UDN INPUT NODE NESTED IN SUBFLOWS NOT INPUTTABLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Top-level message flows that contain nested subflows with a UDN
    Input node in the innermost subflow are not marked as
    inputtable. If the top-level message flow is in an integration
    project, it does not appear in the BAR editor as a selectable
    resource.
    
    This problem occurs if the top-level message flow, the nested
    subflows and the UDN Input nodes are each in separate projects.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Toolkit who have a message flow
    that contains no Input node, but instead contains a nested
    subflow with a UDN Input node in the innermost subflow, and all
    the flows are each in a different project.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Toolkit does not correctly resolve to the UDN.msgnode if the
    top-level message flow F1 includes S1 which includes S2 which
    includes UDN,
    F1 -> S1 -> S2 -> UDN (where the UDN is defined as an input
    node),
    if the all the flows are each in a different projects, for
    example,
    P1/F1.msgflow
    P2/S1.msgflow
    P3/S2.msgflow
    P4/UDN.msgnode (UDN Input node)
    
    The top-level message flow is not marked as inputtable. In
    addition, if the top-level message flow is in an integration
    project, it does not appear in the BAR editor as a resource that
    can be included in the Bar file.
    
    The reason is that although P1 has references to P2, P3 and P4,
    the code to resolve the nested flows for an input node uses only
    the project where the flow is.  As a result, P2/S1 is unable to
    resolve P3/S2 and P3/S2 is unable to resolve P4/UDN.
    

Problem conclusion

  • The product now correctly finds all the input nodes from the
    top-level message flow and correctly marks the message flow as
    inputtable.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.6
    v10.0      10.0.0.4
    
    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

    IT13582

  • Reported component name

    IB TOOLKIT

  • Reported component ID

    5724J0531

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-08

  • Closed date

    2016-03-08

  • Last modified date

    2016-03-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

    IB TOOLKIT

  • Fixed component ID

    5724J0531

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020