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-2
Program Files
C++ preprocessed file source-file.C
source-file.cc
source-file.cpp
source-file.cxx
source-file.c++
COBOL preprocessed file source-file.cbl
Executable program file source-file.exe
Module definition file source-file.m
SQL/MX module Use the MODULE directive to name a
module. If you do not specify the catalog and
schema names, NonStop SQL/MX
automatically qualifies the module name with
your current default catalog and schema. If
no default catalog and schema are defined,
NonStop-hosted SQL/MX preprocessors use
your Guardian group and user name for the
default module catalog and schema names.
Windows-hosted SQL/MX preprocessors
use SQLMX_DEFAULT_CATALOG and
SQLMX_DEFAULT_SCHEMA as the default
module catalog and schema names for the
MODULE directive.
If you do not use the MODULE directive to
name a module, the preprocessor generates
a default name.
The complete name of the module (module
file) is displayed by the SQL/MX compiler
after a successful compilation. It is also
written into the module definition file’s
module statement, if one is generated. You
can examine the contents of the module
definition file with any text editor. For
information on module names in embedded
module definitions, see Compiling
Embedded Module Definitions on
page 15-27.
By default, modules are stored in
/usr/tandem/sqlmx/USERMODULES.
However, you can use mxcmp options to
locally place modules. For more information,
see Generating Locally or Globally Placed
Modules on page 17-3.
Table 17-1. File Naming Conventions (page2of2)
File Naming Convention