SQL4001N The character "<character>" in column "<column>" on line "<line>" is not valid.
Cause: The specified character is not a valid character in SQL statements.
The statement cannot be processed.
Action: 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.
Cause: 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.
Action: 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.
Cause: 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.
Action: Repeat the precompile process with the current version of the precompiler.
SQL4004N The package name is not valid.
Cause: 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.
Action: 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>".
Cause: A syntax error in the SQL statement was detected at the specified token "<token>".
The statement cannot be processed.
Action: Examine the statement, especially around the specified token. Correct the syntax.
SQL4010N Illegal nesting of Compound SQL statements.
Cause: This error is returned when a BEGIN COMPOUND clause is detected as a sub-statement of a Compound SQL statement.
Action: Resubmit the precompilation without the nested BEGIN COMPOUND.
SQL4011N Invalid SQL sub-statement in a Compound SQL statement.
Cause: This error is returned when an invalid sub-statement is detected in a Compound SQL statement. Valid statements are:
Action: Resubmit the precompilation without the invalid sub-statement.
SQL4012N Invalid use of COMMIT in a Compound SQL statement.
Cause: This error is returned when a sub-statement is detected after a COMMIT has been found in a COMPOUND SQL statement.
Action: 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.
Cause: This error is returned when an END COMPOUND statement has been found without a preceding BEGIN COMPOUND.
Action: Either remove the END COMPOUND, or add a BEGIN COMPOUND, and resubmit the precompilation.
SQL4014N Invalid Compound SQL syntax.
Cause: This error is returned when a Compound SQL statement contains a syntax error. Possible causes include:
Action: Fix the syntax error and re-precompile.