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-28
Compiling Embedded Module Definitions
settings of embedded CONTROL QUERY DEFAULT, DECLARE, or SET
statements, which are set in the input source file. For more information, see the
SYSTEM_DEFAULTS table in the SQL/MX Reference Manual.
The OSS shell is used to invoke mxCompileUserModule, which in turn uses the
OSS shell to invoke mxcmp. Consequently, you must adjust the syntax for setting
CONTROL QUERY DEFAULT attribute values for MP_SYSTEM and
MP_VOLUME. The OSS shell performs command/parameter substitution and
allows a \ (backslash) to quote special characters such as $.
This example shows how to set MP_SYSTEM and MP_VOLUME as
mxCompileUserModule command-line options:
to get MP_SYSTEM=\KINGPIN --> use -d MP_SYSTEM=\\\\KINGPIN
to get MP_VOLUME=$TX012 --> use -d MP_VOLUME=\\\$TX012
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.