In this section: |
Result Set Management improves the way result sets are managed using Controlled Data Transfer and Query Interrupt.
Controlled Data Transfer offers the user the option to minimize the amount of processing on the server without interruption. This feature is not available for transaction adapters.
Controlled Data Transfer provides:
Server users with the option to minimize their wait time after issuing a cancel or disconnect request from a connector application.
A solution to the possible issues caused by a connector having to spool all the data for a request locally before being able to send a second request on the same physical connection.
Application control over the number of records retrieved by the client in response to a single fetch.
Support for LOB retrieval.
The SLIM setting allows the user to control the amount of data that will be downloaded from the server to the client at any one time. By default, this is set to zero (0) or no limit. A setting of zero (0) indicates that once a client requests some data from the server, the server cannot be interrupted until all of the requested data has been retrieved.
If the SLIM is set to a value other than zero (0), only n (where "n" is the number to which SLIM is set) rows will be downloaded to the client at one time. If the application cancels the request, only n-x (where "x" is the number of records already received for that block) records will be retrieved by the client after the request is cancelled.
Important: SLIM cannot be set to ON once processing starts. If you know in advance that a change will be necessary, set the SLIM parameter prior to the request.
This setting will override the SLIM set on the server.
If a valid SCB is referenced, the SLIM will only take effect for statements associated with that SCB. If only the EID is referenced, the SLIM is global, and will affect all SCBs in that session.
Setting the local SLIM to zero (0) will turn off SLIM processing (or Controlled Data Transfer). Setting it to -1 will revert SLIM to the server default.
The SLIM parameter should only be changed in between requests, not in the middle of a fetch loop.
Note: Remote procedure results are not currently subject to Controlled Data Transfer.
Query Interrupt enables the API to cancel a server thread in any state. To invoke Query Interrupt processing, the server must be enabled for Query Interrupt and the EDAQUIT method call must be issued with the variable, EDA_VAR_QUIT_ALL (19), set to one (1).
See your iWay Server Administration manual for your specific platform for details on how to invoke Query Interrupt processing on the server.
| iWay Software |