IBM Support

IT20942: MAPPING MANDATORY ELEMENT IN OPTIONAL SEQUENCE CAN BE INVALID

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 mapping from mandatory input XML element (minOccurs=1) to a
    mandatory output XML element (minOcccurs=1) which is a member
    of an XML schema "sequence" or "all" grouping that is marked as
    optional (minOccurs=0) and the input element is not present
    (missing or for the IIB product set to NULL) the output element
    will not be created, causing the output XML document to be
    invalid against it's XML schema.
    

Local fix

  • Ensure input element is always present, or add explicit if/else
    logic in the mapping
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 who use the Mapping node
    with Graphical Data Maps that move a mandatory input element to
    a mandatory output element that is a member of an optional
    sequence or all group
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When mapping from mandatory input element (minOccurs=1) to a
    mandatory output XML element (minOcccurs=1) which is a member
    of an XML schema "sequence" or "all" grouping that is marked as
    optional (minOccurs=0) and the input element is not present, XML
    element missing or none XML, eg DFDL, element set NULL the
    output element will not be created, causing the output XML
    document to be invalid against it's XML schema.
    

Problem conclusion

  • The Mapping node is corrected so that in the defined case the
    element will now be created as empty or nilled in accordance
    with the schema meaning the output document is valid.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.10
    
    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

    IT20942

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-08

  • Closed date

    2017-08-31

  • Last modified date

    2017-08-31

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

    IT20900

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

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

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