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-30
Compiling a Module Definition File
environment variable. This environment variable is used by the ecobol or nmcobol
utility and enables you to direct ecobol or nmcobol to use another version of the
mxCompileUserModule utility.
To set the MXCMPUM environment variable, enter this command at an OSS prompt
before invoking the ecobol or nmcobol utility:
export MXCMPUM="/G/usr/mydir/mxCompileUserModule"
For more information, see the Open System Services Shell and Utilities Reference
Manual.
Compiling a Module Definition File
Embedded SQL application source files preprocessed with the -x and -m options or
that set the SQLMX_PREPROCESSOR_VERSION=800 environment variable continue to
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 user-specified local application directory, user-specified Guardian or OSS
location(s) or both, application DLL location(s), or in the global
/usr/tandem/sqlmx/USERMODULES 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.
mxcmp [ -e ] [ -v ]
[ -g {moduleGlobal|moduleLocal[=OSSdir]}]
[ -d compiler-attribute-name=compiler-attribute-value]...
module-definition-file