SQL/MX Connectivity Service Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

-SSLPWD password
specifies the password for the encrypted server key. This option is mandatory when
starting MXOAS in SSL Encryption mode. password value is not encrypted.
-SSLTRACE trace-level
indicates that SSL calls must be traced. The trace-level specifies the granularity
for tracing the SSL calls. Value range is 0–9999.
-CACERT filename[,filename,filename]
specifies the CA certificates for signing. The value is a list of comma separated
filenames. The first file on the list must contain a certificate for signing the given
server certificate. Subsequent files must contain certificates that sign the previous
certificate in the list. filename must be the absolute Guardian file path.
-SRVCERT filename
specifies the server certificate.
-SRVKEY filename
specifies the private key.
NOTE: The certificates must be in PKCS#8 format, with DER encoding. Encrypt the server key
with a password. The certificates must have file code 800.
The following example command starts MXOAS in SSL Encryption mode:
run mxoas /name $SSLR, nowait/ -pn 33005 -ssl -ssltrace 50 -sslpwd 123456
-CACERT $DATA05.CERTS.CACERT2,$DATA05.CERTS.CACERT1 -SRVCERT $DATA05.CERTS.SERVCERT
-SRVKEY $DATA05.CERTS.SERVKEY
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.
• When the MXCS service is started, if the same option is given multiple times, the value of the
last occurrence is taken into consideration.
• Check for port range configuration settings if the application response is slow, or new
connection requests fail with connection errors. Check for the EMS message “020007” on
the server side, the following is a message sample:
2-09-24 01:37:27 \ODBM.$MXZTI TANDEM.ODBCMX.G06 020007 A NonStop
Process Service error No more ports available to spawn new
MXOSRVR,there were a total of 18
available/connected MXOSRVR, 2 more ports
used by ODBC/MX and 0 more MXOSRVR were
spawned. This is a total of 20 ports.
Current port range is 20, Details for
each DS follows :DS
(TDM_Default_DataSource) had MXOSRVR
Spawned = 0 and Connencted/Available
MXOSRVR = 1 ,DS (mmxodbc01) had MXOSRVR
Spawned = 0 and Connencted/Available
MXOSRVR = 17 , has occurred.
Event Type: 1
22 Installing, Starting, and Uninstalling MXCS