HP NonStop SQL/MX, Messages Manual

Page: 420 / 752

MXCI Messages (15000 through 15999)
HP NonStop SQL/MX Messages Manual — 640324-001
15 -32
SQL 15298
Cause. The object name or some component of it did not have the correct format.
Effect. The operation fails. A preceding message states the problem, and this
message shows the valid syntax for an object name.
Recovery. Enter the command using the correct name syntax.
SQL 15299
Cause. The command contains a syntax error.
Effect. The operation fails. A preceding message states the problem, and this
message shows the valid syntax.
Recovery. Enter the command using the correct syntax.
SQL 15300
Where
string0
is the DS name.
Cause. The lower levels returned a status indicating no ability to provide state
information for this DS. There could be several reasons for this. Look at additional
lower level messages.
Effect. The operation fails.
Recovery. Issue the
INFO DS*
command to determine if the DS exists.
SQL 15305
Where
function-name
is the client library function name.
Cause. The DS is in an active state with a service.
Effect. The operation fails.
Recovery. Enter the
STOP DS
* command. Use the wild card
*
for the service name.
15298 USAGE: [[ system .] groupname.membername ] are the name
components for a USER object.
15299 USAGE: command obj-type [obj-name][, attribute]...;
15300 Could not get the status for DS string0 .
15305 SUBSYSTEM: DS still in use somewhere, library call
function-name failed.