This manual documents two basic types of messages:
Warning Messages |
 |
Warning messages are followed by DBWARN and a number enclosed
in parentheses. For example:
Output will be truncated. (DBWARN 1) |
Warnings do not cause your program or command to be aborted,
but the entire command or the incorrect part of the command is either
ignored by ALLBASE/SQL or modified by ALLBASE/SQL so that command
processing may continue. In some cases, the transaction may be completed
in a way other than intended and will need to be corrected. In other cases,
warning messages are informational in nature and thus require no
action to be taken. This manual will inform the user whether action
needs to be taken or not.
Error Messages |
|
Error messages are followed by DBERR and a number enclosed
in parentheses. For example:
Number of copies must be in the range 1..20. (DBERR 5) |
Errors are usually caused by a user's attempting to perform
a command with invalid information or without the required capability
or authority.
There are three basic types of errors. ALLBASE/SQL responds
to them differently depending on the severity of the error.
The first type of
error is a syntax or authority-related error which keeps the current command
from executing. This is the most common type.
The second type of error causes the current transaction
to be aborted. In addition, a warning message is returned to inform
you that the error was serious enough to terminate the transaction.
For example:
A transaction in progress was aborted. (DBWARN 2010) |
The third type of error, a DBCore internal system
error, is the least common and sometimes causes ALLBASE/SQL to be
aborted.
In addition to messages with a DBWARN or DBERR number, you
may receive unnumbered messages returned to the HP-UX system console
from the ALLBASE/SQL daemon process. Console error messages typically
alert the system administrator to a condition that affects the DBEnvironment
as a whole.
