Table 31. XML exceptions that allow continuation (continued)
Code Description Parser action on continuation
57 The document was encoded in ASCII,
and the document encoding declaration
specied a supported ASCII encoding, but
the parser does not support the CCSID
specied by the CCSID of the COBOL source
member.
The parser uses the encoding specied by the
document encoding declaration.
58 The document was encoded in ASCII, and
the CCSID of the COBOL source member is
a supported ASCII CCSID, but the document
encoding declaration specied a supported
EBCDIC encoding.
The parser uses the encoding specied by the
CCSID of the COBOL source member.
59 The document was encoded in ASCII, and
the CCSID of the COBOL source member is
a supported ASCII CCSID, but the document
encoding declaration specied a supported
Unicode encoding.
The parser uses the encoding specied by the
CCSID of the COBOL source member.
60 The document was encoded in ASCII, and
the CCSID of the COBOL source member is a
supported ASCII CCSID, but the document
encoding declaration specied a Unicode
encoding that the parser does not support.
The parser uses the encoding specied by the
CCSID of the COBOL source member.
61 The document was encoded in ASCII, and
the CCSID of the COBOL source member is
a supported ASCII CCSID, but the document
encoding declaration specied an encoding
that the parser does not support.
The parser uses the encoding specied by the
CCSID of the COBOL source member.
62 The XML document was larger than
16,000,000 bytes.
Parsing continues. XML-TEXT or XML-NTEXT
for the subsequent START-DOCUMENT event is
truncated at 16,000,000 bytes.
100,001
-
165,535
The document was encoded in EBCDIC, and
the encodings specied by the CCSID of the
COBOL source member and the document
encoding declaration are both supported
EBCDIC CCSIDs, but are not the same. XML-
CODE contains the CCSID for the encoding
declaration plus 100,000.
If you set XML-CODE to zero before returning
from the EXCEPTION event, the parser uses
the encoding specied by the CCSID of the
COBOL source member. If you set XML-CODE
to the CCSID for the document encoding
declaration (by subtracting 100,000), the
parser uses this encoding.
200,001
-
265,535
The document was encoded in ASCII, and
the encodings specied by the CCSID of the
COBOL source member and the document
encoding declaration are both supported
ASCII CCSIDs, but are not the same. XML-
CODE contains the CCSID for the encoding
declaration plus 200,000.
If you set XML-CODE to zero before returning
from the EXCEPTION event, the parser uses
the encoding specied by the CCSID of the
COBOL source member. If you set XML-CODE
to the CCSID for the document encoding
declaration (by subtracting 200,000), the
parser uses this encoding.
related tasks “Handling errors in XML documents” on page 274
XML exceptions that do not allow continuation
With these XML exceptions, no further events are returned from the parser, even if you set XML-CODE to
zero and return control to the parser after processing the exception. Control is passed to the statement
556
IBM i: ILE COBOL Programmer's Guide