IBM Support

JR43092: Dynamic terminals and connecting wires of a Custom Mediation maybe missing after flow converts to new mediation flow format

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • There are two bugs in this PMR. Both of them are related to the
    behavior change in Custom Mediation
    1. In 6.2, the input and output terminals of Custom Mediation
    are deducible. For example, if you wire out terminal to a typed
    X terminal, the in terminal will also gets the type X. However,
    in 7.5, type X will not be propagated to the in terminal. It has
    to be explicitly type. Since MFCFlow conversion didn't handle
    this special case, the customer is seeing some terminals become
    untyped after migration.
    2. Prior to 6.1, Custom Mediation did not support adding dynamic
    input and output terminals. Since MFCFlow conversion didn't
    handle this special case, the customer notices that the dynamic
    in terminal of the Custom Mediation is gone.
    
    The fix for this problem requires that the modules be migrated
    once again after this fix is applied.
    
    USER AFFECTED:
    User using Custom Mediation prior to 7.5, with multiple
    input/output terminals
    

Local fix

  • None, the user have to manually recreate the missing terminals
    and wires
    

Problem summary

  • Fixes planned for upcoming cumulative fixes for V7.5.1 and V8,
    targetting Q3 and Q4 2012, respectively.
    
    Fix plan,
    
    1. Handle the special Custom Mediation case to preserve the
    dynamic terminals
    2. Improve type propagation system
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR43092

  • Reported component name

    INTEGRATION DES

  • Reported component ID

    5725C9702

  • Reported release

    751

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-06-14

  • Last modified date

    2012-06-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R751 PSY

       UP

  • R800 PSY

       UP

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

Document Information

Modified date:
14 June 2012