SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Falling Back to SQL/MX Release 1.8
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
8-10
Managing Locally Placed Module Files and
Applications During Fallback
5. In SQL/MX Release 1.8, use mxcmp to SQL compile every SQL/MX Release 2.x
application’s module definition file to generate a new globally placed module. New
module files are automatically placed in the
/usr/tandem/sqlmx/USERMODULES directory.
Managing Locally Placed Module Files and Applications During
Fallback
Before you fall back, identify the version of SQL/MX Release 1.8 to which you are
falling back. If the version supports locally placed modules (SQL/MX Release 1.8.5
SPR AAV or later), and your application module files were SQL compiled using the
Release 1.8.5 SPR AAV or later compiler, you do not need to convert your locally
placed modules to globally placed modules.
If you fall back to an earlier version of SQL/MX Release 1.8, you need to manage your
locally placed modules and their applications accordingly:
•
Falling Back SQL/MX Release 1.8 Applications and Locally Placed Modules From
SQL/MX Release 2.x on page 8-10
•
Falling Back SQL/MX Release 2.x Applications and Locally Placed Modules From
SQL/MX Release 2.x on page 8-10
Falling Back SQL/MX Release 1.8 Applications and Locally
Placed Modules From SQL/MX Release 2.x
Applications and their locally placed modules that were originally compiled in SQL/MX
Release 1.8.5 AAV or later do not need to be modified or SQL compiled when you fall
back from SQL/MX Release 2.x to SQL/MX Release 1.8.5.
1. Fall back your SQL/MX Release 2.x environment to an SQL/MX Release 1.8
environment as described in Steps for Falling Back From SQL/MX Release 2.x to
SQL/MX Release 1.8 on page 8-3.
2. Verify that you are falling back to SQL/MX Release 1.8.5 AAV or later, which
supports locally placed modules. If not, see Converting Locally Placed User
Modules to Globally Placed User Modules on page 8-11.
Falling Back SQL/MX Release 2.x Applications and Locally
Placed Modules From SQL/MX Release 2.x
Applications and their locally placed modules that were compiled from SQL/MX
Release 2.x need to fall back as follows:
1. For each application whose locally placed module was SQL compiled by the
SQL/MX Release 2.x compiler, determine whether or not a module definition file is
present.