In addition to the output data destination, FastExport accesses four different data sets/files or input/output devices. The following table lists Data Sets, Files and Devices for Teradata FastExport.
| Data Set/File or Device | Provides |
|---|---|
| Standard input | FastExport commands and Teradata SQL statements that make up a FastExport job |
| Standard output | Destination for FastExport output responses and messages |
| Standard error | Destination for FastExport errors |
| Configuration | Optional specification of FastExport utility default values |
When running FastExport in interactive mode, the terminal keyboard functions as the standard input device and the display screen is the standard output/error device. When running FastExport in batch mode, a data set or file name must be specified for each of these functions. The method of doing this varies, depending on the configuration of the client system:
- On network-attached client systems, use the standard redirection mechanism (< infilename and > outfilename), the recommended approach, to specify the FastExport files when invoking the utility. Teradata FastExport script files can also be piped to Teradata FastExport when invoking the utility.
- On mainframe-attached client systems, use standard z/OS JCL control statements (DD) to allocate and create the FastExport data sets or files before invoking the utility.On z/OS client systems, the export file should not be a member of a partitioned data set (PDS). If it is, and a Teradata Database or client system failure interrupts the FastExport job, the restart operation will fail.