SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java523726-003
D-17
Semantic Analysis (0201-000100—0201-022306)
Recovery. Check the CAST cast-type and resubmit with the correct casting. For
details, see Iterator Conversion Clause on page A-6 and Creating an Iterator From a
JDBC Result Set on page 3-56.
0201-002100
Cause. The SQLJ translator could not perform semantic analysis because it received
an error from the database while trying to establish a connection. The cause might be
a missing JDBC driver.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Examine the error message and resubmit with corrective action. For
details, see the JDBC Driver for SQL/MX Programmer’s Reference. If the error recurs,
report the entire message to your service provider.
0201-002200
Cause. You tried to use a host variable with a Java primitive data type to insert into or
select from a table that accepts a null value.
Effect. A NullPointerException might occur at run time.
Recovery. Convert the Java primitive data type to a corresponding wrapper object
and resubmit. For details, see Null Values on page 3-29 and Data Type Support on
page 3-32.
0201-002302
Cause. The SQLJ translator could not find an offline checker for the connection
context context-name.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Report the entire message to your service provider.
[0201-002100] Unable to perform semantic analysis on
connection
connection by user username. Error returned by
database is:
error-message
[0201-002200] The column javatype col is not nullable, even
though it may be NULL in the select list. This may result in
a runtime error.
[0201-002302] No offline checker specified for context
context-name.