Shared-Object File:
 
      (1)                            (2)
|--+--------| C Shared-Object File |---------+------------------|
   |  (3)                               (4)  |
   '--------| Java Shared-Object File |------'
 

1. C only
2. See C Shared-Object File
3. Java only
4. See Java Shared-Object File

If the IFX_EXTEND_ROLE configuration parameter is set to 1 or to ON, only users to whom the DBSA has granted the built-in EXTEND role are authorized to use this segment.

The Database Server Administrator should include in the DB_LIBRARY_PATH configuration parameter settings every file system where the security policy authorizes DataBlade modules and UDRs to reside. Unless DB_LIBRARY_PATH is absent or has no setting, the database server cannot access a file that this segment specifies unless its pathname begins with a string that exactly matches one of the values of DB_LIBRARY_PATH.

For example, if "$INFORMIXDIR/extend" is one of the DB_LIBRARY_PATH values on a Linux system, then shared-object files can have pathnames within the $INFORMIXDIR/extend file system or its subdirectories. (This is also the file system where built-in DataBlade modules reside, and the default location where the DataBlade Developer's Kit creates user-defined DataBlade modules.)

The syntax by which you specify a shared-object filename depends on whether the external routine is written in the C language or in the Java language. Sections that follow describe each of these external languages.