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-26
Managing Module Files and Their Applications
During Fallback From Release 2.1 or Release 2.0
For instructions on falling back, see Appendix A, Falling Back From NonStop SQL/MX
Release 2.1 or Release 2.0.
Falling Back Release 2.1 or Release 2.0 Applications and Their Globally
Placed Modules From Release 2.1 or Release 2.0
Applications that were compiled from Release 2.1 or Release 2.0 and their globally
placed modules need to fall back as follows:
1. For each application whose globally placed module was SQL compiled by the
Release 2.1 or Release 2.0 compiler, determine whether or not a module definition
file is present.
2. Fall back your Release 2.1 or Release 2.0 environment to a Release 1.8
environment as described in Appendix A, Falling Back From NonStop SQL/MX
Release 2.1 or Release 2.0
3. If a module definition file was not found for a Release 2.1 or Release 2.0
application in Step 1, preprocess the application’s source file from Release 1.8 to
generate a module definition file.
4. From Release 1.8, host-language compile the Release 1.8 annotated source file
created in Step 3. For more information about host language compilation, see the
SQL/MX Programming Manual for C and COBOL.
5. From Release 1.8, use mxcmp to SQL compile every Release 2.1 or Release 2.0
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 Their
Applications During Fallback
If you have locally placed modules on your Release 2.1 or Release 2.0 system and
need to fall back to Release 1.8, you must:
1. 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.
2. From Release 1.8, host-language compile the Release 1.8 annotated source file
created by preprocessing the application.
3. From Release 1.8, SQL compile the module definition file of every Release 2.x
application to create a new globally placed module.
Before you fall back, identify the version of Release 1.8 to which you are falling back. If
the version supports locally placed modules (Release 1.8.5 SPR AAV IPM 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 or SQL compile your modules for fallback.