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

For more information, see “Converting the CPU list format from SQL/MX Release 3.2 to SQL/MX
Release 2.3.x” (page 53).
The following is the syntax:
mxtool fixmxcsmd -v target [-d]
Where target is the major SQL/MX release that corresponds to the required target format. The
values allowed are 2 and 3.
The -d flag enables mxtool to display the source and target CPU list values without performing
any conversion. Using the -d flag is optional.
NOTE: You must perform the mxtool fixmxcsmd operation only when MXCS is in the Stopped
state.
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.
Upgrading the metadata after system upgrade
UPGRADE is a syntax-based utility command that can be executed from MXCI. The UPGRADE
command transforms the metadata from the existing version to the current schema version for the
SQL/MX Software Version (MXV). For more information, see the SQL/MX Reference Manual.
The following describes the SQL/MX Release 3.2 features and limitations related to upgrading the
database, which includes physical data files and all related objects.
• An upgrade of v1200 metadata to v3200 is supported.
• Databases created on SQL/MX Release 2.x (v1200 schemas) are supported. The metadata
upgrade is optional.
• v3200 schemas can be created created in new catalogs without having to upgrade v1200
metadata.
• New SQL/MX Release 3.2 features are supported with v3200 metadata only. The features
are not supported in v1200, v3000, and v3100 schemas. For more information on how to
use the new SQL/MX Release 3.2 features, see “Upgrading the metadata and using new
features on existing and new databases” (page 44).
• New schemas in an existing, non-empty catalog will be of the same version as the existing
schemas in the catalog. The version of a new schema in an empty catalog will be 3200,
unless the CREATE_DEFINITION_SCHEMA_VERSION CQD is set to another supported version.
Migrating applications after system upgrade
Embedded SQL-based programs, ODBC, and JDBC-based programs that use Module File Caching
(MFC) can create modules. The embedded modules that were generated on SQL/MX Release
2.3.4 or earlier are no longer compatible. Therefore, all such modules must be compiled after the
system is upgraded to SQL/MX Release 3.2 and before the applications are started.
SQL/MX Release 3.2 enables upgrading of applications from a SQL/MX Release 2.3.x system to
a SQL/MX Release 3.2 system without requiring you to recreate and reload the database. You
do not need to preprocess, compile the host language, and link when you migrate from SQL/MX
Release 2.3.x to SQL/MX Release 3.2. However, SQL/MX Release 3.2 does not support user
40 Upgrading the system to SQL/MX Release 3.2