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™.
Improve UDR performance
Memory considerations
Virtual-memory cache for routines
The sysprocedures system catalog table

The sysprocedures system catalog table

When any session requires the use of an SPL routine for the first time, the database server reads the sysprocedures system catalog tables and stores the information in the buffer pool in shared memory. The database server uses this information in shared memory if it is present for subsequent sessions that invoke the UDR.

The database server keeps the sysprocedures system catalog information in the buffer pool on a most recently used basis.

The sysprocedures table includes the following information:

Name of routine
Compiled size (in bytes) of return values
Compiled size (in bytes) of p-code for the routine
Number of arguments
Data types of parameters
Type of routine (function or procedure)
Location of external routine
Virtual-processor class in which the routine executes