15.10 - TDP-release - Call-Level Interface Version 2

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

Call-Level Interface Version 2
Programming Reference

The TDP‑release might be used to aid in problem diagnosis.

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 the release identifiers for the TDP being used.

Note: The intent of this data is not to deduce TDP functionality, but simply to provide the current TDP release identification for whatever diagnostic value it may be. The value should not be parsed for any reason since its format is subject to change.


Item Code


Response DBQERTDR (DbqerTDR for C)





('release' for C)

Up to fifty-one EBCDIC characters, identifying from one to three TDP components, separated by commas.




The first, which begins with 'TDP.', is present if available and identifies TDP itself.




The second, which begins with either 'PC', 'SVC', or 'IUCV' and is enclosed in parentheses, is always present and identifies the interface from CLIv2 to TDP.




The third, which begins with either 'SXMS' or 'OSSI' and is enclosed in parentheses, is present if applicable and available, and identifies the interface from TDP to CLIv2.




Each identifier is normally eight characters consisting of a two‑character offering number; the one-character major release number and one-character minor release number; and the two‑character maintenance release number; each separated by periods. Each may also end with a period followed by a two-character E-tape number, but this is omitted if not applicable.