SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-25
Semantic Analysis (0201-000100—0201-022306)
0201-007102
Cause. A connection context in a context clause was not declared with a connection
declaration clause. For example, you did not use a connection declaration clause, like
this one, to generate a connection context class:
#sql context SQLMXCtx;
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Declare a connection context class with a connection declaration clause,
declare and instantiate the declared type, and then use the instantiated connection
context object in the context clause. For details, see Connection Contexts on page 3-8.
0201-007200
Cause. An iterator variable used in left-hand side (LHS) of an assignment clause did
not have a Java type. The cause might be that an iterator class was not created.
Effect. The SQLJ translator fails during semantic analysis phase.
Recovery. Verify that the LHS is an iterator type and resubmit. For details, see the
Assignment Clause on page A-5 and Iterators and Result Sets on page 3-48.
0201-007300
Cause. The SQLJ translator encountered an invalid Java type for host variable #num.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Verify that host variable #num is a valid Java type and resubmit. For
details, see Data Type Support on page 3-32.
0201-007301
Cause. The SQLJ translator encountered an invalid Java type for the host variable
name at position #num.
[0201-007102] Connection context must have been declared with
#sql context ... It can not be declared as a
ConnectionContext.
[0201-007200] Left hand side of assignment does not have a
Java type.
[0201-007300] Invalid Java type for host item #
num.
[0201-007301] Invalid Java type for host item
name (at
position #
num).