(C) Copyright International Business Machines Corporation 2009. All 
rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Microsoft(R) Applications: 
Active Directory Agent, Version 6.2.0
           
Component ID: 5724C71AO

Interim Fix 0006 (6.2.0-TIV-ITM_ADO-IF0006)

Date: February 25, 2009

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.3.
  
2.0 Problems fixed
===================
 The following problems are addressed by this fix.

  2.1 APARS
  ----------
   APAR: IZ40661    
   Abstract: ADO AGENT CRASHES WHEN GPO GUID IS BLANK
   Additional Information: The agent crashes while fetching 
   Group Policy Information if the GUID created for any group is blank.
  
  2.2 Defects
  ------------ 
   Defect: 91195
   Abstract: Default Sitution does not get triggered after upgrade. 
   Problem: Triggered default situations become untriggered after 
   6.2.0-TIV-ITM_ADO-LA0005 is installed.
   
   Defect: 92019
   Abstract: Memory leak in the agent.
   Problem: A memory leak is found in the agent when historical data 
   collection feature is turned on.
   
  2.3 Superseded fixes
  ----------------------
   6.2.0-TIV-ITM_ADO-LA0005
   6.2.0-TIV-ITM_ADO-LA0004
   6.2.0-TIV-ITM_ADO-LA0003
   6.2.0-TIV-ITM_ADO-LA0002
   6.2.0-TIV-ITM_ADO-LA0001

  2.4 APARS and defects included from superseded fixes
  -----------------------------------------------------
   6.2.0-TIV-ITM_ADO-LA0005
   -------------------------
   APAR: IZ37477
   Abstract: PING OPERATION FAILS TO PARSE PING OUTPUT ON NON ENGLISH M/C
   Additional Information: When the agent is installed on non-English 
   operating systems, the output of the domain controller availability is 
   not parsed correctly. The domain controller is shown as not available.
		
   6.2.0-TIV-ITM_ADO-LA0004
   -------------------------
   APAR: IZ37139
   Abstract: AD Agent crashes on Replication Latency Workspace
   Additional Information: The Monitoring Agent for Active Directory
   crashes on Replication Latency workspace. The agent enters an 
   infinite loop and crashes.
		  
   6.2.0-TIV-ITM_ADO-LA0003
   -------------------------  
   APAR: IZ26510    
   Abstract: Active Directory Agent crashes on DNSADIntegrated workspace 
   Additional Information: The Monitoring Agent for Active Directory crashes,
   when one of the domain controllers is unreachable. This happens when the 
   agent tries to retrieve the canonical name of that domain controller. 
	 
   6.2.0-TIV-ITM_ADO-LA0002
   ------------------------
   APAR: IZ21902     
   Abstract: After opening Group policy workspace, the agent hangs 
   Additional Information: While navigating the Group Policy Object 
   workspace, the Monitoring Agent for Active Directory stops data 
   collection and no data is displayed in the Tivoli Enterprise Portal.
   This occurs when the Group Policy Object name is  null.  

   6.2.0-TIV-ITM_ADO-LA0001
   ------------------------
   APAR: IZ13845     
   Abstract: AD Agent stops data collection at DCA
   Additional Information: The Monitoring Agent for Active Directory  
   stops data collection and no data is displayed in the Tivoli Enterprise 
   Portal. No error is displayed. In the Domain Controller Availability 
   workspace, data is collected by contacting the Sites for each Global Catalog
   Server. When the Global Catalog Server is available, but not reachable 
   due to any network issues, then the function GetSiteForServer hangs. 
   Hence, the Monitoring Agent for Active Directory stops performing the data 
   collection.
     
   APAR: IZ08797     
   Abstract: AD Agent Crashing - No. of Replication Partners exceeds 
   limit. Additional Information: The Monitoring Agent for Active Directory 
   crashes when the number of replication partners is greater than 64. No error
   is displayed. With this fix, the monitoring agent for active directory 
   supports 128 replication partners for an active directory domain controller.

   APAR: IZ10118    
   Abstract: ITM ADO Agent crashes when checking connectivity with replication 
   partners. Additional Information: The Monitoring Agent for Active Directory  
   crashes when it receives a ping response with a packet size larger than the 
   allocated buffer size. The agent log shows the error message 
   "Buffer too small" as the last message.
  
  
3.0 Architecture and prerequisites
==================================
 This fix is supported on all operating systems listed in Chapter 2 of 
 the IBM Tivoli Monitoring: Active Directory Agent User's Guide, 
 version 6.2.0.

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

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

 3.1 Prerequisites for this fix:
 -------------------------------
 - IBM Tivoli Monitoring, Version 6.2.0 
 - IBM Tivoli Monitoring, Version 6.2.0: Active Directory agent


