CSQL-I-005: Passing precompiler-directive COBSQL has encountered directives after the END-COBSQL directive. These directives are for the database precompiler and COBSQL
will pass them on. This message is only displayed if the CONFIRM directive is set.
CSQL-F-007: COBSQL/Checker incompatible -- Terminating When COBSQL has to interact with other COBOL Integrated Preprocessors (for example, CP or HTMLPP), it needs to make sure that
the subordinate preprocessor(s) are using the same line buffer size as COBSQL. If they are not, this error message is generated.
CSQL-F-010: Irrecoverable error writing STK record In a stacked environment (for example when COBSQL invokes another Integrated Preprocessor such as CP), COBSQL stores information
returned from the other Integrated Preprocessor in a side file that has an extension of STK. The file has the same basename
as the input file.
CSQL-F-011: Environment unsupported by COBSQL/Informix COBSQL is being run with a version of COBOL for which, to the best of our knowledge, no Informix COBOL precompiler is available.
This message is also displayed if the wrong Informix COBSQLTYPE is specified for the COBOL release that COBSQL is running
CSQL-F-016: UNIX Exec error Return Code is Return-Code This message is displayed when running under UNIX. On UNIX this is not a fatal error. If a database precompiler came across
errors in the source file, it is likely it would produce a non-zero return code. Because this might happen, COBSQL will continue
after displaying this message.
CSQL-F-021: Precompiler did not complete -- Terminating After calling the database precompiler COBSQL checks to make sure that it completed. It does this by trying to open the files
that the precompiler should have produced. If it cannot open the files, it reports this error.
CSQL-E-023: File Status file-status COBSQL displays this error message after a file operation has failed. This message is normally preceded by another COBSQL
error message identifying the file in error.