IT13612: DFDL PARSER INCORRECTLY DETECTS NULL VALUES RESULTING IN A BIP5843E ERROR

APAR status

• Closed as program error.

Error description

• DFDL parser incorrectly detects null values resulting in a
  BIP5843E error. In the customer's case they saw :
  .
  /build/slot1/S900_P/src/MTI/MTIforBroker/DfdlParser/ImbDFDLUserT
  raceHand ler.cpp line:172 message:5843.BIPmsgs 'DFDL Fatal
  Error' , 'Unexpected data found at offset '878' after parsing
  completed. Data: '0x00...'.'
  2016-01-27 12:25:35.924148    27648
  UserTrace   BIP5843E: ''Unexpected data found at offset '878'
  after parsing completed. Data: '0x00...'.'' """""
  
  Working back through the user trace, there will be entries
  indicating that a nil literal value was matched for an element,
  but the offset does not move on. The nil literal value is
  actually a nil literal character with a raw byte value (eg,
  %#r00;) so in order to match at least 1 byte must have been
  consumed.
  
  When reproducing the problem, access violations were seen to
  occur, so this could conceivably happen for customers too.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the DFDL parser in IBM Integration Bus who have
  created a DFDL schema from a COBOL copybook, have selected the
  option to create nil values for elements, have chosen a raw byte
  value as the nil character such as %#r00; (LOW-VALUE), and the
  copybook contains one or more PIC X (text) fields that
  immediately follow PIC 9 (binary) fields.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The DFDL parser (C) was failing to reset a pointer when parsing
  a binary element, and the pointer was being examined when
  parsing the next text element but only if it was nillable with a
  nil literal character defined as a raw byte entity. This caused
  the parser incorrectly to match the nil value, and further to
  fail to move the offset on. Parsing eventually fails with a
  BIP5843E (Unexpected data found at offset xxx after parsing
  complete).
  
  <i>There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm</i>
  

Problem conclusion

• The product now correctly handles the NULL values in a DFDL
  message.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.6
  v10.0      10.0.0.1
  
  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 is sysrouted FROM one or more of the following:

  IT13598

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

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0530

Applicable component levels

• R900 PSY

     UP