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-8
Module Management Naming
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
To accomplish these tasks, you need not change the C, C++, or COBOL source file or
rely strictly on the MODULE directive or on module naming defaults. Instead, you can
specify the catalog and schema and the target, version, and group attributes for the
module names during SQL preprocessing. The external naming of the module files
during preprocessing influences the targeting, versioning, and grouping properties of
an application.
For more information, see:
•
How Modules Are Named on page 17-9
•
Effect of Module Management Naming on page 17-12
•
Targeting on page 17-12
•
Versioning on page 17-19
•
Grouping on page 17-21
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.