One Request at a Time - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

One Request at a Time

There are times when CLI sends a request to the Teradata Database for the next buffer-full of a response and it conflicts with a more recent request of the Teradata Database. The rule is that a session may have the Teradata Database active on its behalf for only one request at a time. This applies to the requests the application knows about as well as to the re-stocking requests done “behind the scenes.” If CLI is re-stocking response buffers, CLI will return “busy” from a call to DBCHCL for the Fetch function if Wait For Response is “N.” This phenomenon is a possibility when a new request has been “refused.”

Note: If CLIv2 is running a FastExport application that set a buffer length (using keyword BLOCKSIZE in the FastExport script) that is too small, CLIv2 will automatically try to fix the problem. The CLIv2 software, in this event, will expand the buffer by between 70 and 100 bytes, depending on parcel overhead. If the buffer expansion is sufficient, the FastExport job will run to completion The database will return the error:

3691: Specified Buffer Size is too small in FastExport

only if the buffer remains too small after the expansion has taken place.