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-27
Managing Module Files and Their Applications
During Fallback From Release 2.1 or Release 2.0
If you are falling back to an earlier version of Release 1.8, you need to manage your
locally placed modules and their applications accordingly:
•
Falling Back Release 1.8 Applications and Their Locally Placed Modules From
Release 2.1 or Release 2.0 on page 11-27
•
Falling Back Release 2.x Applications and Their Locally Placed Modules From
Release 2.1 or Release 2.0 on page 11-27
Falling Back Release 1.8 Applications and Their Locally Placed Modules
From Release 2.1 or Release 2.0
Applications that were compiled from Release 1.8 and their locally placed modules
need to fall back as follows:
1. Fall back your Release 2.x 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.
2. From Release 1.8, make sure that any locally placed modules you will convert to
globally placed modules do not overwrite any existing module with the same name
in the /usr/tandem/sqlmx/USERMODULES directory. You can resolve any
impending module name conflicts by changing the module directive in the
application’s source file as instructed in the SQL/MX Programming Manual for C
and COBOL.
3. Copy every locally placed module from its local directory to the
/usr/tandem/sqlmx/USERMODULES directory.
4. Remove the shared local copies of the now unused modules. See Removing
Modules on page 11-22.
Falling Back Release 2.x Applications and Their Locally Placed Modules
From Release 2.1 or Release 2.0
Applications that were compiled from Release 2.1 or Release 2.0 and their locally
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. From Release 1.8, make sure that the locally placed modules you will convert to
globally placed modules do not overwrite any existing module with the same name
in the /usr/tandem/sqlmx/USERMODULES directory. You can resolve any
impending module name conflicts by changing the MODULE directive in the
application’s source file or by preprocessing the application, using the module
naming directives on the command line, and then language compiling, linking, and