SQL/MX Programming Manual for Java

SQLJ Error Messages
HP NonStop SQL/MX Programming Manual for Java—523726-003
D-10
SQLJ Syntax Checking (0100-000200—0100-
002800)
Effect. SQLJ cannot parse the statement.
Recovery. Correct the syntax and resubmit. See the SQLJ Clause on page A-1.
0100-002400
Cause. SQLJ found an illegal Unicode character while reading the statement from
SQLJ source file (.sqlj).
Effect. SQLJ cannot read and parse the statement from the SQLJ source file.
Recovery. Report the entire message to your service provider.
0100-002500
Cause. An illegal byte sequence was found in a given character set, or an input
character sequence was not a legal 16-bit Unicode sequence.
Effect. SQLJ cannot read and parse the statement from SQLJ source file.
Recovery. Check the file encoding. See -encoding on page 5-22. If the error recurs,
report the entire message to your service provider.
0100-002600
Cause. SQLJ found an invalid Java identifier for the class name in the connection
declaration clause. For example, you tried to use a Java reserved word, such as
package, for the identifier.
Effect. SQLJ cannot parse the connection declaration clause.
Recovery. Correct the syntax and resubmit. For details, see the Connection
Declaration Clause on page A-1.
0100-002700
Cause. SQLJ found an invalid expression in a connection or execution context clause.
For example, a connection or execution context object was not present between
brackets ([]).
[0100-002400] Illegal character in unicode escape sequence:
'
character'
[0100-002500] Malformed input character - check file
encoding.
[0100-002600] Invalid Java class name in context declaration.
[0100-002700] Invalid expression in context clause.