15.10 - Save Response Buffer - Call-Level Interface Version 2

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

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

Save Response Buffer is a one byte field that specifies whether the response buffer is saved when DBCHCL is called for the End Request function.

 

In this language...

The variable name for Save Response Buffer is...

COBOL

DBCAREA‑SAVE‑RESP‑BUF

PL/I

SAVE_RESP_BUF

C

save_resp_buf

IBM Assembler

DBOFSVB

 

This routine...

Does this for Save Response Buffer...

DBCHINI

writes

DBCHCL

reads (CON; RSUP; CMD; IWPF; IRQ; CRQ)

 

Save Response Buffer is used by...

To...

applications

write

Save Response Buffer is initialized by DBCHINI to the default value provided for Save Response Buffer in the HSHSPB.

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.

    Note: 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.