Home
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Guide to SQL: Syntax
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.
Routine modifier
A routine modifier specifies characteristics of how a user-defined routine (UDR) behaves.
Modifier Descriptions
PARALLELIZABLE

SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
- Guide to SQL: Syntax
  - 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.
      - Adding or Modifying a Routine Modifier
        Use this segment in the ALTER FUNCTION, ALTER PROCEDURE, or ALTER ROUTINE statement to add or modify values for routine modifiers of a UDR.
      - Modifier Descriptions
        CLASS
        COSTFUNC (C)
        Use the COSTFUNC modifier to specify the cost of a UDR. The cost of the UDR is an estimate of the time required to execute it.
        HANDLESNULLS
        INTERNAL
        ITERATOR
        NEGATOR
        PARALLELIZABLE
        PERCALL_COST (C)
        Use the PERCALL_COST modifier to specify the approximate CPU usage cost that a UDR incurs each time it executes.
        SELCONST (C)
        Use the SELCONST modifier to specify the selectivity of a UDR. The selectivity of the UDR is an estimate of the fraction of the rows that the query will select.
        SELFUNC (C)
        Use the SELFUNC modifier with a C UDR to name a companion user-defined function, called a selectivity function, to the current UDR. The selectivity function provides selectivity information about the current UDR to the optimizer.
        STACK (C)
        VARIANT and NOT VARIANT
    - 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.
    - Specific Name
    - Statement Block
  - Built-In Routines
  - Appendixes
- Guide to SQL: Reference
  The Informix® Guide to SQL: Reference contains 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
  The Informix® Guide to SQL: Tutorial 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.

PARALLELIZABLE

Use the PARALLELIZABLE modifier to indicate that an external routine can be executed in parallel in the context of a parallelizable data query (PDQ).

By default, an external routine is non-parallelizable; that is, it executes in sequence.

If your UDR has a complex or smart large object data type as either a parameter or a returned value, you cannot use the PARALLELIZABLE modifier.

If you specify the PARALLELIZABLE modifier for an external routine that cannot be parallelizable, the database server returns a runtime error.

A C language UDR that calls only PDQ thread-safe DataBlade® API functions is parallelizable. These categories of DataBlade® API functions are PDQ thread safe:

Data handling
An exception in this category is that collection manipulation functions (mi_collection_*) are not PDQ thread safe.
Session, thread, and transaction management
Function execution
Memory management
Exception handling
Callbacks
Miscellaneous

For details of the DataBlade® API functions that are included in each category, see the Informix® DataBlade® API Function Reference.

If your C language UDR calls a function that is not included in one of these categories, it is not PDQ thread safe and is therefore not parallelizable.

To parallelize Java™ language UDR calls, the database server must have multiple instances of JVPs. UDRs written in the Java™ language and that open a JDBC connection are not parallelizable.