ODBC Server Messages Manual

NonStop™ ODBC Server Messages
NonStop ODBC Server Messages Manual—429394.001
1-16
Messages Displayed on the Workstation
32067
Cause. You cannot reference a null variable. Variables are null when they are declared.
Effect. The statement fails.
Recovery. Before you reference the variable, assign a value to it.
32070
Cause. A communication error occurred while NOSUTIL was processing a request
from the NonStop™ ODBC Server (for a pass-through utility command, for example).
Effect. The statement fails.
Recovery. Verify the NonStop™ ODBC installation and configuration files. Correct
any errors and retry the statement. If the communication error persists, contact your
service provider.
32111
Cause. The specified database name does not exist or is not customized. If the database
is customized and you get this error, the database entry might be missing from the
NonStop™ ODBC Server mapping tables.
Effect. The statement fails.
Recovery. If the database does not exist, take appropriate action. If the database exists
but is not customized, you can drop it by using pass-through mode or SQLCI. If the
database exists and is customized but for some reason is missing from the mapping
tables, execute the REFRESH statement against the system catalog, then retry the
statement.
32112
Cause. The statement attempted to create a database that already exists, or the database
does not exist but is registered in the NonStop™ ODBC Server mapping tables.
Effect. The statement fails.
Recovery. If the database already exists, take appropriate action. If the database does
not exist but for some reason is registered in the mapping tables, execute the REFRESH
statement against the system catalog.
The variable variable-name is NULL.
NOS-NOSUTIL communication error: error.
Cannot drop database database-name because it does not exist.
Database database-name already exists.