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

Executing the following command results in the CPU list 12 and 14, which is wrong if the CPU list

is in SQL/MX Release 3.2 format:

mxtool fixmxcsmd -v 3

However, executing the following command results in the CPU list value 32, which is wrong if the

CPU list is in SQL/MX Release 2.3.x format:

mxtool fixmxcsmd -v 2

HP recommends that prior to converting the CPU list format, you test the option using the -d flag

to view the conversions.

The following are examples:

/home/user: mxtool fixmxcsmd -v 2 -d

*** Display MXCS cpu list transformations to R2 format

Data source DS1, translate '0,1,2' -> '57344'

Data source YOUR_DS, translate '14,15' -> '3'

...

/home/user: mxtool fixmxcsmd -v 2

*** Perform MXCS cpu list transformations to R2 format

Data source DS1, translate '0,1,2' -> '57344'

Data source YOUR_DS, translate '14,15' -> '3'

...

The previous examples highlight the difference in output when you use the -d flag.

Creating the default catalog and schema for MXCS

After upgrading to SQL/MX Release 3.2.1, you must create the default catalog and schema for

MXCS. The default catalog is NONSTOP_SYSTEM_NSK. The default schema is

PUBLIC_ACCESS_SCHEMA.

To create the default catalog and schema, run the following script located at /usr/tandem/

sqlmx/bin:

.\InstallMXCS -loc \$volume

Where,

$volume is the name of an audited, non-SMF DAM volume.

For example,

.\InstallMXCS -loc \$data01

NOTE: When you create a fresh installation of SQL/MX Release 3.2.1, the InstallMXCS script

is executed automatically, and the default catalog and schema are created. You do not have to

run the script.

The NonStop SQL/MX Database Manager (MXDM) requires the default catalog and schema to

display table statistics.

For more information on why the default catalog and schema are required, see Viewing table

statistics and their properties in the HP NonStop MXDM User Guide for SQL/MX Release 3.2.1.

Uninstalling MXCS from the Server

To uninstall MXCS components from the server, you must:

1. Stop the MXCS service.

2. Remove the object files from the installation subvolume.

Creating the default catalog and schema for MXCS 25