Welcome
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 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 extensions
You 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.
Programmer's Guide
The HCL® Informix® DataBlade® API Programmer's Guide describes information about the , the C-language application programming interface (API) provided with HCL Informix.
Database access
Exceptions and events
This section describes exceptions and events, and explains how to handle them in modules.
Callback functions
To catch or handle an event, you create a C function called a callback function. In your module, you can register callback functions to handle recovery from events. The invokes a registered (and enabled) callback when the event associated with the callback occurs.
Write a callback function
Within the body of a callback function, you provide the code that handles a particular event or events. Only certain tasks are valid within a callback. When a callback function is invoked for an event, the passes information about the event to the callback.
Event information
When a callback function is invoked for a particular event, the passes an event-type structure as the third parameter of this function. This event-type structure contains information about the event that triggered the callback.
An error descriptor
The stores information about exceptions and errors in an error descriptor. An error descriptor is an MI_ERROR_DESC structure. It holds information for the MI_Exception and MI_Client_Library_Error event types.

HCL Informix® V15.0.0 documentation
Welcome to the documentation for HCL Informix® 15.0.0 and related client tools and products.
Product overview
HCL Informix® is a fast and scalable database server that manages traditional relational, object-relational, and dimensional databases. Its small footprint and self-managing capabilities are suited to embedded data-management solutions.
Installing
These topics describe how to install HCL Informix® database servers, client products, and modules.
Administering
In addition to administering the database server, you can tune performance, replicate data, and archive data.
Migrating and upgrading
You can upgrade to the 15.0.0 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
Embedding Informix®
When you embed HCL Informix®, you can use enterprise-class high-availability and high performance with embeddability features such as easy programmability, a small disk and memory footprint, and silent deployment.
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 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.
- Informix® extensions and modules
  These topics describe how to use built-in database extensions and separately installed modules.
- Creating extensions
  You 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.
  - Programmer's Guide
    The HCL® Informix® DataBlade® API Programmer's Guide describes information about the , the C-language application programming interface (API) provided with HCL Informix.
    - overview
    - Data manipulation
    - Database access
      - Connection handling
        This section describes how to initialize, establish, and close connections.
      - Execute SQL statements
        One basic task of a module is to send SQL statements to the database server for execution.
      - Execute user-defined routines
        This section provides information about how to call a user-defined routine (UDR).
      - Exceptions and events
        This section describes exceptions and events, and explains how to handle them in modules.
        event types
        For a module, an event is a communication from HCL Informix® software that indicates the existence of some predefined condition, usually the occurrence of an exception (warning or error). The represents an event as one of the enumerated values of the MI_EVENT_TYPE data type.
        Event-handling mechanisms
        An event-handling mechanism provides a way for one module to inform another module (or another part of the same module) that an event has occurred during execution of a function.
        Callback functions
        To catch or handle an event, you create a C function called a callback function. In your module, you can register callback functions to handle recovery from events. The invokes a registered (and enabled) callback when the event associated with the callback occurs.
        Declare a callback function
        To declare a callback function, you provide the MI_CALLBACK_STATUS return type, the optional MI_PROC_CALLBACK modifier, and the parameter declarations.
        Write a callback function
        Within the body of a callback function, you provide the code that handles a particular event or events. Only certain tasks are valid within a callback. When a callback function is invoked for an event, the passes information about the event to the callback.
        Restrictions on content
        Event information
        When a callback function is invoked for a particular event, the passes an event-type structure as the third parameter of this function. This event-type structure contains information about the event that triggered the callback.
        An error descriptor
        The stores information about exceptions and errors in an error descriptor. An error descriptor is an MI_ERROR_DESC structure. It holds information for the MI_Exception and MI_Client_Library_Error event types.
        Access an error descriptor
        Create a copy of an error descriptor
        The passes the error descriptor as an argument to the callback. Therefore, the allocates memory for the error descriptor when it invokes the callback and deallocates this memory when the callback exits. To preserve the error information for the calling routine, you can create a user copy of the error descriptor within the callback.
        A transition descriptor
        The transition descriptor, MI_TRANSITION_DESC, stores information about a transition in the processing state of the database server. It holds information for all state-transition events.
        Database server exceptions
        When the database server or a UDR raises a database server exception, the invokes any callbacks that are registered for the exception.
        State-transition events
        When the database server raises a state-transition event, the database server invokes any callbacks registered for the state transition. This section provides information about state-transition handling in modules, including an explanation of state-transition events and a description of how to handle a state-transition event in a C UDR and a client LIBMI application.
        Client LIBMI errors
        The throws the MI_Client_Library_Error event to indicate an error in the client LIBMI library.
      - XA-compliant external data sources
    - Create user-defined routines
    - Appendix
      This section contains additional reference information.
  - Function Reference
    The IBM® Informix® DataBlade® API Function Reference describes the functions and the subset of functions that the supports.
  - Developers Kit
    The Developers Kit (DBDK) guides contain information about the tools you can use to develop and package modules, which extend the functionality of HCL Informix® databases.
  - J/Foundation Developer's Guide
    The HCL® J/Foundation Developer's Guide describes how to write user-defined routines (UDRs) in the Java™ programming language for Informix®.
  - R-Tree Index User's Guide
    The HCL® Informix® R-Tree Index User's Guide describes the HCL Informix R-tree secondary access method and how to access and use its components.
  - User-Defined Routines and Data Types Developer's Guide
    The HCL® Informix® 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 Informix.
  - Virtual-Table Interface Guide
    The IBM® Informix® Virtual-Table Interface Programmer's Guide explains how to create a primary access method with the Virtual-Table Interface (VTI) so that users have a single SQL interface to HCL Informix tables and to data that does not conform to the storage scheme of HCL Informix.
  - Virtual-Index Interface Guide
    The IBM® Informix® Virtual-Index Interface Programmer's Guide explains how to create a secondary access method with the Virtual-Index Interface (VII) to extend the built-in indexing schemes of HCL Informix typically with a module.
Data warehousing
In addition to designing and implementing Informix® dimensional databases, you can use tools to create data warehouse applications and optimize your data warehouse queries.
Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
JSON compatibility
You can use the popular JSON-oriented query language created by MongoDB to interact with data stored in HCL Informix®.
Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Troubleshooting HCL Informix®
Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL Informix® database server environment.

An error descriptor

The stores information about exceptions and errors in an error descriptor. An error descriptor is an MI_ERROR_DESC structure. It holds information for the MI_Exception and MI_Client_Library_Error event types.

The following table summarizes the memory operations for an error descriptor.


Memory duration	Memory operation	Function name
Current® memory duration	Constructor	mi_error_desc_copy()
Current® memory duration	Destructor	mi_error_desc_destroy()

When an MI_Exception or MI_Client_Library_Error event occurs, the invokes the appropriate callback. To this callback, the passes an initialized error descriptor as the third callback argument. The error descriptor contains information about the MI_Exception or MI_Client_Library_Error event. Within the callback, use the accessor functions in Accessor functions for an error descriptor to obtain the error information from the error descriptor.