A standard input file is an input file that is user-defined as the SYSIN file. It executes automatically in batch mode when BTEQ is invoked. If a standard input file is not specified, the input stream must be entered interactively through a terminal or workstation keyboard.
Depending on system configuration, a standard input file can be specified either when BTEQ is invoked, or before logging on to a Teradata Database.
To specify an input file use one of the following methods:
| System Type | Specification |
|---|---|
| Mainframe-attached | Use either the BTEQ TDSBTEQ JCL procedure or a DD statement in a standard JCL file to specify the input file as the SYSIN file before invoking BTEQ. |
| Workstation-attached* | Use the < character to specify an input file when BTEQ is invoked. |
| *The use of the -c and -e command line options or the “charset_id” value in the clispb.dat file is highly recommended when a Unicode input file is used. Otherwise, BTEQ interprets the input file as Unicode and sets the session character set accordingly, as follows. BTEQ checks the input file for a UTF-16 or UTF-8 BOM and automatically changes the session character set to the appropriate Unicode encoding. The endianness (16-bit output) syntax of a UTF-16 BOM must match that of the machine BTEQ is running on. If a BOM-less UTF-16 input file is used, BTEQ validates the first character and automatically changes the session character set to UTF16. Note that BTEQ does not automatically change the session character set for a BOM-less UTF-8 input file. If none of the above apply, BTEQ detects the input file is not a Unicode file and defaults the session character set to ASCII. | |
For more information and examples of specifying a standard input file, see Using Scripts, Run Files, Macros, and Stored Procedures.