=================================
MACHINE SPECIFIC NOTES
FOR
HCL Informix-Client SDK 4.10.FC10 PRODUCT RELEASE
HCL Informix ODBC Driver Version 4.10.FC10
ON SOLARIS x86 64bit
DATE: 23 Oct 2017
=================================
OS Information : Built on Solaris 10 update 8 on x86 64-Bit.
Certified on Solaris 11.
Machine Specific Notes
======================
1. This product was built and tested on Solaris 10 for Intel using the
following compilers from Oracle Solaris Studio 12.2:
Sun C 5.11 SunOS_i386 2010/08/13
Sun C++ 5.11 SunOS_i386 2010/08/13
The product was built with the following 64-bit compiler flag:
"-m64"
2. For shared library support, environment variable LD_LIBRARY_PATH
needs to be set to include the $INFORMIXDIR/lib/cli directories
where IBM INFORMIX ODBC shared libraries are installed.
(for C Shell)
setenv LD_LIBRARY_PATH $INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:
$INFORMIXDIR/lib/esql:$LD_LIBRARY_PATH
(for Bourne or Korn Shell)
LD_LIBRARY_PATH=$INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql:
$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
3. The thread safe IBM Informix ODBC libraries are supported on this
platform using Native Solaris threads.
4. 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/amd64 and its parameters are listed in
/etc/pam.conf.
5. 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. All Rights Reserved.