=================================
MACHINE SPECIFIC NOTES
FOR
HCL Informix Client-SDK 4.50.FC11 PRODUCT RELEASE
HCL Informix ODBC Driver Version 4.50.FC11
On Linux Power (little endian)
DATE: 19 Jun 2024
=================================
OS Information : Built on Red Hat Enterprise Linux ES release 7.4 (Maipo)
Certified on SUSE SLES 12.3 and 15.
Machine Specific Notes
======================
1. This product was built on Red Hat Enterprise Linux ES 7.4 (Maipo)
for 64-Bit Power Series Architecture little endian with Kernel version
4.10.0 and glibc 2.17 using the following compilers:
gcc/g++ 4.8.5 20150623
2. If you use the ODBC with shared libraries, you must make sure that the
ODBC libraries are made available at run time by including the ODBC
library directory ($INFORMIXDIR/lib/cli) in your LD_LIBRARY_PATH
environment variable value.
For example, a typical value for LD_LIBRARY_PATH in an Informix environment
with ODBC use would look like this:
(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
3. Thread-safe ODBC libraries are supported on this platform using POSIX
threads. Make sure that you set the THREADLIB environment variable to
"POSIX" before linking your ODBC program using the esql script.
4. Pluggable Authentication Module (PAM)
PAM functionality is supported on Linux for Power architecture 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 /lib/security and its parameters are listed in /etc/pam.d.
The pam.conf file is ignored on Linux, if the /etc/pam.d directory is
present.
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
addresss. 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 Linux 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.