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® API Function ReferenceThe HCL OneDB™ DataBlade® API Function Reference describes the DataBlade® API functions and the subset of functions that the DataBlade® API supports.
Function descriptionsThis section gives comprehensive reference information about the functions that are valid within DataBlade® API modules. It lists the function descriptions in alphabetical order, with syntax, usage information, and return values for the functions.
The mi_tracelevel_set() functionThe mi_tracelevel_set() function sets the trace level for specified trace classes.

The mi_tracelevel_set() function

The mi_tracelevel_set() function sets the trace level for specified trace classes.

Syntax

mi_integer mi_tracelevel_set(set_commands)
   const mi_string *set_commands;

set_commands: A list of value pairs that specify trace class names and integer trace levels. A space separates each class-name and trace-level pair from the next pair.


Valid in client LIBMI application?	Valid in user-defined routine?
No	Yes

Usage

The mi_tracelevel_set() function sets the tracing levels for the trace classes that you specify in the set_commands argument. This argument specifies trace classes and their associated trace levels in the following format:

traceclass_name traceclass_level

The following example sets the current trace level of trace class funcEntry to 50 and the level for trace class outData to 35:

mi_integer ret;
...
ret = mi_tracelevel_set("funcEntry 50 outData 35");

Important: A trace-class name must be defined in the systraceclasses system catalog table before you run mi_tracelevel_set().

By default, tracing is off; that is, the current trace level is set to zero for all trace classes. Any nonzero value for a trace level turns tracing on for the specified trace class. A trace level can be any integer from zero to the maximum long integer value for the development platform.

If the trace level for the funcEntry trace class was currently 50, the following tracepoint would execute because the value (10) in the argument to DPRINTF is not greater than the current level (50) of funcEntry:

DPRINTF("funcEntry", 10,
   ("Entering compute_output with inStr = %s", inStr));

The trace message from this DPRINTF call would be written to the current trace-output file. For information about how to set the trace-output file, see the description of the mi_tracefile_set() function.

Return values

MI_OK: The function was successful.
MI_ERROR: The function was not successful.