Neoview Messages Manual (R2.2)

SQL 23015
23015 servername: DDL command could not be found in buffer: description.
servername
is the name of the server program that issued the error.
description
contains details about the missing information in the DDL buffer.
Cause Expected DDL command not found in the XML input file. This might indicate a
problem with mxexportddl XML file generation.
Effect The operation fails.
Recovery Determine the problem with the input file and resubmit.
SQL 23016
23016 servername: Formatted file error was encountered: description.
servername
is the name of the server program that issued the error.
description
contains detailed information about the formatted file in error.
Cause The formatted XML file is invalid. description indicates the nature of the problem.
If the file is damaged or not a valid format, it might indicate a problem with the mxexportddl
program.
Effect The operation fails.
Recovery Determine the problem with the formatted file and resubmit. Contact the GMCSC.
SQL 23017
23017 servername: Expected XML tag is missing: description.
servername
is the name of the server program that issued the error.
description
contains detailed information about the missing XML tag.
Cause When processing an XML input file, an expected tag or tag attribute was not found.
This might indicate a problem with the mxexportddl generated output XML file.
Effect The operation fails.
Recovery Determine the problem with the input file, and resubmit.
SQL 23018
23018 servername: Expected map entry is missing: description.
servername
is the name of the server program that issued the error.
description
contains detailed information about the missing mapping file section name.
Cause When processing a mapping file, an expected section or attribute was not found.
Effect The operation fails.
Recovery Correct the mapping file and resubmit.
SQL 23020
23020 servername: SQL/MX object was not found: object-name.
servername
is the name of the server program that issued the error.
object-name
is the name of the missing HP Neoview database object.
Cause An expected Neoview database object is not on the target system.
Effect The operation fails.
Recovery Correct the target system and resubmit.
286 Utility Messages (20000 Through 23099)