| SQL4001N | The character "<character>" in column "<column>" on line "<line>" is not valid. |
Explanation: The specified character is not a valid character in SQL statements.
The statement cannot be processed.
User Response: Remove or replace the character that is invalid.
| SQL4002N | "<token 1>" and "<token 2>" are undeclared host variables that cannot both be used as descriptor names in a single SQL statement. |
Explanation: The specified identifiers have not been declared as host variables. Descriptor names are not declared before using. Because more than one descriptor name in a single statement is not valid, at least one of the host variables is not valid.
The statement cannot be processed.
User Response: Correct the use of descriptor names or undeclared host variables in the statement. Note that the statement can contain additional undeclared host variables.
| SQL4003N | The SQL statement on line "<line>" is not supported by this version of the precompiler. |
Explanation: The release numbers of the precompiler and the installed version of the database manager are not compatible. The specified statement is supported by the database manager but not the precompiler.
The statement cannot be processed.
User Response: Repeat the precompile process with the current version of the precompiler.
| SQL4004N | The package name is not valid. |
Explanation: The package name contains characters that are not valid. Either the name is too long or no name was specified with the PACKAGE option.
No package is created.
User Response: Resubmit the command with a valid package name or without the PACKAGE option.
| SQL4005N | An invalid token "<token>" was found starting in position "<position>" on line "<line>". |
Explanation: A syntax error in the SQL statement was detected at the specified token "<token>".
The statement cannot be processed.
User Response: Examine the statement, especially around the specified token. Correct the syntax.
| SQL4006N | The structures are nested too deeply. |
Explanation: The number of nested structures exceeded the maximum of 25.
The statement cannot be processed.
User Response: Reduce the number of nested structures.
| SQL4007N | The host structure "<host-structure>" has no fields. |
Explanation: No field can be found within the host structure "<host-structure>".
The statement cannot be processed.
User Response: Add a field to the host structure.
| SQL4008N | The host variable "<name>" cannot be uniquely referenced even with full qualification. |
Explanation: The host variable "<name>" matches with at least one other unqualified or partially qualified host variable even with full qualification.
The command cannot be processed.
User Response: Rename the host variable.
| SQL4009N | The expression for data length is invalid. |
Explanation: The expression for data length has syntax errors or is too complex.
The statement cannot be processed.
User Response: Check the syntax of the size expression.
| SQL4010N | Illegal nesting of Compound SQL statements. |
Explanation: This error is returned when a BEGIN COMPOUND clause is detected as a sub-statement of a Compound SQL statement.
User Response: Resubmit the precompilation without the nested BEGIN COMPOUND.
| SQL4011N | Invalid SQL sub-statement in a Compound SQL statement. |
Explanation: This error is returned when an invalid sub-statement is detected in a Compound SQL statement. Valid statements are:
User Response: Resubmit the precompilation without the invalid sub-statement.
| SQL4012N | Invalid use of COMMIT in a Compound SQL statement. |
Explanation: This error is returned when a sub-statement is detected after a COMMIT has been found in a COMPOUND SQL statement.
User Response: Make the COMMIT sub-statement the last sub-statement, and resubmit the precompilation.
| SQL4013N | An END COMPOUND statement was found without a previous BEGIN COMPOUND statement. |
Explanation: This error is returned when an END COMPOUND statement has been found without a preceding BEGIN COMPOUND.
User Response: Either remove the END COMPOUND, or add a BEGIN COMPOUND, and resubmit the precompilation.
| SQL4014N | Invalid Compound SQL syntax. |
Explanation: This error is returned when a Compound SQL statement contains a syntax error. Possible causes include:
User Response: Fix the syntax error and re-precompile.
| SQL4015N | An error has occurred during preprocessing. |
Explanation: The external preprocessor has terminated with one or more errors.
The command cannot be processed.
User Response: Please refer to the ".err" file for the correponding source file for more details.
| SQL4016N | The preprocessor specified cannot be found. |
Explanation: The preprocessor specified through the PREPROCESSOR option cannot be found.
The command cannot be processed.
User Response: Ensure that the preprocessor can be executed from the current directory, and also check the syntax of the PREPROCESSOR option.
| SQL4017W | Preprocessing has completed successfully. |
Explanation: Preprocessing of the input file has completed successfully using the external command specified through the PREPROCESSOR option.
User Response: No action is required.
| SQL4018W | Starting to process the preprocessed file "<preprocessed-file>". |
Explanation: The precompiler is now processing the preprocessed file.
User Response: No action is required.
| SQL4019W | Completed processing the preprocessed file "<preprocessed-file>". |
Explanation: The precompiler has completed processing the preprocessed file.
User Response: No action is required.
| SQL4020N | The 'long' host variable "<token 1>" is not valid. Use 'sqlint32' instead. |
Explanation: If the LONGERROR YES precompile option is in effect or the precompile option LONGERROR has not been specified and the platform has 8-byte 'long's, then the INTEGER host variable must be declared with the data type 'sqlint32', not 'long'.
On 64 bit platforms with 8-byte 'long' types the precompile option LONGERROR NO can be used to specify that 'long' host variables are to be used for BIGINT data types. For maximum portability the use of 'sqlint32' and 'sqlint64' are recommended for INTEGER and BIGINT data types respectively.
User Response: Replace the current data type of the host variable with the data type specified in the message.