Preprocessing Errors

• Unexpected preprocessor or DBEnvironment termination.

• Preprocessor invocation errors.

• Source file 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. Unexpected preprocessor session termination occurs, for example, when a DBA processes a STOP DBE command during a preprocessor DBE session.

Preprocessor Invocation Errors

If the ALLBASE/SQL message catalog is not available or if the source file named cannot be found, preprocessing terminates with the following messages respectively:

        Message catalog not available - see System Administrator  (DBERR 10008)



        File open error.       (DBERR 10907)

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

        Cannot connect to DBEnvironment.  (DBERR 10953)

        ERRORS  Processing terminated prematurely.  (DBERR 10923)

Source File Errors

When the COBOL 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

Errors sometimes come about because:

Refer to the for information on handling DBEnvironment errors.