SQL/MX 3.2.1 Installation and Upgrade Guide (H06.26+, J06.15+)

Interoperability of SQL/MX releases
SQL/MX Release 3.2.x does not interoperate with older versions of SQL/MX in an EXPAND
network. All interoperating systems in the EXPAND network must have SQL/MX Release 3.2.x
software installed.
To ensure interoperability when your network includes multiple versions of SQL/MX, such as
SQL/MX Release 2.3.3 and SQL/MX Release 2.3.4, you must upgrade all of them to SQL/MX
Release 3.2.x, as shown in Interoperability of SQL/MX Releases.
Table 5 Interoperability of SQL/MX Releases
3.2.13.23.13.02.3.4Releases
NoNoNoNoYes2.3.4
NoNoNoYesNo3.0
NoNoYesNoNo3.1
Yes (with
restrictions)*
YesNoNoNo3.2
YesYes (with
restrictions)*
NoNoNo3.2.1
* You cannot access sequence generators on a 3.2.1 system from a 3.2 system.
Versions of SQL/MX software components
Each SQL/MX software component and persistent entity has a version identifier that identifies its
software release and that can be interpreted by other SQL/MX releases. Software version
components include the SQL/MX system software version (MXV).
Versioned persistent entities, which persist over time and across releases, include:
• Schemas that contain SQL/MX database objects.
• SQL/MX database objects, such as tables, views, and indexes.
• Compiled modules.
SQL/MX uses version identifiers to determine if a software component or persistent entity is
compatible with the SQL/MX release. Before using a software component or operating on a
persistent entity, SQL/MX checks the version identifier of the software component or persistent
entity. If the version identifier is compatible with the SQL/MX release, SQL/MX successfully proceeds
with the operation. If the version identifier is incompatible with the SQL/MX release, SQL/MX fails
the operation and returns a versioning error indicating an incompatibility.
The use of version identifiers enables interoperability between compatible versions and prevents
interoperability between incompatible versions. For more information, see:
• “Software requirements” (page 12)
• “Starting TMF” (page 13)
• “SQL/MX Release Information” (page 17)
Version identification of SQL/MX software components
All version identification in SQL/MX is numeric. General availability (GA) and Controlled Availability
(CA) software releases are assigned version numbers that are multiples of 20. General and
controlled availability releases do not interoperate with Early Adopter Program (EAP) releases or
other releases whose version numbers are not multiples of 20. The following table lists the software
version identifiers for SQL/MX Release 3.2.x.
Interoperability of SQL/MX releases 63