IBM Communications Server for Data Center Deployment v7.1.1.0 Linux System Power (ppc64le) server platform INSTALLATION AND RELEASE NOTES 5725-H32 * © Copyright International Business Machines Corp. 2003, 2023 * 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 Communications Server Linux Streams (CSLiS) 7.1.1 2.2.3 OpenMOTIF 2.2.4 Java 2.2.5 SSL 2.3 Installation process 2.3.1 Installing the v7.1.1 base 3. Uninstallation information 4. Known limitations and problems 4.1 Connectivity Options 4.2 TN3270 Server 4.3 Consideration when building applications on Ubuntu 4.4 Using certain applications and TPs 4.5 Mixing CS Linux levels on servers in a domain 4.6 GSKit8 and SSL support 4.7 WebAdmin package for remote administration 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 Data Center Deployment v7.1.1.0, Linux System p, ppc64le, server platform (CS Linux) provides SNA connectivity for 64-bit System p 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 CS Linux is backwards compatible with Remote API clients v6.4, v7.0 and v7.1. The Remote API Clients which work best with the Communications Server for Data Center Deployment V7.1.1 servers are the v7.1.1 clients. See the "WhatsNew7110.txt" file in the root of the download image for more details. 1.1 New in this release ------------------------ The Communications Server for Data Center Deployment v7.1.1.0 release provides the following updates to the server and Remote API clients: - Additional support for the Linux distributions SLES 15 SP5 and RHEL 9.2 - Integration of CPI-C for Rust APIs - Requirement for Communications Server for Linux Streams at https://github/IBM/CSLiS 1.2 Product fix history ------------------------ This release is a follow-on release to the Communications Server for Data Center Deployment v7.1 product. This PTF release is for version 7.1.1.0: APARS for PTF level v7.1.1.0: LI82796 CRASH IN SNA_V5ROUTER LI82791 INCONSISTENT CONTROLLER STATUS IN SNA DOMAIN LI82706 ADD OPTION TO DISABLE TLS 1.0 AND 1.1 LI82759 RUI PRIMARY WRITES DR1 +RSP FOR DR2 REQUEST LI82758 RUI_INIT FAILS ON REMOTE API CLIENT AFTER REBOOT LI82724 SYSTEMCTL STATUS SNASTART CAN GET OUT OF SYNC LI82726 SUPPORT FOR CSLiS-711 ON RHEL 9.1 LI82727 SNA FAILS TO START: TRACE DAEMON HAS BEEN DEACTIVATED LI82917 CUMULATIVE APAR FOR 7.1.1.0 Please check the web sites: https://www.ibm.com/support/home/product/D383627W52509B26/other_software/communications_server_for_data_center_deployment https://www.ibm.com/it-infrastructure/z/communications-server for the latest information about this product. You can use the Developerworks forums to ask questions and find answers regarding distributed Communications Server products: http://www-01.ibm.com/support/docview.wss?uid=swg21418224 1.3 Product compatibility -------------------------- If the CS Linux is used in a domain of servers, all the servers must be Linux servers. The CS Linux will not support a domain of servers that include Communications Server for AIX. 1.4 Viewing the Documentation ------------------------------ The CS Linux documentation is available on the QuickStart download image 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-05 czx00120.pdf Quick Beginnings on System z GC31-6769-05 czx00220.pdf Administration Command Reference SC31-6770-05 czx00320.pdf Administration Guide SC31-6771-05 czx00420.pdf APPC Application Suite User's Guide SC23-8595-01 czx40510.pdf APPC Programmer's Guide SC23-8592-01 czx40610.pdf CPI-C Programmer's Guide SC23-8591-01 czx40710.pdf CSV Programmer's Guide SC23-8589-01 czx40810.pdf LUA Programmer's Guide SC23-8590-01 czx40910.pdf MS Programmer's Guide SC23-8596-01 czx41110.pdf NOF Programmer's Guide SC31-6778-05 czx01220.pdf Diagnostics Guide GC31-6779-05 czx01320.pdf Glossary GC31-6780-01 czx01401.pdf The CS Linux documentation is also available on the Internet at: https://www.ibm.com/support/pages/node/317755 2. Installation information ---------------------------- The Communications Server for Data Center Deployment product is packaged as 4 download images. The download images contains this README file, several RPMs, the install shell scripts, and licensing tool. This file has details for the server component of CS Linux when installed on a Power System, ppc64le system. If you are installing the server on another architecture, x86_64 for example, 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 sub-directories on the Remote API Clients download image. 2.1 Hardware requirements -------------------------- Communications Server for Linux requires a System p server 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 'ppc64le' to indicate a System p server. 2.2 Software requirements -------------------------- 2.2.1 Linux operating system version ------------------------------------- This version of CS Linux has been tested with the following operating system versions. RedHat Enterprise Linux 7.9 RedHat Enterprise Linux 8 (RHEL 8) RedHat Enterprise Linux 8.x RedHat Enterprise Linux 9 (RHEL 9) RedHat Enterprise Linux 9.x SUSE Linux Enterprise Server 12 (SLES12) SPx SUSE Linux Enterprise Server 15 (SLES15) SPx Ubuntu LTS 18.04 Ubuntu LTS 20.04 Ubuntu LTS 22.04 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 7 (RHEL7) --------------------------------- Required: kernel-3.10.0-*.el7.ppc64le OR kernel-xen-3.10.0-*.el7.ppc64le kernel-devel-3.10.0-*.el7.ppc64le OR kernel-xen-devel-3.10.0-*.el7.ppc64le kernel-headers-3.10.0-*.el7.ppc64le gcc-4.8.2-*.el7.ppc64le make-3.82-*.el7.ppc64le patch-2.7.1-*.el7.ppc64le glibc-2.17-*.el7.ppc64le glibc-devel-2.17-*.el7.ppc64le libgcc-4.8.2-*.el7.ppc64le libXp-1.0.2-*.el7.ppc64le libXt-1.1.4-*.el7.ppc64le nss-softokn-3.15.4-*.el7.ppc64le perl-5.16 Optional, needed for xsnaadmin: motif-2.3.4-7.el7.ppc64le Optional, needed for SSL: libXtst-1.2.2-*.el7.ppc64le libstdc++-4.8.2-*.el7.ppc64le libXrender-0.9.8-*.el7.ppc64le libXft-2.3.2-*.el7.ppc64le Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-6.0-16.35.ppc64le.rpm (download) RedHat Enterprise Linux 8 (RHEL8) --------------------------------- Required: kernel-4.18.0-*.el8.ppc64le OR kernel-xen-4.18.0-*.el8.ppc64le kernel-devel-4.18.0-*.el8.ppc64le OR kernel-xen-devel-4.18.0-*.el8.ppc64le kernel-headers-4.18.0-*.el8.ppc64le gcc-8.2.1-3.5.el8.ppc64le make-4.2.1-9.el8.ppc64le patch-2.7.6-8.el8.ppc64le elfutils-libelf-devel-0.174-6.el8.ppc64le glibc-2.28-42.el8.ppc64le glibc-devel-2.28-42.el8.ppc64le libgcc-8.2.1-3.5.el8.ppc64le libnsl-2.28-42.el8.ppc64le libXp-1.0.3-3.el8.ppc64le libXt-1.1.5-8.el8.ppc64le nss-softokn-3.41.0-5.el8.ppc64le perl-libs-5.26.3-416.el8.ppc64le Optional, needed for xsnaadmin: motif-2.3.4-16.el8.ppc64le Optional, needed for SSL: libXtst-1.2.3-7.el8.ppc64le libstdc++-8.2.1-3.5.el8.ppc64le libXrender-0.9.10-7.el8.ppc64le libXft-2.3.2-10.el8.ppc64le Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0.5.ppc64le.rpm (download) RedHat Enterprise Linux 9 (RHEL9) --------------------------------- Required: kernel-5.14.0-55-*.el9.ppc64le OR kernel-xen-5.14.0-55-*.el9.ppc64le kernel-devel-5.14.0-55-*.el9.ppc64le OR kernel-xen-devel-5.14.0-55-*.el9.ppc64le kernel-headers-5.14.0-55-*.el9.ppc64le gcc-11.2.1-*.el9.ppc64le make-4.3.7.el9.ppc64le patch-2.7.6-16.el9.ppc64le chkconfig-1.20.2.el9.ppc64le elfutils-libelf-devel-0.186-1.el9.ppc64le glibc-2.34-21.el9.ppc64le glibc-devel-2.34-21.el9.ppc64le libgcc-11.2.1-*.el9.ppc64le libnsl-2.34-21.el9.ppc64le libXp-1.0.3-11.el9.ppc64le libXt-1.2.0-6.el9.ppc64le libxcrypt-compat-4.4.18-3.el9.ppc64le nss-softokn-3.71.0-6.el9.ppc64le perl-libs-5.31.1-476.el9.ppc64le Optional, needed for xsnaadmin: motif-2.3.4-24.el9.ppc64le Optional, needed for SSL: libXtst-1.2.3-16.el9.ppc64le libstdc++-11.2.1-9.1.el9.ppc64le libXrender-0.9.10-16.el9.ppc64le libXft-2.3.3-8.el9.ppc64le Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0.5.ppc64le.rpm (download) SUSE Linux Enterprise Server 12 (SLES12) SP5 ---------------------------------------- Required: one or more of: kernel-4.12.14 kernel-default-base-4.12.14 kernel-default-devel-4.12.14 kernel-default-4.12.14 and: kernel-source-4.12.14 kernel-syms-4.12.14 gcc-4.8-5.3 make-4.0-2.21 patch-2.7.1-.5.99 binutils-2.19-8.3 glibc-devel-2.19-11 perl-5.18 xorg-x11-libs-7.6-45 Optional, needed for SSL: libstdc++6-4.8.3 libstdc++6-32bit-4.8.3 libXtst6-32bit libXft2-2.3.1 libXrender1-0.9.8 Optional, needed for xsnaadmin: xorg-x11-7.6-45 motif-2.3.4 (see Section 2.2.3 below) Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0-3.22.ppc64le.rpm (download) SUSE Linux Enterprise Server 15 (SLES15) SP4 ---------------------------------------- Required: one or more of: kernel-5.14.21-150400 kernel-default-base-5.14.21-150400 kernel-default-devel-5.14.21-150400 kernel-default-5.14.21-150400 and: kernel-source-5.14.21-150400 kernel-syms-5.14.21-150400 gcc-7-3.9 make-4.2.1-7 patch-2.7.6 binutils-2.37-7 glibc-2.31-150300 glibc-devel-2.31-150300 perl-5.26.1 Optional, needed for SSL: libstdc++6-11.2.1 libXtst6-1.2.3 libXft2-2.3.2 libXrender1-0.9.10 Optional, needed for xsnaadmin: dbus-1-x11-1.12 xorg-x11-fonts-core-7.6-13 libxkbcommon-x11-0-1.3 xorg-x11-server-1.20.3 ghostscript-x11-9.52 xorg-x11-driver-video-7.6_1-9 libX11-6-1.6.5-3 motif-2.3.4 (see Section 2.2.3 below) Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0-3.22.ppc64le.rpm (download) UBUNTU Linux 18.04 LTS (bionic): ----------------------------------------------- linux-generic-4.15.0 linux-headers-generic-4.15.0 linux-image-generic-4-15.0 linux-libc-dev-4.15.0 gcc/* 4:7.4.* gcc-7/* 7.5.0 gcc-7-base/* 7.5.0 libgcc-7-dev/* 7.5.0 libgcc1/* 1:8.4.0 perl/* 5.26.1 perl-base/* 5.26.1 libstdc++6/ * 8.4.0 libxt6/* 1:1.1.5 libxtst6/* 2:1.2.3 Optional for xsnaadmin: libmotif-common/* 2.3.8 libmotif-dev/* 2.3.8 libx11-6/* 2:1.6.4 x11-apps/* 7.7 x11-common/* 7.7 x11-utils/* 7.7 Optional for SSL: libxrender1/* 0.9.10 libxft2/* 2.3.2 Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0* (download) UBUNTU Linux 20.04 LTS (focal): ----------------------------------------------- linux-headers-5.4.0 linux-image-5.4.0 linux-libc-dev/* 5.4.0 linux-modules-5.4.0* linux-source-5.4.0 gcc-9-base/* 9.3.0 gcc-9/* 9.3.0 gcc/* 9.3.0 libgcc-9-dev/* 9.3.0 libgcc-s1/* 10 perl/* 5.30.0 perl-base/* 5.30.0 libstdc++6/ * 10 libxt6/* 1:1.1.5 libxtst6/* 2:1.2.3 bolt/*.18.04.1 Optional for xsnaadmin: libmotif-common/* 2.3.8 libmotif-dev/* 2.3.8 libx11-6/* 2:1.6.4 x11-apps/* 7.7 x11-common/* 7.7 x11-utils/* 7.7 Optional for SSL: libxrender1/* 0.9.10 libxft2/* 2.3.2 Optional, needed for JavaCPI-C: ibm-java-ppc64le-sdk-8.0* (download) UBUNTU Linux 22.04 LTS (jammy): ----------------------------------------------- linux-base/ 4.5ubuntu9 linux-headers-5.15.0 linux-image-5.15.0 linux-modules-5.15.0 gcc-12-base/* 12 libgcc-s1/* 12 perl/* 5.34.0 perl-base/* 5.34.0 libstdc++6/ * 12 bolt/ 0.9. Optional for xsnaadmin: libmotif-common/* 2.3.8 libmotif-dev/* 2.3.8 libx11-6/* 2:1.7 binutils-ppc64el-linux-gnu/ 2.28 Optional for SSL: binutils-ppc64el-linux-gnu/ 2.28 Optional, needed for JavaCPI-C: ibm-java-ppc6le-sdk-8.0* (download) 2.2.2 Communications Server Linux Streams (CSLiS) 7.1.1 ------------------------------------------------------- Communications Server for Data Center Deployment Linux v7.1.1 server uses the Communications Server Linux Streams implementation provided by the "CSLiS" open source project. The CSLiS-711 level is required and is simpler to install than the previous LiS-2.19 plus patch file. The CSLiS-711 level should be used even if there are later levels available, unless IBM support indicates otherwise. The Communications Server Linux Streams package does not support Secure Boot option in Linux. Secure Boot is way to sign drivers and modules for the kernel. The CSLiS package does not have signing capabilities. Disable Secure Boot before starting the SNA server. If Secure Boot is enabled, the following message will be reported when the SNA server is started: modprobe : ERROR : could not insert 'streams' : Required key not available. The CS Linux ships a copy of the CSLiS-711 release code in the /CSLiS directory. You can use this compressed TAR version or download the latest version from: https://github/IBM/CSLiS The TAR file path on the download image is found in the /CSLiS directory: /CSLiS/CSLiS-7.1.1.0.tgz Unlike previous releases of CS Linux, the CSLiS-7.1.1.0.tgz file is the full project package directory for the Communications Server Linux Streams. Now copy the CSLiS-7.1.1.0.tgz file to the /usr/src directory on your Linux system. If you already have a previous level of LiS installed, or you are about to apply the patch shipped with CS Linux, or are about to change the kernel you are running, including updating the kernel level via a maintenance update, or are about to install a new level of CS 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* /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 any version of SuSE Linux Enterprise Server (SLES), you should run the following commands to make sure the kernel source is consistent with the running kernel: cd /usr/src/linux-4.x ( or /usr/src/linux-5.x) where 4.x matches the kernel-default, kernel-smp, kernel-bigsmp, and kernel-source RPMs make cloneconfig, or make oldconfig for SLES 15 make modules_prepare The CSLiS package can be found on the download image or obtained from the following URL: https://github/IBM/CSLiS The following instructions are for the CS Linux v7.1.1 level of CSLiS. If you have a previous version, save the /opt/ibm/sna/README file and use those instructions for your level of LiS. Unlike previous releases of CS Linux, the CSLiS-7.1.1.0.tgz file is the full project package directory for the Communications Server Linux Streams. Now copy the CSLiS-7.1.1.0.tgz file to the /usr/src directory on your Linux system. Execute the following commands to unpack CSLiS: cd /usr/src tar -xzf CSLiS-7.1.1.0.tgz Execute the following commands to build LiS: PATH=$PATH:/sbin cd /usr/src/CSLiS-711 ./buildLiS The buildLiS script will select defaults and compile, build and install LiS. If you wish to load the LiS driver into memory, you can execute the following commands, or skip this step to let the CS Linux load the LiS driver automatically when it starts: - For all systems other than SLES12, SLES 15 (any level) execute the following: cd modprobe streams - If the kernel level is at the SLES12, SLES15 (any level): cd modprobe --allow-unsupported streams See http://github/IBM/CSLiS for more information on CSLiS. 2.2.3 OpenMOTIF --------------- The CS Linux administration GUI ('xsnaadmin') uses the MOTIF implementation from the Open group at the 2.3 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/. The RPM packages required to support the xsnaadmin Graphic User Interface (GUI) is: motif-2.3.*.ppc64le If you install Motif packages after the CS Linux is installed, you may need to link the older versions of the library to the newer. To do this, issue the following on the respective systems: cd /usr/lib64 (On Ubuntu - cd /usr/lib) ln -s libMrm.so.4 libMrm.so.3 ln -s libXm.so.4 libXm.so.3 2.2.4 Java ---------- A Java may be needed if you use the JavaCPI-C API. Using the latest Java 8 SDK, or later, 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-ppc-sdk-8.0-6.0.ppc.rpm and/or rpm -i ibm-java2-ppc64-sdk-8.0-6.0.ppc64.rpm 2.2.5 SSL --------- The Communications Server for Data Center Deployment v7.1.1.0 media package includes GSKit version 8.0.55.31 used for Telnet encryption (SSL) support. The GSKit package provides TLS 1.3 support and the latest cipher encryption support. If you plan on using SSL with the CS Linux TN3270 server, you will first need to install the optional RPMs: RedHat Enterprise Linux 7 and 8 for Linux (ppc64le) --------------------------------------------------- libXtst-*.ppc64le libstdc++-*.ppc64le SUSE Linux Enterprise Server 12 (SLES12) SUSE Linux Enterprise Server 15 (SLES15) ---------------------------------------- libXtst6-*.ppc64le If the prerequisite RPMs are already installed when CS Linux is installed, then the GSKit RPM will be automatically installed at that time. If the prerequisite RPMs are not installed when CS 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 download image and issue the following command to install GSKit mkdir /mnt/cslinux mount -o ro,loop CDL7110.iso /mnt/cslinux cd /mnt/cslinux ./installgskit 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 The Communications Server for Data Center Deployment V7.1.1 defaults to the following TLS protocol enablement/disablement by default. These defaults can be overriden by setting environment variables in the /etc/opt/ibm/sna/environment file. See the WhatsNew7110.txt for more information: GSK_PROTOCOL_TLSV13=1 # enabled GSK_PROTOCOL_TLSV12=1 # enabled GSK_PROTOCOL_TLSV11=0 # disabled GSK_PROTOCOL_TLSV10=0 # disabled 2.3 Installation process ------------------------- 2.3.1 Installing the v7.1.1 base ---------------------------------- If you have a level of Linux Streams other than CSLiS-711, follow the steps in section 2.2.2 to remove it and move to the new CSLiS level with the new CSLiS package before installing CS Linux. If you have a previous level of CS Linux already installed, follow the steps in section 3 to remove it before installing the v7.1.1.0 level. If you are installing CS Linux V7.1.1.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 CS Linux starts at 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 time-stamp 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 CS Linux follow these instructions. - Log into the machine as root. - Mount the download image and make it the current directory mkdir /mnt/cslinux mount -o ro,loop CDL7110.iso /mnt/cslinux cd /mnt/cslinux - 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 CS Linux domain. If you want to run CS 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 CS 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 CS Linux. After installation this will happen automatically when the machine is rebooted. cd / sna start For machines with limited memory a reboot may be required. For larger systems this may not be needed. If the CS 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 CS Linux MOTIF administration tool. We recommend you use the Motif administration program until you are familiar with CS 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 CS for Linux packages can be removed with the following commands: /opt/ibm/sna/bin/sna stop rpm -e ibm-commserver-docs rpm -e ibm-commserver-cli rpm -e ibm-commserver rpm -e gskssl64 gskcrypt64 (if using SSL) /sbin/shutdown -r now Not all of these packages will be installed on every system. Uninstalling CS 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 Data Center Deployment Linux can connect over Ethernet adapters. CS Linux has been tested with several different ethernet adapters using several different Linux device drivers. If you want to use an adapter for CS 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 CS Linux TN3270 Server 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 Consideration when building applications on Ubuntu ------------------------------------------------------ When compiling and linking code on Red Hat or SuSE Linux systems, the version of gcc used allows for the source to be specified anywhere on the input. For Ubuntu, the version of gcc requires that the source file be specified before the library files. For example, the following line will work on Red Hat or SuSE for building the executable "lua_app": gcc -o lus_app -I /opt/ibm/sna/include -L /opt/ibm/sna/lib64 \ -lsli -llua -lcsv -lsna_r -lpthread -lpLiS lua_app.c The following must be used on Ubuntu in order to successfully build the application "lua_app": gcc -o lus_app -I /opt/ibm/sna/include -L /opt/ibm/sna/lib64 \ lua_app.c -lsli -llua -lcsv -lsna_r -lpthread -lpLiS 4.4 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, CS Linux and LiS. 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 4.5 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 v7.1.1 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 v7.1.1 may not work properly with servers which are less than v7.1 and visa-versa. 4.6 GSKit8 and SSL support ------------------------------ The Communications Server for Data Center Deployment v7.1.1.0 media pack contains the full release level of the product that supports GSKit 8 and TLS. It is recommended that GSKit 8, 8.0.55.31 or higher be installed to support the latest vulnerability fixes. 4.7 WebAdmin package for remote administration ---------------------------------------------- A remote admistration tool that allows one to manage and monitor a Communications Server on Linux is available at this website: https://www.ibm.com/support/pages/web-administration-package The package is free to download and it provides separate secure login for access for administration and non-administration queries. The README file provided details how to install and configure the tool. With this tool installed, one can manage a CS Linux server using a web browser. The tool currently is English only. 5. Documentation updates -------------------- See the WhatsNew7110.txt document. 6. Notices and trademarks -------------------------- 6.1 Notices ----------- IBM may not offer all of 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: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14 Shimotsuruma,, Yamato-Shi Kanagawa 242-8502 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. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. 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: Site Counsel IBM Corporation P.O. Box 12195 3039 Cornwallis Road Research Triangle Park, North Carolina 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. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development- level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. 6.2 Trademarks -------------- IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Adobe and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Ubuntu is a registered trademark of Canonical Limited in the United Kingdom and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and service names might be trademarks of IBM or other companies.