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

Program and Module Management
HP NonStop SQL/MX Programming Manual for C and COBOL—523627-004
17-7
Module Management Behavior
•
Securing the modules
•
Checking module dependencies by using the DISPLAY USE OF command
•
Removing modules
For more information, see the SQL/MX Installation and Management Guide.
Module Management Behavior
By default, in SQL/MX Release 2.x, the SQL preprocessor generates a self-contained
application executable file that contains embedded module definitions. To obtain the
full benefit of the self-contained application code, avoid using the -x or -m options when
preprocessing embedded SQL source files of an application.
If you have applications that use module definition files, you can continue to generate
them by using the environment variable SQLMX_PREPROCESSOR_VERSION=800 and
certain preprocessor options, described under Influencing Module Management
Behavior. The SQL preprocessor generates a separate module definition file that
contains the translated SQL statements of an embedded SQL source file.
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.”