Copyright International Business Machines Corporation 2010.
           All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager Agent for Lotus Domino, Version 6.2.1

Component ID: 5724B98D0 

Interim Fix: 0004, 6.2.1-TIV-ITM_DOM-IF0004
        
Date: Sep 30, 2010

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices

1.0 General description
========================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4. 

2.0 Problems fixed
==================
The following problems are addressed by this fix.

  2.1 APARs
  ---------
 
  APAR: IZ76599
  Abstract:  IF DOMINO AGENT IS RUNNING THEN DOMINO SERVER WILL NOT
             START.
  Additional Information: This is a document APAR. If the Lotus Domino agent is
         running, starting the Domino server fails.  The root cause is
         that the Domino server and Lotus Domino agent run in different modes.
         The Domino server runs in server mode and the Lotus Domino agent runs in 
         service mode.
         In this case, the shared memory created by the Notes API that is 
         called by the Lotus Domino agent cannot be seen by the Domino server, which
         causes the Domino server to start failing.
         To resolve this problem, you must run the Domino server in service
         mode or upgrade it to release 8.0.1 or later.
         See the following Technote for details:       
         http://www-01.ibm.com/support/docview.wss?uid=swg21443651
         
  APAR: IZ76716
  Abstract: WHEN CONFIGURING THE DOMINO PARTITIONED SERVER ON WINDOWS
            2003, THE AGENT CANNOT START.
  Additional Information: When the domino partitioned server was installed
         on Windows 2003, the Domino agent failed to start. 
         From the log, the call to NotesInitExteneded returns 421, 
         becasue NotesInitExtended cannot find the notes.ini file.
         The root cause is that the program for the Domino partitioned server 
         directory is not in the same driver as its data directory. 
         
  APAR: IZ82973
  Abstract: SYSTEM_DOWN AND SYSTEM UP SITUATIONS INCORRECTLY TRIGGERED
  Additional Information:        
         When another UNIX-type find.exe is installed on 
         a Windows system (for example, cgywin or lcf), 
         and find.exe is set before the %systemroot%/system32/find.exe, the
         following error occurs: ERROR: 
		 ERROR: NotesProgram= was not found
         in the notes.ini, so the script is exiting.      
         
  2.2 Defects:
  ------------
  Defect: 133468
  Abstract:  Remove the fix for IZ36147
  Additional Information: Remove the fix for IZ36147, which disables the
         transaction log before calling NotesInitExtended and enables the 
         log after calling. You do not need the fix for IZ36147 because 
         it is a Domino server issue that is to be fixed by the 
         Domino server.
        
  Defect: 132593
  Abstract: Domino server quitting, then stopping agent causes agent 
      starting issue
  Additional Information: When the Domino agent and server are running, 
      quit the Domino server and stop the Domino agent.
      Taking these actions causes kgbagent to exit but, the script(cmd.exe)  
      keeps running. Later, after the Domino server is started, kgbclient is 
      started again without kgbagent running. 
                 
  2.3 Enhancements: 
  -----------------
  None.
 
  2.4 Superseded fixes:
  ---------------------
  6.2.1-TIV-ITM_DOM-IF0002.

  2.5 APARS and defects included from superseded fixes
  ----------------------------------------------------       
  
  6.2.1-TIV-ITM_DOM-IF0002
  ------------------------ 
  APAR: IZ36147
  Abstract:  DOMINO AGENT WILL CRASH DOMINO WHEN TRANSACTIONAL LOG
        UP.
  Additional Information: If transaction logging is enabled on the 
        Domino server, starting the Domino agent causes  
        the Domino server to stop. This fix provides a mechanism to avoid 
        a Domino server stopping.
  
  APAR: IZ60296
  Abstract: DOMINO AGENT CONSUMES HIGH CPU 
  Additional Information: When the Domino agent monitors the replication 
        events in the log.nsf database, if there is a large volume of replication 
        events in the log.nsf database, the kgbclient process consumes high CPU.
        This fix provides a setting to enable or disable the log.nsf monitoring,
        and it is disabled by default.    
  
  ------------                                                           
  Defect: 108623
  Abstract: The "Total Routed SMTP" and "Total Routed NRPC" attributes are not 
        displayed by default
  Additional Information: In the Mail Statistics view of the Mail workspace, the 
        "Total Routed SMTP" and "Total Routed NRPC" attributes are not displayed 
        by default. You can add the two attributes to the view manually, or apply 
        the agent support update in this fix to add them to the view.
        
  Defect: 109237
  Abstract: The "Sess Inbound KB Received Interval" and "Sess Inbound KB Sent Interval"
        attributes are not displayed by default
  Additional Information: In the SMTP Statistics view of the Sessions workspace, 
        the "Sess Inbound KB Received Interval" and "Sess Inbound KB Sent Interval" 
        attributes are not displayed by default. You can add the two attributes to 
        the view manually, or apply the agent support update in this fix to add them 
        to the view.
        
  Defect: 109239
  Abstract: The "KB Received Interval" and "KB Sent Interval" attributes are not
        displayed by default
  Additional Information: In the NET TCPIP Statistics view of the Sessions workspace,
        The "KB Received Interval" and "KB Sent Interval" attributes are not displayed 
        by default. You can add the two attributes to the view manually, or apply 
        the agent support update in this fix to add them to the view.
  
  Defect: 111043
  Abstract:  Local access protected databases are reported as corrupt.
  Additional Information: The Domino agent reports that local access protected 
        databases are corrupt. The following error message can be 
        found in the log of kgbclient when such databases are checked for 
        corruption: "This database has local access protection and you are not 
        authorized to access it." This fix reports local access protected databases 
        as 'Local access protected' instead of as 'Corrupt'.
  
  Defect: 117552
  Abstract: The Mail By Destination view causes Domino server crash
  Additional Information: If RouterEnableMailByDest is set to 1 on the Domino server, the 
        Domino server generates verbose mail routing statistics per destination. These 
        statistics can be useful when attempting to troubleshoot routing problems. 
        However, the Lotus Domino agent had problems in parsing the statistics, and it might
        have caused the Domino server to stop. After applying the fix, this problem can be 
        solved.

