| Reserved Keywords | Connect ODBC UNIX Help | |
COBSQL displays four different types of message. These are as follows:
As COBSQL starts, it displays three banner lines which include the COBSQL version number.
The database precompilers produce information about the program that they are compiling. If the COBSQL "Verbose" or "Display" directives are used, then COBSQL will display this information.
All the database precompilers produce error messages. These messages range from those that are displayed for information only to those describing fatal errors. COBSQL attempts to identify the severity of the errors passed to it by the precompiler. It also extracts the precompiler error number and text and attempts to locate the source line on which the error occurred. The format of precompiler error messages is as follows:
<precompiler error no.> <severity> <precompiler error text>
The precompiler error message is passed to the COBOL Compiler after the source line that the error occurred on, allowing the COBOL Compiler to identify the source line that the error occurred on.
If COBSQL cannot determine the severity of the error passed by the precompiler, it will assume that it is a normal error, rather than a fatal error.
COBSQL itself produces four types of message: information only, warning, error or fatal. Most are fatal. The format of COBSQL errors is as follows:
* CSQL-<severity> <error no.> <error text>
The sections below list current COBSQL messages.
This message is for information only. COBSQL has successfully processed the source file and has passed all the necessary information back to the COBOL Compiler. The program can now be animated or executed. If any errors have been found, these will be highlighted in the source and the error text will be made available.
This message is for information only. COBSQL defaults to using the Oracle precompiler if the COBSQLTYPE directive is not set, is set incorrectly, or is set to an obsolete value.
This message is displayed if the last COBSQLTYPE directive has an incorrect value.
COBSQL attempts to invoke the Oracle precompiler. This will cause further errors if the Oracle precompiler is not present.
COBSQL displays this message to confirm that a directive is valid.
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.
COBSQL has encountered an invalid directive. Either the directive is incorrect or the value supplied for the directive is incorrect.
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. Under normal execution, this message should not appear. If it does, it indicates that an old version of COBSQL is being used with a new Integrated Preprocessor, or vice versa.
This message is displayed when other Integrated Preprocessors are to be invoked. It is for information only.
The Integrated Preprocessor that COBSQL invoked has returned a fatal error message. COBSQL passes this message to the COBOL Compiler and aborts.
For more information about what might have caused the other Integrated Preprocessor to abort, refer to its documentation.
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.
This message is displayed if COBSQL receives a COBOL error while trying to write out a record to the STK side file. COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
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 with.
To be able to use the Informix Precompiler, the environment variable INFORMIXDIR must be set. COBSQL uses the value of the INFORMIXDIR environment variable to locate the ESQL/COBOL precompiler.
This error can occur when COBSQL tries to open the source code file, or tries to process a copy statement in the expanded code. COBSQL attempts to open the source file before it invokes the database precompiler. If it cannot open the file, it will report this error.
This error may also be displayed if COBSQL cannot open a copyfile that appears in the expanded source code. COBSQL needs to process copy statements that are inserted by the database precompiler. If COBSQL did not do this, the COBOL Compiler would treat the copy statement as though it appeared in the original source, and expand it.
Once COBSQL has displayed this error, it will also display error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
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.
COBSQL displays this message, for information only, when the expanded source file is to be kept.
COBSQL displays this message, for information only, to let the user know which database precompiler is about to be called.
COBSQL has attempted to open the STK side file. This file is only used when COBSQL is stacked with other Integrated Precompilers.
COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
COBSQL displays this message once it has successfully called the database precompiler and is about to start processing the expanded code.
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.
If this message is displayed and the precompiler has created both a listing file and the expanded source code, then either COBSQL does not have read permissions on the files, or they have been created in the wrong directory. Ensure that the current directory is set correctly before running COBSQL.
As part of the processing performed after the database precompiler has completed, COBSQL reopens the original source code file. If COBSQL cannot open the file, it displays this error message.
COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
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.
This message is displayed when a write error occurs on either the trace or the debug file.
COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
To process the source file and the expanded code, COBSQL needs to create a number of virtual heaps. If there is a problem when COBSQL tries to create a heap, this message is displayed indicating which heap COBSQL had problems creating.
The most likely cause of this problem is that not enough memory is available or that too many virtual heaps have already been created. The solution is to close down some COBOL applications to free up memory or virtual file slots.
CSQL-F-026: Premature end of expanded source. Check for
CSQL-F-026: precompiler abort when run standalone. This
CSQL-F-026: error is unrecoverable. Hit any key to abort
CSQL-F-026: Source Lines could not be matched by COBSQL.
CSQL-F-026: COBSQL was processing: <Area of Code>
CSQL-F-026: Source lines around line in error are
<Lines of Source Code>
COBSQL has reached the end of the expanded source code before it reached the end of the original source code. There are two possible reasons for this.
The item <Area of Code> corresponds to the position within the original source code that COBSQL was processing. These areas include Working-Storage, Procedure Division and SQL statements.
The item <Lines of Source Code> identifies the original source code lines that COBSQL was processing. These are displayed as they can indicate where the problem lies in the original source code.
This message is displayed, for information only, when COBSQL is running in VERBOSE mode. It indicates that COBSQL has encountered the Working Storage Section and is about to process it.
This message is displayed, for information only, when COBSQL is running in VERBOSE mode. It indicates that COBSQL has encountered the Procedure Division and is about to process it.
This message is displayed, for information only, when COBSQL is running in VERBOSE mode. It indicates that COBSQL has encountered an EXEC SQL statement within the procedure division of a program and is about to process it.
As part of the processing performed after the database precompiler has completed, COBSQL opens the expanded source code file. If COBSQL cannot open the file, it displays this message.
COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.
COBSQL is being run with an old version of COBOL and will not work correctly. Because of this, COBSQL terminates rather than trying to continue.
COBSQL has encountered a directive that is now marked as obsolete.
COBSQL sometimes tries to re-position itself when working through the original source file (ORG) and the source produced by the database precompiler (CBL). It does this by scanning ahead in the CBL file to try to find a matching line. If it does, it displays this message.
The usual reason for a mismatch between the two source files is that the precompiler has produced code that COBSQL is not able to cope with. Until COBSQL is altered to cope with this, using the SQLDEBUG directive provides a temporary work-around.
The code produced when this message has been displayed may not function correctly because some of the original source may have been removed so that COBSQL can re-position itself.
Pro*COBOL has commented out a line of code that was not a part of an EXEC SQL statement. This may alter the way that the program executes and care should be taken if the application is run.
COBSQL tries to determine how the current run-time is configured by examining the settings of the run-time switches. This error is displayed if COBSQL cannot read the current settings.
This error causes COBSQL to abort.
Some external code generators produce COBOL code which contains null characters. COBSQL reads the settings of the run-time switches and attempts to change the settings of the relevant switches in order to enable it to read code containing null characters.
This message is displayed if COBSQL has successfully read the run-time switches but has failed in its attempt to set them.
Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
| Reserved Keywords | Connect ODBC UNIX Help | |