Preprocessing Errors

• Unexpected preprocessor or DBEnvironment termination.

• Preprocessor invocation errors.

• Source file errors.

• DBEnvironment errors.

Preprocessor or DBEnvironment Termination

Whenever the FORTRAN 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 can be found, preprocessing terminates with the following error message in the file sqlmsg:

 File open error.   (DBERR 10907)



 ERRORS   Processing terminated prematurely.   (DBERR 10923)

   $

In addition, the invocation line may name a DBEnvironment that does not exist or contain erroneous syntax:

   DBEnvironment        = SourcePath/SomeDBE





   ******  Cannot connect to DBEnvironment.  (DBERR 10953)

   *** DBECon Error - FSERR (170000).         (DBERR 3078)

   ERRORS Processing terminated prematurely.   (DBERR 10923)



   $

Source File Errors

When the FORTRAN 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:

Refer to the ALLBASE/SQL Database Administration Guide for information on handling DBEnvironment errors.