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®.
Create user-defined routines
Write a user-defined routineThis section outlines some implementation issues for C user-defined routines (UDRs). This section also describes the specific features and tasks of a C UDR.
Virtual processorsTo service multiple client-application SQL requests, the database server uses virtual processors (VPs). The database server breaks the SQL request into distinct tasks, based on the resource that the task requires. Different VP types, called virtual-processor classes (VP classes), service the different kinds of tasks.
Create a well-behaved routine
Define a user-defined VPYou define a new virtual-processor class in the onconfig file with the VPCLASS configuration parameter.
Define a nonyielding user-defined VP classTo create a nonyielding user-defined VP, include the noyield option of the VPCLASS configuration parameter. You can also use the num option to specify the number of VPs in the nonyielding user-defined VP class.

Define a nonyielding user-defined VP class

To create a nonyielding user-defined VP, include the noyield option of the VPCLASS configuration parameter. You can also use the num option to specify the number of VPs in the nonyielding user-defined VP class.

Tip: The noyield option is ignored for predefined virtual-processor classes such as CPU and AIO. For more information about the VPCLASS configuration parameter, see the .

The following code fragment defines the nonyielding user-defined VP class named nonyield_vp with two VPs in the class.

VPCLASS nonyield_vp, num=2, noyield               # Nonyielding VP class

At run time you can determine whether the VP on which a UDR is running is part of a nonyielding user-defined VP class with the mi_vpinfo_isnoyield() function. For more information, see Obtain VP-environment information.

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.