This section describes those Teradata TPump functions that are invoked from the Teradata TPump support environment on the client system. The Teradata TPump support environment is a platform from which Teradata TPump and a number of standard Teradata SQL, DDL, and DML operations can be performed. This client program includes a facility for executing Teradata SQL and is separate from Teradata TPump tasks that run in the database.
- Providing access to the data manipulation and data definition functions of the Teradata SQL language.
- User-defined variables and variable substitution.
- System-defined variables (for example, date and time).
- Conditional execution based on the value of return codes and variables.
- Expression evaluation.
- Redirection of command input.
- Runtime parameters for Teradata TPump invocation, foreign language support, and error logging functions.
- Character set selection options for IBM mainframe and client-based systems for UNIX.
The Teradata TPump support environment allows preparation for an initial invocation or resumption of a Teradata TPump task without having to invoke multiple distinct utilities. For example, the table that is to be loaded may need to be created, a database established as an implicit table-name qualifier, or the relevant permanent journal checkpointed.
Any statement not preceded by a period (.) is assumed to be a Teradata SQL statement and is sent to the database to be processed. An object name in an Teradata SQL statement may contain Katakana or multibyte characters when the appropriate character set is used.
The Teradata TPump support environment interprets the commands and statements that define the job. It also controls the execution of those commands and manages recovery from the database or client failures during processing.
Those commands not directly involved in defining a Teradata TPump task, but providing supportive functions (routing output, for example), are considered Teradata TPump support commands. These are individually executed as they are encountered.
The commands that define a single Teradata TPump task are processed by the client as a single unit. These are considered to be Teradata TPump task commands. The actual execution of the Teradata TPump task is deferred until all pertinent task commands have been considered and validated by the client program.