Holding Error or Failure Parcels - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Holding Error or Failure Parcels

The response buffer must be at least long enough to hold an Error parcel or Failure parcel, so that the application program can detect a problem if it arises.

If the response buffer is not long enough for the longest parcel, CLI will grow the buffer to the required size (if less than the maximum size) at the time it encounters the longest parcel. The growth operation costs CPU time. If an application program is being optimized for performance and Current Response Buffer Length is higher than Response Buffer Length, consider increasing Response Buffer Length.

When the actual row size to be returned is:

  • Less than 32K and the response buffer is not large enough to hold a parcel, the Teradata Database returns a 3116 error. In response to it, CLI will retry with a larger buffer size.
  • Greater than 32K and the response buffer is not large enough to hold a parcel, the Teradata Database returns a 3115 error.
  • CLI will retry with a larger buffer size only if Maximum Parcel is set to H. If Maximum Parcel is set to O, CLI will not retry the 3115 error with a larger buffer size, but will instead return the 3115 error to the user. This prevents retry looping.