SQL/MX 3.1 Programming Manual for C and COBOL (H06.23+, J06.12+)

COBOL Program Compilation
HP NonStop SQL/MX Release 3.1 Programming Manual for C and COBOL—663854-001
16-28
Compiling Embedded Module Definitions
application-file
is the OSS path name of an object file that contains embedded module definitions.
The OSS directory:

Must exist and be accessible. Otherwise, an error is returned, and no module
is created.

Must not specify a Guardian subvolume (/G/...) or a remote directory in an
Expand network (/E/...).

Must not exceed 1024 characters.
module-name
is the fully qualified name of an embedded module definition. This option names
the generated module that is written to the user-specified local application
directory, user-specified Guardian or OSS location(s) or both, application DLL
location(s) or to the global /usr/tandem/sqlmx/USERMODULES directory. For
more information, see Module Management Naming on page 17-9.
Each module-name consists of:
[[catalog.]schema.]module[MODULEGROUP=group]
[MODULETABLESET=target][MODULEVERSION=version]
If catalog and schema are omitted, their default value settings can be supplied
with -d MODULECATALOG=catalog or -d MODULESCHEMA=schema. If
MODULEGROUP, MODULETABLESET, or MODULEVERSION is omitted, the default
setting can be supplied with -d MODULEGROUP=group, -d
MODULETABLESET=target, or -d MODULEVERSION=version.
If no module name is specified, mxCompileUserModule operates on all
embedded module definitions of application-file. Otherwise, each module-
name is the fully qualified three-part name of an embedded module definition in
application-file, and mxCompileUserModule operates only on the named
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