I/O in UDFs | SQL External Routine Programming | Teradata Vantage - I/O - Advanced SQL Engine - Teradata Database

SQL External Routine Programming

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
qwr1571437338192.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1147
lifecycle
previous
Product Category
Teradata Vantage™

The following rules apply to I/O.

IF the UDF … THEN the function …
runs in nonprotected execution mode cannot do any I/O, including standard I/O and network I/O.
specifies the EXTERNAL SECURITY clause in the CREATE FUNCTION or REPLACE FUNCTION statement can do I/O or otherwise interface with the operating system such that the operating system retains resources such as file handles or object handles.

The function executes as a separate process under the authorization of a specific native operating system user established by a CREATE AUTHORIZATION or REPLACE AUTHORIZATION statement.

The function must release opened resources (close handles) before it completes. Table functions must release opened resources before completing the end phase. All other types of functions must release opened resources before each instance of the function terminates.

runs in protected execution mode can do I/O or otherwise interface with the operating system such that the operating system retains resources such as file handles or object handles.

The function executes as a separate process under the authorization of the 'tdatuser' operating system user.

The function must release opened resources (close handles) before it completes. Table functions must release opened resources before completing the end phase. All other types of functions must release opened resources before each instance of the function terminates.

For more information on protected execution mode, see Protected Mode Function Execution.