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-37

Compiling Embedded Module Definitions

To compile one or more of the modules of an embedded SQL/MX application

executable, use the mxCompileUserModule utility on the object file created by the

C/C++ compiler or on the executable file produced by the linker.

If you have a combination of module definition files and applications that contain

embedded module definitions, use mxCompileUserModule to SQL compile the self-

contained object files containing embedded module definitions, and use mxcmp to SQL

compile the application’s separate module definition files. For more information, see

Compiling a Module Definition File on page 15-42 and the example Building and

Deploying a C Application With Embedded Module Definitions and Module Definition

Files on page 15-58.

Command-Line Syntax

To invoke mxCompileUserModule, at an OSS prompt, enter:

-e

directs mxCompileUserModule 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 mxCompileUserModule to display summary information in addition to

error and warning messages for the compilation. For example, use this option to

verify the default settings of the SQL/MX compiler.

mxCompileUserModule { { [-e] [-v] [-g {moduleGlobal |

moduleLocal}]

[-d compiler-attribute-name=compiler-attribute-value]... } |

-m } Application-file ["{"module-name [, module-name]..."}"]

Module-name is:

[[Catalog.]Schema.]Module [MODULEGROUP=group]

[MODULETABLESET=target] [MODULEVERSION=version]