15.10 - Expanded-parcel-header-usage - Call-Level Interface Version 2

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

Call-Level Interface Version 2
Programming Reference

Expanded‑parcel‑header‑usage might be used to ascertain whether Teradata Database allows use of the Alternate Parcel Header before constructing a parcel in Request‑mode.

Refers to the TDP whose TDP identifier is addressed by the QEPTIDP field and has length specified by the QEPTLEN field. Since they do not apply, the QEPRQST and QEPTOKEN fields must contain binary zeroes.

Returns whether parcels greater than 65535 bytes are supported by the Teradata Database.

This item is also included in the Aggregate‑support‑list query item.


Item Code


Response DBQEREPH (DbqerEPH for C)





(requestUsage for C)

A two-byte unsigned integer containing either:

'0' with mnemonic QEREPHN
      (QER_RequestUsageNone for C)

The maximum size of all parcels is limited to 32767 or 65535, depending on the supported setting of the Maximumparcel option.

'1' with mnemonic QEREPHI
     (QER_RequestUsageSubset1 for C)

The maximum size of the following parcel flavors may exceed 65535: 1-5, 7, 13-14, 31-32, 68-69, 71-72, 85, 102, 115-118, 120, 128-129, 140-143, 146-148, 153-154, 157-159.

Note: In addition to those parcel flavors associated with a value of 1, the maximum size of the following parcel flavors may also exceed 65535: 36-38, 41, 45, 52-57, 59-61, 63-65, 73, 75, 77-79, 81, 83, 88-89, 103, 106, 114, 135, 138, 155.

'2' with mnemonic QEPEPHA
     (QER_RequestUsageSubset2 for C)

Note: only those flavors used by normal parcelmode applications are described elsewhere in this document