SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Binder and Compilation Messages (4000 through
4999)
HP NonStop SQL/MX Messages Manual—523730-004
6-25
SQL 4101
Cause. A syntax error has caused SQL/MX to treat object name as an ambiguous
entity.
Effect. The operation fails.
Recovery. Check the syntax for a missing parenthesis and resubmit. If the object is
not intended as a table reference in the FROM clause, use the error messages that
accompany this one to diagnose the problem. Correct the syntax and resubmit.
SQL 4102
Cause. You attempted to use either a FIRST n or an ANY n clause in other than an
outermost SELECT statement.
Effect. The operation fails.
Recovery. Remove the FIRST n or ANY n clause and resubmit.
SQL 4104
Where column name is a delimited ANSI identifier, such as MYCOL.
Cause. You attempted to select from a table using a character literal, but you used
double quotes as the delimiter instead of single quotes.
For example, if you enter this statement, in which "Lower" is a character literal:
>>select * from T050a where a="Lower";
you will receive this error:
*** ERROR[4001] Column "Lower" is not found. Tables in scope:
CAT.SCH.T050A. Default schema: CAT.SCH.
*** ERROR[4104] If a character literal was intended, you must
use the single quote delimiter instead of the double: 'Lower'
instead of "Lower".
4101 If name is intended to be a further table reference in
the FROM clause, the preceding join search condition must be
enclosed in parentheses.
4102 The [FIRST/ANY n] syntax can be used only in an
outermost SELECT statement that is not contained in a UNION
or INSERT.
4104 If a character literal was intended, you must use the
single quote delimiter: ‘literal’. The use of double quotes
causes SQL/MX to interpret column name as a delimited
identifier column name.