SQL/MP Messages Manual

Preprocessor Messages (11000 to 11999)
HP NonStop SQL/MP Messages Manual—427720-006
13-29
SQL 11105
Cause. You specified an Extended Dynamic SQL cursor declaration without both a
cursor variable and a statement variable.
Effect. Compilation continues, but no object code is generated.
Recovery. Add either a cursor variable or a statement variable to the Extended
Dynamic SQL cursor declaration.
SQL 11106
Cause. You tried to compile an embedded SQL program on a system that does not
have a license for SQL/MP development. It may have a SQL/MP runtime license, but a
runtime license alone does not allow compilation of embedded SQL programs.
Effect. Preprocessing aborts after the message is printed to the host listing file.
Recovery. Do your development work on a system that has a license for SQL/MP
development or obtain a license for SQL/MP development for this system.
SQL 11107
Cause. The SQL statement and the descriptions the compiler creates of the input and
output variables of the statement must fit into a message that is no more than 32,767
bytes long. Your statement exceeded that limit.
Effect. Compilation continues, but no object code is generated.
Recovery. If the SQL statement qualifies column names with table names, you may
be able to shorten the statement by using correlation names to give shorter names to
the tables. If the column names are long, consider creating a view that uses shorted
names for the columns. Reduce the number of characters and the number of lines in
the statement (eliminate indentation spaces, other blanks where possible).
11105 Extended Dynamic SQL cursor declarations must have both
a cursor variable and a statement variable.
11106 Development of SQL applications is not supported on
this system.
11107 The SQL statement, which contains the SQL text and the
data types of input and output variables, exceeds 32,767
characters. This is not allowed.