The last parameter - IndicatorValue - in the SQLBindFileToParam() CLI function is currently documented as "output (deferred)". It should be "input (deferred)".
|The following updates are additions to the "Description" column for the |SQL_DESC_AUTO_UNIQUE_VALUE and SQL_DESC_UPDATABLE arguments: |
|The following text replaces the current sentence that appears under the |Explanation column for SQLSTATE 22007 of the SQLSTATEs table for |SQLGetData:
|Conversion from a string to a datetime format was indicated, but an invalid |string representation or value was specified, or the value was an invalid |date.
|The following corrects the information in the "Usage" section under |"Information Returned by SQLGetInfo": |
|The following corrects the footnote in "Table 113. SQLGetLength |Arguments" :
|Note: a This is in characters for DBCLOB data.
The following text should be added to Chapter 5, "DB2 CLI Functions":
Specification: DB2 CLI 7.x
SQLRETURN SQLNextResult (SQLHSTMT StatementHandle1 SQLHSTMT StatementHandle2);
Table 13. SQLNextResult Arguments
| Data Type | Argument | Use | Description |
|---|---|---|---|
| SQLHSTMT | StatementHandle | input | Statement handle. |
| SQLHSTMT | StatementHandle | input | Statement handle. |
A stored procedure returns multiple result sets by leaving one or more cursors open after exiting. The first result set is always accessed by using the statement handle that called the stored procedure. If multiple result sets are returned, either SQLMoreResults() or SQLNextResult() can be used to describe and fetch the result set.
SQLMoreResults() is used to close the cursor for the first result set and allow the next result set to be processed, whereas SQLNextResult() moves the next result set to StatementHandle2, without closing the cursor on StatementHandle1. Both functions return SQL_NO_DATA_FOUND if there are no result sets to be fetched.
Using SQLNextResult() allows result sets to be processed in any order once they have been transferred to other statement handles. Mixed calls to SQLMoreResults() and SQLNextResult() are allowed until there are no more cursors (open result sets) on StatementHandle1.
When SQLNextResult() returns SQL_SUCCESS, the next result set is no longer associated with StatementHandle1. Instead, the next result set is associated with StatementHandle2, as if a call to SQLExecDirect() had just successfully executed a query on StatementHandle2. The cursor, therefore, can be described using SQLNumResultSets(), SQLDescribeCol(), or SQLColAttribute().
After SQLNextResult() has been called, the result set now associated with StatementHandle2 is removed from the chain of remaining result sets and cannot be used again in either SQLNextResult() or SQLMoreResults(). This means that for 'n' result sets, SQLNextResult() can be called successfully at most 'n-1' times.
If SQLFreeStmt() is called with the SQL_CLOSE option, or SQLFreeHandle() is called with HandleType set to SQL_HANDLE_STMT, all pending result sets on this statement handle are discarded.
SQLNextResult() returns SQL_ERROR if StatementHandle2 has an open cursor or StatementHandle1 and StatementHandle2 are not on the same connection. If any errors or warnings are returned, SQLError() must always be called on StatementHandle1.
Table 14. SQLNextResult SQLSTATEs
| SQLSTATE | Description | Explanation |
|---|---|---|
| 40003 08S01 | Communication Link failure. | The communication link between the application and data source failed before the function completed. |
| 58004 | Unexpected system failure. | Unrecoverable system error. |
| HY001 | Memory allocation failure. | DB2 CLI is unable to allocate the memory required to support execution or completion of the function. |
| HY010 | Function sequence error. |
The function was called while in a data-at-execute (SQLParamData(), SQLPutData()) operation. StatementHandle2 has an open cursor associated with it. The function was called while within a BEGIN COMPOUND and END COMPOUND SQL
operation.
|
| HY013 | Unexpected memory handling error. | DB2 CLI was unable to access the memory required to support execution or completion of the function. |
| HYT00 | Time-out expired. | The time-out period expired before the data source returned the result set. Time-outs are only supported on non-multitasking systems such as Windows 3.1 and Macintosh System 7. The time-out period can be set using the SQL_ATTR_QUERY_TIMEOUT attribute for SQLSetConnectAttr(). |
Only SQLMoreResults() can be used for parameterized queries.
|The following is an additional environment attribute that belongs in the |"Environment Attributes" section under "Usage": |
|
|The following replaces the existing information for the statement attribute |SQL_ATTR_QUERY_TIMEOUT: |