SQL/MX Programming Manual for C and COBOL (H06.10+, J06.03+)

C/C++ Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL—544617-003
15-35
Compiling a Module Definition File
generate module definition files as done in SQL/MX Release 1.8 and previous
releases.
To compile a module definition file, use the SQL/MX compiler mxcmp command on the
module definition (.m) file. The SQL/MX compiler places a compiled user module file in
the global /usr/tandem/sqlmx/USERMODULES directory or in the user-specified
local application directory.
Command-Line Syntax
To invoke the SQL/MX compiler, at an OSS prompt, enter:
-e
directs mxcmp 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 a 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 mxcmp to display summary information in addition to error and warning
messages for the compilation.
-g moduleGlobal
specifies that the module is placed globally in the
/usr/tandem/sqlmx/USERMODULES directory.
-g moduleLocal[=OSSdir]
directs mxcmp to place the module into the named OSS directory. If the OSS
directory is omitted, the module is created in the current directory. 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.
mxcmp [ -e ] [ -v ]
[ -g {moduleGlobal|moduleLocal[=OSSdir]}]
[ -d compiler-attribute-name=compiler-attribute-value]...
module-definition-file