IBM Mainframe Client‑Based Systems
Start Teradata TPump with a RUN FILE command, with optional invocation parameters, such as JCL PARM. These are interpreted as a string of Teradata TPump support environment commands, separated by, and ending with, semicolons.
After invocation, the first two commands executed must be LOGON and LOGTABLE. These commands are required and are permitted only once. Either can be supplied in the command string invoking Teradata TPump, and the other (or both) can appear in the INPUT file, or in a file called with the RUN FILE command. No commands can precede the LOGON, LOGTABLE, or RUN FILE commands.
If a RUN FILE command is not used to specify an initial source of commands and Teradata SQL statements, Teradata TPump defaults to the conventional source of control input, such as SYSIN.
If a RUN FILE command is found in the parameter (PARM) input, the input source it identifies is used prior to SYSIN. Whether the input source is specified by RUN FILE, or by SYSIN, processing continues until a LOGOFF command, the end of control input, or a terminating error is encountered, whichever occurs first. If all input is exhausted without encountering a LOGOFF command, or if the program terminates because of an error, Teradata TPump automatically performs the LOGOFF function.
The LOGON command establishes a Teradata SQL session that Teradata TPump uses for processing. The LOGTABLE command specifies a table to be used as the restart log in the event of failure. This table is placed in the default database unless otherwise specified.
CREATE TABLE, INSERT, UPDATE, and SELECT rights must be on the database containing the restart log table.
Preparatory statements, which are processed by the Teradata SQL‑processing function of Teradata TPump, must be executed before beginning a Teradata TPump task. It is here that any desired DATABASE statement and any desired CREATE TABLE statements are specified. At this point, a BEGIN LOAD command initiates a Teradata TPump task.