- Function object. The string that follows is the entry point name of the C or C++ procedure object.
- Specify a delimiter character, such as !. You must use the same delimiter throughout the string specification.
- Name the file on the server. Include files must have the same name specified in the include statement in the C source, without the extension.
- Enables symbolic debugging for the external procedure, which shows source code and displays variables by name. Without this option, external procedures can only be debugged at the machine instruction level. You should always specify this option for debugging purposes when external procedures are being tested. This option adds -g to the C compiler command line. See SET SESSION DEBUG FUNCTION and Teradata Vantage™ - SQL External Routine Programming , B035-1147 .
- The D option only applies only to C and C++ code, not to Java UDFs.
You should not use this option when installing debugged external procedures on production system because it increases the size of the external procedure library.
- The source or object code for the external procedure is stored on the server.
- The source or object code for the external procedure is stored on the client.
Location (path) and name of the source, include file, object, or library. Because packages and libraries must be preinstalled, you must use the server option (S). Path specifications can use forward slashes (/) or backward slashes (\) regardless of whether the function is being created on a Unix or Windows platform.
- Include file (.h).
- Library name for a nonstandard library files needed by the UDF.
- Object file.
- Package name. You cannot use the package option with any other options except F, the C function name option.
- Source file.
- No source file. Source files and include files are not stored in the function table. This option only affects how source code is processed in the creation of a new function and applies to all source code specified in the external string literal.