IT08993: DFDL COMPLEX ELEMENT WITH FIXED CHARACTER LENGTH, WITH DELIMITED CONTENT AND TRAILING ELEMENTS FAILS TO PARSE,CTDP3000E

APAR status

• Closed as program error.

Error description

• If a DFDL model contains a complex element with a fixed length
  (lengthKind of explicit or prefixed) with lengthUnits of
  characters, and contains an element with lengthKind of
  delimited, but there are no delimiters in scope,
  and there are further elements after the delimited element,
  the parse will fail with a CTDP3000E error as the
  delimited element will consume all available data.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V8.0, V9.0 and V10.0 who use
  the Data Format Description Language (DFDL) to parse a message
  where the message model matches the following three criteria:
  1 - The model contains a complex element with a fixed length
  (lengthKind of explicit or prefixed) with lengthUnits of
  characters
  2 - The complex element uses an encoding with variable byte
  length characters
  3 - The complex element contains another element with lengthKind
  of delimited, but where there are no delimiters in scope.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a complex element with a fixed length with lengthUnits of
  characters is encountered, the product imposes a limit on the
  length of the element, which then limits the amount of data that
  can be read from the incoming data stream. For encodings with
  variable byte length characters, this limit is set in characters
  only and not bytes.
  
  When an element with lengthKind of delimited is encountered, the
  product finds the length of that element by scanning for any
  in-scope delimiter. The scanning for this delimiter ignores any
  character length limit imposed by any containing complex
  element.
  
  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
  

Problem conclusion

• The product has been modified so that any complex element with
  lengthUnits of characters will find the number of bytes that is
  equivalent to those characters and use that as the imposed
  length limit, irrespective of whether the encoding uses variable
  byte length characters or fixed byte length characters.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.7
  v9.0       9.0.0.4
  v10.0      10.0.0.2
  
  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:

  IT08854

• 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