Applications using Parcel mode (request_mode='P') - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
17.10
Published
October 2021
Language
English (United States)
Last Update
2021-11-02
dita:mapPath
ttt1608578409164.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities
If extended response support exists at the database, CLI will always send the new parcels defined 'PclBIGKEEPRESP' or 'PclBIGRESP' even when the size of response buffer mentioned by the application is less than 64K.
  • Use of 'PclBIGRESP' or 'PclBIGKEEPRESP' parcel is directed by the client to CLI through DBCAREA field 'keep_resp'.
  • Initial buffer size that needs to be allocated by CLI for collecting the response messages is directed by the client using DBCAREA field 'resp_buf_len'.
CLI now controls the maximum limit of the response size that can directed by the client to CLI in DBCAREA field 'resp_buf_len ' through DBCAREA field 'maximum_parcel'.
  • If 'maximum_parcel' is set to 'O', set 'resp_buf_len' to not more than 32K.
  • If 'maximum_parcel' is set to 'H', set 'resp_buf_len' to any value not more than 2**32 if extended response is supported at server.
  • If 'maximum_parcel' is set to 'H', set 'resp_buf_len' to not more than 64K if extended response is not supported at the database.

If CLI finds that resp_buf_len is set to a value greater than 64K and extended response is not supported at the server, CLI returns an error 302 'BADBUFRQ'.

A new DBCHQEP query item 'QEPIXRS' for the Extended Response is added and has a value of 20. Client utilities can ascertain the support of extended response in the database by using this query item. CLI will return a 'Y' in QEPAREA if extended response is supported at the database and a 'N' otherwise.