SQL/MX 3.2.1 Programming Manual for C and COBOL (H06.26+, J06.15+)

Program and Module Management
HP NonStop SQL/MX Release 3.2.1 Programming Manual for C and COBOL—663854-005
17-9
Influencing Module Management Behavior
Influencing Module Management Behavior
You might have static SQL/MX application build scripts that require that the SQL
preprocessor always generate separate module definition files. By using the
environment variable SQLMX_PREPROCESSOR_VERSION=800 and preprocessor
options -x and -m, you can instruct the SQL preprocessor to generate module definition
files.
To set the SQLMX_PREPROCESSOR_VERSION environment variable, enter this
command on the OSS command line:
export SQLMX_PREPROCESSOR_VERSION=800
The preprocessor interprets the SQLMX_PREPROCESSOR_VERSION environment
variable and the -m and -x options, as indicated in Table 17-2. Suppose that the input
file name sql-file consists of base.extension. Consequently, if the input file
name sql-file were “prog.sql,” its base would be “prog,” and its extension
would be “sql.”
Module Management Naming
Use module management naming to externally qualify the file names of modules to
assist you with these development tasks:

Configuring applications to target different sets of database objects

Managing different versions of an application

Grouping the modules of an application
Table 17-2. Preprocessor Interpretation of SQLMX_PREPROCESSOR_VERSION
Environment Variable and -m and -x Options
SQLMX_PREPROCESSOR_
VERSION
environment variable -m ? -x ?
Module
Definition File?
Embedded
Module
Definition? *
Is >=1200 or is not set at all No No No Yes
Is >=1200 or is not set at all No Yes Yes in base.m No
Is >=1200 or is not set at all
See note **
Yes No Yes in module-
definition-
file
Yes
Is >=1200 or is not set at all Yes Yes Yes in base.m No
Is set to 800 No Error Yes in base.m No
Is set to 800 Yes Error Yes in module-
definition-
file
No
* The embedded module definition is included in the annotated output source file.
** This row shows the settings that you use to generate both module definition file and a single-file annotated
output source file (that contains embedded module definitions). You use these settings when you have a
combination of NonStop SQL/MX Release 1.x and 2.x.