HP 3000 Manuals HP 3000 Manuals
Preprocessing Errors
Several types of errors can occur while you are using the Pascal
preprocessor, for example:
* Unexpected preprocessor or DBEnvironment termination.
* Preprocessor invocation errors.
* Source file errors.
* DBEnvironment errors.
Preprocessor or DBEnvironment Termination
Whenever the Pascal preprocessor stops running unexpectedly while you are
using it in full preprocessing mode, sections stored during the
preprocessor's DBE session are automatically dropped when the
DBEnvironment is next started up. Unexpected preprocessor session
termination occurs, for example, when a DBA issues a STOP DBE command
during a preprocessor DBE session.
Preprocessor Invocation Errors
If the ALLBASE/SQL message catalog is not available when the preprocessor
is invoked, preprocessing terminates with the following error message in
the file SQLMSG:
Message catalog not available - see System Administrator (DBERR 10008)
:
If no source file name is entered, and a file named SQLIN cannot be
found, preprocessing terminates with the following error message in the
file SQLMSG:
File open error. (DBERR 10907)
SQLIN
ERRORS Processing terminated prematurely. (DBERR 10923)
:
In addition, the invocation line may name a DBEnvironment that does not
exist or contains erroneous syntax:
DBEnvironment = DBEnvironmentName
****** Cannot connect to DBEnvironmentName. (DBERR 10953)
*** DBECon Error - FSERR (170000). (DBERR 3078)
ERRORS Processing terminated prematurely. (DBERR 10923)
:
SQLIN Errors
When the Pascal preprocessor encounters errors when parsing the source
file, messages are placed in SQLMSG. Refer to the discussion earlier in
this chapter under "SQLMSG" for additional information on this category
of errors.
DBEnvironment Errors
Some errors can be caused because of the following:
* DBEnvironment is not started yet.
* Resources are insufficient.
* Deadlock has occurred.
Refer to the ALLBASE/SQL Database Administration Guide for information on
handling DBEnvironment errors.