How Messages are Returned

When you use ISQL, SQLUtil, SQLAudit, SQLGEN, SQLMigrate, SQLMON, ALLBASE/NET, or NETUtil interactively, messages are returned to the standard output, which is typically the terminal screen. These messages appear immediately after ALLBASE/SQL encounters a problem. When using ISQL, SQLUtil, SQLAudit, SQLGEN, SQLMigrate, SQLMON, NET, or NETUtil in background, messages are returned to the standard output after processing.

When an error occurs during execution of an ISQL command file, one of two things will occur. If SET CONTINUE is ON, the error message is displayed on the screen and the subsequent commands are executed. If SET CONTINUE is OFF, a message is returned to the terminal screen and none of the subsequent commands are executed. Refer to the ALLBASE/ISQL Reference Manual for additional information on the CONTINUE option of the SET command.

When you use the preprocessors, errors and warnings are returned to a file in your current working directory called sqlmsg. A module is not stored when an error is encountered, and your source code needs to be corrected before re-preprocessing. For additional information, refer to the ALLBASE/SQL application programming guide for the language you are using.

An application program that contains embedded SQL commands must include error handling routines to return runtime errors using the SQLEXPLAIN command. For additional information on SQLEXPLAIN, refer to the ALLBASE/SQL application programming guide for the language you are using.

Some errors are written directly to a file named /tmp/hpsqlerr. Errors are written to this file when they cannot be displayed on the terminal.

Errors from sqldaemon are returned to the system console.