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®.
Database access
Exceptions and eventsThis section describes exceptions and events, and explains how to handle them in DataBlade® API modules.
Database server exceptionsWhen the database server or a UDR raises a database server exception, the DataBlade® API invokes any callbacks that are registered for the exception.
Understanding database server exceptionsA database server exception is an unexpected condition that occurs within the database server.
Status variablesTo identify the particular cause of an exception, the database server sets the SQLSTATE and SQLCODE status variables. The SQLSTATE status variable holds a five-character code that is compliant with ANSI and X/Open standards. The SQLCODE status variable holds an integer value that is specific to HCL Informix®.
SQLCODE status valueEach SQLSTATE value also has an associated status code that is specific to HCL Informix®. The database server saves this status code in the SQLCODE status variable. The SQLCODE variable is an integer that indicates whether the SQL statement succeeded or failed.
Identify runtime errors with SQLCODE

Identify runtime errors with SQLCODE

When an SQL statement results in a runtime error, the database server sets SQLCODE to a negative value and raises an MI_Exception event with an MI_EXCEPTION exception level.

The number in SQLCODE identifies the particular HCL Informix® runtime error. The finderr or Error Messages utility lists error messages and describes corrective actions.

Tip: The database server sets SQLCODE to 100 when a SELECT or FETCH statement encounters NOT FOUND (or END OF DATA). However, the NOT FOUND condition does not cause a database server exception. Therefore, you do not use SQLCODE to detect this condition from within a callback of a DataBlade® API module. Instead, your DataBlade API module can check for the MI_NO_MORE_RESULTS return code from the mi_get_result() function.

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.