Several types of errors can occur while you are using
the C preprocessor:
Unexpected preprocessor or DBEnvironment termination.
Preprocessor invocation errors.
Preprocessor or DBEnvironment Termination |
 |
Whenever the 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 source file specified is currently being accessed,
or if the source file named
cannot be found, preprocessing terminates with the following
messages, respectively:
System error in opening input source file. (DBERR 10922)
File open Error (DBERR 10907)
|
In addition,
the invocation line may
name a DBEnvironment that does not exist or the command may contain
erroneous syntax:
****** Cannot connect to DBEnvironment. (DBERR 10953)
ERRORS Processing terminated prematurely. (DBERR 10923)
|
Source File Errors |
|
When the preprocessor encounters
errors while parsing the source file,
messages are placed in sqlmsg. Refer to the discussion earlier
in this chapter under "ALLBASE/SQL Message File" for additional information on
this category of errors.
DBEnvironment Errors |
|
Some errors result because:
A DBEnvironment is not yet started.
Resources are insufficient.
Refer to the ALLBASE/SQL Database Administration Guide for
information on handling DBEnvironment errors.
