The Teradata FastLoad example is a simple, straightforward exercise can be used to quickly create a job script and run Teradata FastLoad. The following information explains some of the more significant functional alternatives that Teradata FastLoad provides, and provides references to where they are described in greater detail.
Mainframe‑Attached Client Systems
The Teradata FastLoad example assumes UNIX or Windows OS is the operating system on a network‑attached client system.
To run the example using z/OS on a mainframe‑attached client system, use the standard z/OS JCL control statements (DD) to allocate and create the Teradata FastLoad data sets or files before invoking the utility.
For more information about invoking Teradata FastLoad on mainframe‑attached client systems, see “Invoking Teradata FastLoad” on page 33.
The Teradata FastLoad example shows a very simple Teradata FastLoad job, loading a very small amount of data into an empty table.
MultiLoad could have been used to perform the same task, but the job would have run much more slowly. Teradata FastLoad works only on empty tables. MultiLoad can be used to:
Input File Formats
The format of the input data source for the Teradata FastLoad example (insert.input) is UNFORMATTED, as specified by the SET RECORD command.
Teradata FastLoad also supports input data source files with the following formats:
For descriptions of all the supported input file formats, see “SET RECORD” on page 151.
In the Teradata FastLoad example, the utility reads the input data records directly from the specified source file (insert.input).
An alternative would be to write an INMOD routine that Teradata FastLoad could call to obtain input records.
The INMOD routine, for example, could:
In this case, use the optional INMOD name specification of the DEFINE command to identify the name of the INMOD routine.