SQL/MX 3.2 Programming Manual for C and COBOL (H06.25+, J06.14+)

COBOL Program Compilation
HP NonStop SQL/MX Release 3.2 Programming Manual for C and COBOL—663854-002
16-26
Compiling Embedded Module Definitions
Compiling a Module Definition File on page 16-30 and Combining Embedded Module
Definitions and Module Definition Files on page 16-45.
Command Line Syntax
To invoke mxCompileUserModule, at an OSS prompt, enter:
-e
directs mxCompileUserModule to generate a warning rather than an error if a
table or class MAP DEFINE in an SQL statement does not exist during explicit
SQL/MX compilation. To find errors in your program during explicit SQL/MX
compilation, omit the -e option.
If you are using late name resolution and want to use a table or DEFINE that does
not exist during explicit SQL/MX compilation, include the -e option. Then at run
time, the SQL/MX executor automatically recompiles the SQL statement from the
statement’s source in the module by using the run-time version of the table.
-v
directs mxCompileUserModule to display summary information in addition to
error and warning messages for the compilation. For example, use this option to
verify the default settings of the SQL/MX compiler.
-m
directs mxCompileUserModule to display the list of module files associated with
the application file.
mxCompileUserModule { { [-e] [-v] [-g {moduleGlobal |
moduleLocal}]
[-d compiler-attribute-name=compiler-attribute-value]... } |
-m } Application-file ["{"module-name [, module-name]..."}"]
Module-name is:
[[Catalog.]Schema.]Module [MODULEGROUP=group]
[MODULETABLESET=target] [MODULEVERSION=version]
Note.

If -m option is specified, other command line options are ignored.

The OSS tool mxCompileUserModule with the -m option does not display
the module files associated with the DLLs loaded by the embedded SQL
executable.

mxCompileUserModule with the -m option does not display the list of module
names associated with an application file if the modules are generated from a
source SQL file using the -x preprocessor option or if the environment
variable, SQLMX_PREPROCESSOR_VERSION is set to 800.