4.0 Image directory contents
============================
 The fix image contains the following files:

 - 6.2.0-TIV-ITM_ADO-IF0006.README - This README file
 - 6.2.0-TIV-ITM_ADO-IF0006.tar - Fix archive .tar format
 - 6.2.0-TIV-ITM_ADO-IF0006.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.0-TIV-ITM_ADO-IF0006/k3z_tems_teps_tepd_if0006.tar
 - 6.2.0-TIV-ITM_ADO-IF0006/k3z_tems_teps_tepd_if0006.zip
 - 6.2.0-TIV-ITM_ADO-IF0006/k3z_winnt_tema_if0006.cab
 - 6.2.0-TIV-ITM_ADO-IF0006/K3ZWINNT.dsc
 - 6.2.0-TIV-ITM_ADO-IF0006/K3ZCONF.txt

5.0 Installation instructions 
==============================
 This fix can only be installed 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 symbol <CANDLEHOME> 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.
    
  5.2 Local agent update
  -----------------------
  1. Transfer the appropriate archive file (6.2.0-TIV-ITM_ADO-IF0006.zip) 
     to a temporary directory on the system that contains the agent 
     code to be updated. For the purpose of this README, the symbol 
     <TEMP> represents the fully qualified path to this directory. 
     Note: On Windows, this includes the drive letter. 

  2. Expand the archive file using the unzip utility on Windows systems. 
     This creates a directory structure that contains fixes for all of
     the supported platforms.  

  3. Use the itmpatch command to install the fix for that agent platform. 
     For more information on the itmpatch command, see section 6.1.
     
     On a Windows system, if the fix was expanded to 
     <TEMP>/6.2.0-TIV-ITM_ADO-IF0006, the install command would be:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>\6.2.0-TIV-ITM_ADO-IF0006\k3z_winnt_tema_if0006.cab

  5.3 Remote Agent Update
  -------------------------
  1. Transfer the appropriate archive file (6.2.0-TIV-ITM_ADO-IF0006.tar 
     or .zip) to a temporary directory on the IBM Tivoli Enterprise 
     Monitoring Server system.  For the purpose of this README, the 
     symbol <TEMP> represents the fully qualified path to this 
     directory. Note: On Windows, this includes the drive letter.

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

  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 Appendix A. Commands 
     reference of the IBM Tivoli Monitoring Administrator's Guide.
     
     On a UNIX system,
     if the fix was expanded to <TEMP>/6.2.0-TIV-ITM_ADO-IF0006:
     > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.0-TIV-ITM_ADO-IF0006 
                                        
     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
          may require. Please 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. 
     
     On a Windows system,
     if the fix was expanded to <TEMP>/6.2.0-TIV-ITM_ADO-IF0006: 
     > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.0-TIV-ITM_ADO-IF0006
                                         
     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
          may require. Please 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 login 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 Appendix A. Commands
     reference of the IBM Tivoli Monitoring Administrator's Guide.

     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 3Z 
                                         -n <Managed system name> 
			                 -v 062000006

     On a Windows system:
     > %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 3Z
                                           -n <Managed system name> 
					   -v 062000006

     Note:
     - The component (-t) for the updateAgent command is specified as 
       two characters (3Z), not three characters (K3Z).
     - The node (-n) for the updateAgent command is the managed system 
       name of the operating system (OS) agent to be updated. The
       target node for an updateAgent command is always an OS agent.
 
  5.4 Agent support update
  ------------------------------
  Use the following steps to update the Tivoli Enterprise Monitoring 
  Server, Tivoli Enterprise Portal Server or Tivoli Enterprise Portal 
  Desktop. 

  1. Transfer the appropriate archive file (6.2.0-TIV-ITM_ADO-IF0006.tar 
     or .zip) to the IBM Tivoli Enterprise Monitoring Servers, IBM 
     Tivoli Enterprise Portal Servers or Tivoli Enterprise Portal 
     Desktops.

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

  3. Expand the archive file (k3z_tems_teps_tepd_if0006.tar or .zip) 
     that contains the updates for Tivoli Enterprise Monitoring Server,
     Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal 
     Desktop using the tar command on UNIX systems or an unzip utility
     on Windows systems. This 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 can be started by using the following command from within 
     the CD-ROM directory where setup.jar is located.
     
     On a UNIX system:
     > $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar   
           
     On a Windows system:
        > <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar 
        
        where <"C:\Program Files\IBM\Java142"> is the default drive
        and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
        on your system may vary.          
	
     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. The next panel presented by the Application Support Installer asks 
     for the selection of which Tivoli Monitoring components you would 
     like to add application support to. For this fix, the check box 
     should be as follows:
             
             unchecked - Tivoli Enterprise Monitoring Server (TEMS)
             checked - Tivoli Enterprise Portal Server (TEPS)
             unchecked - Tivoli Enterprise Desktop Client (TEPD)

     Continue through the remaining GUI panels selecting the ADO 
     06.20.00.06 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 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 a UNIX system:
  - 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 full qualified IBM Tivoli Monitoring installation
  directory. On Windows, this must include the drive letter.
  <TEMP> represents the full qualified directory specification, where
  the fix is located. On Windows, this must include the drive letter.


  6.2 Verifying the update
  -------------------------
  1. To verify the agent was updated correctly, use the tacmd to view 
     the agent's current version.  You are required to login to a 
     Tivoli Enterprise Monitoring Server prior to viewing the agent 
     version.  

     For example:
     On a UNIX system, 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 3Z

     On a Windows system, 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 3Z 

     When the agent update is successful, the agent version should now 
     be:
     06.20.00.06
  
     Note:
     - The component (-t) for the tacmd listSystems command is 
       specified as two characters (3Z), not three characters (k3z).

  2. To verify the agent support files were updated correctly, use the 
     kincinfo command on Windows systems or the cinfo command on Linux
     or UNIX systems. The sample output below shows the versions of 
     the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
     Server, or Tivoli Enterprise Portal Desktop systems after this
     fix has been successfully applied.  

     Note:
     - The date of the build displayed may not be accurate. This is a
       known problem and is being addressed.      
     - The kincinfo and cinfo command output examples in the sections
       that follow show all components that can be updated.  If you do
       not have all of these components installed, then components not
       installed will not be displayed in the output of these commands. 

    Sample output for the cinfo command on a UNIX or Linux systems
    --------------------------------------------------------------
    To validate that all components have been installed, run the
    following command:

     ./cinfo
     
      This command offers you four options on the CINFO menu shown in
      the example that follows.  Choose the option that meets your 
      needs.

	*********** Thu Feb 19 17:43:39 IST 2009 ******************
    User: root Groups: root bin daemon sys adm disk wheel
    Host name : Unixbox6   Installer Lvl:06.20.01.00
    CandleHome: /opt/IBM/ITM
    ***********************************************************
        -- CINFO Menu --
     1) Show products installed in this CandleHome
     2) Show which products are currently running
     3) Show configuration settings
     4) Show installed CD release versions
     X) Exit CINFO
    1
   
    *********** Thu Feb 19 17:43:39 IST 2009 ******************
    User: root Groups: root bin daemon sys adm disk wheel
    Host name : Unixbox6   Installer Lvl:06.20.01.00
    CandleHome: /opt/IBM/ITM
    ***********************************************************
    ...Product inventory

         3z      Monitoring Agent for Active Directory
         tms     Version: 06.20.00.00
         tpd     Version: 06.20.00.00
         tps     Version: 06.20.00.06
         tpw     Version: 06.20.00.00


    Sample output of the kincinfo command on a Windows System
    ----------------------------------------------------------------
    To validate that all components have been installed, run the
    following command:

     For example:
     > %CANDLE_HOME%\InstallITM\kincinfo -i

    ******** Tuesday, February 17, 2009 5:33:54 PM *********
    User       : administrator Group     : NA
    Host Name  : Winbox6 Installer       Installer : Ver: 0NOVALUE00000
    CandleHome : C:\IBM\ITM
    ********************************************************
	
    ...Product Inventory

    PC  APPLICATION SUPPORT DESC                       PLAT   APP VER      BUILD
     INSTALL DATE

    3Z  Active Directory Support                       WICMS  06.20.00.00  200710181
    324  20090217 1223
    3Z  Active Directory Support                       WICNS  06.20.00.06  200902111
    001  20090217 1223
    3Z  IBM Eclipse Help for Active Directory          WIIEH  06.20.00.00  200710160
    711  20090217 1223
    3Z  Active Directory Support                       WIXEB  06.20.00.00  200710181
    324  20090217 1223
    3Z  Active Directory Support                       WIXEW  06.20.00.00  200710181
    324  20090217 1223

  6.3 Caching Configuration 
  -------------------------------------
    Caching Configuration: With this currently implemented mechanism of 
    configuring caching, the customer can enable or disable caching 
    and also set the cache interval. This is achieved by using an 
    environment variable "ADO_CACHE_INTERVAL" in the environment file 
    K3ZENV. When this fix is applied, a prescript (k3z_preinstall.cmd) 
    is run which sets the ADO_CACHE_INTERVAL in the K3ZENV file. 
    If the variable ADO_CACHE_INTERVAL already exists in the K3ZENV 
    file, the script quits without making any changes. 
    ADO_CACHE_INTERVAL not only acts as ON/OFF flag, but the value 
    which is given in seconds, forms the caching interval (time 
    interval between consecutive data collection). Any positive integer
    value turns ON the caching mechanism and negative or zero value 
    turns it OFF. The k3z_preinstall.cmd script verifies the present 
    installation of the Monitoring Agent for Active Directory. By 
    default the value of ADO_CACHE_INTERVAL is set as 0. The customer
    needs to turn it ON if required.
    
  
  Caching can be turned ON or OFF during run time through Manage Tivoli 
  Enterprise Monitoring Services (kinconfig.exe). The steps are as 
  follows:

    1. In Manage Tivoli Enterprise Monitoring Services (kinconfig.exe), 
	   select the Active Directory Agent.
    2. Right click and go to “Advanced” options.
    3. Select "Edit ENV File" from the options. This opens the 
       K3ZENV file for editing. 
    4. The ADO_CACHE_INTERVAL variable exists in the K3ZENV file.
       To turn OFF caching, set ADO_CACHE_INTERVAL to 0. 
       To turn ON caching, set ADO_CACHE_INTERVAL to any positive 
       integer value. This value forms the caching interval 
       in seconds. For instance, a value of 180 would mean a
       3 minute interval. 
    5. After editing the K3ZENV file, save and close the file to 
       implement the new cache interval value.
    6. A message box will appear asking if agent needs to be recycled 
       to include the changes in agent functionality. 
       - "Yes" recycles the agent with the new caching interval value. 
       - "No" lets the agent continue to run without the changes to 
         caching interval. When the agent is restarted, the changes 
	 will be implemented.

    Note: A negative or zero value turns off caching. 
          Non-integers (alphabetics, special characters and 
	  alphanumerics are not supported for the cache interval and 
	  might result in unexpected behavior of the Monitoring Agent
	  for Active Directory. The value recommended for the cache 
	  interval is 240 seconds.

  6.4 Disabling the GetSiteForServer function
  ---------------------------------------------------
    In Domain Controller Availability workspace, there are two 
    attributes GCs InSite and GCs InSite Pinged. Data collection for 
    these attributes is done by connecting to the sites of each Global 
    Catalog in the Active Directory network. The Sites of each Global 
    Catalog are connected by using a function "GetSiteForServer". 
    With this currently implemented mechanism, you can enable or 
    disable this GetSiteForServer functionality. This is achieved by 
    using an environment variable "ADO_GETSITEFORSERVER_FLAG" in the 
    environment file K3ZENV. When this fix is applied, a prescript 
    (k3z_preinstall.cmd) is run which sets the ADO_GETSITEFORSERVER_FLAG
    in the K3ZENV file. If the ADO_GETSITEFORSERVER_FLAG already exists 
    in the K3ZENV file, the script quits without making any changes. 
    
    The default value of the variable ADO_GETSITEFORSERVER_FLAG 
    variable is "ON" which enables the GetSiteForServer function.

    The value "OFF" for ADO_GETSITEFORSERVER_FLAG disables the 
    GetSiteForServer functionality. If the functionality is disabled, 
    then the data collection is not done for the two attributes 
    GCs InSite and GCs InSite Pinged in the workspace Domain Controller
    Availability. Hence, their values will be displayed as 
    "Not_Collected" in the Tivoli Enterprise Portal. 	  
    
    To turn the GetSiteForServer ON or OFF during run time use the 
    Manage Tivoli Enterprise Monitoring Services (kinconfig.exe). The 
    steps are as follows:

    1. In Manage Tivoli Enterprise Monitoring Services (kinconfig.exe), 
	   select the Active Directory Agent.
    2. Right click and go to “Advanced” options.
    3. Select "Edit ENV File" from the options. This opens the 
       K3ZENV file for editing. 
    4. The ADO_GETSITEFORSERVER_FLAG variable exists in the K3ZENV file.
       To disable the GetSiteForServer, set ADO_GETSITEFORSERVER_FLAG 
       to 0FF. 
       To enable the GetSiteForServer, set ADO_GETSITEFORSERVER_FLAG 
       to ON.
    5. After editing the K3ZENV file, save and close the file to 
       implement the new flag value.
    6. A message box appears asking if agent needs to be recycled 
       to include the changes in agent functionality. 
       - "Yes" recycles the agent with the new flag value. 
       - "No" lets the agent continue to run without the changes to 
         flag value. When the agent is restarted, the changes are
	 implemented.

7.0 Known problems and workarounds
==================================
 None.
 

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 Corporation in the 
United States, other countries, or both. If these and other IBM 
trademarked terms are marked on their first occurrence in this 
information with a trademark symbol (R or TM), these symbols 
indicate U.S. registered or common law trademarks owned by IBM 
at the time this information was published. Such trademarks may 
also be registered or common law trademarks in other countries. 
current list of IBM trademarks is available on the Web at 
"Copyright and trademark information" at 
http://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.

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