3.0 Architecture and prerequisites
==================================
This fix is supported on the following operating systems:
    - AIX 5.2 (32 and 64-bit)
    - AIX 5.3 (32 and 64-bit)
    - AIX 6.1 (32 and 64-bit)
    - Red Hat Enterprise Linux (RHEL) 4.0 AS/ES x86-32
    - Red Hat Enterprise Linux (RHEL) 4.0 AS/ES x86-64*
    - Red Hat Enterprise Linux (RHEL) 4.0 AS system z 31-bit
    - Red Hat Enterprise Linux (RHEL) 5.0 AS System z 64-bit*
    - Red Hat Enterprise Linux (RHEL) 5.0 AS/ES x86-32
    - Red Hat Enterprise Linux (RHEL) 5.0 AS/ES x86-64*
    - SuSE Linux (SLES) 10.0 Enterprise Server x86-32
    - SuSE Linux (SLES) 10.0 Enterprise Server x86-64*
    - SuSE Linux (SLES) 10.0 Enterprise Server System z 64-bit*
    - SuSE Linux (SLES) 9.0 Enterprise Server x86-32
    - SuSE Linux (SLES) 9.0 Enterprise Server x86-64*
    - SuSE Linux (SLES) 9.0 Enterprise Server System z 31-bit
    - SuSE Linux (SLES) 9.0 Enterprise Server System z 64-bit*
    - Windows Server 2003 Enterprise Edition x86-32
    - Windows Server 2003 Enterprise Edition x86-64*
    - Windows 2000 Server
    - Solaris 10 SPARC 32
    - Solaris 10 SPARC 64*
    - Solaris 9 SPARC 32
    - Solaris 9 SPARC 64*
    - Solaris 8 SPARC 32
    - Solaris 8 SPARC 64*
    
* For the 64-bit operating systems marked with an asterisk (*), 
  32-bit Domino servers can be monitored locally by running the 
  32-bit Domino agent, and 64-bit Domino servers must be monitored
  through remote monitoring.

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest 
certification information:

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

  3.1 Prerequisites for this fix
  -------------------------------
  The prerequisite level for this fix is as follows:
  - IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino Agent, Version 6.2.1
  
  Becasue this fix is cumulative, it can be installed on any fix level for
  this version, release, and modification level above the prerequisite.    
  
4.0 Image directory contents
============================
This fix image contains the following files:
- 6.2.1-TIV-ITM_DOM-IF0004.README - This README file
- 6.2.1-TIV-ITM_DOM-IF0004.tar    - Fix archive .tar format
- 6.2.1-TIV-ITM_DOM-IF0004.zip    - Fix archive .zip format

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file 
if you are working in a Windows(R) environment. 

