SQL/MX Programming Manual for Java

Processing SQLJ Programs
HP NonStop SQL/MX Programming Manual for Java—523726-003
5-34
mxCompileUserModule Command Line
mxCompileUserModule Command Line
To invoke SQL compilation, you must run the mxCompileUserModule utility after you
run the SQLJ translator program, sqlj.tools.Sqlj.
Pass an extended profile (.ser file) or a JAR file containing extended profiles to the
mxCompileUserModule utility. The mxCompileUserModule utility invokes the
SQL/MX compiler (MXCMP) to SQL compile the embedded SQL statements in each
extended profile and produce a module. For more information about SQL compilation,
see Compilation by mxCompileUserModule on page 1-14.
Command-Line Syntax
To invoke mxCompileUserModule, enter this command at an OSS prompt:
-e
causes mxCompileUserModule to generate a warning rather than an error if a
table or DEFINE in an SQL statement does not exist during explicit SQL
compilation. To find errors in a program during explicit SQL compilation, omit the
-e option.
By default, customization requires database objects to exist at the time the
program is customized. To use a table or DEFINE that does not exist at the time of
customization, you must set the -missingSQLObject option to true, which
results in no entries of those SQL statements in the embedded module definition. If
SQL statements have entries in the embedded module definition, they should refer
to existing database objects during SQL compilation. Therefore, avoid using the -e
option when running mxCompileUserModule. Otherwise, SQL compilation
occurs with warnings when a referenced database object cannot be found.
-v
causes mxCompileUserModule to display summary information in addition to
error and warning messages for the compilation. For example, use this option to
verify the MXCMP default settings.
Caution. If you do not run mxCompileUserModule, you will not generate module files, and
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.
mxCompileUserModule [-e] [-v]
[-g moduleGlobal]
[-d
compiler-attribute-name=compiler-attribute-value]...
extended-profile | jar-file
[ "{"
module-name[, module-name]..."}" ]
module-name is:
[[
catalog.]schema.]module [MODULEGROUP=group]
[MODULETABLESET=
target] [MODULEVERSION=version]