SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-58
Semantic Analysis (0201-000100—0201-022306)
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Use a supported character set in the MODULE directive. For details, see
the SQL/MX Reference Manual and MODULE Directive on page 4-12.
0201-021300
Cause. The MODULE directive contained a reserved SQL keyword as part of the
module name. For example, you specified:
#sql {MODULE cat.sch.select};
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Either avoid using reserved words in module names or delimit the reserved
words in a module name. For details, see the MODULE Directive on page 4-12. For a
list of reserved words, see the SQL/MX Reference Manual.
0201-021400
Cause. The MODULE directive contained incorrect syntax near token that could not
be diagnosed as a specific type of syntax error. For example, you omitted the ARE
keyword in the NAMES ARE clause:
#sql {MODULE cat.sch.mod NAMES ISO88591};
As a result, this error message occurs:
Invalid syntax in Module statement near ISO88591.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Correct the syntax of the MODULE directive. For details, see the SQL/MX
Reference Manual.
0201-021500
Cause. The MODULE directive was missing the ARE keyword and character set
specifier in the NAMES ARE clause.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Correct the syntax of the MODULE directive. For details, see the SQL/MX
Reference Manual.
[0201-021300] name is a reserved word and cannot be used as a
module name
[0201-021400] Invalid syntax in Module statement near
token
[0201-021500] Invalid syntax in Module statement, expected
ARE but found end of statement