MX Release 3.2.1 (H06.26+, J06.15+)

DescriptionISVFile Name

MXCS event messages.ZTEMPLSMXOTMPL

SQL/MX and MXCS module filesZOSSUTLT0611PAX

Migrating from SQL/MX Release 2.3.4 to SQL/MX Release 3.2

NOTE: The same procedure is applicable when you migrate from SQL/MX 2.3.4 to 3.2.1.

The format of the CPU lists stored in the ODBC metadata, in SQL/MX Release 2.3.x is different

from the format of the CPU lists stored in SQL/MX Release 3.2. The SQL/MX Release 2.3.x CPU

list format is not recognized in SQL/MX Release 3.2. Starting with SQL/MX Release 3.2, mxtool

includes the fixmxcsmd option. The fixmxcsmd option supports the conversion of the SQL/MX

Release 2.3.x CPU list format to the SQL/MX Release 3.2 CPU list format in the

ENVIRONMENTVALUES MXCS metadata table. To convert the SQL/MX Release 2.3.x CPU list

format to the SQL/MX Release 3.2 CPU list format, you must run the mxtool command with the

fixmxcsmd option.

To convert the SQL/MX Release 2.3.x CPU list format to the SQL/MX Release 3.2 CPU list format,

you must run the mxtool command with the fixmxcsmd option after cold loading with SQL/MX

Release 3.2 objects.

NOTE: The fixmxcsmd option also supports the conversion of the SQL/MX Release 3.2 CPU

list format to the SQL/MX Release 2.3.x CPU list format in the ENVIRONMENTVALUES MXCS

metadata table.

To convert the SQL/MX Release 3.2 CPU list format to the SQL/MX Release 2.3.x CPU list format,

you must run the mxtool command with the fixmxcsmd option before cold loading with SQL/MX

Release 2.3.x objects.

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.

If a given CPU list value is a number between 1 and 15, you cannot determine the format. For

such CPU list values, a wrong target format specification generates appropriate error messages.

For example, the CPU list value 10 can imply a SQL/MX Release 3.x format CPU list consisting

of the CPU, 10 only, or it can imply a SQL/MX Release 2.x format CPU list with bits set for CPU

12 and 14.

24 Installing, Starting, and Uninstalling MXCS