SQL/MX 3.2 Programming Manual for C and COBOL (H06.25+, J06.14+)

Program and Module Management
HP NonStop SQL/MX Release 3.2 Programming Manual for C and COBOL—663854-002
17-7
Specifying the search locations for the module files
mxCompileUserModule
-g moduleGlobal | -g moduleLocal=[OSSdir]
mxcmp
-g moduleGlobal | -g moduleLocal=[OSSdir]
Specifying the search locations for the module files
The modules placed in the user-specified locations are loaded by the embedded SQL
program using Define =_MX_MODULE_SEARCH_PATH or the OSS environment
variable _MX_MODULE_SEARCH_PATH.
Guardian DEFINE
The Guardian DEFINE class must be SEARCH. You can specify either a single
location or multiple locations using the SUBVOL0-20 or RELSUBVOL0-20 or both
attributes of SEARCH DEFINE. Guardian DEFINE is supported for both Guardian and
OSS embedded SQL programs. The order of the module file search is SUBVOL0,
RELSUBVOL0...SUBVOL20, RELSUBVOl20.
The following are examples of Guardian DEFINE:

Single search location
add define =_MX_MODULE_SEARCH_PATH, class search, subvol0
$DATA01.USRMODS

Multiple search locations
add define =_MX_MODULE_SEARCH_PATH, class search, subvol0
($DATA01.USRMOD1,$DATA02.USRMOD2)
OSS environment
You can specify multiple OSS locations using the OSS environment variable. The OSS
locations must be separated by colons (:). Therefore, SQL/MX does not support
module files placed in a directory that contains a colon. If you are using the OSS
environment variable, and you want to locate the module files in a Guardian location,
you can specify the Guardian module location in the OSS format. For example,
/G/data01/mxmods. The OSS environment is supported only for OSS-embedded
SQL programs.
The module files are searched for in the specified order of the directories, in the
environment variable. For example,
export
_MX_MODULE_SEARCH_PATH=/home/usermodule1:/home/usermodule2:/G/da
ta01/mxmods