HP 3000 Manuals HP 3000 Manuals
Preprocessing Errors
Several types of errors can occur while you are using the COBOL
preprocessor:
* Unexpected preprocessor or DBEnvironment termination
* Preprocessor invocation errors
* SQLIN errors
* DBEnvironment errors
Preprocessor or DBEnvironment Termination
Whenever the COBOL 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 processes a STOP DBE command
during a preprocessor DBE session.
Preprocessor Invocation Errors
If a file named SQLIN cannot be found, preprocessing terminates with the
following message:
Input source file not found. (DBERR 10921)
In addition, the invocation line may name a DBEnvironment that does not
exist or contain erroneous syntax:
Cannot connect to DBEnvironment. (DBERR 10953)
DBECON Error - Privileged file violation. (DBERR 3067)
Error in preprocessor command line. (DBERR 10908)
Expected right parenthesis after MODULE/OWNER name. (DBERR 10919)
SQLIN Errors
When the COBOL preprocessor encounters errors when parsing SQLIN,
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:
* A DBEnvironment is not started yet.
* Resources are insufficient.
* A deadlock has occurred.
Refer to the ALLBASE/SQL Database Administration Guide for information on
handling DBEnvironment errors.