HP NonStop SQL/MX Messages Manual page 133

Parser and Compilation Messages (3000 through
3999)
Recovery. Declare the cursor in a way that matches the statement and resubmit.
SQL 3007
3007 In an ALLOCATE CURSOR statement, both the cursor and the
statement must be named using string host variables.
Cause. You specified an ALLOCATE CURSOR statement with invalid syntax. Both the
cursor and the statement must be named using string host variables.
Effect. The operation fails.
Recovery. Name the cursor and statement with string host variables and resubmit.
SQL 3008
3008 The specified precision, precision, for a DECIMAL
UNSIGNED data type exceeds the maximum supported precision of
9.
Where precision is the precision you specified.
Cause. You specified a statement with a precision value greater than nine for the
PRECISION field of a DECIMAL UNSIGNED column, which is not supported.
Effect. The operation fails.
Recovery. Correct the syntax and resubmit.
SQL 3009
3009 DROP ASSERTION statement is not yet supported.
Cause. You attempted to perform a DROP ASSERTION statement, which is not
supported.
Effect. The operation fails.
Recovery. None.
SQL 3010
3010 Character set name is not yet supported.
Where name is the name of the character set.
Cause. You specified character set name that is not supported for use in an SQL/MX
object, such as a table or module. Examples include creating a KANJI or KSC5601
column in an SQL/MX table.
HP NonStop SQL/MX Messages Manual—640324-001
5 -3