MX 2.x)

Installing, Starting, and Uninstalling MXCS

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

2-3

Step 1: Install the MXCS Server Components

Use DSM/SCM to install the MXCS server components from the Software Update Tape

(SUT). This installs the server components and the ODBC/MX Client installation

program in the ZMXODBC installation subvolume.

Step 2: Add Logical Table Names to SQL/MX

By default, MXCS uses logical table names (ANSI names); the same logical name can

be used by a SQL/MX application running on the NonStop server and a client

application using MXCS.

You can use NSM/web to create an SQL/MP alias, or enter the SQL/MX command

CREATE SQLMP ALIAS in MXCI, to add the logical name mapping for each SQL/MP

table that you want to be available to a client application.

Step 3: Configure for Statistics Collection and Server Trace

(optional)

If you want the capability to collect resource statistics or trace server activity, you must

configure and start an alternate EMS collector(s) before the MXCS service is started. If

you do not configure and start an alternate collector, statistics or server trace

messages go to the default collector, $0. If you specify an alternate collector, but it is

not running, an error message is sent to the default collector. See Configuring Statistics

Collection on page 3-15 and Configuring Server Tracing on page 3-18.

Step 4: Start the MXCS Service

There are two ways to start the MXCS service:

•

from the installation subvolume (ZMXODBC)

•

duplicate the installed files to another location and start the MXCS service from the

new location

See Starting the MXCS Service on page 2-4.

Configuring MXCS as a Persistent Process

You can configure and start MXCS as a persistent process. This means that whenever

your NonStop server is coldloaded or manually restarted, MXCS will automatically

restart.

Note. You can configure MXCS as a persistent process through SCF. For more

information, see Configuring MXCS as a Persistent Process on page 2-3.