SQL/MX Programming Manual for Java

HP NonStop SQL/MX Programming Manual for Java—523726-003
6-1
6
Program and Module Management
This section explains how to manage the files of an SQLJ application and covers these
topics:
•
Program Files on page 6-1
•
Packaging the Program in a JAR File on page 6-5
•
Managing Program Files on page 6-11
•
Managing Modules on page 6-11
•
Module Management Naming on page 6-12
Program Files
For effective program and module management, you should be familiar with the types
of program files generated by the SQLJ translator program and know where the
program files are stored on your system.
The program files generated by the SQLJ translator program depend on how you code
the SQLJ source file and whether and how you choose to customize the SQLJ
program. For example, if you do not declare connection contexts or iterators in the
SQLJ source file, the SQLJ translator program does not generate connection context
or iterator class files. If you choose to process the SQLJ source file in the default mode
for SQL/MX Release 2.x, the SQLJ translator program does not generate module
definition files. If you do not customize the SQLJ program, the SQLJ translator program
does not extend the profiles and does not generate module definitions (either
embedded module definitions in extended profiles or module definition files).
The locations of the program files depend on either the OSS directory where you store
the SQLJ source file (that is, the default directory) or the OSS directories you specify
for the -dir and -d command-line options during SQLJ translation. The modules are
stored in the
/usr/tandem/sqlmx/USERMODULES directory and should never be
placed outside this directory.
This subsection groups the program files based on whether you customize the SQLJ
program:
•
Customized SQLJ Program Files
•
Noncustomized SQLJ Program Files
Note. Currently, SQL/MX does not support locally placed modules for SQLJ applications. The
modules of an SQLJ application must be stored in the /usr/tandem/sqlmx/USERMODULES
directory. Otherwise, the program will either run dynamically or return an SQL exception
indicating that the module is missing or corrupted. For more information, see SQL/MX
Compiler Errors on page 4-5.