



IBM Communications Server v6.2.2.1 for Linux (i686)
INSTALLATION AND RELEASE NOTES
5724-I33




*  Copyright International Business Machines Corp. 2002, 2006
* 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
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
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.2.2.1 base
3.  Uninstallation information
4.  Known limitations and problems
5.  Documentation updates
6.  Notices and 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, WAN, and 802.2 connections.

The Remote API Clients which work best with the
Communications Server for Linux v6.2.2.1 servers are the 6.3.0.2 clients.
The release numbers do not match because the
clients are also shipped with CS/AIX v6.3.


1.1  New in this release
------------------------

This release includes enhancements for:
   - client-server via HTTPS
   - RHEL5 & SLES10 Linux distributions
   - Windows 64bit client, including HTTPS
   - Windows Vista support
   - Linux x86_64 client & server
   - WAN (sdlc & x.25) OEM adapter support

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 CS Linux 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.

See the "WhatsNew6221.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.2.1 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.


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-01  czx00101.pdf
   Quick Beginnings on System z         GC31-6769-01  czx00201.pdf
   Administration Command Reference     SC31-6770-01  czx00301.pdf
   Administration Guide                 SC31-6771-01  czx00401.pdf
   APPC Application Suite User's Guide  SC31-6772-01  czx00501.pdf
   APPC Programmer's Guide              SC31-6773-01  czx00601.pdf
   CPI-C Programmer's Guide             SC31-6774-01  czx00701.pdf
   CSV Programmer's Guide               SC31-6775-01  czx00801.pdf
   LUA Programmer's Guide               SC31-6776-01  czx00901.pdf
   MS Programmer's Guide                SC31-6777-01  czx01101.pdf
   NOF Programmer's Guide               SC31-6778-01  czx01201.pdf
   Diagnostics Guide                    GC31-6779-01  czx01301.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 un-zip 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 32bit intel system (i686).  If you are