The fix archive file contains the following files:
   6.2.1-TIV-ITM_DOM-IF0004/gb_dd.properties
   6.2.1-TIV-ITM_DOM-IF0004/gb_dd_062100004.xml
   6.2.1-TIV-ITM_DOM-IF0004/kgb_aix523_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_aix526_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_li6243_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_li6263_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_ls3243_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_ls3246_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_lx8263_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_sol283_tema_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_tems_teps_tepd_if0004.tar
   6.2.1-TIV-ITM_DOM-IF0004/kgb_tems_teps_tepd_if0004.zip
   6.2.1-TIV-ITM_DOM-IF0004/kgb_winnt_tema_if0004.cab
   6.2.1-TIV-ITM_DOM-IF0004/kgbaix523.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbaix526.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbli6243.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbli6263.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbls3243.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbls3246.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgblx8263.dsc
   6.2.1-TIV-ITM_DOM-IF0004/kgbsol283.dsc
   6.2.1-TIV-ITM_DOM-IF0004/KGBWINNT.dsc
                       
5.0 Installation instructions 
=============================
This fix can be installed only over an existing installation.  Use
the following steps to install this fix.

 5.1 Before installing the fix
 -----------------------------
 - The prerequisites listed under section 3.1 entitled 'Prerequisites
   for this fix' must be installed before this fix can be installed.

 - For the purpose of this README, the <CANDLEHOME> symbol is the
   IBM Tivoli Monitoring installation directory. The default value
   for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
   on Windows systems.

   Before installing this fix on UNIX systems, set the environment 
   variable CANDLEHOME to the IBM Tivoli Monitoring installation 
   directory.

   For example: 
   > CANDLEHOME=/opt/IBM/ITM 
   > export CANDLEHOME
   
 - Because there is no uninstallation utility for this fix, 
   perform a backup of your environment before installing this fix.

 5.2 Local agent update
 ----------------------
 1. Transfer the appropriate archive file
    (6.2.1-TIV-ITM_DOM-IF0004.tar or .zip) to a temporary directory
    on the system that contains the agent code to be updated.
    For the purpose of this README, the <TEMP> symbol represents the
    fully-qualified path to this directory.
    Note: On Windows systems, this path includes the drive letter.  

 2. Expand the archive file using the tar command on UNIX systems or
    an unzip utility on Windows systems. Expanding the file creates a 
    directory structure that contains fixes for all of the supported
    operating systems.

 3. Use the itmpatch command to install the fix for the operating
    system of that agent. For more information on the 
    itmpatch command, see section 6.2.      

    On UNIX systems, if the fix was expanded to 
    <TEMP>/6.2.1-TIV-ITM_DOM-IF0004, the install command is:
     
    > itmpatch -h <CANDLEHOME> 
       -i <TEMP>/6.2.1-TIV-ITM_DOM-IF0004/kgb_xxxxxx_tema_if0004.tar
       where:
       - xxxxxx corresponds to the value in the first column returned
           by the ./cinfo -i command. 
       
         In the following example, the file is: 
         kgb_aix523_tema_if0004.tar.        
         > ./cinfo -i
         gb      IBM Tivoli Monitoring for Domino
         aix523  Version: 06.21.00.04

    On Windows systems, if the fix was expanded to 
    <TEMP>\6.2.1-TIV-ITM_DOM-IF0004, the install command is:

    > itmpatch -h <CANDLEHOME> 
      -i <TEMP>\6.2.1-TIV-ITM_DOM-IF0004\kgb_winnt_tema_if0004.cab

 5.3 Remote agent update
 -----------------------
 1. Transfer the appropriate archive file 
    (6.2.1-TIV-ITM_DOM-IF0004.tar or .zip) to a temporary directory
    on the Tivoli Enterprise Monitoring Server system.
    For the purpose of this README, the <TEMP> symbol represents the
    fully-qualified path to this directory. 
    Note: On Windows systems, this path includes the drive letter.

 2. Expand the archive file using the tar command on UNIX systems or
    an unzip utility on Windows systems. Expanding the file creates a
    directory structure that contains fixes for all of the supported
    operating systems.

 3. To add the agent fix bundles into the remote deploy depot, use the
    tacmd addBundles command found in $CANDLEHOME/bin on UNIX systems
    or in %CANDLE_HOME%\bin on Windows systems. For more information
    on the tacmd addBundles command, see the IBM Tivili Monitoring Command 
    Reference.

    On UNIX systems,
    if the fix was expanded to <TEMP>/6.2.1-TIV-ITM_DOM-IF0004:
    > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.1-TIV-ITM_DOM-IF0004

    On Windows systems,
    if the fix was expanded to <TEMP>/6.2.1-TIV-ITM_DOM-IF0004:
    > %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.1-TIV-ITM_DOM-IF0004

    where:
      -n indicates that prerequisite bundles are not automatically
         added. The -n parameter must be used because the fix 
         directory does not contain any prerequisites that the fix
         might require.  See Section 3.1 for the prerequisites
         for this fix.
      -i is the directory that contains the deployment bundles to be
         added to the depot. 

 4. To log in to the Tivoli Enterprise Monitoring Server, and deploy
    the fix to the appropriate nodes where the agent is running, use
    the following tacmd commands.  For more information on the
    tacmd login and updateAgent commands, see the IBM Tivili Monitoring 
    Command Reference.

    On a UNIX system: 
    > $CANDLEHOME/bin/tacmd login -s <server>
                                  -u <itmuser> 
                                  -p <password>

    > $CANDLEHOME/bin/tacmd listSystems
          
     The output shows the Managed System Name for the OS agent on the
     remote system to be updated. Use this value as the target of the
     tacmd updateAgent command.
     
    > $CANDLEHOME/bin/tacmd updateAgent -t gb
                                        -n <Managed system name> 
                                        -v 062100004

   On Windows systems:
    > %CANDLE_HOME%\bin\tacmd login -s <server>
                                    -u <itmuser> 
                                    -p <password>
                                    
    > %CANDLE_HOME%\bin\tacmd listSystems
          
    The output shows the Managed System Name for the OS agent on the
    remote system to be updated. Use this value as the target of the
    tacmd updateAgent command.

    > %CANDLE_HOME%\bin\tacmd updateAgent -t GB 
                                          -n <Managed system name>    
                                          -v 062100004

    Note:
    - The component (-t) for the updateAgent command is specified as 
      two characters (gb), not three characters (kgb).
    - The node (-n) for the updateAgent command is the managed system
      name of the operating system agent to be updated. The
      target node for an updateAgent command is always an OS agent.
     
 5.4 Agent support update
 ------------------------
 The agent support update is optional, and it is for the Tivoli Enterprise 
 Portal Server only. 
 
 This fix resolves three defects for agent support files: 108623, 109237, 
 and 109239. Section 2.2 contains descriptions of these defects. If the 
 attributes listed in the defect abstracts do not need to be shown in the 
 workspace view, or you want to add them to the workspace view manually, 
 you do not need to install the agent support update.
 
 Use the following steps to update the Tivoli Enterprise Portal Server.

 1. Transfer the appropriate archive file (6.2.1-TIV-ITM_DOM-IF0004.tar
    or .zip) to the IBM Tivoli Enterprise Portal Servers. 
    
 2. Expand the archive file using the tar command on UNIX systems or an 
    unzip utility on Windows systems. Expanding the file creates a directory structure that 
    contains fixes for all of the supported platforms.

 3. Expand the archive file (kgb_tems_teps_tepd_if0004.tar or .zip)
    that contains the updates for the Tivoli Enterprise Portal Server
    using the tar command on UNIX systems or an unzip utility on Windows
    systems. Expanding the file creates a directory structure that includes a 
    subdirectory called CD-ROM with the necessary updates.

 4. Start the Application Support Installer GUI to install the fix.  The GUI 
    install can be started by using one of the following commands from within 
    the CD-ROM directory where the setup.jar file is located: 
               
    On a UNIX system, GUI install:
     > ./itmasi.sh    

    On a Windows system, GUI install:
     > < itmasi
                       
    For a GUI install, when prompted by the Application Support Installer for the 
    installable media directory, select the CD-ROM directory, not the
    component directory. The installer can install updates for 
    multiple components at the same time.
     
 5. For a GUI install, the next panel presented by the Application Support 
    Installer asks for you to select the Tivoli Monitoring components to which 
    you want to add application support.  For this fix, the check boxes
    must be as follows:

    checked/unchecked - Tivoli Enterprise Monitoring Server (TEMS)
    checked/unchecked - Tivoli Enterprise Portal Server (TEPS)
    checked/unchecked - Tivoli Enterprise Desktop Client (TEPD)

    Continue through the remaining GUI panels selecting the IBM Tivoli Composite 
    Application Manager Agent for Lotus Domino - 06.21.00.04 support to complete 
    the installation.
     
 6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal 
    Browser was running when the update was installed, it must be 
    restarted.

