RUN
Purpose
Processes the Teradata SQL requests and BTEQ commands from the specified run file.
Syntax
where:
Syntax Element |
Specification |
filename |
The name of the file that contains the BTEQ commands and SQL requests on workstation-attached systems. If the name of the file includes a comma, semicolon, or blank space character, enclose the entire file name in either single or double quotation marks. Additionally, any time text follows a file name, that file name must be enclosed in quotation marks. File names are case sensitive on systems running on a UNIX system, and case-insensitive on systems running under Windows or TSO. For mainframe-attached systems, this is the name of the z/OS JCL DD statement that defines the file from which BTEQ commands are read. An ALLOCATE statement must be used for TSO. |
SKIP = n |
The number of lines skipped from the beginning of a data set or file before reading BTEQ commands. The valid range of numbers is 0 to 2147483647. |
Usage Notes
BTEQ supports all QSAM-compatible record formats. The maximum acceptable line length is 254 characters.
If specifying a RUN command within a run file, BTEQ switches and begins reading from the new file; BTEQ does not return to the previous file.
Files created with a RUN command can be chained, but not nested. If a run file contains a RUN command to run itself, BTEQ generates an out-of-memory message after several iterations. Always avoid such a loop.
Note: For information on I/O errors and abends, refer to “I/O Errors and Abends” on page 95.
After exhausting the run file, BTEQ resumes reading commands and requests from the standard input stream.
The RUN command cannot be used in a Teradata SQL macro.
For workstation-attached systems, a BOM is optional at the beginning of a UTF-8 or UTF-16 RUN file when a Unicode I/O encoding is being used. Also, when BTEQ is started with the -m command line option, stdio is based on the system locale. Therefore, the RUN file must contain locale-specific characters (instead of UTF-8 or UTF-16 encoded characters) and cannot contain a BOM.
For mainframe-attached systems, a RUN file must be encoded in EBCDIC, even for Unicode sessions.
Example
To read commands from the file POSTING, type:
.RUN FILE=POSTING