SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-40
Semantic Analysis (0201-000100—0201-022306)
0201-011600
Cause. SQLJ could not find the stored procedure name with num arguments.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Verify that the stored procedure you are trying to call exists in the database
and resubmit. See the SQL/MX Guide to Stored Procedures in Java.
0201-011700
Cause. The SQLJ translator could not find the stored procedure that you specified and
instead found a procedure with the same name but with different arguments. The
found-string is usually the error 0201-011502 on page D-39.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Verify that the name and arguments of the stored procedure are what you
intended to call and resubmit. See the SQL/MX Guide to Stored Procedures in Java.
0201-012000
Cause. SQLJ encountered an unexpected internal error.
Effect. The SQLJ translator fails during semantic analysis.
Recovery. Report the entire message to your service provider.
0201-012100
Cause. SQLJ ignored the connection context specified in the FETCH statement.
Effect. The SQLJ translator returns a warning during semantic analysis.
Recovery. Remove the connection context to avoid this warning. For details, see
Associating an SQLJ Executable Clause with a Connection Context on page 3-15.
[0201-011600] Did not find stored procedure name with num
arguments.
[0201-011700] Did not find stored procedure
name with num
arguments.
found-string
[0201-012000] INTERNAL ERROR SEM-label. Should not occur -
please notify.
[0201-012100] Context
name ignored in FETCH statement.