The following table describes the messages that may be generated when an error occurs in XML Extensions:
| Message Number | Severity and Message Text | Description |
| -6 | Warning - ambiguous import name. | An element name in an imported XML document is defined more than once in the symbol table determined by the ModelFileName#DataName parameter of the XML IMPORT statement. Further, the element name is defined more than once subordinate to the model data name. XML Extensions assumes the first of the duplicates found, which is the lexically last defined duplicate, should be used and continues. If that name already has an imported value for the current import and is not a table (array) element, the next duplicate is assumed; that is, a lexically previous duplicate definition. For arrays, the array is consecutively filled before moving on to look for another duplicate. If there is no duplicate name without a previously imported value, a -02 extraneous element warning is produced and the imported text value is discarded. This warning is not produced if the XML document does not have any text content, after ignoring whitespace, for the element. This warning is also not produced if the XML document contains sufficient qualification, that is, parent element names, to make the reference unique. When a duplicate name is not subordinate to the model data name, this warning is not produced unless all duplicate names are not subordinate to the model data name. |
| -5 | Warning - ambiguous model data name | More than one matching data name was found in the document. The most recently found data name is used. |
| -4 | Warning - subscript out of range | A subscript is out of range on import. The offending item is not imported. |
| -3 | Warning - data truncation | A nonnumeric import item has been truncated to fit the associated COBOL data item. |
| -2 | Warning - extraneous element | The import data contains one or more elements that do not belong anywhere in the COBOL data structure; the element(s) have been ignored. |
| 0 | Success | A normal completion occurred. No informative, warning, or error message was detected. |
| 1 | Informative - directory contains no documents | An XML FIND FILE statement did not find any XML documents (files with an .xml extension) in the specified directory. |
| 2 | Informative - document file - no data | An XML EXPORT FILE or an XML EXPORT TEXT statement generated a document that contained no element values. |
| 3 | Warning - internal logic - memory not deallocated | During process cleanup, memory blocks that should have already been deallocated were still allocated. |
| 9 | Error - in function: CreateDocument | The underlying XML parser detected an error while trying to create an XML document. |
| 10 | Error - cannot create URL | The XML Extensions library detected that a URL (a string beginning with the sequence http://, https://, or file://) was used as an output document name. |
| 12 | Error - data item - not found | The XML Extensions library detected that there are no occurrences of the specified data item name in the model template file. |
| 13 | Error - document file - create failure | An attempt to create an XML document file failed. |
| 14 | Error - document file - file open failure | The XML Extensions library detected an error while attempting to open an XML document file. |
| 15 | Error - extraneous element | The XML Extensions library detected an extra occurrence of a scalar data element. |
| 17 | Error - in function: GetFirstChild | The XML Extensions library detected an error in the function GetFirstChild while parsing an XML document. |
| 18 | Error - in function: GetNextSibling | The XML Extensions library detected an error in the function GetNextSibling while parsing an XML document. |
| 19 | Error - in function: GetNodeData | The XML Extensions library detected an error in the function GetNodeData while parsing an XML document. |
| 20 | Error - in function: GetRootNode | The XML Extensions library detected an error in the function GetRootNode while parsing an XML document. |
| 21 | Error - internal logic - memory allocation | An attempt to allocate a block of memory failed. |
| 22 | Error - internal logic - memory corruption | An attempt to deallocate (free) a block of memory failed either because the block header or trailer was corrupted or because the free memory call returned an error. |
| 23 | Error - internal logic - node not found | The XML Extensions library detected an inconsistency in its internal tables. Specifically, an expected entry in the Document Object Model is missing. |
| 24 | Error - in function: Initialization | Either an XML statement (other than XML INITIALIZE) was executed without first executing the XML INITIALIZE statement or the XML INITIALIZE statement failed. |
| 25 | Error - invalid data address | The XML Extensions library detected that the data structure address specified in an XML IMPORT or an XML IMPORT statement does not match the data address specified in the template file. This normally means that the COBOL program has been re-compiled but the model files produced by the XMLGEN compiler directive were not re-generated and are outdated. |
| 28 | Error - in function: LoadDocument | An error was detected while trying to load an XML document. This normally means that there was a problem locating the document (either the document does not exist or there is a problem with permissions). Occasionally, XML Extensions generates documents that are then loaded as input documents. In the unlikely event that the generated document contains errors, a load document error will be encountered. |
| 29 | Error - in function: LoadSchema | An error was detected while trying to load an XML schema file. This normally means that there was a problem locating the document (either the document does not exist or there is a problem with permissions) or that the schema itself is in error. |
| 30 | Error - in function: LoadStyleSheet | An error was detected while trying to load an internal or external XSLT stylesheet. This normally means that there was a problem locating the document (either the document does not exist or there is a problem with permissions). Another possible cause is that the XML parser software is not properly installed. |
| 32 | Error - in function: LoadTemplate | An error was detected while trying to load an XML template file. This normally means that there was a problem locating the document (either the document does not exist or there is a problem with permissions). Another possible cause is that the XML parser software is not properly installed. |
| 35 | Error - subscript out of range | While executing an XML IMPORT FILE or an XML IMPORT TEXT statement, the XML Extensions library detected that a subscript reference is out of range (the subscript value is greater than the maximum for the array). This may occur either when the subscript is explicitly supplied in an attribute or when the subscript is generated implicitly (when an extra occurrence is present). |
| 36 | Error - temporary file access error | The XML Extensions library encountered an error while attempting to access a temporary intermediate file. This error can occur during the XML IMPORT TEXT, XML EXPORT TEXT, XML VALIDATE TEXT, or XML TEST WELLFORMED-TEXT statements. |
| 37 | Error - in function: TransformDOM | An unexpected error occurred while performing an XSLT transform of an XML document. This might be an internal error, but can be caused by an error in an external stylesheet. |
| 38 | Error - in function: TransformText | An error occurred while performing an XSLT transform of an XML document using an external (user-supplied) XSLT stylesheet. This error may occur in the XML Extensions library. |
| 39 | Error - symbol table - not present in model file | The symbol table was not found in the specified model file. The model file was probably not produced by the XMLGEN compiler directive. |
| 42 | Error - in function: WriteDocument | An error occurred while attempting to write an XML document from the internal Document Object Model representation. |
| 45 | Error - invalid encoding selection | The value of the Encoding parameter of the XML SET ENCODING statement was neither "local" nor "utf-8". |
| 46 | Error - invalid UTF-8 data | An XML export operation failed because the data supplied was not valid for UTF-8. |
| 47 | Error - invalid MF_XMLEXT_LOCAL_ENCODING value | The value of the MF_XMLEXT_LOCAL_ENCODING environment variable on UNIX is not any of "mflatin1", "mflatin9", or a name recognized by the available iconv library. |
| 48 | Error - unable to locate iconv library | The value of the MF_XMLEXT_LOCAL_ENCODING environment variable on UNIX is not "mflatin1" nor "mflatin9", but an iconv library for character conversions could not be found. |
| 49 | Error - directory open failure | The XML FIND FILE statement was not able to locate and open the specified directory. |
| 50 | Error - missing XML parser (MSXML6) | The XML parser could not be found. This error occurs only on Windows and indicates the MSXML 6.0 parser is not installed in the Windows system. The MSXML 6.0 parser is normally installed when Visual COBOL is installed on Windows, but could not be found. MSXML 6.0 can be obtained by downloading it from Microsoft's web site. |
| 51 | Error - data item - illegal name format | A data-name being exported does not begin with an initial name character (letter, colon or underscore). This error should not occur; XML Extensions prepends an underscore to COBOL data-names that begin with a digit when creating XML names. |
| 52 | Error - CodeBridge conversion failure | The attempted conversion of data to or from a COBOL data type and a displayable string acceptable to XML failed. |
| 53 | Error - Name specified is not a data-item | When specifying a data structure name, a name was provided that is not a data item. For example, it might be a file-name, an index-name, a constant-name, and so forth. A data item name is required. |
| 62 | Error - requested template file cannot be found | Requested template file specified by the model file data name parameter cannot be found. |
| 63 | Error - resolved file name is too long | The resolved filename from one of the following statements is too large to fit in the buffer provided: XML EXPORT FILE, XML EXPORT TEXT, XML IMPORT FILE, XML IMPORT TEXT, XML RESOLVE DOCUMENT-FILE, XML RESOLVE SCHEMA-FILE, XML RESOLVE STYLESHEET-FILE, XML RESOLVE MODEL-FILE |
| 64 | Error - resolved file name does not exist | The file name passed to one of the following statements cannot be resolved. It may not exist and is not accessible. XML EXPORT FILE, XML EXPORT TEXT, XML IMPORT FILE, XML IMPORT TEXT, XML RESOLVE DOCUMENT-FILE, XML RESOLVE SCHEMA-FILE, XML RESOLVE STYLESHEET-FILE |
| 65 | Error - name / value pair required | The XML SET XSL-PARAMETERS statement requires an even number of parameters (name / value pairs). |
| 66 | Error - excessive number of XSL parameters | The XML SET XSL-PARAMETERS statement is limited to a maximum of 40 parameters (20 name / value pairs). |
| 67 | Error - unique identifier too long for buffer | The buffer supplied in the XML GET UNIQUEID statement is too small. Unique identifiers require 38 character positions. |
| 68 | Error - add attribute node failed | Adding an attribute to the document failed. |
| 69 | Error - add element node failed | Adding an element to the document failed. |
| 70 | Error - add text node failed | Adding a text mode to the document failed. |
| 71 | Error - validate DOM document | Validating the DOM document failed. |
| 72 | Error - import offset outside target data structure |
An attempt to store outside the target data structure determined by the DataItem parameter of the XML IMPORT statement has been detected. This can happen because of a model template file that is out-of-date with the executing COBOL program; in this case, the model template file needs to be regenerated from the revised COBOL program. Another cause can be duplicate data names in the symbol table and insufficient qualification (parent elements) in the imported XML document to choose the correct data item target for the import. The attempted import is suppressed along with any further import operations for the affected XML IMPORT statement. |
| 73 | Error - trace file open failed | The trace file name specified in an XML TRACE statement could not be opened. The most common cause of this error is that a directory name that does not exist is specified as part of the file name. Other errors that could cause this are access denied (because the file is read-only or the user does not have permissions to the file) or the program does not have permission to write to the directory specified. The program can continue, but tracing will be disabled. This error is only returned when the XML TRACE statement opens the trace file for the first time. Subsequent trace file open failures while the program is running other XML Extensions statements cause tracing to be suppressed. |
| 74 | Error - exported DataItem smaller than data structure in ModelFile | The COBOL data item being exported is smaller than the data structure described by the data-name specified for export. This would cause an attempt to access data beyond the end of the data item in the COBOL program, possibly causing a memory access violation. Make sure that the data item name, sometimes referred to as the data structure name, references an area in the COBOL program that is at least as large as the data-name. |
| 75 | Error - incorrect XML statement parameters | One or more of the parameters passed into the XML statement are invalid. This includes errors such as too few or too many parameters in the XML statement. This error also can indicate an invalid type of parameter, such as a POINTER data item specified where a pointer is not allowed or a nonnumeric or numeric parameter specified where a POINTER data item is required. Additional information, which can be obtained with XML GET STATUS-TEXT, describes the specific problem with the parameter or parameters. Only the first detected parameter error is described by the additional information. An incorrect number of parameters is always detected first. |