SQL/MX Programming Manual for Java

Program and Module Management
HP NonStop SQL/MX Programming Manual for Java—523726-003
6-3
Customized SQLJ Program Files
If you do not specify the -dir and -d command-line options during translation, the
default directory of all programs files is the same as the OSS directory of the SQLJ
source file (.sqlj file). For more information about the -dir and -d options, see
Options for Output Files and Directories on page 5-18.
By default, the SQLJ translator program does not generate module definition files (.m).
Module definition files occur only when you choose to generate them during SQLJ
processing. For more information, see Processing With Module Definition Files on
page 1-17 and Commands for Processing With Module Definition Files on page 5-4.
Files Necessary for Execution
These program files are necessary for the successful execution of a customized SQLJ
program:
•
Java class file of the SQLJ program (for example, MyProg.class)
•
Connection context class files if generated (for example, SQLMXCtx.class)
•
Iterator class files if generated (for example, MyProg$Iter.class)
•
Keys file (for example, MyProg_SJProfileKeys.class)
•
Extended profile (for example, MyProg_SJProfile0.ser)
•
Modules (for example, CAT.SCH.GRP1^MOD1^TABLESET1^VER1)
For more information, see Static SQLJ Execution on page 1-20.
Note. Do not confuse module files, which do not have file extensions and reside in the
/usr/tandem/sqlmx/USERMODULES directory, with module definition files (.m), which are
optionally generated during SQLJ processing and are precursors to modules. For more
information, see Module
on page 1-16 and Module Definition File on page 1-19.