BTEQ resides on the client portion of either a mainframe-attached or workstation-attached system, and communicates with one or more Analytics Database instances on servers as described in the following table:
| Client System | Communication Mode |
|---|---|
| Mainframe-Attached | High-speed I/O channel or Local Area Network (LAN) |
| Workstation-attached | Local Area Network (LAN) |
Starting TTU 17.20, z/OS BTEQ (also known as Mainframe-attached client) is available in two variants:
- the pre-existing variant that uses TDP-mediated CLI, where CLI executes on MVS.
- the new variant that uses Gateway-mediated CLI, where CLI executes under Unix System Services (USS).
-
The external name for the Gateway variant is 'Mainframe Cloud-Network Connectivity'. For more details, see "IBM z/OS Mainframe Support" in Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems, B035-2418.
- Throughout this document, the two variants are referred to as Mainframe-attached (or z/OS) BTEQ employing TDP-mediated CLI, and Mainframe-attached (or z/OS) BTEQ employing Gateway-mediated CLI, wherever the context is the TDP or Gateway CLI being used. Usage of just Mainframe-attached means z/OS BTEQ is being referred to in general, as in when referring to differences between Workstation and z/OS BTEQ.
- BTEQ's SHOW VERSIONS command's output on z/OS indicates whether TDP-mediated or Gateway-mediated CLI is being used, along side the CLIV2 version number.