Home
Extending Informix®Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix® includes many built-in extensions that are fully integrated in the database server. Informix® 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 Informix®.
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 Informix® databases.
DataBlade® API Programmer's GuideThe Informix® DataBlade® API Programmer's Guide describes information about the DataBlade® API, the C-language application programming interface (API) provided with HCL Informix®.
Create user-defined routines
Develop a user-defined routineA C user-defined routine (UDR) is a UDR that is written in the C language and uses the server-side implementation of the DataBlade® API to communicate with the database server. C UDRs (functions and procedures) are implemented as C-language functions. DataBlade® modules often include C UDRs that are made available for use by registering them in the database.
Debug a UDRBecause a UDR runs as part of the database server process, the routine must not do anything that might negatively affect the running of the database server, such as exiting. This section provides information about how to use a C debugger to attach to a virtual processor, handle the debugging session of a C UDR, and use DataBlade® API tracing.
TracingA tracepoint is a point within the code that can send special information about the current executing state of the UDR.

Tracing

A tracepoint is a point within the code that can send special information about the current executing state of the UDR.

Each tracepoint has the following parts:

A trace class groups related tracepoints together so that they can be turned on and off at the same time.
A trace message is the text that the database server sends to the tracing-output file.
A tracepoint threshold determines when the tracepoint executes; if a tracepoint threshold is not greater than the current trace level, the DataBlade® API writes the associated trace message to the trace output file.

The DataBlade API tracing support is available only in C UDRs. Do not use this feature within client LIBMI applications.

The mitrace.h header file defines the functions and data type structures of the tracing interface. The mi.h header file automatically includes the mitrace.h header file. You must include either mi.h or mitrace.h in any C UDR that uses a DataBlade API tracing function.

The DataBlade API provides the following tracing support.


Time of use	Tracing support
At UDR-development time	Adds tracepoints in the C UDR with associated trace-level thresholds
At UDR run time	Turns on different trace classes at specified trace levels

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.