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.
DataBlade® Developers KitThe DataBlade® Developers Kit (DBDK) guides contain information about the tools you can use to develop and package DataBlade® modules, which extend the functionality of HCL OneDB™ databases.
DataBlade® Developers Kit User's GuideThe HCL OneDB™ DataBlade® Developers Kit Users Guide describes how to use OneDB® DataBlade® Developers Kit (DBDK) tools to develop and package DataBlade® modules.
Programming DataBlade® module routines in CThis section contains information to help you edit and compile C language source code generated by DataBlade®.
Generated code
Tracing and error handlingBladeSmith adds tracing and error handling code throughout the generated source code if the tracing option is set to True when you generate source code in BladeSmith.
Add tracing and error handlingTo add tracing and error handling to the generated source code, edit the generated source code file and insert DBDK_TRACE macro calls.
The DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macrosIf you have tracing enabled and the trace threshold set to 20 or above, the DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macros write messages to the trace file when the called routine is entered and exited. BladeSmith automatically adds these macros to generated code for every routine.

The DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macros

If you have tracing enabled and the trace threshold set to 20 or above, the DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macros write messages to the trace file when the called routine is entered and exited. BladeSmith automatically adds these macros to generated code for every routine.

The syntax for the DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macros is as follows:

DBDK_TRACE_ENTER(caller);
DBDK_TRACE_EXIT(caller);

caller: The parameter that specifies the name of the C routine to which you are adding the macro.

For example, if you have a routine called ExmAmortize(), the following code fragment sends a message to the message file when the ExmAmortize() routine is entered:

DBDK_TRACE_ENTER("ExmAmortize");