XML-CODE Exception Codes
Your COBOL system supports a subset of the exception codes that are available on the mainframe for the XML-CODE special register. Support is provided for the following exception codes:
| 1 | The parser found an invalid character while scanning white space outside element content. |
| 2 | The parser found an invalid start of a processing instruction, element, comment or document type declaration outside element content. |
| 3 | The parser found a duplicate attribute name. |
| 4 | The parser found the markup character '<' in an attribute value. |
| 5 | The start and end tag names of an element did not match. |
| 6 | The parser found an invalid character in element content. |
| 8 | The parser found in element content the CDATA closing character sequence '' without the matching opening character sequence ''. |
| 9 | The parser found an invalid character in a comment. |
| 10 | The parser found in a comment the character sequence '--' (dashdash) not followed by '>'. |
| 11 | The parser found an invalid character in a processing instruction data segment. |
| 12 | A processing instruction target name was 'xml' in lower-case, upper-case or mixed-case. |
| 13 | The parser found an invalid digit in a hexadecimal character reference (of the form �). |
| 14 | The parser found an invalid digit in a decimal character reference (of the form &#dddd;). |
| 15 | The encoding declaration value in the XML declaration did not begin with lower- or upper-case A through Z |
| 16 | A character reference did not refer to a legal XML character. |
| 17 | The parser found an invalid character in an entity reference name. |
| 18 | The parser found an invalid character in an attribute value. |
| 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. |
| 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 ':'. |
| 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. |
| 201 | Miscellaneous XML document parsing errors. |
| 300 | The document was encoded in EBCDIC, but the CODEPAGE compiler option specified a supported ASCII code page. |
| 306 | The document was encoded in ASCII, but the CODEPAGE compiler option specified a supported EBCDIC code page. |
| 310 | The CODEPAGE compiler option specified a supported EBCDIC code page, but the document was encoded in Unicode. |
Related
Topics