Changing the Value for Save-response-buffer - Teradata Tools and Utilities

Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Teradata Tools and Utilities
Release Number
June 2021
English (United States)
Last Update
Product Category
Teradata Tools and Utilities
When the value for Save-response-buffer is not appropriate for the application, you should perform the following procedure before calling DBCHCL for any of the following functions:
  • Connect
  • RunStartUp
  • Initiate with Protocol-function
  • Command
  • Initiate Request
  1. Set Change-options to ‘Y‘.
  2. Change the value for Save-response-buffer as follows.
    If the response buffer is to be... Then change the value for Save-response-buffer to...
    saved and reused for another response buffer request Y
    deallocated N

Use mnemonics for the codes. Mnemonics are provided in the language definition file for the DBCAREA.

If Save-response-buffer is set to ‘Y‘, one response buffer with its associated Request Context Block is saved.

However, if the next request requires a buffer larger than the one saved, the saved buffer is freed and another is allocated.

Proper use of this option can reduce the CPU overhead that would be incurred by always allocating a buffer for a call to DBCHCL for the Connect, RunStartUp, Initiate with Protocol-function, Command, or Initiate Request function and always deallocating it with a call to DBCHCL for the End Request function.