SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

MXCI Messages (15000 through 15999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
16-17
Cause. A token separator is incorrect, likely in the object name
Effect. The operation fails.
Recovery. Enter the command using the correct separator value.
SQL 15235
Where string0 string1 string2 is the remaining string.
Cause. The parser could not locate the terminator for the attribute. All attributes end
with a comma or semicolon.
Effect. The operation fails.
Recovery. Enter the command using the correct syntax.
SQL 15237
Cause. The command name, which is the first token, is missing, possibly because the
command starts with a comma.
Effect. The operation fails.
Recovery. Enter the complete command, including the command name.
SQL 15238
Where string0 is the portion of the input following the problem.
Cause. You entered an extra comma instead of a value.
Effect. The operation fails.
Recovery. Enter the value instead of a comma and resubmit.
15235 Attribute value not terminated with a comma or
semicolon, command had: string0 string1 string2. +++SUGG:
Command could be missing a comma or the whole value may need
quotes. Only one token permitted for an attribute value.
15237 Command was missing the command name.
15238 Empty command attribute found (extra comma) just
before: string0.