The following table describes the things to consider when using the RUN FILE command.
Topic | Usage Notes |
---|---|
Executing the RUN FILE Command | After Teradata MultiLoad executes the RUN FILE command, it reads additional commands from the specified source until a LOGOFF command or end of file condition is encountered, whichever occurs first. An end of file condition automatically causes Teradata MultiLoad to resume reading its commands and DML statements from the previously active source:
SYSIN/stdin remains the active input source after Teradata MultiLoad processes any user-provided invocation parameters.
|
Nested RUN Commands | The source specified by a RUN FILE command can have up to 16 levels of nested RUN commands. |
-i scriptencoding parameter | When the -i scriptencoding parameter is used, the specified encoding form and byte order apply to all the command files specified by the .RUN FILE command and any nested RUN FILE commands. |
Specifying the System Console/Standard Input Device | Use the asterisk character (*) as the fileid specification for the system console/standard input (stdin) device. The system console is the:
For more information about the keyboard and standard input devices, see File Requirements. |
z/OS fileid Usage Rules | If a DDNAME is specified, Teradata MultiLoad reads data records from the specified source. A DDNAME must obey the same construction rules as Teradata SQL column names except that:
The DDNAME must obey the applicable rules of the external system and may reference a sequential or VSAM data set. If the DDNAME represents a data source on magnetic tape, the tape may be either labeled or non-labeled, as supported by the operating system. |