MX 2.x)

Installing, Starting, and Uninstalling MXCS

HP NonStop SQL/MX Connectivity Service Manual—524944-008

2-6

Upgrading to MXCS 2.0 from a Previous Version of

ODBC/MX

-TMC alternate-collector-name

specifies the name of the alternate EMS collector to be used for server tracing

generated by MXCS. If option [-TMC alternate-collector-name] is not provided,

MXCS Server Trace sends trace messages to the primary EMS collector. You must

start the alternate collector before starting MXCS. If server tracing is enabled but

the alternate collector is not started, an error message is logged to the default

collector ($0). See Configuring Server Tracing on page 3-18.

Additional Information

•

After the MXCS service is started, you use NSM/web or MXCI to enable the MXCS

service.

•

Only the parameters described here are valid. The IN, OUT, stdin, stdout, or stderr

parameters are not recognized by MXCS.

•

If you specify an invalid value for any parameter, the default value is used (if

available). If the parameter has no default value, MXOAS terminates with an error.

•

When the MXCS service is started, it then starts the other MXCS server

components, as specified in the configuration. When the server components are

started and available, the MXCS service is ready to accept incoming connections.

Upgrading to MXCS 2.0 from a Previous

Version of ODBC/MX

To upgrade to MXCS 2.0 (from a previous version of ODBC/MX), perform the following

steps:

1. Uninstall the previous version (optional):

a. Drop the ODBC/MX metadata tables in the system catalog (ZOAS2DS,

ZONAM2ID, ZODS, ZOENV, ZORES, ZODT).

b. Use the rm command in OSS to remove ODBC/MX module files.

c. Use the TACL command FUP PURGE to remove the MXCS files from the

installation subvolume.

2. Install MXCS 2.0. See MXCS Configuration and Metadata Tables on page 2-1.

3. Use the MIGRATE utility to upgrade MXCS and preserve previous settings for

MPALIAS, MPDEFAULTS, and configuration tables ZONAM2ID, ZODT, ZOAS2DS,

ZOENV, ZODS and ZORES.

Use NSM/web or MXCI to create a new configuration.

Note. If you uninstall version 1.8, you can run version 2.0, but you must recreate the

configuration with NSM/web or MXCI.