Welcome
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Guide to SQL: Syntax
The Informix® Guide to SQL: Syntax describes the syntax of the statements, data types, expressions, operators, and built-in functions of the Informix dialect of the SQL language.
Other syntax segments
These topics describe syntax segments, which are language elements, such as database object names or optimizer directives, that appear as a subdiagram reference in the syntax diagrams of some SQL or SPL statements.
Shared-Object Filename
Use a shared-object filename to specify a pathname to an executable object file when you register or alter an external routine.
Java™ Shared-Object File
To specify the name of a Java™ shared-object file, specify the name of the static Java method to which the UDR corresponds and the location of the Java binary that defines the method.

HCL Informix® V14.10 documentation
Welcome to the documentation for HCL Informix® 14.10 and related client tools and products. The current fix pack level of Informix is 14.10.xC13.
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 DataBlade® 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 14.10 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 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.
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.
- Guide to SQL: Syntax
  The Informix® Guide to SQL: Syntax describes the syntax of the statements, data types, expressions, operators, and built-in functions of the Informix dialect of the SQL language.
  - Overview of SQL syntax
    These topics provide an overview about how to use the SQL statements, SPL statements, and syntax segments.
  - SQL statements
    This chapter describes the syntax and semantics of SQL statements that are recognized by Informix®.
  - SPL statements
    These topics describe Stored Procedure Language (SPL) statements, which you use to write SPL routines. You can store these routines in the database as user-defined routines (UDRs).
  - Data types and expressions
    These topics describe the data types and expressions that Informix®supports.
  - Other syntax segments
    These topics describe syntax segments, which are language elements, such as database object names or optimizer directives, that appear as a subdiagram reference in the syntax diagrams of some SQL or SPL statements.
    - Arguments
    - Collection-Derived Table
      A collection-derived table is a virtual table in which the values in the rows of the table are equivalent to elements of a collection. Use this segment where you see a reference to Collection-Derived Table in a syntax diagram. This syntax is an extension to the ANSI/ISO standard for SQL.
    - Database Name
    - Database Object Name
    - External Routine Reference
      Include the External Routine Reference clause when you write an external routine. This option is not available for SPL routines.
    - Identifier
      An identifier specifies the unqualified name of a database object, such as an access method, aggregate, alias, blobspace, cast, column, constraint, correlation, data type, index, operator class, partition, procedure, table, trigger, sequence, synonym, or view. Use the Identifier segment whenever you see a reference to an identifier in a syntax diagram.
    - Jar Name
      Use the Jar Name segment to specify the name of a jar ID. Use this segment whenever you see a reference to Jar Name in a syntax diagram.
    - Optimizer Directives
      The Optimizer Directives segment specifies keywords that you can use to partially or fully specify the query plan of the optimizer. Use this segment whenever you see a reference to Optimizer Directives in a syntax diagram.
    - Owner name
      The owner name specifies the owner of a database object. Use this segment whenever you see a reference to Owner Name in a syntax diagram.
    - Purpose Options
    - Return Clause
    - Routine modifier
      A routine modifier specifies characteristics of how a user-defined routine (UDR) behaves.
    - Routine Parameter List
    - Shared-Object Filename
      Use a shared-object filename to specify a pathname to an executable object file when you register or alter an external routine.
      - C Shared-Object File
        To specify the location of a C shared-object file, you can specify the path to the dynamically-loaded executable file within a quoted pathname or as a variable.
      - Java™ Shared-Object File
        To specify the name of a Java™ shared-object file, specify the name of the static Java method to which the UDR corresponds and the location of the Java binary that defines the method.
    - Specific Name
    - Statement Block
  - Built-In Routines
  - Appendixes
- Guide to SQL: Reference
  These topics contain the reference information for the system catalog tables, data types, and environment variables of the HCL Informix® dialect of the SQL language, as implemented in HCL Informix. These topics also include information about the stores_demo, sales_demo, and superstore_demo databases that are included with HCL Informix.
- Guide to SQL: Tutorial
  This publication shows how to use basic and advanced structured query language (SQL) to access and manipulate the data in your databases. It discusses the data manipulation language (DML) statements as well as triggers and stored procedure language (SPL) routines, which DML statements often use.
Troubleshooting HCL Informix®
Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL Informix® database server environment.
Informix PDF guides

Java™ Shared-Object File

To specify the name of a Java™ shared-object file, specify the name of the static Java™ method to which the UDR corresponds and the location of the Java™ binary that defines the method.

Java™ Shared-Object File

Notes:

¹ See Jar Name


Element	Description	Restrictions	Syntax
class_id	Java™ class whose method implements the UDR	Class must exist in the .jar file that Jar Name identifies	Must conform to rules for Java™ identifiers
java_type	Java™ data type for a parameter in the Java-method signature	Must be defined in a JDBC class or by an SQL-to-Java mapping	Must conform to rules for Java™ identifiers
method_id	Name of the Java™ method that implements the UDR	Must exist in the Java™ class that java_class_name specifies	Must conform to rules for Java™ identifiers
package_id	Name of package that contains the Java™ class	Must exist	Must conform to rules for Java™ identifiers
quote	Single ( ' ) or double ( '' ) quotation mark delimiters	Opening and closing quotation marks must match	Literal symbol ( ' or '' ) entered at the keyboard

Before you can create a UDR written in the Java™ language, you must assign a jar identifier to the external jar file with the sqlj.install_jar procedure. (For more information, see sqlj.install_jar.) You can include the Java™ signature of the method that implements the UDR in the shared-object filename.

If you do not specify the Java™ signature, the routine manager determines the implicit Java™ signature from the SQL signature in the CREATE FUNCTION or CREATE PROCEDURE statement.
It maps SQL data types to the corresponding Java™ data types with the JDBC and SQL-to-Java mappings. For information on mapping user-defined data types to Java™ data types, see sqlj.setUDTextName.
If you do specify the Java™ signature, the routine manager uses this explicit Java™ signature as the name of the Java™ method to use.

For example, if the Java™ method explosiveReaction( ) implements the Java™ UDR sql_explosive_reaction( ) as discussed in sqlj.install_jar, its shared-object filename could be:

course_jar:Chemistry.explosiveReaction

The preceding shared-object filename provides an implicit Java™ signature. The following shared-object filename is the equivalent with an explicit Java™ signature:

course_jar:Chemistry.explosiveReaction(int)