SQL/MP Messages Manual

Message Handling
HP NonStop SQL/MP Messages Manual—427720-006
1-3
Message File Versions
Sometimes when variables are moved or deleted, HP adds a new message that
replaces the old one. HP does not delete the old message until that version of the
message file is no longer supported.
Message File Versions
The message file contains a record that describes the message file version. To display
the version of an SQL message file, use the SQL/MP conversational interface (SQLCI)
ENV command. The MESSAGEFILE VRSN variable lists the current version. For more
information about message file versions and how to specify an alternate message file,
see the SQL/MP Version Management Guide.
Sources of Messages
SQL/MP errors are generated by SQL/MP components and other system components.
For example, the file system generates messages that apply only to SQL objects:
catalog tables, base tables, indexes, views, collations, and partitions of tables and
indexes. The C, Pascal, and TAL compilers generate messages that apply only to C,
Pascal, and TAL host programs.
Messages in this manual are organized by the component that generates them. When
possible, error number ranges are included in section headings.
Destinations of Messages
The SQL/MP software returns errors to a program or to SQLCI, depending on whether
the request was programmatic or interactive. In addition, these SQL/MP components
can send messages to $0:
•
SQLCI
•
Catalog manager
•
SQL compiler
•
Executor
•
File system
•
COBOL85 preprocessor
•
Audit fix-up process
Caution. Although the meaning and variables associated with a specific error do not change,
there are cases in which an SQL statement can return a different error than it did in a previous
release. New features can change the order in which errors are checked by SQL software. This
aspect of NonStop SQL/MP can affect programmatic error handling. For more information, see
Programmatic Recovery Information
on page 1-5.