6.0  Additional installation information
========================================
 6.1 Installation instructions for agent baroc file
  -----------------------------------------------------
  None.
  
 6.2 Additional information on using itmpatch command
 ----------------------------------------------------
 The itmpatch command has the following syntax:

 Usage: itmpatch -h <installation home> [OPTIONS]

 itmpatch -h <installation home> 
          -t { <patch_file_directory> | <patch_file> }
           
 itmpatch -h <installation home> 
          -i { <patch_file_directory> | <patch_file> }

 where:
 -h  Specifies the IBM Tivoli Monitoring installation directory.
 -i  Specifies the path to the directory or patch file to be installed.
 -t  Generates a report of the actions to be taken by the patch.
  

 For example, on UNIX systems:
 - To preview the fix installation, use the "-t" option:
   > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
    
 - To install the fix, use the "-i" option:
   > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
    
 where:   
 <CANDLEHOME> is the fully-qualified IBM Tivoli Monitoring 
 installation directory. On Windows systems, this command must include 
 the drive letter.
 <TEMP> represents the fully-qualified directory specification,
 where the fix is located. On Windows systems, this command must include 
 the drive letter.

 6.3 Verifying the update
 ------------------------
 1. To verify that the agent was updated correctly, use the tacmd command
    to view the current version of the agent after the agent is restarted.
    You are required to log in to a Tivoli Enterprise Monitoring
    Server before viewing the agent version.  
                 
    For example:
    On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
    installation directory. the default location is '/opt/IBM/ITM'.   
   
    > $CANDLEHOME/bin/tacmd login -s <server>
                                  -u <itmuser> 
                                  -p <password>
    > $CANDLEHOME/bin/tacmd listSystems -t gb

    On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
    Monitoring installation directory, the default location
    is 'C:\IBM\ITM'.   
     > %CANDLE_HOME%\bin\tacmd login -s <server>
                                     -u <itmuser> 
                                     -p <password>
                                    
    > %CANDLE_HOME%\bin\tacmd listSystems -t GB 
    Note:
    - The component (-t) for the tacmd listSystems command is specified 
      as two characters (gb), not three characters (KGB).
    
    When the agent update is successful, the agent version is 
    06.21.00.04.

    Note:
    - The component (-t) for the tacmd listSystems command is
    specified as two characters (gb), not three characters (kgb).

