SQL/MX Programming Manual for Java

HP NonStop SQL/MX Programming Manual for Java—523726-003
D-1
D SQLJ Error Messages
This appendix lists SQLJ error messages according to when the errors occur:
•
SQLJ Processing Errors on page D-1
•
SQLJ Run-Time Errors on page D-90
SQLJ Processing Errors
The SQLJ translator generates error messages during each phase of its operation.
This subsection lists the error messages in numeric order according to when the errors
occur during processing:
•
Command-Line Options Processing (0000-000100—0002-007100) on page D-1
•
SQLJ Syntax Checking (0100-000200—0100-002800) on page D-6
•
Semantic Analysis (0201-000100—0201-022306) on page D-11
•
Profile-to-Class Conversion (0300-000100—0300-001500) on page D-61
•
Java Syntax Checking (0500-000400—0500-005000) on page D-62
•
Customization (0600-001100—0600-004200) on page D-72
•
Java Code Generation (0700-000100—0700-001600) on page D-76
•
Data Customization (0900-000100—0900-003000) on page D-81
•
SQLJ Customizer (1000-000200—1000-000700) on page D-88
Command-Line Options Processing (0000-000100—0002-007100)
These messages occur during the processing of command-line options for the SQLJ
translator.
0000-000100
Cause. SQLJ found a file with an invalid suffix on the command line.
Effect. SQLJ cannot process the SQLJ file.
Recovery. Verify that file name has a valid suffix, such as
.sqlj, .java, .ser,
.jar, or .m, and reissue the command. For details, see the SQLJ Translator
Command Line on page 5-10.
0000-000200
Cause. The file specified on the command line does not exist.
Effect. SQLJ cannot read the specified file.
Recovery. Verify that the file exists and reissue the command.
[0000-000100] name is not a valid input filename
[0000-000200] unable to read input file
name