HP NonStop SQL/MX Messages Manual page 398

MXCI Messages (15000 through 15999)
SQL 15203
15203 Maximum of int1 error messages exceeded, dropping the
rest.
Where int1 gives the maximum number of errors permitted for one command.
Cause. Excessive error messages are issued, and at least one is dropped.
Effect. The command fails with errors previously reported. This message is always
the last one reported for a given error.
Recovery. Correct the problem defined by the first error, which is normally the most
meaningful.
SQL 15205
15205 SUBSYSTEM: Request for LowLayer error message failed,
return code int1 from CFGFetchError.
Where int1 is the subsystem error number.
Cause. An attempt to determine a subsystem error fails. If the int1 value is 500, 501,
or 516, connection to the service is not operational. In rare cases, a disconnect arrived
from the SERVICE being examined.
Effect. A lower-level error might have been lost unless the connection just failed.
Recovery. See the first error message displayed for the event (primary message) to
determine the problem and the recovery action.
SQL 15206
15206 SUBSYSTEM: Bad return code int1, library call
function-name failed.
Where int1 is the value of the return code from the library call. This code is provided
for problem analysis by support or development personnel.
Where function-name is the name of the library function called.
Cause. A subsystem error is not converted to a meaningful string. The error number
has meaning only to the library subsystem for the specified function call.
Effect. The command and subsequent call to the subsystem fails.
Recovery. See the first error message displayed for the event to determine the
problem and recovery action. If provided, also see lower-level error messages for
additional information. Using an appropriate MACL INFO command, check the status
of the target object or related object for indication of a problem.
HP NonStop SQL/MX Messages Manual—640324-001
15 -10