The maximum size of a response parcel that may be fetched by the application has been increased several times, but to ensure compatibility for existing CLIv2 applications, the acceptability of these increases must be indicated in the DBCAREA.
The default DBCAREA Maximum-parcel option value of 'O' limits response parcels to 32767 bytes. Specifying a value of 'H' allows a maximum of 65535 bytes. If the size of a response parcel exceeds 32767, but Maximum-parcel is not 'H' then Teradata Database returns a 3115 error to the application.
The default DBCAREA APH-response-OK option value of 'N' limits response parcels to 65535 bytes. Specifying a value of 'Y' allows a maximum of 2,147,483,647 bytes. If the size of a response parcel exceeds 65535, but Maximum-parcel is not 'H' then Teradata Database returns a 3177 error to the application.
The default Large-row-OK option value of 'N' limits parcels to 65,535 bytes. Specifying a value of 'Y' allows a maximum of 1,048,976 bytes. If the size of a parcel exceeds 65,535, but Large-row-OK is not 'Y', then Teradata Database returns an error to the application.
CLIv2 allocates an internal buffer to receive response parcels. The initial size of this buffer is specified by the DBCAREA Fetch-maximum-data-length value. If Teradata Database indicates that a response parcel exceeds the size of this buffer, CLIv2 will increase its size to receive the parcel, subject to limitations imposed by the previously described Maximum-parcel and APH-response-OK options, and the Inhibit-buffer-expansion option.