SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-24
Semantic Analysis (0201-000100—0201-022306)
0201-007002
Cause. You specified more than one connection context or more than one execution
context in a context clause. You must specify one connection context and one
execution context in a context clause. For example, this statement is incorrect:
#sql [ctx, execCtx, ctx1] {/* SQL statement */};
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Correct the syntax of the context clause and resubmit. For details, see
Executable Clause on page A-4.
0201-007100
Cause. A connection context did not have a Java type. The cause might be a
misspelled name in the context clause or an undeclared connection context object.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Verify that the connection context declaration is valid and that you are
using the correct connection context object in the context clause and then resubmit.
For details, see Connection Contexts on page 3-8.
0201-007101
Cause. An execution context did not have a Java type. The cause might be a
misspelled name in the context clause or an undeclared execution context object.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Verify that the execution context declaration is valid and that you are using
the correct execution context object in the context clause and then resubmit. For
details, see Execution Contexts on page 3-20.
[0201-007002] Syntax (<connection context>, <execution
context>, ...) is illegal. Only two context descriptors are
permitted.
[0201-007100] Connection context expression does not have a
Java type.
[0201-007101] Statement execution expression does not have a
Java type.