IBM Support

IT25279: HTTP HEADER PARSER DEFAULTS TO CODEPAGE 819 WHEN FIRST USED IN EVENT GATHERING

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 HTTP header is serialized for the first time during
    event gathering, the 'next parser coded charset ID' is
    incorrectly set to 819 by default. This will cause the
    subsequent message serialization to use CCSID 819 rather than
    the default for the message being serialized. Subsequent
    messages are unaffected due to the parser being reset after the
    first message.
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s):HTTP Header,
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enterprise v11 using an HTTP node with delayed message parse
    timing where the message payload is not valid ASCII data and is
    used in Event Monitoring.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an HTTP header is serialized for the first time during
    event gathering, the 'next parser coded charset ID' is
    incorrectly set to CCSID 819 by default. This will cause the
    subsequent message serialization to use CCSID 819 rather than
    the default for the message being serialized. Subsequent
    messages are unaffected due to the parser being reset after the
    first message.
    

Problem conclusion

  • The HTTP header parser will now not set a default CCSID and will
    instead infer the CCISD from the other parsers or the message
    content.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version     Maintenance Level
    v10.0       10.0.0.15
    v11.0       11.0.0.3
    
    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

    IT25279

  • 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

    2018-06-06

  • Closed date

    2018-12-18

  • Last modified date

    2018-12-18

  • 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

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

Document Information

Modified date:
18 December 2018