This 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#DataFileName 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, the next duplicate is assumed, that is, a lexically previous duplicate definition. 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 import target name (model dataname) | The model data name determined by the ModelFileName#DataFileName parameter of the XML IMPORT statement is defined more than once in the symbol table determined by that parameter (either in the object program or from a model template file). Additional qualification is necessary to uniquely define the model data name, which is the description of the target data structure for the import. (Note that in the case of nested programs, the program name can be used as a qualifier and might be necessary to differentiate duplicate data-names defined in different programs.) |
| -4 | Warning - subscript out of range | A subscript is out of range on import, either due to a subscript specified explicitly as an attribute or an implicit subscript inferred from repeated elements in the input document. 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 | A URL (a string beginning with the sequence Error! Hyperlink reference not valid., Error! Hyperlink reference not valid., or file://) was used as an output document name. |
| 13 | Error - document file - create failure | An attempt to create an XML document file failed. |
| 14 | Error - document file - file open failure | An error was detected while attempting to open an input document file. The file might not exist or there might be a problem with permissions. |
| 15 | Error - extraneous element | An extra occurrence of a scalar data element was detected. |
| 17 | Error - in function: GetFirstChild | There was insufficient memory to process a document. |
| 18 | Error - in function: GetNextSibling | There was insufficient memory to process a document. |
| 19 | Error - in function: GetNodeData | There was insufficient memory to process a document. |
| 20 | Error - in function: GetRootNode | There was insufficient memory to process a 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 memory management information was corrupted or because the free memory call returned an error. |
| 23 | Error - internal logic - node not found | An inconsistency in its internal tables, specifically a missing entry in the Document Object Model, has been detected. |
| 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. |
| 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). This error may also occur if the input document contains an XML header but no elements. |
| 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 a program's XML symbol table. |
| 36 | Error - temporary file access error | An error has been encountered 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 error occurred while performing an XSLT transform of an XML document. This error may occur during the XML EXPORT FILE, XML IMPORT FILE and XML IMPORT TEXT statements. |
| 38 | Error - in function: TransformText | An error occurred while performing an XSLT transform of an XML document. This error may occur during the XML EXPORT FILE and XML TRANSFORM FILE statements. |
| 39 | Error - symbol table - not present in COBOL object | The ACUCOBOL-GT compiler did not produce an XML-format symbol table. |
| 41 | Error - old runtime version | The ACUCOBOL-GT runtime system is too old for this version of XML Extensions. |
| 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 RM_ENCODING value | The value of the X_XMLIF_ENCODING environment variable on UNIX is not any of XMLIF_LATIN_1, XMLIF_LATIN_9, or a name recognized by the available iconv library. |
| 48 | Error - unable to locate iconv library | The value of the X_XMLIF_ENCODING environment variable on UNIX is not any of XMLIF_LATIN_1, XMLIF_LATIN_9, 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 ACUCOBOL-GT 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). XML Extensions attempts to modify data item names that do not conform to XML tag name requirements. This error indicates a data item name has been encountered that was not successfully modified. |
| 52 | Error - data conversion failure | The attempted conversion of data between 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. |
| 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:
|
| 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 in function: AddAttribute | An attribute node could not be added during export of a document. Attributes are only added by XML Extensions when the XML ENABLE ATTRIBUTES statement has been executed. This error will not normally happen. One cause could be that the XML engine did not have enough memory to add the attribute node to the document. |
| 69 | Error in function: AddElement | An element node could not be added during export of a document. This error will not normally happen. One cause could be that the XML engine did not have enough memory to add the element node to the document. |
| 70 | Error in function: AddText | A text node could not be added during export of a document. This error will not normally happen. One cause could be that the XML engine did not have enough memory to add the text node to the document. The error can also happen if incorrect parameters are passed to the XML EXPORT FILE or XML EXPORT TEXT statement. |
| 71 | Error in function: ValidateDOMDocument | An attempt to validate a document failed. This normally means that the document is not valid, but could also mean the supplied schema is not a valid schema or there was not enough memory to validate the document. Additional error lines are produced to indicate why the validation 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 | Trace file open failed | This message is produced if the XML TRACE statement is unable to open the specified file. When this occurs, tracing is disabled. If subsequent file operations fail to open the file from other XML Extensions statements, tracing is suppressed, but will be resumed if a later open operation is successful. |