DBFERQ
DBFERQ is the End Request function of DBCHCL.
DBFEEQ is used to explicitly close a request, discard its response, and de-allocate internal data structures related to the request.
How It Works
DBFERQ performs the following functions:
Successful End Request Operation
The sequence of operations for a successful end request operation is:
1 Call DBCHCL for DBFERQ
2 Check for return code of zero
The DBFERQ applies to requests generated by calling DBCHCL for the DBFCON, DBFRSUP, and DBFIRQs.
The DBFERQ ensures that the Teradata SQL request’s response is discarded, thus freeing space on the database computer, and de-allocates CLI internal buffers (thus freeing space on the client).
These space-saving operations make it valuable to call DBCHCL for the DBFERQ as soon as the response is no longer required by the application program. In fact, it is still valuable (especially on IBM PC clients) to call DBCHCL for the DBFERQ even if the request was submitted with Keep Response set to N and the response was consumed or discarded by the Teradata Database.
DBCHCL always de-allocates the response buffer.
DBCHCL does not use the Open Requests field.
Values Read and Used, But Not Stored
The values for Wait Across Crash, Tell About Crash, Return Time, and Wait For Response are read and used, but not stored.
Interface
Function: |
DBFERQ - End Request |
Purpose: |
Terminate/cleanup specified request |
Parms: |
|
DBCAREA Parameters
The following fields in the DBCAREA may be read or written to by DBFERQ, depending on the application program’s environment.