code_specification - Advanced SQL Engine - Teradata Database

Single character code. Depending on the initial code in the sequence, the string specifies either the external function object name for the UDF or an encoded name or path for the components needed to create the external function.

F

Function object. The string that follows is the entry point name of the C or C++ external function object.

F!function_entry_point_name

D

Enables symbolic debugging for the UDF, which shows source code and displays variables by name. Without this option, UDFs can only be debugged at the machine instruction level. You should always specify this option for debugging purposes when UDFs are being tested. This option adds -g to the C compiler command line. See SET SESSION DEBUG FUNCTION and "C/C++ Command-line Debugging for UDFs" in Teradata Vantage™ - SQL External Routine Programming , B035-1147 .

The D option applies only to C and C++ code, not to Java UDFs.

You should not use this option when installing debugged UDFs on production system because this option increases the size of the UDF library.

S

Server. The source or object code for the external function is stored on the server.

C

Client. The source or object code for the external function is stored on the client.