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

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
10-56
Cause. A CLI application attempted to access a stored procedure result set at position
index, but the number of result sets returned from the CALL statement was less than
index.
Effect. The operation fails.
Recovery. None. Contact the GMCSC and report this condition.
SQL 8916
where,
index is an integer specifying a position in the ordered set of result sets returned from
a CALL statement.
max-result-sets is the maximum number of result sets that can be returned from
the associated CALL statement.
Cause. A call-level interface (CLI) application specified an invalid index in a request to
bind a stored procedure result set to a specific result set index. A valid index ranges
from 1 to the maximum number of result sets that can be returned from the CALL
statement.
Effect. The operation fails.
Recovery. None. Contact GMCSC and report this condition.
SQL 8917
where,
index is an integer specifying a position in the ordered set of result sets returned from
a CALL statement.
Cause. A call-level interface (CLI) application attempted to bind multiple stored
procedure result set statements to the same result set index.
Effect. The operation fails.
Recovery. None. Contact GMCSC and report this condition.
8916 The request to allocate a stored procedure result set at
position index failed because the position is out of range.
Valid positions range from one up to the maximum number of
result sets that can be returned from the specified CALL
statement, which in this case is max-result-sets.
8917 The request to allocate a stored procedure result set at
position index failed because a result set at position index
already exists.