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

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—523723-004
11-24
Converting Globally Placed Modules to Locally
Placed Modules
4. When you deploy the application in the production environment, copy any
compilation scripts that replace the previous compilation scripts.
5. If you recompile the modules in the production environment, change the
compilation script so that it is consistent with the changes made in Step 2.
6. Remove the shared global copies of the now unused modules from the
/usr/tandem/sqlmx/USERMODULES directory.
7. Start the new version of the application.
Converting Applications in a Production Environment
On a production system, convert applications that use globally placed modules to
those that use locally placed modules:
1. If you know which modules are used by programs that make up an application,
skip this step. Otherwise, use the mxCompileUserModule utility to determine
which modules are used by the programs that make up an application.
a. Copy the executable to an empty temporary directory.
b. From the OSS prompt, invoke mxCompileUserModule:
mxCompileUserModule -g moduleLocal
temp-directory/application-executable
The -g moduleLocal option of mxCompileUserModule generates a locally
placed module in the temporary directory. Using the temporary directory
prevents disruptions to the application and prevents overwriting of any existing
modules.
c. Note the names of the module files that are generated in the temporary
directory.
d. Delete the contents of the temporary directory.
If you are not using embedded module definitions, you can find the name of the
modules in the module statement of the Module Definition file (MDF).
2. Copy the globally placed modules you want to convert to the directory where you
will deploy the application. Do not move the globally placed modules because this
would disrupt the existing application environment.
If a module is used by more than one applications and all modules are being
converted to locally placed modules, copy the globally placed modules to each
application directory that uses the common module.
3. If it has not yet been done, copy the executables for each application associated
with a locally placed module to the same local directory as the module.
4. Before you create any new modules for the local environment, set the
MXCMP_PLACES_LOCAL_MODULES attribute ON in the SYSTEM_DEFAULTS
table.