Home
Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
ESQL/C Guide
The Informix® ESQL/C Programmer's Manual explains how to use Informix ESQL/C, the Informix implementation of Embedded Structured Query Language (SQL) for C (ESQL/C), to create client applications with database-management capabilities.
Database server communication
Exception handling
Exception handling with SQLSTATE
Check for exceptions with SQLSTATE
Runtime errors in SQLSTATE

Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
- Change Data Capture API Programmer's Guide
  The Informix® Change Data Capture API Programmer's Guide describes how to program applications to process changed data from HCL Informix databases using the Informix Change Data Capture API.
- Embedded SQLJ for HCL Informix®
  The Informix® Embedded SQLJ User's Guide contains information about using Informix Embedded SQLJ.
- ESQL/C Guide
  The Informix® ESQL/C Programmer's Manual explains how to use Informix ESQL/C, the Informix implementation of Embedded Structured Query Language (SQL) for C (ESQL/C), to create client applications with database-management capabilities.
  - What is Informix® ESQL/C?
  - Database server communication
    - Exception handling
      - Obtain diagnostic information after an SQL statement
      - Exception handling with SQLSTATE
        The GET DIAGNOSTICS statement
        The SQLSTATE variable
        The SQLSTATE variable is a five-character string that the database server sets after it executes each SQL statement.
        Check for exceptions with SQLSTATE
        Determining the cause of an exception in SQLSTATE
        To determine the cause of an exception in SQLSTATE, use the GET DIAGNOSTICS statement.
        Success in SQLSTATE
        NOT FOUND in SQLSTATE
        Warnings in SQLSTATE
        Runtime errors in SQLSTATE
        GET DIAGNOSTICS failure
        If the GET Diagnostics statement fails, SQLState contains a value of ix001. No other failure returns this value. The sqlcode indicates the specific error that caused the failure.
        Multiple exceptions
      - Exception handling with the sqlca structure
        An alternative way to obtain diagnostic information is through the SQL Communications Area. When an SQL statement executes, the database server automatically returns information about the success or failure of the statement in a C structure that is called sqlca.
      - Choose an exception-handling strategy
      - Library functions for retrieving error messages
      - A program that uses exception handling
    - Working with the database server
      These topics explain how the Informix® ESQL/C program can interact with a database server.
    - Informix® libraries
      These topics describe how to link the static, shared, and thread-safe HCL Informix® general libraries with your Informix ESQL/C application.
  - Dynamic SQL
  - Appendixes
    This section contains additional reference information.
- GLS User's Guide
  The Informix® GLS User's Guide describes the Global Language Support (GLS) feature available in Informix products.
- API
  The Informix® GLS API Programmer's Guide describes the global language support (GLS) application programming interface (API) available in Informix ESQL/C and HCL Informix DataBlade® modules.
- Informix® Object Interface for C++ Guide
  The Informix® Object Interface for C++ Programmer's Guide describes how to develop HCL Informix client applications by using the object-oriented C++ programming language.
- Informix® ODBC Driver Guide
  The Informix® ODBC Driver Programmer's Manual serves as a user guide and reference for Informix ODBC Driver, which is the Informix implementation of the Microsoft™ Open Database Connectivity (ODBC) interface, Version 3.0.
- .NET provider options
  The Data Server Provider for .NET DB2® provider option is the preferred Informix® provider for developing new applications.
- Informix® JDBC Driver Guide
  The Informix® JDBC Driver Programmer's Guide describes how to install, load, and use Informix JDBC Driver to connect to the Informix database from within a Java™ application or applet.
- Informix International Language Supplement (ILS) User Guide
  These topics include information about the translated user interface files for Informix® UNIX™ products, locales, and code set conversion tables
- Informix® OLE DB Provider Guide
  The Informix® OLE DB Provider Programmer's Guide describes the software requirements for using Informix OLE DB Provider, show how to install and configure the provider for your use, and explain how to use Informix OLE DB Provider to enable client applications, such as ActiveX Data Object (ADO) applications and web pages, to access data on the Informix server.

Runtime errors in SQLSTATE

When an SQL statement results in a runtime error, the database server stores a value in SQLSTATE whose class code is greater than "02". The actual class and subclass codes identify the particular error. Class and subclass codes for SQLSTATE lists the class and subclass codes for SQLSTATE. To retrieve the error message text, use the MESSAGE_TEXT field of the GET DIAGNOSTICS statement. The CLASS_ORIGIN and SUBCLASS_ORIGIN exception fields have a value of "ISO 9075" to indicate the source of the error.

If the SQL statement generates an error that the ANSI or X/Open standards do not support, SQLSTATE might contain either of the following values:

An SQLSTATE value of "IX000" indicates an error that is specific to HCL Informix®.
The SQLCODE variable contains the error code, and the MESSAGE_TEXT field contains the error message text and any ISAM message text. The CLASS_ORIGIN and SUBCLASS_ORIGIN exception fields have a value of "IX000" to indicate the source of the error.
An SQLSTATE value of "U0001" indicates a user-defined error message from a user-defined routine.
The MESSAGE_TEXT field contains the error message text. The CLASS_ORIGIN and SUBCLASS_ORIGIN exception fields have a value of "U0001" to indicate the source of the error.