IBM Support

IT21044: HTTPASYNCRESPONSE NODE PARSES USING WRONG CCSID WHEN PARSE TIMING IS SET TO COMPLETE OR IMMEDIATE

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 an HTTPAsyncResponse node receives special characters, for
    example chinese characters or "áëíöù", in the body, and the node
    is configured to use the XMLNSC domain, and Parse timing is set
    to Complete or Immediate, then the special characters get
    garbled or parser errors may result. The user may see the
    following error :
    
    BIP5004E  An XML parsing error:An invalid XML character
    (Unicode: 0x4c) was found in the prolog of the document.
    
    It is observed that HTTPAsyncResponse node always parses
    the body using CCSID 819 when Parse Timing is set to
    Complete or Immediate.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 and V9.0 with
    HttpAsyncResponse nodes.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When special characters (non-utf-8) are received by the
    HTTPAsyncResponse node, which is configured to use XMLNSC
    domain, and parse timing is set to "complete" or "Immediate", it
    is seen that the character encoding in HTTPResponse header does
    not take effect and the node tries to parse the bitstream in
    utf-8 code page.
    
    This can either lead to a parser error with the BIP message
    "BIP5004E", or the characters get garbled by the node.
    

Problem conclusion

  • The HttpAsyncResponse node now uses the correct codepage from
    the HTTPResponse header to parse the body.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.12
    v11.0      11.0.0.1
    v9.0       9.0.0.11
    
    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

    IT21044

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-15

  • Closed date

    2018-06-13

  • Last modified date

    2018-06-13

  • 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

    5724J0530

Applicable component levels

[{"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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 March 2020