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_MSG() and DBDK_TRACE_ERROR() macrosWhen tracing is enabled, use the DBDK_TRACE_MSG() and DBDK_TRACE_ERROR() macros to write messages to the trace message file. The DBDK_TRACE_ERROR() macro also raises an error.

The DBDK_TRACE_MSG() and DBDK_TRACE_ERROR() macros

When tracing is enabled, use the DBDK_TRACE_MSG() and DBDK_TRACE_ERROR() macros to write messages to the trace message file. The DBDK_TRACE_ERROR() macro also raises an error.

If tracing is not enabled, no messages are written to the trace message file; DBDK_TRACE_ERROR() still raises an error.

The syntax for the DBDK_TRACE_MSG() and DBDK_TRACE_ERROR() macros is as follows:

DBDK_TRACE_MSG(caller, mesgNo, level);
DBDK_TRACE_ERROR(caller, mesgNo, level);

caller

The name of the C routine to which you are adding the macro.

mesgNo

The number for an error or trace message in the syserrors or systraceclasses system catalog. Use numbers for messages defined in the BladeSmith project or messages BladeManager installs with all DataBlade® modules.

See Define errors for instructions on creating error and trace messages with BladeSmith.

The standard error messages are listed in ids_dbdk_182.html#ids_dbdk_182.

level

An integer that determines the trace level for the message. If level is less than or equal to the tracing threshold, then the message is printed in the trace file. For example, the trace level for the DBDK_TRACE_ENTER() and DBDK_TRACE_EXIT() macros is 20.

See Set a trace output file and a trace threshold for more information.

For example, if you have a function called ExmAmortize() and a trace message number UE001 with a trace level of 20, use the following code fragment to add tracing to the ExmAmortize() function:

DBDK_TRACE_MSG("ExmAmortize", "UE001", 20);