IBM Support

IT12626: ERROR FOR MAIN & SUBMAP SAME QNAME DIFFERENT OBJECTS

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 a map references a submap, the XSD types of the parameters
    in the caller map and the submap must match.
    In the past, if the two parameter types have the same namespace
    and name, but are two distinct Java objects, an error is
    flagged in the caller map for a "mismatch" between the caller
    and called.
    Some users may get into this scenario with two XSD types which
    are carbon copies of each other, but cannot use one single Java
    object instead.
    In response to such a scenario, GDM will flag such "mismatch"
    as a warning instead of an error.
    
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the IBM Integration Toolkit V10 with a map calling
    a submap.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a map references a submap, the XSD types of the parameters
    in the caller map and the submap must match. A prerequisite for
    two XSD types to be considered "match" is that they are either
    defined in the same XML schema, or defined in two XML schema
    with one include or import the other.
    
    In the past, if the two parameter types have the same namespace
    and name, but are defined in two unrelated XML schemas, an error
    is flagged in the caller map for a "mismatch" between the caller
    and called.
    
    You can get into this scenario with two XSD types which are
    carbon copies of each other, but the two XML schemas defining
    them are completed separated.
    
    
    
    <i>There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm</i>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT12626

  • Reported component name

    IIB TOOLKIT

  • Reported component ID

    5724J0541

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-07

  • Closed date

    2016-03-08

  • Last modified date

    2016-03-08

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

    IT12576

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

Fix information

  • Fixed component name

    IIB TOOLKIT

  • Fixed component ID

    5724J0541

Applicable component levels

  • RA00 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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020