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-27
SQL 15276
Cause. The service name is an asterisk (*), which is invalid when trying to access a
server.
Effect. The operation fails.
Recovery. Retry the command specifying a valid service name. To list valid service
names, use the INFO SERVICE command.
SQL 15277
Where invalid-char displays the invalid character.
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.
15276 SERVICE name component * not permitted when accessing a
SERVER.
15277 Extra token invalid-char was found, command had:
string1.
Note. As of the ABU SPR, this message is no longer generated.
15278 Leading spaces are not allowed in SQL identifiers,
command had: ‘string1’.