IT19727: EDI DE-ENVELOPE SERVICE DOES NOT RECOGNIZE BYTE ORDER MARK (BOM)CHARACTERS

Media_IM_5020603_2
iSeries_Media_5020603_2.zip
iSeries_Media_5020603_2.zip
Media_IM_5020603_2

APAR status

• Closed as program error.

Error description

• Standards.jar
  
  When processing EDI data that contains the BOM characters, the
  EDI DeEnvelope service throws an error on Bad data found between
  0 and 3.
  

Local fix

• STRTC 513459
  WW/WW
  
  The EDI DeEnvelope service does not stop the flow to the
  appropriate Standards De Envelope service. The issue seems to
  be behind the scenes, unless the translation report is sent to
  Process Data, then the business process with show Error.
  

Problem summary

• Users Affected:
  All customers who use standards de-enveloping
  and those customers process data with byte order mark (BOM)
  characters.
  
  Problem Description:
  EDI De-envelope service does
  not recognize byte order mark (BOM) characters even though
  these characters are common. The service marks it as
  "unrecognized data" and the service reports an ERROR status. It
  is not enough to use the service option to ignore unrecognized
  data and report SUCCESS. Customers want to process data with
  BOMs and still report an ERROR status when unrecognized data
  truly exists.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  
  Add byte order mark (BOM) processing
  service parameter options to the EDI deenveloping service.
  Use new BP parameter ByteOrderMarkToIgnore to define a byte
  order mark to ignore. Use indexes to define more than one byte
  order mark (e.g. ByteOrderMarkToIgnore1,
  ByteOrderMarkToIgnore2).
  Custom byte order marks can be defined or use one of the three
  supposed out-of-the-box byte order marks:
  <assign to="ByteOrderMarkToIgnore">0xEF,0xBB,0xBF</assign>
  ...or...
  <assign to="ByteOrderMarkToIgnore">UTF-8</assign>
  Example defining multiple byte order marks to ignore:
  <assign to="ByteOrderMarkToIgnore1">UTF-8</assign>
  <assign to="ByteOrderMarkToIgnore2">EBCDIC</assign>
  
  Delivered In:
  5020500
  5020603
  5020601_8
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• DEENVLP
  

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels