SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

Errors are generated under the following circumstances:
• If you assign a wrong value for number
• If a normal user executes the command (Only a SUPER ID user can convert the MXCS metadata.)
Warnings are generated under the following circumstances:
• If a qualifying row from ENVIRONMENTVALUES has an inconsistent value, the row is skipped
and a warning is issued.
• If a qualifying row from ENVIRONMENTVALUES has an ambiguous value, the row is converted
according to the format specification and a warning is issued.
Installing SQL/MX Release 2.x
To install SQL/MX Release 2.x, complete the following steps:
1. Install SQL/MX Release 2.x. For more information on installing SQL/MX Release 2.x, see
“Installing SQL/MX” (page 14).
2. Perform the operations described in “Migrating applications after system fallback” (page 54).
Migrating applications after system fallback
The modules that were generated on SQL/MX Release 3.2 are no longer compatible after a system
fallback to an earlier release. Therefore, all such modules must be recompiled after system fallback.
An alternate method is to save a copy of the modules before system upgrade and then reinstate
that copy after fallback. This method is applicable for the following scenarios:
• If the database layout after the fallback is similar to the layout before the system upgrade.
• If the application executables are not pre-processed, language-compiled and linked on SQL/MX
Release 3.2.
Changes required after falling back
Falling back might require changes to some or all of these corequisite product versions, particularly
if you fall back to an earlier RVU:
• RDF (Independent Product)
• NonStop Server for Java (Independent Product)
• JDBC Driver for SQL/MX (Independent Product)
• DP2
• TMF
• Measure
• Backup and Restore 2
For more information, see the H06.25 or J06.14 Release Version Update Compendium.
54 Falling back from SQL/MX Release 3.2