IBM Communications Server v6.4.0 for Linux on x86_64 INSTALLATION AND RELEASE NOTES 5724-I33 * © Copyright International Business Machines Corp. 2002, 2009 * All Rights Reserved * Licensed Material - Property of IBM * * US Government Users Restricted Rights - Use, duplication or * disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Table of Contents ----------------- 0. Third-party license terms and conditions, notices, and information 1. About this release 1.1 New in this release 1.2 Product fix history 1.3 Product compatibility 1.4 Viewing the Documentation 2. Installation information 2.1 Hardware requirements 2.2 Software requirements 2.2.1 Linux operating system version 2.2.2 Linux Streams (LiS) 2.19.0 plus patch 2.2.3 OpenMOTIF 2.2.4 Java 2.2.5 SSL 2.2.6 WebSphere Application Server 2.3 Installation process 2.3.1 Installing the 6.4.0 base 3. Uninstallation information 4. Known limitations and problems 4.1 Connectivity Options 4.2 TN3270 Server 4.3 Using certain applications and TPs 4.4 Mixing CS Linux levels on servers in a domain 4.5 NOF applications may have to be recompiled 5. Documentation updates 6. Notices and trademarks 6.1 Notices 6.2 Trademarks 0. Third-party license terms and conditions, notices, and information ---------------------------------------------------------------------- The relevant terms and conditions, notices and other information are provided in the "LICENSE.TXT" file in the 'drivers' subdirectory on the installation media for this product. Please note that any non-English version of the information in this is unofficial and is provided to you for your convenience only. The English version of the file is the official version. 1. About this release ---------------------- Communications Server for Linux provides SNA connectivity for 32-bit Intel based Linux systems, allowing it to connect to IBM z/OS Communications Server and other SNA implementations that support Enterprise Extender and 802.2 connections. The Remote API Clients which work best with the Communications Server for Linux V6.4.0 servers are the 6.4.0 clients. The Communications Server for Linux is backwards compatible with Remote API clients V6.3.1, 6.3.0. 1.1 New in this release ------------------------ - SLES 11 support - Enterprise Extender, HPR/IP, enhancements for Progressive ARB - Path Switch Delay for RTP connections See the "WhatsNew6400.txt" file in the root of the CD for more details. 1.2 Product fix history ------------------------ This release contains all the fixes for the Communications Server for Linux v6.4.0 product. Please check the web sites: http://www.ibm.com/software/network/commserver/linux http://www.ibm.com/software/network/commserver/support for the latest information about this product. You can use the public newsgroup: news://news.software.ibm.com/ibm.software.commserver.linux for informal Question & Answer support. 1.3 Product compatibility -------------------------- If you are using EE (HPR/IP) connections to z/OS v1r5, you should have the fix for z/OS APAR OA06668 applied to the z/OS system. If you are using EE (HPR/IP) Connection Networks with z/OS v1r7, v1r8, or v1r9 you should have the fix for z/OS APAR OA21948 applied to the z/OS system. If you are using EE (HPR/IP) to z/OS v1r8, v1r9 or v1r10, you should have the fix for z/OS APAR OA26490 applied to the z/OS system. You can find the PTF level for this APAR in: UA44023 - PTF for R1A0 (CSV1R10) UA44024 - PTF for R180 (CSV1R8) UA44025 - PTF for R190 (CSV1R9) 1.4 Viewing the Documentation ------------------------------ The Communications Server for Linux documentation is available on the QuickStart CD in the 'DOCS' subdirectory in PDF format. The publication names and numbers map to the PDF file names as shown below: Publication name Book number PDF filename ----------------------------------- ------------ ------------ Quick Beginnings GC31-6768-03 czx00103.pdf Quick Beginnings on System z GC31-6769-03 czx00203.pdf Administration Command Reference SC31-6770-03 czx00303.pdf Administration Guide SC31-6771-03 czx00403.pdf APPC Application Suite User's Guide SC23-8595-00 czx40500.pdf APPC Programmer's Guide SC23-8592-00 czx40600.pdf CPI-C Programmer's Guide SC23-8591-00 czx40700.pdf CSV Programmer's Guide SC23-8589-00 czx40800.pdf LUA Programmer's Guide SC23-8590-00 czx40900.pdf MS Programmer's Guide SC23-8596-00 czx41100.pdf NOF Programmer's Guide SC31-6778-03 czx01203.pdf Diagnostics Guide GC31-6779-03 czx01303.pdf Glossary GC31-6780-01 czx01401.pdf For Adobe Acrobat users on Windows, there is a zip file in the DOCS subdirectory which contains the indices needed to enable cross-manual searching. To install this index: - copy the zip file to a Windows PC and unzip it - from within Adobe Acrobat: Select Edit --> Search --> Select Indexes Within the index selection, add the books.pdx file. To perform a search: - Select Edit -->Search -->Query. - Select the index you want to search, in this case, Communications Server for Linux books. OR -- insert the term for which you want to search the library. Search results will be across all the books in the library. The Communications Server for Linux documentation is also available on the Internet at: http://www.ibm.com/software/network/commserver/library 2. Installation information ---------------------------- The Communications Server for Linux product is packaged as a CD-ROM containing this README file, several RPMs, the install shell scripts, and licensing tool. This file has details for the server component of Communications Server for Linux when installed on a x86_64 (AMD64 or Intel EM64T) system. If you are installing the server on another architecture (i686 or ppc64) see the README file for that platform. If you are installing one of the IBM Remote API Clients see the appropriate README file in the ibm-commserver-clients subdirectories on the Remote API Clients CD. 2.1 Hardware requirements -------------------------- Communications Server for Linux requires an x86_64 (AMD64 or Intel EM64T) system supported by one of the Linux distributions listed in section 2.2.1 Linux operating system version. Use the 'uname -m' command to verify the CPU class. It must report 'x86_64' to indicate the proper type of system. 2.2 Software requirements -------------------------- 2.2.1 Linux operating system version ------------------------------------- This version of Communications Server for Linux has been tested with the following operating system versions. RedHat Enterprise Linux 4 (RHEL4) RedHat Enterprise Linux 5 (RHEL5) - 'Server' version, not 'Client' SUSE Linux Enterprise Server 9 (SLES9) SP3 or later SUSE Linux Enterprise Server 10 (SLES10) SP1 or later SUSE Linux Enterprise Server 11 (SLES11) For each operating system version you also need to have loaded a set of optional RPMs. Some of these RPMs come from the Linux install media and some need to be downloaded (the URLs or FTP sites for the download sites are described later). Each of the RPMs which you need to download are noted with "(download)". Use the "rpm -q -a" command to see what packages are currently installed. The lists below specify the minimum recommended levels of these RPMs. Later levels should also work. RedHat Enterprise Linux 4 (RHEL4) --------------------------------- Required: one or more of: kernel-largesmp-2.6.9-34.EL kernel-smp-2.6.9-5.EL kernel-2.6.9-5.EL and one or more of: kernel-largesmp-devel-2.6.9-34.EL kernel-smp-devel-2.6.9-5.EL kernel-devel-2.6.9-5.EL and: glibc-kernheaders-2.4-9.1.87 gcc-3.4.3-9.EL4 make-3.80-5 patch-2.5.4-20 xorg-x11-libs-6.8.1-23.EL xorg-x11-deprecated-libs-6.8.1-23.EL libgcc-3.4.4-2.13 glibc-devel-2.3.4-2.13.i386 (note 'i386') glibc-devel-2.3.4-2.13.x86_64 Optional, needed for xsnaadmin: xorg-x11-6.8.1-23.EL openmotif-2.2.3-6.RHEL4.2 Optional, needed for SSL: compat-libstdc++-33-3.2.3-47.3.i386 (note 'i386') Optional, needed for JavaCPI-C: ibm-java2-i386-sdk-5.0-5.0 (download) and/or ibm-java2-x86_64-sdk-5.0-5.0 (download) RedHat Enterprise Linux 5 (RHEL5) --------------------------------- Required: kernel-2.6.18-*.el5.x86_64 or kernel-xen-2.6.18-*.el5.x86_64 kernel-devel-2.6.18-*.el5.x86_64 or kernel-xen-devel-2.6.18-*.el5.x86_64 kernel-headers-2.6.18-*.el5.x86_64 gcc-4.1.1-*.el5.x86_64 make-3.81-*.x86_64 patch-2.5.4-*.x86_64 glibc-2.5-*.x86_64 glibc-2.5-*.i686 (note 'i686') glibc-devel-2.5-*.x86_64 glibc-devel-2.5-*.i386 (note 'i386') libgcc-4.1.1-*.x86_64 libgcc-4.1.1-*.i386 (note 'i386') libXp-1.0.0-*.i386 (note 'i386') libXt-1.0.2-*.i386 (note 'i386') Optional, needed for xsnaadmin: openmotif22-2.2.3-*.i386 (note 'i386') Optional, needed for SSL: libXtst-*.i386 (note 'i386') compat-libstdc++-33-*.i386 (note 'i386') Optional, needed for JavaCPI-C: ibm-java2-i386-sdk-5.0-5.0 (download) and/or ibm-java2-x86_64-sdk-5.0-5.0 (download) SUSE Linux Enterprise Server 9 (SLES9) -------------------------------------- Required: one or more of: kernel-smp-2.6.5-7.145 kernel-default-2.6.5-7.145 and: kernel-source-2.6.5-7.145 kernel-syms-2.6.5-7.145 gcc-3.3.3-43.24 make-3.80-184.1 patch-2.5.9-141.1 binutils-2.15.90.0.1.1-32.5 glibc-devel-2.3.3-98.28 glibc-devel-32bit glibc-32bit-9-200512100800 XFree86-libs-4.3.99.902-43.22 XFree86-libs-32bit-9-200512021458 Optional, needed for SSL: libstdc++-3.3.3-43.24 Optional, needed for xsnaadmin: openmotif-2.2.2-519.1 openmotif-libs-2.2.2-519.1 openmotif-libs-32bit Optional, needed for JavaCPI-C: ibm-java2-i386-sdk-5.0-5.0 (download) and/or ibm-java2-x86_64-sdk-5.0-5.0 (download) SUSE Linux Enterprise Server 10 (SLES10) ---------------------------------------- Required: one or more of: kernel-default-2.6.16 kernel-smp-2.6.16 kernel-xen-2.6.16 and: kernel-source-2.6.16 kernel-syms-2.6.16 gcc-4.1.0 make-3.80 patch-2.5.9 binutils-2.16.91 binutils-32bit-2.16.91 glibc-devel-2.4 glibc-devel-32bit-2.4 glibc-32bit-2.4 xorg-x11-libs-32bit-6.9.0 xorg-x11-libs-6.9.0 Optional, needed for SSL: xorg-x11-6.9.0 compat-libstdc++-5.0.7 libstdc++-4.1.0 libgcc-4.1.0 Optional, needed for xsnaadmin: openmotif-libs-2.2.4 openmotif-libs-32bit-2.2.4 openmotif-2.2.4 Optional, needed for JavaCPI-C: ibm-java2-i386-sdk-5.0-5.0 (download) and/or ibm-java2-x86_64-sdk-5.0-5.0 (download) SUSE Linux Enterprise Server 11 (SLES11) ---------------------------------------- Required: one or more of: kernel-2.6.27.8-1.1 kernel-default-base-2.6.27.8-1.1 kernel-default-2.6.27.8-1.1 and: kernel-source-2.6.27.8-1.1 kernel-syms-2.6.27.8-1.1 gcc-4.3-59.104 make-3.81-129.18 patch-2.5.9-287.25 binutils-2.19-8.3 glibc-devel-2.9-3.2 xorg-x11-libs-7.4-7.4 Optional, needed for SSL: libstdc++33-3.3.3-7.7 or libstdc++43-4.3.3_20081022-9.7 Optional, needed for xsnaadmin: xorg-x11-7.4-8.18 openmotif-libs-2.2.4 (not in SLES11 distro, see Section 2.2.3) openmotif-2.2.4 (not in SLES11 distro, see Section 2.2.3) Optional, needed for JavaCPI-C: ibm-java2-x86_64-sdk-5.0-5.0 (download) 2.2.2 Linux Streams (LiS) 2.19.0 plus patch ------------------------------------------- Communications Server for Linux uses the LiS streams implementation provided by the "LiS" open source project. The 2.19.0 level is required plus a Communications Server for Linux v6.4.0 specific patch. The 2.19.0 level should be used even if there are later levels available, unless IBM support indicates otherwise. If you already have a previous level of LiS installed or you are about to apply the patch shipped with Communications Server for Linux 6.4.0 or are about to change the kernel you are running, or are about to install a new level of Communications Server for Linux, LiS should be completely uninstalled by doing: /opt/ibm/sna/bin/sna stop /opt/ibm/sna/bin/snaulmod /opt/ibm/sna/bin/snarmdrv unset LD_PRELOAD PATH=$PATH:/sbin cd /usr/src/LiS make uninstall make very-clean cd rm -rf /usr/src/LiS* vi /etc/modprobe.conf remove any references to 'LiS' or 'streams' /sbin/shutdown -r now You may want to delay this reboot until after the 'installibmcs' step is run later in the install process. If you are running SLES9 you should run the following commands to make sure the kernel source is consistent with the running kernel: cd /usr/src/linux-2.6.5-7.xxx where 2.6.5-7.xxx matches the kernel-smp and kernel-source RPMs make cloneconfig make modules_prepare If you are running SLES10 SP1 or later you should run the following commands to make sure the kernel source is consistent with the running kernel: cd /usr/src/linux-2.6.16.xxx where 2.6.16.xxx matches the kernel-default, kernel-smp, kernel-xen, and kernel-source RPMs make cloneconfig make modules_prepare If you are running SLES10 SP1 or later with the XEN kernel you should do the following to allow LiS to build with this kernel source: vi /usr/src/linux-2.6.16.xxx/include/linux/autoconf.h where 2.6.16.xxx matches the kernel-xen and kernel-source RPMs comment out this line from autoconf.h: #define CONFIG_XEN 1 If you are running with SLES11, you should run the following commands to make sure the kernel source is consistent with the running kernel: cd /usr/src/linux-2.6.27.xxx where 2.6.27.xxx matches the kernel-default, kernel-smp, kernel-bigsmp, kernel-xen, and kernel-source RPMs make cloneconfig make modules_prepare cp /usr/src/linux-2.6.27*obj/x86_64/xxx/Modules.symvers . where xxx matches the kernel-default, kernel-smp, kernel-bigsmp, kernel-xen, and kernel-source RPMs If you are running RHEL5 you should run the following commands to make sure the kernel source is consistent with the running kernel: vi /usr/src/kernels/2.6.18*/include/linux/module.h add this line at the top of the module.h file: #include If you are running RHEL5 with SELinux in 'enforcing' mode you should run the following commands to allow the LiS and gskit libraries to be used properly: semanage fcontext -a -t textrel_shlib_t \ /usr/lib/libLiS.so semanage fcontext -a -t textrel_shlib_t \ /usr/lib/libpLiS.so semanage fcontext -a -t textrel_shlib_t \ /usr/local/ibm/gsk7/lib/libgsk7krsw.so semanage fcontext -a -t textrel_shlib_t \ /usr/local/ibm/gsk7/icc/osslib/libcrypto.so.0.9.7 chcon -f -t textrel_shlib_t /usr/lib/libLiS.so chcon -f -t textrel_shlib_t /usr/lib/libpLiS.so chcon -f -t textrel_shlib_t /usr/local/ibm/gsk7/lib/libgsk7krsw.so chcon -f -t textrel_shlib_t /usr/local/ibm/gsk7/icc/osslib/libcrypto.so.0.9.7 The LiS package can be obtained from the following URL: ftp://ftp.wanware.com/pub/LiS/LiS-2.19.0.tgz The LiS-2.19.0-CS6400.patch file is in the 'patches' directory on the Communications Server for Linux CD. Now copy the LiS-2.19.0.tgz and LiS-2.19.0-CS6400.patch files to the /usr/src directory on your Linux system. Make sure to use binary mode if you FTP the tgz file. Execute the following commands to unpack LiS: cd /usr/src tar -xzf LiS-2.19.0.tgz Apply the patch by running the commands: cd /usr/src/LiS-2.19 patch -g0 -p1 < ../LiS-2.19.0-CS6400.patch Execute the following commands to build LiS: PATH=$PATH:/sbin cd /usr/src/LiS-2.19 make select the default answer to all the questions, make install If you are running with a SLES10 XEN kernel you should do the following to allow LiS to build with this kernel source: vi /usr/src/linux-2.6.16.xxx/include/linux/autoconf.h where 2.6.16.xxx matches the kernel-xen and kernel-source RPMs comment in this line from autoconf.h: #define CONFIG_XEN 1 cd km26 make setup make -C /usr/src/linux-2.6.16.xxx SUBDIRS=`pwd` modules make install If you are running with a SLES11 kernel you should do the following to allow LiS to build with this kernel source: cd km26 make setup make -C /usr/src/linux-2.6.27.xxx SUBDIRS=`pwd` modules make install If you are running with a RHEL5 XEN kernel you should do the following to allow LiS to build with this kernel source: cd km26 make setup make -C /usr/src/kernels/2.6.18-xxx.el5-xen-x86_64 SUBDIRS=`pwd` modules make install If you are running with a kernel that is earlier than SLES11 (2.6.27.*): cd modprobe streams If the kernel level is at the SLES11 release (2.6.27.*, or later): cd modprobe --allow-unsupported streams See http://lis.wanware.com for more information on LiS. 2.2.3 OpenMOTIF --------------- The Communications Server for Linux administration GUI ('xsnaadmin') uses the MOTIF implementation from the Open group at the 2.2 level. This is not required for the command-line administration tool ('snaadmin'). You can find a rpm package for your platform at http://www.motifzone.net/. Note that this is the 32-bit (i686) openmotif RPM, not the 64-bit (x86_64) RPM. 2.2.4 Java ---------- A Java may be needed if you use the JavaCPI-C API. Using the latest Java 5 SDK from the web site below satisfies all the requirements. http://www.ibm.com/developerworks/java/jdk Install the Java SDK package with a command like: rpm -i ibm-java2-i386-sdk-5.0-5.0.i386.rpm and/or rpm -i ibm-java2-x86_84-sdk-5.0-5.0.x86_64.rpm 2.2.5 SSL --------- If you plan on using SSL with the Communications Server for Linux TN3270 server, you will first need to install the optional RPMs: RedHat Enterprise Linux 4 (RHEL4) --------------------------------- compat-libstdc++-33-3.2.3-47.3.i386 RedHat Enterprise Linux 5 (RHEL5) --------------------------------- libXtst-*.i386 compat-libstdc++-33-*.i386 SUSE Linux Enterprise Server 9 (SLES9) -------------------------------------- libstdc++-3.3.3-43.24 SUSE Linux Enterprise Server 10 (SLES10) ---------------------------------------- compat-libstdc++-5.0.7 libstdc++-4.1.0 libgcc-4.1.0 SUSE Linux Enterprise Server 11 (SLES11) ---------------------------------------- libstdc++33-3.3.3-7.7 or libstdc++43-4.3.3_20081022-9.7 If the prerequisite RPMs are already installed when Communications Server for Linux is installed, then the gskit RPM (gsk7bas) will be automatically installed at that time. If the prerequisite RPMs are not installed when Communications Server for Linux is installed and at a later time you wish to install the gskit toolkit and co-requisite updates, follow these instructions. - Log into the machine as root. - Mount the CD and issue the following command to install gskit mount /dev/cdrom cd /media/cdrom ./installgskit The "/media/cdrom" directory name may be different if you have a DVD drive. Use the "df" command to see where Linux mounted the CD. The key manager function of gskit requires a customized Java JRE, which is shipped as part of the product. To invoke the key manager, just type: snakeyman 2.2.6 WebSphere Application Server ---------------------------------- If you use the HTTPS mode in a client-server environment you need a WebSphere Application Server (WAS) to perform the server side HTTPS function. You should check: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21210053 for information on the latest WAS PTFs. If you are using WAS 6, then the 6.0.2 update or later is required. 2.3 Installation process ------------------------- 2.3.1 Installing the 6.4.0 base ---------------------------------- If you have a level of LiS other than 2.19.0 + CS6400 patch, follow the steps in section 2.2.2 to remove it and move to the new LiS level with the new patch before installing Communications Server for Linux. If you have a previous level of Communications Server for Linux already installed, follow the steps in section 3 to remove it before installing the 6.4.0 level. If you are installing Communications Server for Linux V6.4.0 over a previous version of the product, you will need to make a backup copy of the /etc/rc.d/init.d/snastart to save any changes made to how the Communications Server starts are boot time. After the product is installed, replace the modified "snastart" file or make the changes to the new "snastart" file. NOTE: The installation process for Communications Server for Linux will make a copy of the /etc/rc.d/init.d/snastart file with a timestamp in the /etc/opt/ibm/sna directory. This may be useful to recover settings from previous installations. The existing information found in /etc/opt/ibm/sna configuration files will be left in place for use by the new installation. To install Communications Server for Linux follow these instructions. - Log into the machine as root. - Mount the CD and make it the current directory mount /dev/cdrom cd /media/cdrom The "/media/cdrom" directory name may be different if you have a DVD drive. Use the "df" command to see where Linux mounted the CD. - Run the installibmcs shell script ./installibmcs The installibmcs shell script will test for certain prerequisites and issue warning messages if they are not met. You will be prompted to read and accept the license agreement. You will then prompted for the name of the server that will be the master server in the Communications Server for Linux domain. If you want to run Communications Server for Linux as a stand-alone node, do not specify this parameter. Once the prompts have been answered the installibmcs tool will install the RPMs. You can convert the node from stand-alone to being in a domain and visa-versa at a later time using the snanetutil command. - Add the Communications Server for Linux binary directories to your PATH. You may wish to change your profile to do this automatically. export PATH="$PATH:/opt/ibm/sna/bin:/opt/ibm/sna/bin/X11" export LD_LIBRARY_PATH=/usr/lib:/opt/ibm/sna/lib export LD_RUN_PATH=/usr/lib:/opt/ibm/sna/lib If you are running 64-bit applications, you would use: export LD_LIBRARY_PATH=/usr/lib64:/opt/ibm/sna/lib64 export LD_RUN_PATH=/usr/lib64:/opt/ibm/sna/lib64 For Java CPI-C applications you should also set the environment variable: export CLASSPATH=$CLASSPATH:/opt/ibm/sna/java/cpic.jar - Start Communications Server for Linux. After installation this will happen automatically when the machine is rebooted. Make sure you are not still in the CD's directories when this is done. cd / sna start For machines with limited memory a reboot may be required. For larger systems this may not be needed. If the Communications Server for Linux node fails to start, check the /var/log/messages file for an entry like: kernel: SNA Trace Driver can only get X blocks of memory - please reboot If these messages persist even after rebooting you need more memory or you need to reduce the number of kernel modules. - Run the Communications Server for Linux MOTIF administration tool. We recommend you use the Motif administration program until you are familiar with Communications Server for Linux operation. Simply follow the instructions you are given. You may use a remote XWindows server instead of graphics mode on the Linux system. On the XWindows server, run: xhost +XX where XX is the TCP/IP name or address of the Linux system. Now tell the xsnaadmin client where the X server is and start it up: export DISPLAY=YY:Z xsnaadmin & where YY is the TCP/IP name or address of the XWindows server and Z is the virtual display number (typically '0'). 3. Uninstallation information ----------------------------- The Communications Server for Linux packages can be removed with the following commands: /opt/ibm/sna/bin/sna stop rpm -e CS-LINUX rpm -e CS-LINUX-Docs rpm -e CS-LINUX-ecl rpm -e CS-LINUX-ptf rpm -e ibm-commserver-ptf rpm -e ibm-commserver-docs rpm -e ibm-commserver-ecl rpm -e ibm-commserver-cli rpm -e ibm-commserver /sbin/shutdown -r now Not all of these packages will be installed on every system. Uninstalling Communications Server for Linux will leave any customized configuration information behind for use by a later installation. 4. Known limitations and problems ---------------------------------- 4.1 Connectivity Options ------------------------ Communications Server for Linux can be used over Ethernet or Token ring adapters. Communications Server for Linux has been tested with several different ethernet adapters using several different Linux device drivers. Communications Server for Linux has been tested with the IBM 16/4 PCI Token ring adapter (olympic driver) and the IBM LANStreamer adapter (lanstreamer driver). Other adapters (such as Madge) using these or other drivers are also expected to work. Communications Server for Linux v6.4.2 added support for WAN adapters (sdlc & x.25). The OEM WAN adapter support requires device driver and dlc code from the adapter vendor. IBM does not provide these adapters or device drivers. See the support web site for details on available WAN adapter vendors. The OEM WAN support may not be available for all platforms or all Linux distributions supported by Communications Server for Linux. Communications Server for Linux v6.4.0 and later will require a level or the OEM WAN support which is different from the level used with CS Linux v6.4.2, so make sure you install the right level of the OEM WAN support for your level of CS Linux. See the web site http://www.ibm.com/software/network/commserver/linux/sysreqs for a complete list of adapters and drivers which have been tested. If you want to use an adapter for Communications Server for Linux but not for TCP/IP, you have to manually tell Linux to load the device driver and enable the adapter. For RedHat this is done by having an entry in the /etc/modules.conf file for that adapter and modifying the appropriate /etc/sysconfig/network-scripts/ifcfg-* file to look something like this: DEVICE=eth1 ONBOOT=yes BOOTPROTO=none For SUSE this is done by having an entry in the /etc/modules.conf file for that adapter and modifying the appropriate /etc/sysconfig/network/ifcfg-* file to look something like this: DEVICE=eth1 BOOTPROTO="none" STARTMODE="onboot" 4.2 TN3270 Server ----------------- The Communications Server for Linux TNServer is limited to a certain number of open files/sockets. The actual limit depends on how much memory the Linux system has available. Use the 'cat /proc/sys/fs/file-max' command to see what the current limit is. For any value of file-max you must have: ( (#_of_ReDir_clients * 2) + #_of_TN3270_clients ) < file-max This limit can be increased by following the instructions in: /usr/src/linux*/Documentation/filesystems/proc.txt in the section titled "file-nr and file-max". If the customer hits this limit they will see this in /var/opt/ibm/sna/sna.err: hh:mm:ss TZ dd mmm yyyy 4102-6(0-1) E (hostname) PID pid# (snatnsrvr_mt) O/S accept call failed with error code 23. hh:mm:ss TZ dd mmm yyyy 4102-8(1-1) E (hostname) PID pid# (snatnsrvr_mt) Failed to initialize TN3270 or TN Redirector Client due to serious error. 4.3 Using certain applications and TPs ------------------------------------- There are two issues when trying to use applications and TPs that are either JavaCPI-C or were compiled on older levels of Linux, Communications Server for Linux and LiS. a) The level of LiS which is required for this release may also require that you set the environment variable: LD_PRELOAD=/usr/lib/libpLiS.so for old applications and TPs and JavaCPI-C to work properly. If the application is a 64-bit binary you would use: LD_PRELOAD=/usr/lib64/libpLiS.so You should not 'export LD_PRELOAD=/usr/lib/libpLiS.so' on an x86_64 system because the default shell ('/bin/bash') may be a 64-bit binary and you cannot run a 64-bit binary with LD_PRELOAD set to a 32-bit library. In the case were you have to run a 32-bit binary, use a syntax like: LD_PRELOAD=/usr/lib/libpLiS.so 32bitbinaryname so that the LD_PRELOAD environment variable is only set for that 32-bit binary. b) Some new distributions are based on a Linux kernel level (2.4.20 or later) which includes a new threading model. You may have to recompile your applications on these distributions for them to work properly or you may be able to set the environment variable: export LD_ASSUME_KERNEL=2.4.1 to force the old threading model. You cannot use LD_ASSUME_KERNEL=2.4.1 on SLES10 or RHEL5. 4.4 Mixing CS Linux levels on servers in a domain ------------------------------------------------- If you have a client/server domain with multiple servers then you should plan to update all the servers to the CS Linux v6.4.0 level at the same time. You can run a domain with mixed levels of CS Linux servers, but the NOF, snaadmin, and xsnaadmin commands from 6.4.0 will not work properly with servers which are <6.4.0 and visa-versa. 4.5 NOF applications may have to be recompiled ---------------------------------------------- NOF applications compiled with CS/AIX V6.3.0 or before, which use the TN_REDIRECTION_INDICATION, IPDLC_PORT_SPEC_DATA, IPDLC_LINK_SPEC_DATA, DEFINE_TN3270_ACCESS, DELETE_TN3270_ACCESS, TN3270_ACCESS_SUMMARY, TN3270_ACCESS_DETAIL, QUERY_TN3270_ACCESS_DEF, TN3270_SSL_LDAP_DEF_DATA, DEFINE_TN3270_EXPRESS_LOGON, QUERY_TN3270_EXPRESS_LOGON, TN_SERVER_SESSION_USER_INFO, TN_REDIRECT_ADDRESS, TN_REDIRECT_DEF_DATA, DEFINE_RTP_TUNING, or QUERY_RTP_TUNING structures will have to be recompiled to work on CS/AIX v6.3.1, CS/AIX V6.4.0 or later. 5. Documentation updates -------------------- See the WhatsNew6400.txt document. 6. Notices and trademarks -------------------------- 6.1 Notices ----------- This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation P.O. Box 12195 3039 Cornwallis Road Research Triangle Park, NC 27709-2195 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. 6.2 Trademarks -------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: Advanced Peer-to-Peer Networking AIX Application System/400 AS/400 CICS IBM MQSeries MVS MVS/ESA MVS/XA NetView OpenPower OS/2 Power5 pSeries S/390 SP System p System x System z System/370 System/390 SAA Systems Application Architecture VTAM WebSphere z/OS z9 zSeries The following terms are trademarks or registered trademarks of other companies: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. Intel and Pentium are trademarks of Intel Corporation. AMD64 is a trademark of Advanced Micro Devices, Inc. Linux is a trademark of Linus Torvalds. Microsoft, Windows, Windows NT, Windows XP, Windows 2003, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.