installing the server on another architecture (ppc64 or x86_64)
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 Pentium II or later 32-bit Intel
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 'i686' to indicate a Pentium II or later 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 3 (RHEL3)
  RedHat Enterprise Linux 4 (RHEL4)
  RedHat Enterprise Linux 5 (RHEL5) - 'Server' version, not 'Client'
  SUSE Linux Enterprise Server 8 (SLES8)
  SUSE Linux Enterprise Server 9 (SLES9)
  SUSE Linux Enterprise Server 10 (SLES10)


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 3 (RHEL3)
  ---------------------------------
    Required:
      one or more of:
        kernel-smp-2.4.21-27.EL
        kernel-2.4.21-27.EL
      and:
        kernel-source-2.4.21-27.EL
        glibc-kernheaders-2.4-8.34
        gcc-3.2.3-20
        make-3.79.1-17
        XFree86-libs-4.3.0-35.EL
        rpm-4.2.3-13      (http://rhn.redhat.com/errata/RHBA-2004-501.html)
    Optional, needed for xsnaadmin:
      XFree86-4.3.0-35.EL
      openmotif-2.2.2-16
    Optional, needed for SSL:
      libgcc-3.2.3-20
      libstdc++-3.2.3-20
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.0				(download)


  RedHat Enterprise Linux 4 (RHEL4)
  ---------------------------------
    Required:
      one or more of:
        kernel-smp-2.6.9-5.EL
        kernel-2.6.9-5.EL
      and one or more of:
        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
    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
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.0				(download)


  RedHat Enterprise Linux 5 (RHEL5)
  ---------------------------------
    Required:
      kernel-2.6.18-*.el5
      kernel-devel-2.6.18-*.el5
      kernel-headers-2.6.18-*.el5
      gcc-4.1.1-*.el5
      make-3.81-*
      patch-2.5.4-*
      glibc-2.5-*.
      glibc-devel-2.5-*
      libgcc-4.1.1-*
      libXp-1.0.0-*
      libXt-1.0.2-*
    Optional, needed for xsnaadmin:
      openmotif22-2.2.3-*
    Optional, needed for SSL:
      libXtst-*
      compat-libstdc++-33-*
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.0				(download)


  SUSE Linux Enterprise Server 8 (SLES8)
  --------------------------------------
    Required:
      one or more of:
        k_deflt-2.4.21-266
        k_smp-2.4.21-266
        k_psmp-2.4.21-266
      and:
        kernel-source-2.4.21-266
        gcc-3.2-45
        make-3.79.1-407
        binutils-2.12.90.0.15-50
        glibc-devel-2.2.5-163
        xshared-4.2.0-188
    Optional, needed for xsnaadmin:
      xf86-4.2.0-188
      openmotif-2.2.2-124
    Optional, needed for SSL:
      libgcc-3.2.2-38
      libstdc++-3.2.2-38
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.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
       kernel-bigsmp-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
      XFree86-libs-4.3.99.902-43.22
    Optional, needed for SSL:
      libstdc++-3.3.3-43.24
    Optional, needed for xsnaadmin:
      openmotif-libs-2.2.2-519.1
      openmotif-2.2.2-519.1
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.0				(download)


  SUSE Linux Enterprise Server 10 (SLES10)
  ----------------------------------------
   Required:
     one or more of:
       kernel-smp-2.6.16
       kernel-default-2.6.16
       kernel-bigsmp-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
      glibc-devel-2.4
      xorg-x11-libs-6.9.0
    Optional, needed for SSL:
      compat-libstdc++-5.0.7
    Optional, needed for xsnaadmin:
      openmotif-libs-2.2.4
      openmotif-2.2.4
    Optional, needed for JavaCPI-C:
      ibm-java2-i386-sdk-5.0-3.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.2.2.1 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.2.2.1
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*
    # for 2.4 kernels -
      vi /etc/modules.conf
        remove any references to 'LiS' or 'streams'
    # for 2.6 kernels -
      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 SLES8 with the -266 kernel 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.4.21-XXX
    where 2.4.21-XXX matches the k_deflt, k_smp, k_psmp, and kernel-source RPMs
  make clean
  make mrproper
  make cloneconfig
  make dep


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-default, kernel-smp, kernel-bigsmp, and kernel-source RPMs
  make cloneconfig
  make modules_prepare


If you are running SLES10 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-bigsmp, and kernel-source RPMs
  make cloneconfig
  make modules_prepare


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 <linux/autoconf.h>

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-CS6221.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-CS6221.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-CS6221.patch

If you are installing on RHEL5, then apply
the LiS-2.19.0-RHEL5.patch as well:

    patch -g0 -p1 < ../LiS-2.19.0-RHEL5.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
    modprobe 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').



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-3.0.i386.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 3 (RHEL3)
  ---------------------------------
    libgcc-3.2.3-20
    libstdc++-3.2.3-20

  RedHat Enterprise Linux 4 (RHEL4)
  ---------------------------------
    compat-libstdc++-33-3.2.3-47.3

  RedHat Enterprise Linux 5 (RHEL5)
  ---------------------------------
    libXtst
    compat-libstdc++-33

  SUSE Linux Enterprise Server 8 (SLES8)
  --------------------------------------
    libgcc-3.2.2-38
    libstdc++-3.2.2-38

  SUSE Linux Enterprise Server 9 (SLES9)
  --------------------------------------
    libstdc++-3.3.3-43.24

  SUSE Linux Enterprise Server 10 (SLES10)
  ----------------------------------------
    compat-libstdc++-5.0.7


If the prerequistite RPMs are already installed when
Communications Server for Linux is
installed, then the gskit RPM
will be automatically installed at that time.

If the prerequistite 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 1.4.2 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.2.2.1 base 
----------------------------------

If you have a level of LiS other than 2.19.0 + CS6221 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.2.2.1 level.
Any old Communications Server for Linux configuration
information 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
   pre-requisites 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 standalone 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 standalone 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

   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 TokenRing 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.2.2 adds
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.

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 Number of concurrent LUA+APPC+CPI-C+NOF applications
--------------------------------------------------------

There is an O/S limit that prevents more than 255 open Streams
(i.e. applications) on Communications Server for Linux at once
when run on 2.4 kernels.
Communications Server for Linux itself uses
some of these streams internally.  That means the total number
of concurrent LUA+APPC+CPI-C+NOF applications must be less than
about 230.  A single application can have multiple SNA sessions
open and that only counts as 1 open stream.

If the customer hits this limit they will see this in /var/opt/ibm/sna/sna.err:
  hh:mm:ss TZ dd mmm yyyy 16388-10(1-0) E (hostname) PID pid# (application)
  Error opening Stream to SNA kernel subsystem.
  Errno = 28 (No space left on device)
  hh:mm:ss TZ dd mmm yyyy 16385-6(1-10) E (hostname)
  SNA Kernel open error 28.


4.5 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:
     export LD_PRELOAD=/usr/lib/libpLiS.so
   for old applications and TPs and JavaCPI-C to work properly.

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.




5.  Documentation updates
--------------------

See the WhatsNew6221.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.


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.

