If you use Client-Library™ functions not represented by text (such as ct_cursor or ct_dynamic) to issue SQL commands, Client-Library encodes the information for efficiency, and Adaptive Server generally decodes and displays key command information. For example, if you open a cursor with ct_cursor and the command is running, the Adaptive Server Monitor event summary displays the cursor name and the cursor declare statement.
Table 4-3 lists a complete list of the Client-Library functions not represented by text:
Client-Library routine |
DB-Library routine |
Presentation name |
Presentation data |
|---|---|---|---|
ct_cursor |
N/A |
CLOSE_CURSOR |
Cursor name, statement |
ct_cursor |
N/A |
DECLARE_CURSOR |
Cursor name, statement |
ct_cursor |
N/A |
DELETE_AT_CURSOR |
Cursor name, statement |
ct_cursor |
N/A |
FETCH_CURSOR |
Cursor name, statement |
ct_fetch (when processing the results of ct_cursor) |
N/A |
FETCH_CURSOR |
Cursor name, statement |
ct_cursor CURSOR_ROWS, or ct_cancel when the connection has Client-Library cursors |
N/A |
CURSOR_INFO |
Cursor name, statement |
ct_cursor |
N/A |
OPEN_CURSOR |
Cursor name, statement |
ct_cursor |
N/A |
UPDATE_AT_CURSOR |
Cursor name, statement |
ct_command (CS_RPC_CMD) (default behavior) |
dbrpcinit (only in version 10.0.1 or later) |
DBLIB_RPC |
RPC name |
ct_dynamic |
N/A |
DYNAMIC_SQL |
Dynamic statement name, statement |
ct_command (CS_MSG_CMD |
N/A |
MESSAGE |
None |
ct_param |
dbrpcparam |
PARAM_FORMAT |
None |
ct_param |
dbrpcparam |
PARAMS |
None |
ct_command (CS_RPC_CMD) (only when a TDS version earlier than 5.0 is used) |
dbrpcparam (in DB-Library version earlier than 10.0.1) |
RPC |
RPC name |
For more information about SQL commands not represented by text, see your Open Client documentation.
