17.10 - Changing the Value for Maximium Parcel - 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
Release Date
October 2021
Content Type
Programming Reference
Publication ID
B035-2418-061K
Language
English (United States)

Maximum Parcel is initialized to the default value provided for Maximum Parcel in the site’s CLISPB. If the value is not appropriate for the application, perform the following before calling DBCHCL for Connect, Run Startup and Initiate Request:

  1. Set Change Options to 'Y'.
  2. Change the value as appropriate.
    • O, if the original limit of 32 KB is the maximum size of one parcel.
    • H, if the limit of 64 KB or 1 MB (APH-requests/extended response support exists at the server) is the maximum size of one parcel.
    When the actual row size to be returned is:
    • Less than 32 KB and the response buffer is not large enough to hold a parcel, the Teradata server returns a 3116 error. In response, CLI will retry with a larger buffer size.
    • Greater than 32 KB and the response buffer is not large enough to hold a parcel, the Teradata server 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 return the 3115 error to the user. This prevents retry looping.
    • Greater than 64 KB and the response buffer is not large enough to hold a parcel, the Teradata server returns a 3177 error followed by an ErrorInfo parcel with an InfoType of 1 (PCLBUFFERSIZE). 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 3177 error with a larger buffer size, but will return the 3177 error to the user. This prevents retry looping.