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

C/C++ Program Compilation
HP NonStop SQL/MX Release 3.2 Programming Manual for C and COBOL—663854-002
15-38
Compiling Embedded Module Definitions
-m
directs mxCompileUserModule to display the list of module files associated with
the application file.
-g moduleGlobal
specifies that the module is placed globally in the
/usr/tandem/sqlmx/USERMODULES directory.
-g moduleLocal[=<OSSdir>]
directs mxCompileUserModule to place the module in the OSS directory. The
OSS directory can be either a Guardian or OSS location in the OSS format. If the
OSS directory is omitted, the module is created in the current directory. The
following rules related to the OSS directory apply:

The OSS directory must exist and be accessible.

The directory must not be a remote directory in an Expand network.

The OSS directory must not exceed 1024 characters.
If these conditions are not met, an error is generated, and no module is created.
If you do not specify -g moduleLocal[=<OSSdir>] but set
MXCMP_PLACES_LOCAL_MODULES ON, you must be in the same directory as the
application executable when you invoke mxCompileUserModule. Otherwise,
mxCompileUserModule writes the module in the current directory, and you will
need to move the module to the global USERMODULES directory or co-locate the
module with its application. For more information, see Generating Locally or
Globally Placed Modules on page 17-3.
-d compiler-attribute-name=compiler-attribute-value
specifies default attribute settings for compilation and existing settings for the
module name. The module name settings are:
modulecatalog=cat
moduleschema=sch
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.