SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—544536-007
11-15
Managing Modules
For details on how to analyze query execution plans and determine an optimal plan,
see the SQL/MX Query Guide.
Managing Modules
Topics in this subsection:
•
Producing Locally Placed Modules or Globally Placed Modules on page 11-15
•
Securing User Modules on page 11-16
•
Checking Module Dependencies with DISPLAY USE OF on page 11-19
•
Grouping Applications and Modules to Run Multiple DISPLAY USE OF Operations
on page 11-23
•
Removing Modules on page 11-27
•
Converting Globally Placed Modules to Locally Placed Modules on page 11-28
•
Managing Module Files and Their Applications During Fallback From SQL/MX
Release 2.x on page 11-29
In SQL/MX Release 1.8, all user modules were globally placed modules located in the
/usr/tandem/sqlmx/USERMODULES directory. For SQL/MX Release 2.x,
applications written in C, C++, or COBOL can use either globally placed modules or
locally placed modules.
A locally placed module can reside in any OSS directory other than the
/usr/tandem/sqlmx/USERMODULES directory and is co-located with its application
executable. The format and contents of locally placed modules are identical to globally
placed modules.
Producing Locally Placed Modules or Globally Placed Modules
You can specify that locally placed modules always be produced by setting the
MXCMP_PLACES_LOCAL_MODULES attribute ON in the SYSTEM_DEFAULTS
table. The system-defined default value for this attribute is OFF, which means that by
default all modules are globally placed in the /usr/tandem/sqlmx/USERMODULES
directory.
On a case-by-case basis, you can specify local and globally placed modules with these
command-line options:
mxCompileUserModule
-g moduleGlobal | -g moduleLocal
mxcmp
-g moduleGlobal | -g moduleLocal