IBM Support

IT16876: IF A MAPPING NODE PARSES AN INVALID INPUT MESSAGE THEN THIS CAN CAUSE AN ABEND.

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 message flow processes an input message, by default it
    uses partial parsing.  When such an input message is propagated
    to a mapping node then it is possible the Mapping node will
    need to parse the message.  If the input message is invalid
    then the integration server may abend.
    

Local fix

  • The problem can be worked around by discovering the message is
    invalid before the Mapping node. For example, this can be done
    by setting the input node parse timing to Immediate/Complete
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.0 with a message flow using
    the default parse timing (partial parsing) in an input node, as
    well as a Mapping node that will require the input message to be
    parsed.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an input message is propagated to a Mapping node, then it
    is possible it will need to parse the message for the first time
    in the message flow.  If the input message is invalid then the
    integration server may abend.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT16876

  • 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

    2016-09-09

  • Closed date

    2016-09-09

  • Last modified date

    2016-09-09

  • 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

    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