The SQL preprocessor expects to find either a PROCEDURE statement or a PACKAGE statement in the program.
The source program contains no SQL statements.
All references must be unambiguous.
A host structure must contain only scalar members.
An indicator variable must be declared as FIXED BIN(15).
Indicator variables specified in an array must be sequential beginning with 1.
The characters after the two hyphens (--) toward the end of the line are treated as comments.
Arrays as host variables are not allowed.
Invalid host data type used for host variable.
Invalid host data type used for host structure member.
The DECLARE TABLE statement is treated as a documentation only statement. It is ignored and does not have any effect on the program.
The DECLARE STATEMENT statement is treated as a documentation only statement. It is ignored and does not have any effect on the program.
An SQL informational message has been returned.
An SQL warning message has been returned.
An SQL error message has been returned.
An SQL severe error message has been returned.
A fatal database error occurred. Check to see that the database is installed correctly.
A fatal SQL Preprocessor occurred. Check that the file IBMSUDB2.DLL is present.
A fatal SQL Preprocessor occurred. Contact the provider of IBMSUDB2.DLL.
The SQL Preprocessor detects an error in its own code.
Examine the statement for missing end delimiters for the indicated string. The statement cannot be processed.
The comment is not terminated properly. The statement cannot be processed.
The file "<filename>" was requested but could not be opened. The source program could not be processed.
During processing, there was not enough memory to continue processing.
The precompilation has completed with the stated number of errors and warnings.
The statement could not be processed because it exceeds a system limit for either length or complexity. The statement cannot be processed.
The syntax error in the SQL statement was detected at the specified token following the text "<text>". The "<text>" field indicates the characters of the SQL statement that preceded the token that is not valid. The statement cannot be processed.
The name returned as "<name>" is too long. The maximum length permitted for names of that type is indicated by "<length>". The statement cannot be processed.
The host variable "<name>" is not declared any DECLARE SECTION. The statement cannot be processed.
The host variable "<name>" has already been declared in a DECLARE SECTION. The statement cannot be processed.
The limit on the number of host variables is dependent on how many will fit in the HOST_VARS column of SYSPLAN. This limit has been reached. The source program could not be processed.
The host variable "<name>" is not declared correctly. Some possible reasons may be that the type specified is not one that is supported, that the length specification is 0, negative, or too large, that an initializer is used, or that an incorrect syntax is specified. The variable remains undefined. The source program could not be processed.
The end of input was reached during processing of a DECLARE SECTION. The source program could not be processed.
Precompiler Services must be initialized before the requested function call can be processed. The source program could not be processed.
While reading or writing file "<name>", an error was encountered. The source program could not be processed.
An error was encountered while trying to load the DB2 Precompiler Services module (DSNHPSRV). Check that the dataset concatenation in your job is correct. The source program could not be processed.
An error was encountered while trying to locate the DBRM library. Check that there is a DBRMLIB DD card included in your job. The source program could not be processed.
The PL/I Compiler option DEFAULT(IEEE|HEXADEC) does not match the PL/I SQL Preprocessor option FLOAT(IEEE|S390). Make sure they are consistent and resubmit your job. The source program could not be processed.