KeepResp - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
ggf1488824663364.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Purpose

Typically, the KeepResp parcel conveys the current length of the input (response) buffer.

Usage Notes

The KeepResp ( respond) parcel requests as many response parcels as will fit in the specified Byte Count. If the KeepResp parcel is used in a start request or continue request and the start response or continue response contains the EndRequest parcel, the spool file is retained on the Teradata Database. In general, the spool file is deleted when:
  • A Cancel parcel is issued in a (dis)continue request,
  • The EndRequest parcel is returned in response to a continue request that contained a Resp parcel,
  • An abort operation occurs, or
  • A logoff operation occurs.

This parcel is generated by CLI at the direction of the application.

Parcel Data

The following table lists field information for the KeepResp parcel.

Flavor Field Parcel Body Length Parcel Body Fields
5 6 MaxMsgSize: 2 byte integer

Field Notes

MaxMsgSize is the maximum number of bytes that can be returned to the client in one response. The minimum allowable buffer size is 256 bytes, hence MaxMsgSize must be greater than or equal to 256. Also, MaxMsgSize must be less than or equal to the size of the input (response) buffer. If the next parcel to be returned by the Teradata Database is larger than MaxMsgSize, an Error parcel that specifies how large the buffer must be is returned. If the buffer size is too small, a larger buffer must be allocated by the application program.