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

Terminating exception codes

Table 34. Terminating Exceptions
Number
Description
100
The parser reached the end of the document while scanning the start of the XML declaration.
101
The parser reached the end of the document while looking for the end of the XML declaration.
102
The parser reached the end of the document while looking for the root element.
103
The parser reached the end of the document while looking for the version information in the XML declaration.
104
The parser reached the end of the document while looking for the version information value in the XML declaration.
106
The parser reached the end of the document while looking for the encoding declaration value in the XML declaration.
108
The parser reached the end of the document while looking for the standalone declaration value in the XML declaration.
109
The parser reached the end of the document while scanning an attribute name.
110
The parser reached the end of the document while scanning an attribute value.
111
The parser reached the end of the document while scanning a character reference or entity reference in an attribute value.
112
The parser reached the end of the document while scanning an empty element tag.
113
The parser reached the end of the document while scanning the root element name.
114
The parser reached the end of the document while scanning an element name.
115
The parser reached the end of the document while scanning character data in element content.
116
The parser reached the end of the document while scanning a processing instruction in element content.
117
The parser reached the end of the document while scanning a comment or CDATA section in element content.
118
The parser reached the end of the document while scanning a comment in element content.
119
The parser reached the end of the document while scanning a CDATA section in element content.
120
The parser reached the end of the document while scanning a character reference or entity reference in element content.
121
The parser reached the end of the document while scanning after the close of the root element.
122
The parser found a possible invalid start of a document type declaration.
123
The parser found a second document type declaration.
124
The first character of the root element name was not a letter, '_' or ':'.
125
The first character of the first attribute name of an element was not a letter, '_' or ':'.
126
The parser found an invalid character either in or following an element name.
127
The parser found a character other than '=' following an attribute name.
128
The parser found an invalid attribute value delimiter.
130
The first character of an attribute name was not a letter, '_' or ':'.
131
The parser found an invalid character either in or following an attribute name.
132
An empty element tag was not terminated by a '>' following the '/'.
133
The first character of an element end tag name was not a letter, '_' or ':'.
134
An element end tag name was not terminated by a '>'.
135
The first character of an element name was not a letter, '_' or ':'.
136
The parser found an invalid start of a comment or CDATA section in element content.
137
The parser found an invalid start of a comment.
138
The first character of a processing instruction target name was not a letter, '_' or ':'.
139
The parser found an invalid character in or following a processing instruction target name.
140
A processing instruction was not terminated by the closing character sequence '?>'.
141
The parser found an invalid character following '&' in a character reference or entity reference.
142
The version information was not present in the XML declaration.
143
'version' in the XML declaration was not followed by a '='.
144
The version declaration value in the XML declaration is either missing or improperly delimited.
145
The version information value in the XML declaration specified a bad character, or the start and end delimiters did not match.
146
The parser found an invalid character following the version information value closing delimiter in the XML declaration.
147
The parser found an invalid attribute instead of the optional encoding declaration in the XML declaration.
148
'encoding' in the XML declaration was not followed by a '='.
149
The encoding declaration value in the XML declaration is either missing or improperly delimited.
150
The encoding declaration value in the XML declaration specified a bad character, or the start and end delimiters did not match.
151
The parser found an invalid character following the encoding declaration value closing delimiter in the XML declaration.
152
The parser found an invalid attribute instead of the optional standalone declaration in the XML declaration.
153
'standalone' in the XML declaration was not followed by a '='.
154
The standalone declaration value in the XML declaration is either missing or improperly delimited.
155
The standalone declaration value was neither 'yes' nor 'no' only.
156
The standalone declaration value in the XML declaration specified a bad character, or the start and end delimiters did not match.
157
The parser found an invalid character following the standalone declaration value closing delimiter in the XML declaration.
158
The XML declaration was not terminated by the proper character sequence '?>', or contained an invalid attribute.
159
The parser found the start of a document type declaration after the end of the root element.
160
The parser found the start of an element after the end of the root element.
300
The document was encoded in EBCDIC, but the CODEPAGE compiler option specified a supported ASCII code page.
301
The document was encoded in EBCDIC, but the CODEPAGE compiler option specified Unicode.
302
The document was encoded in EBCDIC, but the CODEPAGE compiler option specified an unsupported code page.
303
The document was encoded in EBCDIC, but the CODEPAGE compiler option is unsupported and the document encoding declaration was either empty or contained an unsupported alphabetic encoding alias.
304
The document was encoded in EBCDIC, but the CODEPAGE compiler option is unsupported and the document did not contain an encoding declaration.
305
The document was encoded in EBCDIC, but the CODEPAGE compiler option is unsupported and the document encoding declaration did not specify a supported EBCDIC encoding.
306
The document was encoded in ASCII, but the CODEPAGE compiler option specified a supported EBCDIC code page.
307
The document was encoded in ASCII, but the CODEPAGE compiler option specified Unicode.
308
The document was encoded in ASCII, but the CODEPAGE compiler option did not specify a supported EBCDIC code page, ASCII or Unicode.
309
The CODEPAGE compiler option specified a supported ASCII code page, but the document was encoded in Unicode.
310
The CODEPAGE compiler option specified a supported EBCDIC code page, but the document was encoded in Unicode.
311
The CODEPAGE compiler option specified an unsupported code page, but the document was encoded in Unicode.
312
The document was encoded in ASCII, but both the encodings provided externally and within the document encoding declaration are unsupported.
313
The document was encoded in ASCII, but the CODEPAGE compiler option is unsupported and the document did not contain an encoding declaration.
314
The document was encoded in ASCII, but the CODEPAGE compiler option is unsupported and the document encoding declaration did not specify a supported ASCII encoding.
315
The document was encoded in UTF-16 Little Endian, which the parser does not support on this platform.
316
The document was encoded in UCS4, which the parser does not support.
317
The parser cannot determine the document encoding. The document may be damaged.
318
The document was encoded in UTF-8, which the parser does not support.
319
The document was encoded in UTF-16 Big Endian, which the parser does not support on this platform.
501, 502, 503
An internal error occurred in PLISAX(A|B). Please contact IBM support.
500
Memory allocation failed for the PLISAXA internal data structures. Increase the amount of storage available to the application program.
520
Memory allocation failed for the PLISAXB internal data structures. Increase the amount of storage available to the application program.
521
An internal error occurred in PLISAX(A|B). Please contact IBM support.
523
PLISAXB encountered a file I/O error.
524
Memory allocation failed in PLISAXB while attempting to cache the XML document from the file system. Increase the amount of storage available to the application program.
525
An unsupported URI scheme was specified to PLISAXB.
526
The XML document provided to PLISAXB was less than the minimum of 4 characters or was too large.
527, 560
An internal error occurred in PLISAX(A|B). Please contact IBM support.
561
No event handler was specified to either PLISAX(A|B).
562, 563, 580, 581
An internal error occurred in PLISAX(A|B). Please contact IBM support.
600
to
99,999
Internal error. Please report the error to your service representative.

Terms of use | Feedback

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