Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
User-Defined Routines and Data Types Developer's GuideThe HCL OneDB™ User-Defined Routines and Data Types Developer's Guide describes how to define new data types and enable user-defined routines (UDRs) to extend HCL OneDB™.
Run a user-defined routine
Invoke a UDR in an SPL routine

Invoke a UDR in an SPL routine

You use the CALL statement only to invoke a UDR from within an SPL program. You can use CALL to invoke both user-defined functions and user-defined procedures, as follows:

When you invoke a user-defined function with the CALL statement, you must include a RETURNING clause and the name of the value or values that the function returns.
The following statement invokes the equal() function:
```
CALL equal (arg1, arg2) RETURNING result
```
You cannot use the CALL statement to invoke a user-defined function that contains an OUT parameter.
A RETURNING clause is never present when you invoke a user-defined procedure with the CALL statement because a procedure does not return a value.
The following CALL statement invokes the log_compare() procedure:
```
CALL log_compare (arg1, arg2)
```