SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-57
Semantic Analysis (0201-000100—0201-022306)
0201-020900
Cause. SQLJ could not find an argument in the CALL statement. For example, you
specified an extra comma in the argument list or forgot to specify the name of an
argument:
#sql {CALL foo(IN1,OUT1,)};
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Correct the syntax and resubmit with the proper arguments. For more
information, see the SQL/MX Guide to Stored Procedures in Java.
0201-021000
Cause. You specified an invalid DECLARE statement.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Resubmit with a valid DECLARE statement. See Supported SQL
Statements on page A-8.
0201-021100
Cause. The SQLJ parser was unable to parse the SELECT statement at or before
token.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Correct the syntax of the SELECT statement and resubmit. For details, see
the SQL/MX Reference Manual.
0201-021200
Cause. You specified an unsupported character set in the NAMES ARE clause of the
MODULE directive. For example, you specified:
#sql {MODULE cat.sch.mod NAMES ARE LikeTotallyCalifornian};
[0201-020900] Missing argument in procedure call. There are
adjacent commas.
[0201-021000] Invalid DECLARE statement
[0201-021100] SQLJ parser unable to parse SELECT statement at
or before:
token
[0201-021200] Illegal Character Set specified in Module
statement:
charset