Command Reference Guide

MXCS Architecture Overview
SQL/MX Connectivity Service Administrative Command Reference—526350-005
1-8
Error Message Overview
A multiple error message for one error event looks like:
CS>start ds catalog_ds;
-- START DS \ODBC.$ASM.CATALOG_DS Failed
*** ERROR[15380] DS not found, \ODBC.$ASM.CATALOG_DS.
*** ERROR[15309] SUBSYSTEM: DS not found, library call CFGStartDS failed.
*** ERROR[15202] LOWLAYER 1: Data source does not exist.
These examples show actual error reports. See the SQL/MX Messages Manual for
explanations of each message number, such as 15380, 15309, 15202, and so forth:
In some cases, error messages from lower layers appear redundant, as the preceding
example shows. Note that the first line starts with a pair of hyphens (--) and is a result
summary, not an error message. This first line of the message gives the basic action,
the full object name, and summary status as success or failure.
Most commands using a wild card can produce multiple error events from one
command. For example, if you request information on all DS objects and the system is
busy, it is possible the command will fail for several, or even all, the DS objects it
iterates over. Such iterative commands often stop after the fourth error event. A
command with a wild card can quickly exceed the ten-message limit for error reports,
with the tenth message stating that some messages were dropped.
Each MXCS administrative command error message starts with three asterisks (***),
followed by ERROR or WARNING and the error message number. Warnings are
informational and do not stop command processing. Errors usually stop command
processing on the object where the error occurred. However, some commands can
continue processing additional objects if the asterisk (*) wild card is specified.
When more than one error is reported for an event, the first message is the primary
message describing the error and possible recovery. Subsequent messages result
from internal calls to subsystems and often provide more details about the problem.
Although primary error messages have no leading keyword, subsequent messages
can contain one of these keywords:

USAGE: Warning messages resulting from command entry syntax error

SUBSYSTEM: Messages translated from client library codes

LOWLAYER 1: Messages from layers below the client library

LOWLAYER 2: Additional messages from layers below the client library
In the SQL/MX Messages Manual, notation for an MXCS administrative command
error message often contains substitution variables, similar to this example:
Substitution variables appearing as int1 are integers, and those appearing as
string1 are strings. Some cases use a more meaningful variable, such as
functions-name, but substitution variables are always shown in italic.
15206 SUBSYSTEM: Bad return code int1, library call
functions-name failed.