SQL/MP Programming Manual for COBOL

Explicit Program Compilation
HP NonStop SQL/MP Programming Manual for COBOL—529758-003
6-37
SQL Compiler Messages

Be the local owner of the table or a remote owner with purge access to the table
(or be the local super ID user)
For information about process access, see Required Access Authority on page 7-1.
In these examples, the first statement updates the statistics for all columns in the
ORDERS table. The second statement updates the statistics columns in the primary
key or clustering key or in any indexes for the table ODETAIL.
EXEC SQL UPDATE ALL STATISTICS FOR TABLE =ORDERS END-EXEC.
EXEC SQL UPDATE STATISTICS FOR TABLE =ODETAIL END-EXEC.
For more information about the UPDATE STATISTICS statement, see the SQL/MP
Reference Manual.
SQL Compiler Messages
The SQL compiler issues messages for error and warning conditions. An error can
prevent successful compilation of a program file, but a warning does not. For a
description of all SQL compiler messages, see the SQL/MP Messages Manual.
Error Conditions
An error condition results from an invalid reference to an SQL object in an SQL
statement. Examples of invalid references are an incorrect column name or an
incompatible data type. If an error occurs, the SQL compiler generates a listing, but it
does not record the program file in the catalog and does not validate it for execution.
You can force an SQL compilation regardless of errors by specifying the SQLCOMP
FORCE option. The FORCE option directs the compiler to record the SQL program file
in the catalog and to validate it for execution even if errors occur. The SQL compiler
also writes the SQL statements with errors to the program file so that the statements
can be automatically recompiled at run time. You can use the FORCE option to debug
a program when you are not concerned about executing the SQL statements that
produce errors.
Dynamic SQL statements are not compiled during explicit SQL compilation. Errors in
these statements are returned at run time after dynamic compilation by a PREPARE or
EXECUTE IMMEDIATE statement.
Warning Conditions
A warning condition usually occurs when the SQL compiler has insufficient information
available. If a warning occurs, the SQL compiler still records the program file in the
catalog, validates the file for execution, and then returns a warning message.
In these two situations, the SQL compiler issues a warning message but still compiles
the statement:

Compiler assumption. The SQL compiler made an assumption necessary to
complete the compilation. For example, if the number of columns in the SELECT