15.10 - KeepRespond - Call-Level Interface Version 2

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

Call-Level Interface Version 2
Programming Reference


Conveys the current length of the input (response) buffer.

Usage Notes

The KeepRespond parcel requests as many response parcels as will fit in the specified MaxMsgSize.

If the KeepRespond 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 in any of the following situations:

  • A Cancel parcel is issued
  • The EndRequest parcel is returned in response to a continue request that contained a Resp parcel
  • An abort operation occurs
  • A logoff operation occurs
  • This parcel is generated by CLIv2 at the direction of the application.

    Parcel Data

    Table 89 provides field information for the KeepRespond parcel.


    Table 89: KeepRespond Parcel Field Information

    Flavor Field

    Parcel Body Length

    Parcel Body Fields



    MaxMsgSize: 2 byte unsigned integer

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

    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. The maximum value is 65535.

    The KeepRespond parcel is supported by all versions of the Database.