Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Programming Guide

Coded character sets for XML documents

Supported code pages
Specifying the code page
Using a number:
Using an alias

The PLISAXC built-in subroutine supports only XML documents in WIDECHAR encoded using Unicode UTF-16 or in CHARACTER encoded using either UTF-8 or one of the explicitly supported single-byte character sets listed below. The parser uses up to three sources of information about the encoding of your XML document, and signals an exception XML event if it discovers any conflicts between these sources:

  1. The parser determines the basic encoding of a document by inspecting its initial characters.
  2. If step 1 succeeds, the parser then looks for any encoding declaration.
  3. Finally, it refers to the codepage value on the PLISAXC built-in subroutine call. If this parameter was omitted, it defaults to the value provided by the CODEPAGE compiler option value that you specified explicitly or by default.

If the XML document begins with an XML declaration that includes an encoding declaration specifying one of the supported code pages listed below, the parser honors the encoding declaration if it does not conflict with either the basic document encoding or the encoding information from the PLISAXC built-in subroutine. If the XML document does not have an XML declaration at all, or if the XML declaration omits the encoding declaration, the parser uses the encoding information from the PLISAXC built-in subroutine to process the document, as long as it does not conflict with the basic document encoding.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)