PM26943: VALID XML BEING MARKED AS INVALID

APAR status

• Closed as program error.

Error description

• This issue affect maps that use typetrees imported from XML
  Schemas using the Xerces->AllElements option
  
  A mismatch can be reported between the typetree and XSD when
  none exists.
  
  The following may be observed in the input content trace:
  
  External Parser returned Error:
  TYPE X'000B' (Error (-1), "XMLParser: Input XML data is
  invalid."
  There is a mismatch between the typetree and input data. All
  type objects are not built.).
  
  and in the XML trace:
  
  <DetailedStatusMessage>
  Error (-1), "XMLParser: Input XML data is invalid."
  There is a mismatch between the typetree and input data. All
  type objects are not built.
  </DetailedStatusMessage>
  

Local fix

• WTXCQ - WTX00036174
  PB / PB
  Using the Xerces WellFormed option avoids the error.
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender XML parser users
  
  Problem Description:
  Type tree mismatch error when using type tree generated using
  the 'All Elements' option.
  
  Platforms Affected:
  All
  

Problem conclusion

• Prevent type tree mismatch error. When looking for element in
  type tree, code was premature breaking out of the element loop
  when XML validation was turned on. Now just indicate that
  element is required and continue.
  
  Delivered in:
  8.2.0.6, 8.3.0.4
  

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:

  PM31116 PM31123 PM31126 PM31128 PM31141

Fix information

• Fixed component name

  WTX COMMON COMP

• Fixed component ID

  5655R9500

Applicable component levels

• R820 PSY

     UP

• R830 PSY

     UP