Notes on Using SQL CALL Statements|CREATE PROCEDURE SQL - Notes on Using SQL CALL Statements - Parallel Transporter
Teradata® Parallel Transporter Application Programming Interface Programmer Guide - 17.20
- Product
- Parallel Transporter
- Release Number
- 17.20
- Published
- June 2022
- Language
- English (United States)
- Last Update
- 2022-10-11
- dita:mapPath
- fag1645201363032.ditamap
- dita:ditavalPath
- obe1474387269547.ditaval
- dita:id
- B035-2516
- Product Category
- Teradata Tools and Utilities
- When issuing the SQL CALL statements, always specify the full path for any necessary input or output file. In these statements infile.littleEndian, outfile.littleEndian, input.lod are examples of input and output files for which the full path should be specified.
- Read access is required for all input files and the directories in which they are located. On Linux, this requires giving read access to the others group.
- Write access is required for all output files and the directories where they will be located. On Linux, this requires giving write access to the others group.
- All examples using the Export driver require pre-existing data in the table from which data will be exported.
- See the input.exp input file for instructions on how to create the input.exp2 input file.