SQL/MX 3.2.1 Programming Manual for C and COBOL (H06.26+, J06.15+)

COBOL Program Compilation
HP NonStop SQL/MX Release 3.2.1 Programming Manual for C and COBOL—663854-005
16-29
Compiling Embedded Module Definitions
In summary, modules can be named as:

A fully qualified delimited module name, such as
cat.sch.\"GRP^MODULE^TGT^VER\"

A qualified module name followed by module specification strings, such as
cat.sch.module MODULEGROUP=grp MODULETABLESET=tgt
MODULEVERSION=ver

A simple, unqualified module name (for example, mod), with the catalog,
schema, group, table set, or version specified as -d compiler attributes.
You can run mxCompileUserModule more than once.
mxCompileUserModule extracts the application-file’s selected module
definitions. For each selected module definition m, mxCompileUserModule passes m
to mxcmp for SQL compilation. Each compilation of a selected module definition either
succeeds or fails just like any mxcmp invocation. An mxcmp compilation failure does not
affect preceding or following mxcmp invocations. In particular, an mxcmp compilation
failure does not prevent mxCompileUserModule from proceeding with the mxcmp
compilation of the next selected module definition.
Examples—mxCompileUserModule

This command compiles the embedded module definition:
mxCompileUserModule sqlprog.exe

This command places the module file in the same OSS directory as the application
executable:
mxCompileUserModule -g moduleLocal sqlprog.o

These settings affect statement recompilation at execution time:
mxCompileUserModule -d AUTOMATIC_RECOMPILATION=ON \
-d SIMILARITY_CHECK=ON sqlprog.exe

The following command compiles the embedded module definition and places the
module file in the user-specified OSS location, /usr/mymodules:
mxcompileusermodule -g moduleLocal=/usr/mymodules sqlprog.exe

The following command compiles the embedded module definition and places the
module file in the user-specified Guardian location, /G/data01/mymod:
mxcompileusermodule -g moduleLocal=/G/data01/mymod
sqlprog.exe