SQL/MX Connectivity Service Administrative Command Reference

MXCS Architecture Overview
SQL/MX Connectivity Service Administrative Command Reference—526350-005
1-7
Error Message Overview
All MXCS objects can be viewed or manipulated with MACL commands supported by
MXCI. Through MACL and the configuration client library, MXCI establishes and
terminates connections to the process that makes up the logical service and, in some
cases, connections directly to the MXCS configuration database.
Although Figure 1-2 shows one system, an Expand network can connect to other
systems. Each system must have its own copy of the configuration database, MXCI
and its own MXCS services.
Server objects owned by one service can run on any CPU specified by the DS
definition. Service objects can also run on any specified CPU when you manually start
services from a TACL prompt by using the MXOAS command. No MXCS
administrative command is available to launch a service.
The START SERVICE command requires that the MXOAS command has already
started the processes and, as such, only moves the service from stopped to started
and allows users to start connecting. Also, the STOP SERVICE command does not kill
the service process. It merely prevents establishment of new connections and
terminates existing connections and the servers supporting them.
Error Message Overview
MXCS administrative command error messages for any single event consist of one or
more lines of error messages (limit of ten), displayed in this general format:
CS> command
*** Error[15nnn] Primary error message numbered 15200 to 15499 stating reason for
failure of the MXCS command.
*** Error[15nnn] (KEYWORD): Detailed error info from client library or usage
information. Keyword is "SUBSYSTEM" or "USAGE".
*** Error[15nnn] LOWLAYER 1: Report of problems from layers below client library.
*** Error[15nnn] LOWLAYER n: Additional report from layers below client library,
where n is 2, 3, 4, and so forth, indicating the sequential number
of the message up to 8.
To easily locate all errors for a particular event, you must be able to recognize all error
report formats. Some error reports contain several error events, so it can be useful to
group errors by event. Note that the initial message for an event contains no keyword
after the error number.
A single error message for one error event looks like:
CS>info ds abc, option;
-- INFO DS \ODBC.$ASM.ABC Failed
*** ERROR[15242] Command has an invalid attribute "OPTION". +++SUGG: Check spelling
or use of extra commas.
A usage error message for one error event looks like:
CS>info xx abc;
*** ERROR[15453] Unknown object type, XX.
*** WARNING[15288] USAGE: "INFO" command supports object types: DS, EVAR, SERVER,
SERVICE, USER.
Note. A message with content as shown in the first line of this example is always displayed.
Successive lines containing additional details are frequently displayed.