SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

MXCI Messages (15000 through 15999)
HP NonStop SQL/MX Messages Manual—523730-004
14-26
Where string1 displays the start of the error.
Cause. A | character follows a string within quotes.
Effect. The operation fails.
Recovery. Retry the command, either specifying a valid concatenation operator || or
removing the invalid character.
SQL 15278
Where string1 is a portion of the input showing the start of the problem.
Cause. A component of the object name starts with a blank or tab character. Names
with a leading space are not valid.
Effect. The operation fails.
Recovery. Enter the command without a space at the start of the component name, or
use an underscore character.
SQL 15279
Where string1 displays the start of the error.
Cause. A component of the object name ends with a blank or tab character.
Effect. The operation fails.
Recovery. Enter the command without a space at the end of the component name, or
use underscores. Names ending with a space are invalid.
SQL 15280
Where string0 displays the characters causing the parsing error.
Cause. The parser detected the opening vertical bar after a quoted string ended, but
the syntax after that was not legal. Concatenation requires two bars.
Effect. The operation fails.
Note. As of the ABU SPR, this message is no longer generated.
15278 Leading spaces are not allowed in SQL identifiers,
command had: ‘string1’.
15279 Trailing spaces are not allowed in SQL identifiers,
command had: ‘string1’.
15280 A quoted string was followed by syntax error in the
concat operator “||“, command had: string0.