Informix ODBC Driver Version 4.50.FC11, Solaris Sparc 64bit

 
                      =================================
                            MACHINE SPECIFIC NOTES
                                    FOR
               HCL Informix Client-SDK 4.50.FC11 PRODUCT RELEASE
                    HCL Informix ODBC Driver Version 4.50.FC11
                            On Solaris Sparc 64bit
                               DATE: 19 Jun 2024
                      =================================
 
OS Information : Built on Solaris 11.3.

Machine Specific Notes
======================

1. This product was built on Solaris 11.3 using the following compilers
   from Oracle Solaris Studio 12.3:

       Sun C 5.12 SunOS_sparc December 2011
       Sun C++ 5.12 SunOS_sparc December 2011

   The product was built with the following 64-bit compiler flag:

       "-m64"

2. Setting the environment variable LD_LIBRARY_PATH ( or LD_LIBRARY_PATH_64)

   (for Bourne or Korn Shell)
       LD_LIBRARY_PATH=
            $INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql:$LD_LIBRARY_PATH
       export LD_LIBRARY_PATH

   (for C Shell)
       setenv LD_LIBRARY_PATH
          $INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql:$LD_LIBRARY_PATH

   If there are 64-bit shared object libraries (.so files)
   which you want the runtime linkers ld and ild to link with your
   C++ API applications, you must either add the directory paths for
   these libraries to LD_LIBRARY_PATH or LD_LIBRARY_PATH_64.
   Note that if you add them to LD_LIBRARY_PATH but not to
   LD_LIBRARY_PATH_64 and you define LD_LIBRARY_PATH_64, they will not
   be found as LD_LIBRARY_PATH is ignored when searching for 64-bit
   libraries if LD_LIBRARY_PATH_64 is set.
   You should either set LD_LIBRARY_PATH to all 32-bit and 64-bit
   paths required by your applications and not set LD_LIBRARY_PATH_64
   at all, or set LD_LIBRARY_PATH to only 32-bit paths and 
   LD_LIBRARY_PATH_64 to 64-bit paths.

   See the Solaris man pages for ld and ild for more information
   on the environment variables LD_LIBRARY_PATH and LD_LIBRARY_PATH_64.
   See also the Solaris Linker and Libraries Guide.
 
3. The thread safe ODBC libraries are supported on this platform using
   Native Solaris threads.

4. Migration of existing ODBC applications from 32 bit versions of
   HCL Informix Client-SDK to HCL Informix Client-SDK 4.50.FC11.

   ALL the existing 32-bit ODBC applications WILL need to be recompiled
   to make them work with HCL Informix Client-SDK 4.50.FC11.
   Before recompiling these existing applications, changes will be
   required to be made to the application sources, if above mentioned ODBC
   API and/or ODBC Datatypes are being used. Also applications   should
   not have any "long" and/or "unsigned long" C-Data types declared
   which is being passed to any Informix ODBC APIs. Informix recommends
   use of SQLINTEGER/SQLUINTEGER, SDWORD/UDWORD standard ODBC types as
   defined in Informix header files.

5. Pluggable Authentication Module (PAM)

   PAM functionality is supported on Solaris operating systems. The PAM is 
   dependent on the libpam.so library supplied by the Operating System vendor.

   Use of PAM can be enabled or disabled by the system administrator. By 
   default, IBM IDS will use the traditional authentication mechanism in 
   order to avoid widespread changes required by the users.

   The PAM service identifies the PAM module. This PAM module typically
   resides in /usr/lib/security and its parameters are listed in
   /etc/pam.conf.

6. IPv6 Support

   IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
   Addresses) as well as IPv4 (32 Bit Addresses).

   In order for the machine name specified in the SQLHOSTS file to resolve to
   the correct IP address, the name services files on the operating system
   should be correctly configured. If the machine has IPv6 address configured
   and the listener thread is bound to an IPv6 address, then the name
   resolution files /etc/nsswitch.conf should be configured to fetch IPv6
   address. Also use the appropriate /etc/hosts setting if local machine
   settings are used.

   For compatibility with older IBM Informix client and server products,
   assign the same hostname with both an IPv4 address and an IPv6 address.
   If the listener needs to be bound to an IPv4 address and the name services
   resolve the name in the order of the IPv6 address followed by IPv4 address,
   then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
   file. Client applications should also use the same setting.

Check the following web site for the latest Solaris system requirements:

   http://www-01.ibm.com/support/docview.wss?rs=630&uid=swg27016673


(C) Copyright IBM Corp. 2002, 2017
(C) Copyright HCL Technologies Ltd. 2017, 2024. All Rights Reserved.