7.0 Known problems and workarounds
==================================
  Abstract: Domino server fails to restart if the IBM Tivoli Composite Application 
        Manager Agent for Lotus Domino is restarted manually during the procedure of 
        restarting the Domino server.
  Problem: When the Domino server is restarting and the Lotus Domino agent
        is restarted manually at the same 
        time, the Domino server cannot restart successfully. 
        The following error message can be found in the Domino server
        console and log file:
        
        Lotus Notes: error 0x1767
        2010-07-08 14:15:15: server shutdown complete
        Server exiting:
        Server is already running(in another process)
        
  Workaround: When the Domino server is restarting, do not try to restart 
              the Lotus Domino agent manually. The Lotus Domino agent
              restarts automatically.
  See the following Technote for details:  
  http://www-01.ibm.com/support/docview.wss?uid=swg21445708
              
  Abstract: The 32-bit Domino agents on 64-bit AIX and 64-bit Linux for
  IBM System z cannot be updated remotely.

  Problem: If the 32-bit Lotus Domino agents run on the 64-bit AIX systems or
  64-bit Linux for IBM System z systems, they cannot be updated
  remotely through the Tivoli Enterprise Portal client or command line. 
  
  Workaround: Update the agent locally instead of remotely.            

  
                
8.0 Additional product information
==================================
None.

9.0 Notices
=======
This information was developed for products and services offered in the United 
States. 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 grant 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.

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.

Trademarks and service marks
------------------------------------

IBM, the IBM logo, and ibm.com(R) 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(R) trademarks is available on the 
Web at "Copyright and trademark information" at 
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or 
both.

UNIX is a registered trademark of The Open Group in the United States 
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.