TDP's Role in a Teradata System - Teradata Director Program

Teradata Director Program Reference

Product
Teradata Director Program
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-09
dita:mapPath
hwt1488824663348.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2416
lifecycle
previous
Product Category
Teradata Tools and Utilities

As shown in the following figure, Teradata supports a variety of clients that can be attached using either a mainframe channel or a network connection. Client applications communicate with the Teradata Database to load, update, and query data that it holds. This book describes the software interface for mainframe clients.

Typical Teradata System

TDP provides a high-performance communication interface between mainframe applications and the Teradata Database. One Teradata Database is logically subdivided into multiple Logical-hosts, each of which can be connected to one and only one TDP: any mention of a Teradata Database in TDP documentation implies one of these Logical-hosts, on whatever physical Database server it might reside. Every mainframe system connected to a Teradata Database has at least one TDP associated with it. Therefore, a mainframe connected to more than one Teradata Database has more than one TDP. The connections and so the TDPs might be on any number of IBM LPARs running MVS. On any MVS, any number of TDPs, each of any release, may be started simultaneously. The operation and resources, of every TDP are completely independent of any others. The TDP executable modules for a release may be shared by any number of TDPs of that same release, except that those TDP modules in the MVS LPA for one release must be differentiated from the same modules for a different release using different one character suffixes.

Each TDP is identified by a tdpid, which is meaningful only within the mainframe system. On z/OS and VOS3, a tdpid corresponds to a Subsystem id so consists of four characters, the first three of which are 'TDP' and the fourth uniquely differentiates TDPs on that system. Each TDP operates in its own address space.

TDP displays messages and accepts commands from operator consoles, or software that emulates such consoles. Under z/OS and VOS3, TDP-defined records are written to the System Recording Facility (SMF). When channel devices are used to communicate with the Teradata Database, standard records are written to LOGREC for problems with the devices used. Under z/OS and VOS3, internal diagnostics can utilize the Generalized Trace Facility (GTF).