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

$zhome, name $mxo, StartMode

2-> application

2-> startupmsg “-pn 35000”, program $system.zmxodbc.mxoas

3-> start #mxoas

4-> status #mxoas

The above example indicates that the process $mxo starts from file

$system.zmxodbc.mxoas and uses the port number 35000.

Your installation might require different parameters or to configure a different set of CPUs. For

more information, see the SCF Manual for the Kernel Subsystem.

Starting an MXCS Service manually

NOTE: Starting with H06.27 or J06.16 RVU, you can start MXOAS in Secure Sockets Layer

(SSL) Encryption mode. SSL and its successor Transport Layer Security (TLS) are cryptographic

protocols that provide communication security over the network. JDBC T4 driver uses SSL for

communicating with the ODBC/MX server. Enabling NonStop SSL may degrade the performance.

To start the MXCS service, execute the MXOAS command at the TACL prompt to start the association

server:

NOTE: Before starting MXCS, set the following parameters if the application uses Java 1.6:

PARAM CIPHERSUITES 0.4

PARAM MINVERSION 3.0

MXOAS /NAME proc-name, NOWAIT, TERM terminal-name,

CPU cpu-number/ [-TCP tcp-process] [-EMS collector-name]

[-PN port-number] [-PR port-range] [-I] [-E detail-level]

[-RMC alternate collector-name]

[-TMC alternate collector-name ]

[ -SSL [-SSLPWD password] [-SSLTRACE trace-level] [-CACERT filename[, filename, filename]] [-SRVCERT filename] [-SRVKEY

filename] ]

NAME as-name

specifies the process name of the MXCS association server.

TERM terminal-name

specifies the name of a valid terminal to be used as the home terminal for all MXCS

processes. Specify a terminal that is always available, for example, $ZHOME.

If a home terminal is not specified, or it is a dynamic telnet window, the default is

the terminal used to start the MXOAS process. If that terminal is a dynamic telnet

window and it closes, MXCS stops accepting new connections because the window

is valid only for current server connections.

NOTE: If the home terminal closes, the MXCS service cannot create new servers

or process new connection requests.

CPU cpu-number

specifies the primary CPU in which the association server is to run.

-TCP tcp-process

specifies the Guardian name of the TCP/IP process. If TCPIP^process^name is

defined before starting MXOAS, that name is used. If TCPIP^process^name is

not defined, the default name is $ZTC0.

-EMS collector-name

20 Installing, Starting, and Uninstalling MXCS