z/OS XML System Services parsing limitations

The following limitations apply to z/OS XML System Services processing:

• Because the z/OS XML System Services parser stops parsing when it encounters an error, native-schema-enabled maps that use z/OS XML System Services parsing do not support the REJECT function.
• The z/OS XML System Services parser and the xsdorg command flag null characters at the end of a file as invalid data. To use z/OS XML System Services processing, specify variable-length record format for the input data set. Fixed-length records pad the data set with nulls to the specified block size.
• Native-schema-enabled maps that use the z/OS XML System Services parser do not support CDATA.

In addition, these limitations that are common to native-schema-enabled maps also apply to native-schema-enabled maps that are parsed by z/OS XML System Services:

• IBM® Transformation Extender maps do not handle XML schema sequences that contain elements with the same name. When an XML schema contains a sequence of elements that do not have unique names, a map creates the output correctly only for the first element. The map creates the output with empty values for all the subsequent elements that have the same name.
• A map that runs successfully in versions of WebSphere Transformation Extender earlier than version 8.2.0.4 might fail to run in version 8.2.0.4 and later versions. The process of mapping items from the schema changed in version 8.2.0.4, and you might have to revise the map.