The introduction to the mandatory external method body reference clause.
- EXTERNAL only.
- EXTERNAL NAME plus an external method name and, optionally, a Parameter Style specification.
The entry point for the method object. This name must be unique within the SYSUDTLIB database.
Case is significant and must match the C or C++ method name.
A string that specifies the source and object components needed to build the method.
Depending on the initial code in the sequence, the string specifies either the C/C++ object name for the method or an encoded name or path for the components needed to create the method.
The following list briefly documents the path specifications for the external method. The character ¡ represents an arbitrary user-defined delimiter.
You must use the same delimiter throughout the string specification.
- Method object
For more information about these file types, see SQL Data Definition Language - Detailed Topics, B035-1184.
The following codes specify component locations.
- The string that follows is the entry point name of the C or C++ method object.
- Enables symbolic debugging for the UDM, which shows source code and displays variables by name. Without this option, UDMs can only be debugged at the machine instruction level. You should always specify this option for debugging purposes when UDMs are being tested. This option adds -g to the C compiler command line. See SET SESSION DEBUG FUNCTION and the appendix on "C/C++ Command-line Debugging for UDFs" in SQL External Routine Programming, B035-1147.
- The D option only applies only to C and C++ code.
- You should not use this option when installing debugged UDMs on production system because it increases the size of the UDM library.
- The source or object code is stored on the client and the string that follows is the path to its location.
- The source or object code is stored on the server and the string that follows is the path to its location.