Applications Using Parcel Mode|CLI|DBCAREA - Applications Using Parcel Mode - Call-Level Interface Version 2

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
20.00
Published
January 2024
Language
English (United States)
Last Update
2024-05-14
dita:mapPath
bmn1691484839905.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
fvz1470444150352
Product Category
Teradata Tools and Utilities

In this mode, CLI is responsible for building the parcels as per the protocol used for submitting the requests and data (optionally) to the database.

CLI will always use the alternate header for the set of parcels that has the alternate parcel support if:
  • The utilities use parcel mode (if DBCAREA option request_mode is set to 'P') for submitting requests. The database should have the APH support for those sets of parcels.
  • DBCAREA field maximum_parcel is set to 'H'. The size limit on the request buffer will increase from 64K to 1 MB, if APH support exists.
  • The total request size (includes size of [EXTENDED] [KEEP] RESP + LAN Header + [options parcel] exceeds 64K. CLI will return an error “REQOVFOW” 350, if APH support does not exist.
  • The DBCHQEP query item code to determine the alternate parcel header support at the database is “QEPAREA” and has a value of 21. It returns a 2-byte unsigned binary value in QEPAREA.
    • Value returned would be zero if no APH support exists.
    • Returns “1” if the first set of parcels supports APH.