One of several exception codes might be returned in the XML-CODE special register during XML generation. If one of these exceptions occurs, control is passed to the statement in the ON EXCEPTION phrase, or to the end of the XML GENERATE statement if you did not code an ON EXCEPTION phrase.
| Code | Description |
|---|---|
| 400 | The receiver was too small to contain the generated XML document. The COUNT IN data item, if specified, contains the count of character positions that were actually generated. |
| 401 | A DBCS data-name contained a character that, when converted to Unicode, was not valid in an XML element or attribute name. |
| 402 | The first character of a DBCS data-name, when converted to Unicode, was not valid as the first character of an XML element or attribute name. |
| 403 | The value of an OCCURS DEPENDING ON variable exceeded 16,777,215. |
| 410 | The CCSID page specified by the CODEPAGE compiler option is not supported for conversion to Unicode. |
| 411 | The CCSID specified by the CODEPAGE compiler option is not a supported single-byte EBCDIC CCSID. |
| 414 | The CCSID specified for the XML document was invalid or was not supported. |
| 416 | The XML namespace identifier contained invalid XML characters. |
| 417 | Element character content or an attribute value contained characters that are illegal in XML content. XML generation has continued, with the element tag name or the attribute name prefixed with 'hex.' and the original data value represented in the document in hexadecimal. |
| 418 | Substitution characters were generated by encoding conversion. |
| 419 | The XML namespace prefix was invalid. |
| 600-699 | Internal error. Report the error to your service representative. |
related tasks
Handling errors in generating XML output