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-25
Managing Module Files and Their Applications
During Fallback From Release 2.1 or Release 2.0
5. Depending on the application environment, use the appropriate management
commands to drain the currently executing applications, and restart the
applications using the copy in the local environment.
6. Remove the shared global copies of the now unused modules. See Removing
Modules on page 11-22.
Managing Module Files and Their Applications During Fallback
From Release 2.1 or Release 2.0
•
Managing Globally Placed Modules and Their Applications During Fallback on
page 11-25
•
Managing Locally Placed Module Files and Their Applications During Fallback on
page 11-26
Managing Globally Placed Modules and Their Applications
During Fallback
If you have globally placed modules on a Release 2.1 or Release 2.0 system and need
to fall back to Release 1.8, you must:
•
From Release 1.8, preprocess the source file of every Release 2.x application that
does not have a module definition file to generate a new module definition file.
•
From Release 1.8, host-language compile the Release 1.8 annotated source file
created by preprocessing the application.
•
From Release 1.8, SQL compile the module definition file of every Release 2.x
application to create a new globally placed module.
If you fall back to Release 1.8, you need to manage your globally placed modules and
their applications accordingly:
•
Falling Back Release 1.8 Applications and Their Globally Placed Modules From
Release 2.x on page 11-25
•
Falling Back Release 2.1 or Release 2.0 Applications and Their Globally Placed
Modules From Release 2.1 or Release 2.0 on page 11-26
Falling Back Release 1.8 Applications and Their Globally Placed Modules
From Release 2.x
Applications that were originally compiled from Release 1.8 and their globally placed
modules do not need to be modified or SQL compiled when you fall back from Release
2.x to Release 1.8.
Caution. If a module is used by more than one application and at least one of those
applications continues to use globally placed modules, do not remove the global copy of the
module. Removing the global copy of a module used by an application disrupts the application.