(C) Copyright International Business Machines Corporation 2007, 2008.
All rights reserved.

Date: October 29, 2008

IBM(R) Tivoli(R) Monitoring, Version 6.2.0: Fix Pack 2

Table of contents:

1.0 GENERAL DESCRIPTION
    1.1 INSTALLATION INSTRUCTIONS
    1.2 VALIDATING WHAT YOU INSTALLED
    1.3 BACKWARD COMPATIBILITY WITH PRIOR VERSIONS OF THIS PRODUCT
2.0 PROBLEMS FIXED
    2.1 PROBLEMS FIXED IN FIX PACK 6.2.0-TIV-ITM-FP0002
    2.2 PROBLEMS FIXED IN INTERIM FIX 6.2.0.1-TIV-ITM-IF0002
    2.3 PROBLEMS FIXED IN INTERIM FIX 6.2.0.1-TIV-ITM-IF0001
    2.4 FIXES FORWARDED FROM 6.1.0.7-TIV-ITM-IF0001
    2.5 FIXES FORWARDED FROM 6.1.0.7-TIV-ITM-IF0002
    2.6 FIXES FORWARDED FROM 6.1.0-TIV-ITM-FP0007
3.0 PREREQUISITES OR COREQUISITES
4.0 NEW AND DEPRECATED PLATFORM SUPPORT
5.0 FIX PACK IMAGE DIRECTORY CONTENTS
6.0 KNOWN PROBLEMS AND WORKAROUNDS
    6.1 LIMITED SUPPORT FOR WINDOWS SERVER 2008
7.0 NOTICES



1.0 GENERAL DESCRIPTION
=======================

 This is a cumulative fix pack for IBM Tivoli Monitoring, Version 6.2.0.
 This fix pack supersedes all previous IBM Tivoli Monitoring versions,
 including the most recent, Version 6.2.0 Fix Pack 1 Interim fix 2
 (6.2.0.1-TIV-ITM-IF0002).

 The rest of this section is a summary of what to expect when installing
 this maintenance deliverable.

 The IBM Tivoli approach for IBM Tivoli Monitoring fix packs and interim
 fixes is to deliver regular, incremental quality improvements.

 The main areas of quality improvements that are made in this maintenance
 deliverable relative to the most recently shipped Tivoli Monitoring
 maintenance (IBM Tivoli Monitoring 6.2.0 Fix Pack 1 Interim Fix 2) are shown
 below.  A complete list of all of the quality improvements made can be
 found in section 2.0 PROBLEMS FIXED.

 - Resolution of several eWAS related scenarios that can prevent the user
   from successfully logging into the TEP after an upgrade.  (APARs IZ24556,
   IZ26644, IZ26713, IZ26837, and IZ26870)

 - APAR parity with IBM Tivoli Monitoring 6.2.0 Fix Pack 1 Interim Fix 2.


1.1 INSTALLATION INSTRUCTIONS
-----------------------------

 NOTE: Please read this entire section before proceeding with the upgrade.

 - As a best practice, it is recommended that all running IBM Tivoli
   Monitoring processes must be stopped manually prior to performing an
   upgrade from a previous version or maintenance level to IBM Tivoli
   Monitoring 6.2.0 Fix Pack 2.  While the upgrade installer will attempt to
   stop all running process, there are times when a running process will fail
   to stop and lead to unexpected upgrade failures if the upgrade is allowed
   to continue.  If any process fails to stop during a manual shutdown,
   restart the system before proceeding with the upgrade.

 - VERY IMPORTANT: Before a TEPS Upgrade Installation, each respective
   directory requires the following available space:

   Unix/Linux:
   $CANDLEHOME (/opt/IBM/ITM)   1300 MB
   /tmp/                         300 MB

   Windows:
   %CANDLEHOME% (C:\IBM\ITM)    1100 MB

 - The following information applies to users upgrading from IBM Tivoli
   Monitoring 6.1 using a non-root user ID for the TEMS and TEPS.  These
   steps assume the itmuser user ID and itmgrp group have been created.

   1.  Perform the TEMS and TEPS upgrade while signed on as user itmuser
   2.  During the installation of gskit, enter the root password when
       prompted.
   3.  After the installation completes, run "SetPerm -a" as user root
   4.  Optionally, if TEMS security was enabled, run "SetPerm -s" as user
       root to re-enable TEMS security.
   5.  Add Application Support to the HUB TEMS
   6.  Configure TEPS as user root (This step will run the
       InstallPresentation and add application support on the TEPS.
   7.  Execute the following command as user root to change the ownership of
       all files in $CANDLEHOME to user itmuser and group itmgrp:

       chown -Rf itmuser:itmgrp $CANDLEHOME

   8.  Run "SetPerm -a" as root user again
   9.  Optionally, if TEMS security was enabled, run "SetPerm -s" as user
       root to re-enable TEMS security.
   10. Start the HUB TEMS and TEPS as user itmuser

 - IBM Tivoli Monitoring 6.2 Fix Pack 1 Installation Guide, table 17
   "Supported databases for the portal server", footnote 8 states:

   For Linux on zSeries, you must modify the /<install_dir>/config/cq.ini
   file by changing the $DB2DIR$/lib value in LD_LIBRARY_PATH and SHLIB_PATH
   to $DB2DIR$/lib32 or adding $DB2DIR$/lib32 before $DB2DIR$/lib.

   This workaround is NOT required and can be safely ignored.  The footnote
   will be corrected in a future update of the documentation.

 - Before installing, execute the cinfo/kincinfo command per the
   instructions in section 1.2 below.  After the installation completes, this
   will help in validating the installation.  When you complete the
   installation, continue with section 1.2 below to complete the installation
   validation.

 - Additional notes for upgrading TEPS that is running as non-root on AIX
   or Linux Systems (APAR IZ24556).

   If the TEPS is running as non-root on Unix or Linux systems and you plan
   to upgrade using a non-root user ID, then the following procedure must be
   performed prior to upgrade.

   Step 1:

   In the following example the TEPS database is called "TEPS" and the
   db2 user used is "itmuser".  Also the db2admin ID is "db2inst1".

   1) Log in as the db2 admin:

      su - db2inst1

   2) Connect to the TEPS database as the TEPS db2 user ID:

      db2 connect to TEPS user itmuser using ********

      (where ******** is the password)

   3) Get the authorizations for the TEPS user ID:

      $ db2 get authorizations

       Administrative Authorizations for Current User

       Direct SYSADM authority                    = NO
       Direct SYSCTRL authority                   = NO
       Direct SYSMAINT authority                  = NO
       Direct DBADM authority                     = NO
       Direct CREATETAB authority                 = NO
       Direct BINDADD authority                   = NO
       Direct CONNECT authority                   = NO
       Direct CREATE_NOT_FENC authority           = NO
       Direct IMPLICIT_SCHEMA authority           = NO
       Direct LOAD authority                      = NO
       Direct QUIESCE_CONNECT authority           = NO
       Direct CREATE_EXTERNAL_ROUTINE authority   = NO
       Direct SYSMON authority                    = NO

       Indirect SYSADM authority                  = NO
       Indirect SYSCTRL authority                 = NO
       Indirect SYSMAINT authority                = NO
       Indirect DBADM authority                   = NO
       Indirect CREATETAB authority               = YES
       Indirect BINDADD authority                 = YES
       Indirect CONNECT authority                 = YES
       Indirect CREATE_NOT_FENC authority         = NO
       Indirect IMPLICIT_SCHEMA authority         = YES
       Indirect LOAD authority                    = NO
       Indirect QUIESCE_CONNECT authority         = NO
       Indirect CREATE_EXTERNAL_ROUTINE authority = NO
       Indirect SYSMON authority                  = NO

      $

      If the settings below are not set to YES, as shown, then perform
      steps 4) to 5) below:

       Direct DBADM authority                     = YES
       Direct CREATETAB authority                 = YES
       Direct BINDADD authority                   = YES
       Direct CONNECT authority                   = YES
       Direct CREATE_NOT_FENC authority           = YES
       Direct IMPLICIT_SCHEMA authority           = YES
       Direct LOAD authority                      = YES
       Direct QUIESCE_CONNECT authority           = YES
       Direct CREATE_EXTERNAL_ROUTINE authority   = YES

   4) Connect to the TEPS database as the db admin ID:

      db2 connect to TEPS user db2inst1 using ********

   5) Grant authorizations to the TEPS db2 user ID:

      db2 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,
      IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON DATABASE
      to user itmuser

   6) Reconnect to the TEPS database as the TEPS db2 user ID and re-check the
      authorizations

      db2 connect to TEPS user itmuser using ********

         Database Connection Information

       Database server        = DB2/LINUX 8.2.8
       SQL authorization ID   = ITMUSER
       Local database alias   = TEPS

      [db2inst1@rimmer ~]$ db2 get authorizations

       Administrative Authorizations for Current User

       Direct SYSADM authority                    = NO
       Direct SYSCTRL authority                   = NO
       Direct SYSMAINT authority                  = NO
       Direct DBADM authority                     = YES
       Direct CREATETAB authority                 = YES
       Direct BINDADD authority                   = YES
       Direct CONNECT authority                   = YES
       Direct CREATE_NOT_FENC authority           = YES
       Direct IMPLICIT_SCHEMA authority           = YES
       Direct LOAD authority                      = YES
       Direct QUIESCE_CONNECT authority           = YES
       Direct CREATE_EXTERNAL_ROUTINE authority   = YES
       Direct SYSMON authority                    = NO

       Indirect SYSADM authority                  = NO
       Indirect SYSCTRL authority                 = NO
       Indirect SYSMAINT authority                = NO
       Indirect DBADM authority                   = NO
       Indirect CREATETAB authority               = YES
       Indirect BINDADD authority                 = YES
       Indirect CONNECT authority                 = YES
       Indirect CREATE_NOT_FENC authority         = NO
       Indirect IMPLICIT_SCHEMA authority         = YES
       Indirect LOAD authority                    = NO
       Indirect QUIESCE_CONNECT authority         = NO
       Indirect CREATE_EXTERNAL_ROUTINE authority = NO
       Indirect SYSMON authority                  = NO

      You should now see the authorizations for the following items as YES:

       Direct DBADM authority                     = YES
       Direct CREATETAB authority                 = YES
       Direct BINDADD authority                   = YES
       Direct CONNECT authority                   = YES
       Direct CREATE_NOT_FENC authority           = YES
       Direct IMPLICIT_SCHEMA authority           = YES
       Direct LOAD authority                      = YES
       Direct QUIESCE_CONNECT authority           = YES
       Direct CREATE_EXTERNAL_ROUTINE authority   = YES

   Step 2 (This step only applies to AIX.  If you are not running your TEPS
   on AIX, then skip it.)

   As the *root* user, the AIX command slibclean must be run

   su -c "/usr/sbin/slibclean"

 You should now proceed to the step-by-step installation and setup
 instructions.  This information can be found in the Installation and Setup
 Guide in the IBM Tivoli Monitoring 6.2 Information Center that can be
 accessed using the following URL:

 http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc/


1.2 VALIDATING WHAT YOU INSTALLED
---------------------------------

 You can validate your installation by running the kincinfo command on
 Windows or the cinfo command on Linux or UNIX.  If you run these commands
 before and after your upgrade, you can clearly see the component versions
 that have changed.

 Only components that have been updated during this release have the
 current listed version (6.20.02.00).  If a component has not been updated,
 the component will list the most recent GA copy, which could be less than
 the current version.  The installation programs ensure that all provided
 components are maintained at the latest available version.

 Note: 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 kincinfo command on Windows
 -------------------------------------------------

 The following example shows the output of the kincinfo -i command:
    >kincinfo -i

 *********** Monday, October 27, 2008 10:14:19 AM ************
 User       : Administrator         Group     : NA
 Host Name  : ITMSERV1              Installer : Ver: 062002000
 CandleHome : C:\IBM\ITM
 Installitm : C:\IBM\ITM\InstallITM
 *************************************************************
 ...Product Inventory

 A4        i5/OS Support
           WINNT Version: 06.20.02.00 Build: 200810091725

 A4        i5/OS Support
           WINNT Version: 06.20.02.00 Build: 200810091726

 A4        i5/OS Support
           WINNT Version: 06.20.02.00 Build: 200810091726

 A4        i5/OS Support
           WINNT Version: 06.20.02.00 Build: 200810091725

 AX        Tivoli Enterprise Monitoring Agent Framework
           WINNT Version: 03.50.07.00 Build: 200701051459

 CJ        Tivoli Enterprise Portal Desktop Client
           WINNT Version: 06.20.02.00 Build: 200810172140

 CQ        Tivoli Enterprise Portal Server
           WINNT Version: 06.20.02.00 Build: 200810172138

 CW        Tivoli Enterprise Portal Browser Client
           WINNT Version: 06.20.02.00 Build: 200810172139

 GL        Tivoli Enterprise Monitoring Agent Framework
           WINNT Version: 06.20.02.00 Build: 200810201725

 HD        Warehouse Proxy
           WINNT Version: 06.20.02.00 Build: 200810172134

 IT        TEC GUI Integration
           WINNT Version: 06.20.02.00 Build: 200707230704

 IT        TEC GUI Integration
           WINNT Version: 06.20.02.00 Build: 200707230704

 IT        TEC GUI Integration
           WINNT Version: 06.20.02.00 Build: 200707230704

 IW        Tivoli Enterprise Portal Server Extensions
           WINNT Version: 06.10.13.00 Build: 200810172140

 KF        IBM Eclipse Help Server
           WINNT Version: 06.20.02.00 Build: 200810171759

 LZ        Linux OS Support
           WINNT Version: 06.20.02.00 Build: 200810201056

 LZ        Linux OS Support
           WINNT Version: 06.20.02.00 Build: 200810201056

 LZ        Linux OS Support
           WINNT Version: 06.20.02.00 Build: 200810201056

 LZ        Linux OS Support
           WINNT Version: 06.20.02.00 Build: 200810201056

 MS        Tivoli Enterprise Monitoring Server
           WINNT Version: 06.20.02.00 Build: 200810172135

 NS        NLS Support
           WINNT Version: 03.50.07.00 Build: 200510061051

 NT        Monitoring Agent for Windows OS
           WINNT Version: 06.20.02.00 Build: 200810090913

 NT        Windows OS Support
           WINNT Version: 06.20.02.00 Build: 200810090913

 NT        Windows OS Support
           WINNT Version: 06.20.02.00 Build: 200810090913

 NT        Windows OS Support
           WINNT Version: 06.20.02.00 Build: 200810090913

 NT        Windows OS Support
           WINNT Version: 06.20.02.00 Build: 200810090913

 SY        Summarization and Pruning Agent
           WINNT Version: 06.20.02.00 Build: 200810140959

 SY        Summarization and Pruning Agent
           WINNT Version: 06.20.02.00 Build: 200810140959

 SY        Summarization and Pruning Agent
           WINNT Version: 06.20.02.00 Build: 200810140959

 SY        Summarization and Pruning Agent
           WINNT Version: 06.20.02.00 Build: 200810140959

 TM        IBM Tivoli Monitoring 5.x Endpoint Support
           WINNT Version: 06.20.02.00 Build: 200707231141

 TM        IBM Tivoli Monitoring 5.x Endpoint Support
           WINNT Version: 06.20.02.00 Build: 200707231141

 UF        Universal Agent Framework
           WINNT Version: 06.20.02.00 Build: 200809270418

 UI        Tivoli Enterprise Services User Interface
           WINNT Version: 06.20.02.00 Build: 200810172135

 UL        UNIX Logs Support
           WINNT Version: 06.20.02.00 Build: 200809291105

 UL        UNIX Logs Support
           WINNT Version: 06.20.02.00 Build: 200809291105

 UL        UNIX Logs Support
           WINNT Version: 06.20.02.00 Build: 200809291105

 UL        UNIX Logs Support
           WINNT Version: 06.20.02.00 Build: 200809291104

 UM        Universal Agent
           WINNT Version: 06.20.02.00 Build: 200809270418

 UM        Universal Agent Support
           WINNT Version: 06.20.02.00 Build: 200809270417

 UM        Universal Agent Support
           WINNT Version: 06.20.02.00 Build: 200809270418

 UM        Universal Agent Support
           WINNT Version: 06.20.02.00 Build: 200809270417

 UM        Universal Agent Support
           WINNT Version: 06.20.02.00 Build: 200809270417

 UX        UNIX OS Support
           WINNT Version: 06.20.02.00 Build: 200810201043

 UX        UNIX OS Support
           WINNT Version: 06.20.02.00 Build: 200810201043

 UX        UNIX OS Support
           WINNT Version: 06.20.02.00 Build: 200810201043

 UX        UNIX OS Support
           WINNT Version: 06.20.02.00 Build: 200810201043


 Sample output for the cinfo command on UNIX or Linux
 ----------------------------------------------------

 To validate that all components have been installed, run the following
 command:

 ./cinfo -i

 *********** Mon Oct 27 19:32:45 EDT 2008 ******************
 User: root Groups: root bin daemon sys adm disk wheel
 Host name : itmserv2       Installer Lvl:06.20.02.00
 CandleHome: /products/IBM/ITM
 ***********************************************************
 ...Product inventory

 a4      Monitoring Agent for i5/OS
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 ax      IBM Tivoli Monitoring Shared Libraries
          lia246  Version: 06.20.02.00
          ls3263  Version: 06.20.02.00

 cq      Tivoli Enterprise Portal Server
          ls3263  Version: 06.20.02.00

 cw      Tivoli Enterprise Portal Browser Client
          ls3263  Version: 06.20.02.00

 hd      Warehouse Proxy
          ls3263  Version: 06.20.02.00
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 it      TEC GUI Integration
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 iw      IBM Tivoli Enterprise Portal Server Extensions
          ls3263  Version: 06.10.13.00

 jr      Tivoli Enterprise-supplied JRE
          lia266  Version: 04.29.00.00
          ls3263  Version: 05.05.00.00

 kf      IBM Eclipse Help Server
          ls3263  Version: 06.20.02.00

 lz      Monitoring Agent for Linux OS
          lia266  Version: 06.20.01.00
          ls3263  Version: 06.20.02.00
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 ms      Tivoli Enterprise Monitoring Server
          ls3263  Version: 06.20.02.00

 nt      Monitoring Agent for Windows OS
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 oq      Monitoring Agent for Microsoft SQL Server
          tms     Version: 06.20.00.00
          tps     Version: 06.20.00.00
          tpw     Version: 06.20.00.00

 or      Monitoring Agent for Oracle
          tms     Version: 06.20.00.00
          tps     Version: 06.20.00.00
          tpw     Version: 06.20.00.00

 oy      Monitoring Agent for Sybase Server
          tms     Version: 06.20.00.00
          tps     Version: 06.20.00.00
          tpw     Version: 06.20.00.00

 p5      Base Monitoring Agent for AIX
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 ph      Base Monitoring Agent for HMC
          tms     Version: 06.10.01.00
          tps     Version: 06.10.01.00
          tpw     Version: 06.10.01.00

 pk      Base Monitoring Agent for CEC
          tms     Version: 06.10.02.00
          tps     Version: 06.10.02.00
          tpw     Version: 06.10.02.00

 pv      Base Monitoring Agent for VIOS
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 px      Premium Monitoring Agent for AIX
          tms     Version: 06.10.01.00
          tps     Version: 06.10.01.00
          tpw     Version: 06.10.01.00

 qr      Monitoring Agent for Microsoft Virtual Server
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 qv      Monitoring Agent for VMware ESX
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 qx      Monitoring Agent for Citrix Access Suite
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 sh      Tivoli Enterprise Monitoring SOAP Server
          ls3263  Version: 06.20.02.00

 sy      Summarization and Pruning Agent
          ls3263  Version: 06.20.02.00
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 tm      Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00

 ud      Monitoring Agent for DB2
          tms     Version: 06.20.00.00
          tps     Version: 06.20.00.00
          tpw     Version: 06.20.00.00

 uf      Universal Agent Framework
          ls3263  Version: 06.20.02.00

 ui      Tivoli Enterprise Services User Interface
          lia246  Version: 06.20.02.00
          ls3263  Version: 06.20.02.00

 ul      Monitoring Agent for UNIX Logs
          ls3263  Version: 06.20.02.00
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 um      Universal Agent
          ls3263  Version: 06.20.02.00
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 ux      Monitoring Agent for UNIX OS
          tms     Version: 06.20.02.00
          tps     Version: 06.20.02.00
          tpw     Version: 06.20.02.00

 va      Premium Monitoring Agent for VIOS
          tms     Version: 06.10.00.00
          tps     Version: 06.10.00.00
          tpw     Version: 06.10.00.00

 ******************************************


1.3 BACKWARD COMPATIBILITY WITH PRIOR VERSIONS OF THIS PRODUCT
--------------------------------------------------------------

 This is a cumulative fix pack that includes all maintenance from prior
 levels of IBM Tivoli Monitoring.  It can be installed in just one step on
 top of any level of IBM Tivoli Monitoring version 6.1.0 or 6.2.0.


2.0 PROBLEMS FIXED
===================

2.1 PROBLEMS FIXED IN FIX PACK 6.2.0-TIV-ITM-FP0002
---------------------------------------------------

 Tivoli Enterprise Monitoring Installation APARs
 -----------------------------------------------

 APAR IZ24556 - TEPS INIT FAILS AFTER UPGRADE 6.2 TO 6.2 FP1 EWAS NOT UPGRADED

 Symptoms:
   After installing or upgrading to IBM Tivoli Monitoring 6.2.0 Fix Pack 1, Fix
   Pack 1 Interim Fix 1 or Fix Pack 1 Interim Fix 2, TEPS will not start due
   to a down-level version of eWAS being detected by the TEPS.  When this
   error occurs, the eWAS SystemOut.log file will contain a message like the
   following:

   WebSphere Platform 6.1 [embeddedEXPRESS 6.1.0.3 cf40644.23]

 APAR IZ26644 - LACK OF /TMP SPACE DURING 62FP1 UPGRADE - CANNOT LOGIN TO TEPS

 Symptoms:
   After upgrading a UNIX or Linux TEPS to IBM Tivoli Monitoring 6.2.0 Fix Pack
   1, Fix Pack 1 Interim Fix 1 or Fix Pack 1 Interim Fix 2, it is no longer
   possible to log in to the TEPS from the TEP console (browser or client).
   There are no obvious signs during the upgrade that anything went wrong.

   After the TEPS server has been restarted, trying to log in to the TEPS
   will result in the error message below:

   KFWITM009I The Tivoli Enterprise Portal Server is still being
   initialized and is not ready for communications.

   This APAR addresses problems with the upgrade caused by lack of space
   in /tmp file system.


 APAR IZ26713 - OPERATING SYSTEM NOT SUPPORTED - CANNOT LOGIN TO TEPS

 Symptoms:
   After upgrading a RedHat 5.1 or Windows 2003 SE 64-bit SP2 TEPS to IBM
   Tivoli Monitoring 6.2.0 Fix Pack 1, Fix Pack 1 Interim Fix 1 or Fix Pack 1
   Interim Fix 2, it is no longer possible to log in to the TEPS from the TEP
   console (browser or client).  There are no obvious signs during the
   upgrade that anything went wrong.

   After the TEPS server has been restarted, trying to log in to the TEPS
   will result in the error message below:

   KFWITM009I The Tivoli Enterprise Portal Server is still being
   initialized and is not ready for communications.

   This APAR addresses problems with the upgrade caused by the Update
   Installer failing to recognize RedHat 5.1 and Windows 2003 SE 64-bit
   SP2 as supported operating systems.


 APAR IZ26837 - BAD PLUGIN NAMES AFTER 6.2FP1 UPG - CANNOT LOGIN TO TEPS

 Symptoms:
   During upgrade to IBM Tivoli Monitoring TEPS 6.2.0 Fix Pack 1, you receive
   the following errors during TEPS configuration.

   Note: the TEC configuration panel still appears and accepts configuration
   data.

   Popup - Callpoint preconfig response file content:
    Tivoli Portal Server
   Failed to deploy [kfwewas.properties]

   Note: The popup error is displayed 3 times.

   You may also see a message box that states:
   !Error: BuildPresentation failed.
   -- Refer to the Problem Determination Guide for
             troubleshooting help
   -- After correcting the reason for failure
   -- rerun BuildPresentation.bat from the CNPS directory
   -- in "CANDLE_HOME" and restart TEPS.


  When installation is complete and the TEPS server has been
  started, trying to log in to the TEPS will result in the
  error message below:

  KFWITM009I The Tivoli Enterprise Portal Server is still being
  initialized and is not ready for communications.


 APAR IZ26870 - LDAP CONNECTION MESSAGE DURING TEPS CONFIG 6.2FP1 UPGRADE

 Symptoms:

   During the upgrade to IBM Tivoli Monitoring 6.2.0 Fix Pack 1, you receive
   the following message during TEPS configuration:

   ***************************
   Response file information
   Callpoint postconfig response file content:
   Tivoli Portal Server
   LDAP connection cannot be configured - verify firewall setting
   and LDAP connection parameters.  To configure with updated LDAP
   parameters, reconfigure the Tivoli Enterprise Server.
   Tivoli Enterprise Browser client
   INST_COMP_PLUGIN_RETURN_CODE:000
   ----- WebHelp to Eclipse Help Converter -----

   After clicking OK, the user is still able to proceed with the
   installation.  The user may see the message two more times before the
   installation moves on.  The TEPS does configure and start after the
   upgrade.

   The message will occur regardless of the LDAP checkbox settings in the
   TEPS (or TEMS) configuration boxes.

   In the event this message occurs, the embedded WAS does not upgraded as it
   should.  The version of eWAS contained in IBM Tivoli Monitoring 6.2.0
   Fix Pack 1 is 6.1.0.13.


 APAR IZ27003 - DIGUP DOES NOT CORRECTLY DETERMINE BIT MODE FOR LINUX

 Symptoms:
   The digup script didn't handle and record 64 bit machine types in
   the output.  It only tested for 64 bit on zLinux machines.

 APAR IZ27811 - SETPERM IN 6.2 FP1 CREATES INCORRECT LINK FOR X86_64 SYSTEMS

 Symptoms:
   SetPerm in 6.2 Fix Pack 1 creates an incorrect link for x86_64 systems.
   This causes the kddos binary to fail with the following error message when
   the Oracle agent is run as non-root after SetPerm has been run.

   kddos: error while loading shared libraries: libkbb.so: cannot open
   shared object file: No such file or directory

 APAR IZ28884 - SLOW PERFORMANCE DURING INSTALL STARTUP AND CLOSE DOWN
                (ITM 6.2 GA OR ITM 6.2 FP1 INSTALL)

 Symptoms:
   After launching setup.exe, the user must wait an extended period of time
   before the Welcome screen appears.  After pressing Finish on the last
   install screen, the user must wait an extended period of time before the
   install actually completes.


 Tivoli Enterprise Monitoring Server APARs
 -----------------------------------------

 APAR IZ20689 - TEMS CRASHES DURING STARTUP

 Symptoms:
   TEMS crash during situation autostart process at startup.


 APAR IZ21497 - TACMD CREATESIT PROBLEMS WITH SITINFO

 Symptoms:
   The tacmd createsit and editsit commands did not allow "Informational" as
   a valid SITINFO severity.


 APAR IZ25855 - TACMD EDITUSER NOT CORRECTING AMMENDING USER ACCOUNT

 Symptoms:
   The tacmd editUser and tacmd editUserGroup commands do not modify the
   memberOf and members details correctly.  Running the command clears the
   member of and members value.  Also when editing other properties the
   memberOf and members details are reset.


 APAR IZ26697 - WRONG TYPE FOR EMBEDDING SITUATION IS SHOWN ON TEP

 Symptoms:
   When a pure event situation is created and then embedded into another
   situation, it becomes a sampled, or polled situation.  This type of
   situation is being treated as PURE at the TEP.


 APAR IZ26838 - TACMD EXPORTWORKSPACES FAILS WITH JAPANESE WORKSPACE NAME.

 Symptoms:
   While exporting workspaces in a Japanese environment, the file name is
   truncated even though the workspaces information was written to the file
   correctly.


 APAR IZ28981 - TACMD CREATESIT -I FAILS WITH KUICCS007E.

 Symptoms:
   The tacmd createsit -i command fails to create a situation if the TEC
   forwarding option is disabled on the TEMS.


 APAR IZ30495 - CT_ACK CRASHES HUB TEMS ON WINDOWS

 Symptoms:
   Simultaneous SOAP requests to a HUB TEMS that has LDAP enabled can result
   in the HUB TEMS crashing.  This occurs on TEMS running on Windows only.


 APAR IZ34220 - REMOTE UPGRADE OF 6.2 FP1 ORACLE AGENT FAILS ON UNIX

 Symptoms:

   Attempting to upgrade an Oracle agent with tacmd updateAgent fails to
   update the database agent common component (dd).


 APAR IZ34688 - NO PACKAGES FOR AIX 6.1 IN ITM 6.2

 Symptoms:
   Attempting to create a Managed System Node on AIX 6.1 using Remote Deploy
   fails with a failure message indicating that a suitable package for
   deployment to the target endpoint could not be found.


 Tivoli Enterprise Monitoring Agent APARs
 ----------------------------------------

 APAR IZ24933

 Symptoms:

   The TSITSTSH table for Status_History defines the Managed_System name as
   NOT NULL.  This fails on IBM Tivoli Monitoring 6.2 because this field can
   be NULL.

   The error message in the WPA logs show:

   (4805AE83.45FD-7E8:khdxbase.cpp,266,"setError") Error
     "[Oracle][ODBC][Ora]ORA-01400: cannot insert NULL into ("ITMUSER"."Status_
     History"."Managed_System") +4805AE83.4612  appl:"O4SRV" len:5,
     object:"Status_History" len:14, table:"TSITSTSH" len:8

   This fix only handles the case when a new Status_History table is created
   in the warehouse database where the Managed_System column will be set to
   NULL.  For an already existing Status_History table, the following SQL
   can be run to manually change the Managed_System column from NOT NULL to
   NULL.

   alter table "Status_History" modify "Managed_System" varchar2(32) NULL;


 Tivoli Enterprise Portal Client APARs
 -------------------------------------

 APAR IZ15770 - ITM 6.2 CREATE ANOTHER SIT PLACED AT ROOT REOPEN EDITOR FIXES

 Symptoms:
   When doing a "create another" from the situation editor on a situation
   that was just created the new situation is placed at the ROOT level of the
   situation editor tree instead of under the proper parent node.


 APAR IZ16732 - Z/OS TEMS NOT BEING ADDED TO AVAILABLE MSL LIST

 Symptoms:
   If the TEPS is connected to a z/OS hub that is running one of the OMEGAMON
   XE probe agents such as OMEGAMON XE for z/OS the *HUB and *EIB MSL's do
   not show up in the MSL editor.  Additionally when creating new MSL's from
   the TEMS node in the MSL editor, the TEMS that have probe agents running
   do not show up in the available list in the MSL editor.


 APAR IZ20884 - TAKEACTION MONITORED APPLICATION LIST EMPTY AFTER 6.2 UPGRADE

 Symptoms:
   The Take Action dialogs do not display any Monitored Application or
   Destination System information when launched from either an operating
   system node or a physical machine node, but they do display correct
   information when launched from an agent or report level node.


 APAR IZ21324 - ITM 6.2 NOT ABLE TO PLAY ALERT SOUNDS WITH SPACES IN FILENAME.

 Symptoms:
   If a sound file with spaces in its file name is associated with a
   situation, the sound will not play when the situation becomes true.


 APAR IZ23932 - LINKS DISAPPEARING WHEN TIME + - DELTA FUNCTION USED IN REPORT
                FILTER

 Symptoms:
   Various problems occur when the "Compare Time to a time + or - delta"
   (MKTIME) function is used with the "Current Time" (*TIME) argument.

   Symptoms of this problem include being unable to close the view Properties
   dialog,  the appearance of a "TokenMgrError: Lexical error at line"
   message in the client  log, or a workspace rendering failure, depending on
   the scenario.  The workspace  rendering failure occurs after workspaces
   using the "Compare Time to a time + or - delta" (MKTIME) function have
   been upgraded to IBM Tivoli Monitoring 6.2.0 Fix Pack 1 level.


 APAR IZ24725 - PARSER CANNOT PROCESS #'TBL'.COL CONSTRUCTS

 Symptoms:
   Filters and thresholds cannot be set for views using custom SQL queries
   referencing quoted table names like those of data warehouse tables.


 APAR IZ25751 - UNABLE TO CREATE WORKSPACE LINKS WITH SLASH IN TABLE NAME

 Symptoms:
   The link expression processor is unable to resolve symbolic references
   where the symbol name includes a '/' character.


 APAR IZ28360 - SYSTEM PROPERTIES BEING RESET WHEN TEPS DATA LAYER API IS
                INITIALIZED

 Symptoms:
   When using the TEPS Data Layer API, the construction of a TEPDataProvider
   instance is resulting in the loss of  any previously established Java
   System properties.  Since these properties  are often crucial to the
   execution of the application using the TEPS API,  their removal is
   resulting in unexpected and incorrect behavior in the  consuming
   application.


 Tivoli Enterprise Portal Server APARs
 -------------------------------------

 APAR IZ23063 - TEPS SEEDING FAILS IF INSTALL PATH CONTAINS SPACES

 Symptoms:
   If the TEPS is installed to a path that contains spaces in one or more of
   the directory names, the TEPS seeding step will fail, and the following
   error message will appear in the InstallPresentation.log:

   'D:\Program' is not recognized as an internal or external
   command, operable program or batch file. KfwServices: 5/22/2008
   9:31:05 AM: KFW1016E Migration failed.

   The TEPS may or may not start, depending on if the install was a
   first-time installation or an upgrade.


 APAR IZ26922 - TEPS MAY CRASH WITH CTAUTH TRACE AND DISTINGUISHED NAME IS
                BLANKWHEN CREATING USER ACCOUNTS

 Symptoms:
   Creating a user from the TEP client and leaving the "Distinguished Name"
   field  blank while the TEPS has any of the following trace settings
   enabled will cause the TEPS to terminate abnormally.

   (UNIT:CTAuth DETAIL)
   (UNIT:CTAuthorization DETAIL)
   (UNIT:CTAuthorizationManager DETAIL)

   Substituting "ALL" for "DETAIL" in any of the UNIT trace statements above
   will also cause server to terminate abnormally.


 APAR IZ30286 - MIGRATE-IMPORT FAILS BECAUSE NUMERIC LITERAL IS NOT VALID

 Symptoms:
   The migrate-import.bat script file fails with an error message similar to
   the following:

   [IBM][CLI Driver][DB2/NT] SQL0103N The numeric literal
   "0x9D57CD6F1B45149F244E9A3A6968D2925268C956848A4A74BD7692425A5A6A3B4BEA"
   is not valid.  SQLSTATE=42604

   After the failure of migrate-import.bat, users are unable to log in using
   the TEP client.


 IBM Tivoli Data Warehouse APARs
 -------------------------------

 APAR IZ31752 - '/ BY ZERO' ERROR WHEN *WHSC ATTRIBUTE IS 0

 Symptoms:
   The Summarization and Pruning agent fails with a "division by zero" error
   for aggregation tables with an attribute group that uses the *WHSC tag.


 Event synchronization APARs
 ---------------------------

 APAR IZ24984 - UPGRADED 6.2 FP1 HUB TEMS DOES NOT CORRECTLY TRANSLATE SEVERITY
                FOR A SITUATION ON A BACK-LEVEL RTEMS.

 Symptoms:
   When an IBM Tivoli Monitoring 6.2.0 Fix Pack 1 Hub TEMS with TEC event
   integration enabled is connected to an IBM Tivoli Monitoring 6.1 RTEMS,
   then the severity of situations running on the agents connected to the
   RTEMS, is not updated for TEC events.  This is due to a change in the
   format of severity information in IBM Tivoli Monitoring 6.2.


 APAR IZ25230 - PERFOMANCE ISSUE WITH OMEGAMON.RLS RULESET

 Symptoms:
   There is a performance degradation caused by the update rules in the
   omegamon.rls file.


 Tivoli Universal Agent APARs
 ----------------------------

 APAR IZ20560 - PAGE TITLE DISPLAYED INCORRECTLY WHEN PAGE SIZE 0 AND MULTIPLE
                URLS BEING MONITORED

 Symptoms:
   When attempting to monitor a URL that does not actually exist using the UA
   HTTP data provider, the displayed 'Page Title' attribute value will be the
   'Page Title' value from the last valid URL among the list of URLs being
   monitored.  If a nonexistent URL is the only URL listed for monitoring,
   then its 'Page Title' value will display as 'No page title available'.


 APAR IZ21860 - IPADDRESSTONAME FUNCTION TRUNCATES HOSTNAME TO IPADDR LENGTH

 Symptoms:
   When using the Universal Agent's derived function named IPADDRESSTONAME in
   an attribute definition, if the host name of specified IP address is
   longer than the string length of IP address, the resultant hostname value
   will be truncated by UA and the truncated hostname value will appear in
   TEP.


 APAR IZ23790 - UA COMMON DP NOT USING METAFILE RECORD SIZE OVERRIDE IF SIZE IS
                GREATER THAN 4K

 Symptoms:
   Products using the Common Data Provider (CDP) such as the AgentBuilder,
   are not able to process metafiles with logical records larger than 4096
   bytes.  There is a Environment Variable, KUMP_META_MAX_RECORD_SIZE, that
   when set, is being ignored for overriding the default maximum size of
   4096.


 APAR IZ24563 - HTTP DP SHOWS STATUS OK FOR A '404:RESOURCE NOT FOUND' URL

 Symptoms:
   Using the UA HTTP data provider to monitor a URL that returns an HTTP
   status value from 1 to 999 (for example, 404: resource not found) results
   in a 'Status' of OK being displayed.


 APAR IZ28023 - UA RECORDSET DOES NOT WORK WITH NEWLINE DELIMITER

 Symptoms:
   When using the //RECORDSET feature and DLM=NEWLINE on specific attributes
   with either SCRIPT or FILE data providers, the attribute values are
   incorrect as viewed in the TEP report/table display.


 APAR IZ28212 - UA FILE DATA PROVIDER OMITS PARTS OF A UNICODE DATA FILE

 Symptoms:
   When using the File data provider to monitor a UNICODE encoded file, many
   of the resulting data rows (records) have parts of the record missing.
   Additionally, there is a skewing of the records, where many rows in the
   TEP client reports do not begin with the correct data.


 APAR IZ32968 - UA FILE DP {LOCALHOST} DOES NOT SUBSTITUTE IN FILE NAME

 Symptoms:
   When defining a //SOURCE FILE in a metafile that includes only a
   {LOCALHOST} construct, the hostname value is substituted but is later
   overwritten with the original //SOURCE statement declaration, thereby
   reverting back to a SourceString that contains the {LOCALHOST} construct.


 i5/OS monitoring agent APARs
 ----------------------------

 APAR IZ18562 - I5/OS AGENT FAILS TO START DURING IPL

 APAR IZ20212 - SITUATION CAN NOT BE CREATED ON ATTRIBUTES WITH BLANK ENUM
                VALUES

 APAR IZ24818 - ITM 6.1 I5/OS AGENT FAILS TO START ON I5/OS V6R1

 APAR IZ25542 - SITUATIONS CREATED ON CPU % USED ATTRIBUTE RAISE INCORRECTLY


 Linux OS monitoring agent APARs
 -------------------------------

 APAR IZ19339 - 6.1 AND 6.2 LZ OS AGENT SHOWS WRONG VALUES FOR 'AVERAGE REQUEST
                QUEUE LENGTH' ATTRIBUTE

 APAR IZ26921 - LINUX OS AGENT DOESN'T DIFFERENTIATE BETWEEN THE PROCESSES MORE
                THAN 256 CHARACTERS

 APAR IZ28846 - LINUX OS AGENT OCCUPIES HIGH-CPU/HANGS WHEN THE FILESYSTEM
                NAMESARE MORE THAN 64 CHARACTERS

 APAR IZ31056 - ITM62- THE ITM LINUX OS AGENT DOESN'T FIRE THE MISSING FILE
                SITUATIONS PROPERLY.

 APAR IZ31321 - LINUX OS AGENT SHOWS UNCORRECT DATA FOR WORKSPACE 'MEMORY
                UTILIZATION (AVG OVER MONTHS)' UNDER HISTORICAL SUMMARIZED
                CAPACITY

 APAR IZ31951 - NUMBER OF PROCESSES IN ZOMBIE STATEIS ALWAYS ZERO


 UNIX Logs monitoring agent APARs
 --------------------------------

 APAR IZ32545 - ABSTRACT: THE ITMCMD CONFIG COMMAND HANGS IF EXECUTED AS A TAKE
                COMMAND VIA UL AGENT.


 Windows OS monitoring agent APARs
 ---------------------------------

 APAR IZ17024 - WINDOWS AGENT CAUSES MEMORY LEAK.

 APAR IZ17149 - STARTUP OF AGENT CAUSES LARGE AMOUNTS OF PAGE FAULTS

 APAR IZ18645 - WINDOWS AGENT CRASHES WHEN A PERFORMANCE COUNTER IS DISABLED.

 APAR IZ19100 - WINDOWS AGENT LOGS SHOW ERROR IN IOCTL FOR LOGICAL DISK MESSAGE

 APAR IZ21498 - PERFMON API COUNTER MEMORY LEAK

 APAR IZ24416 - DESCRIPTION_U IS BLANK ON TEP WHEN USING MORE THAN 1128

 APAR IZ25861 - WINDOWS OS AGENT NOT ABLE TO READ THE EVENT LOG ON WINDOWS 2008
                RUNNING IN 64BIT

 APAR IZ25873 - ITM 6.2 FP1 WINDOWS AGENT LEAKS MEMORY IN WMI INTERFACE

 APAR IZ26746 - HIGH CPU FOR EVENT LOG PROCESSING

 APAR IZ28876 - WINDOWS AGENT LEAKS MEMORY IN PRINTER WORKSPACE

 APAR IZ31644 - KNTCMA.EXE CRASHES WHEN SELECTING EVENT LOGS WORKSPACES FROM TEP

 APAR IZ32564 - 64-BIT PERFMON COUNTER CALCULATION FAILS ON OVERFLOW


 UNIX OS monitoring agent APARs
 ------------------------------

 APAR IZ16547 - WORKSPACES SYSTEM SUMMARY OVER TIME (DAILY, HOURLY),
                AVAILABILITY (HOURLY)DON'T SHOW DATA FOR THE UNIX SYSTEMS

 APAR IZ18892 - ITM6.2 UNIX OS AGENT SHOWS THE CPU STATUS AS OFFLINE

 APAR IZ18894 - UX AGENT RUNNING ON HP REPORTS INCORRECT CPU STATS

 APAR IZ18926 - UNIX OS AGENT GIVES FALSE ALERTS FOR SITUATIONS BASED ON DISK
                ATTRIBUTE

 APAR IZ22729 - THE ITM6.2 TEP DOESN'T ALLOW USER TO CREATE SITUATIONS FOR CPU
                UTILIZATION WITH VALUES GREATER THAN 100

 APAR IZ24169 - ON AIX MACHINES THE ATTRIBUTE 'NUMBER OF SYSTEM PROCS' WILL ONLY
                SHOW A MAXIMUM OF 10000 PROCESSES

 APAR IZ25942 - THE ITM62 UNIX OS AGENT DOESN'T ALLOW THE SITUATIONS TO BE
                CREATED FOR CERTAIN ATTRIBUTES WITH VALUES GREATER THAN 10.

 APAR IZ31059 - ITM62-THE UNIX OS AGENT DOESN'T MONITOR FOR THE MISSING FILES
                SITUATION PROPERLY.

 APAR IZ31328 - ITM UNIX OS AGENT ON SOLARIS PLATFORM SHOWS ONLY UP TO 80
                CHARS FOR ATTRIBUTE 'PROCESS COMMAND (UNICODE)'

 APAR IZ31852 - THE ITM62 UNIX OS AGENT SHOWS PARTIAL DATA FOR THE PROCESS

 APAR IZ32551 - ITM UNIX OS AGENT ON HP MACHINES DOESN'T REPORT CORRECT
                VALUES FOR THE ATTRIBUTE 'AVERAGE QUEUE'.


2.2 PROBLEMS FIXED IN INTERIM FIX 6.2.0.1-TIV-ITM-IF0002
--------------------------------------------------------

 The following APAR was fixed in IBM Tivoli Monitoring 6.2.0 Fix Pack 1
 Interim Fix 2.

 Note: This MDV contained only one additional fix relative to 6.2.0 Fix Pack 1
 Interim Fix 1.  This fix is required for the ITCAM for Transactions
 product set.

 IZ31908


2.3 PROBLEMS FIXED IN INTERIM FIX 6.2.0.1-TIV-ITM-IF0001
--------------------------------------------------------

 The following APARs were fixed in IBM Tivoli Monitoring 6.2.0 Fix Pack 1
 Interim Fix 1.

 IZ16076, IZ16864, IZ18683, IZ19147, IZ20360, IZ20367, IZ21380, IZ21591,
 IZ22104, IZ22257, IZ22412, IZ24838, IZ26269, IZ26475


2.4 FIXES FORWARDED FROM 6.1.0.7-TIV-ITM-IF0002
-----------------------------------------------

 The following APARs were fixed in IBM Tivoli Monitoring 6.1 Fix Pack 7
 Interim Fix 2 and have also been included in this fix pack:

 IZ02484, IZ02749, IZ03164, IZ03777, IZ04009, IZ04730, IZ05788, IZ07577,
 IZ08437, IZ08680, IZ08882, IZ08892, IZ08927, IZ09645, IZ09924, IZ09930,
 IZ09956, IZ10013, IZ11695, IZ11702, IZ11704, IZ12381, IZ12792, IZ14135,
 IZ14203, IZ14365, IZ14466, IZ14550, IZ15560, IZ16489, IZ18906, IZ21307,
 IZ23700, IZ25537, IZ27001, IZ27941, IZ29153, IZ30099

2.5 FIXES FORWARDED FROM 6.1.0.7-TIV-ITM-IF0001
-----------------------------------------------

 The following APARs were fixed in IBM Tivoli Monitoring 6.1 Fix Pack 7
 Interim Fix 1 and have also been included in this fix pack:

 IY93504, IY96518, IY97381, IY97830, IY98311, IY98328, IY99114, IY99619,
 IY99711, IZ00649, IZ01311, IZ01880, IZ01886, IZ02683, IZ06235, IZ08737,
 IZ10287, IZ10668, IZ15118, IZ15267, IZ16536, IZ16573, IZ16810, IZ17689,
 IZ17745, IZ20192, IZ21081, IZ21105, IZ22022, IZ22029

2.6 FIXES FORWARDED FROM 6.1.0-TIV-ITM-FP0007
---------------------------------------------

 The following APARs were fixed in IBM Tivoli Monitoring 6.1 Fix Pack 7
 and have also been included in this fix pack:

 IZ18978


3.0 PREREQUISITES OR COREQUISITES
=================================

 For a complete set of prerequisites, refer to the "Hardware and software
 requirements" section in the IBM Tivoli Monitoring Installation and Setup
 Guide Version 6.2.0 Fix Pack 1 available at the following URL:

 http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc/welcome.htm

 This section lists updated prerequisites which supersede the requirements
 documented in the Installation and Setup Guide.


 OS Prerequisites
 ----------------

 AIX prerequisites:
 - bos.rte.libc:5.3.0.53 or greater is required for GSKit running on AIX 5.3
   and to enable the Warehouse Proxy Agent to run

 HPUX prerequisites:
 - Patches: PHSS_26946, PHSS_30970, PHSS_33033

 Windows prerequisites:
 - Windows Script Host at least at version 5.6


 LDAP Support
 ------------

 The following directory servers have been tested and are supported by
 IBM Tivoli Monitoring 6.2.0 Fix Pack 1 Interim Fix 1 and later:

 - IBM SecureWay Directory Server
 - IBM Tivoli Directory Server Version 4, 5.1, 5.2, 6, and 6.1
 - z/OS Integrated Security Services LDAP Server
 - IBM Lotus Domino Version 5, 6, and 6.5
 - Novell Directory Services
 - Sun ONE
 - Microsoft Windows 2000 Server Active Directory
 - Microsoft Windows Server 2003 Active Directory
 - Microsoft Active Directory Application Mode


4.0 NEW AND DEPRECATED PLATFORM SUPPORT
=======================================

 For a complete matrix of supported platforms for IBM Tivoli Monitoring
 6.2 components, refer to the "Supported operating systems" section of
 the IBM Tivoli Monitoring Installation and Setup Guide Version 6.2 Fix
 Pack 1 available at the following URL:

 http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.fp1/itm_install78.htm

 Support for the following platforms has been added in IBM Tivoli
 Monitoring 6.2.0 Fix Pack 2 and later:

 - Windows 2008 Server on Itanium2 (IA64) - TEMA only
 - Windows 2008 Server on Intel (x64) - TEMA only

 Support for the following platforms has been deprecated in IBM Tivoli
 Monitoring 6.2.0 Fix Pack 2 and later:

 - None

5.0 FIX PACK IMAGE DIRECTORY CONTENTS
========================================

 You can download the IBM Tivoli Monitoring, Fix Pack 2 files
 from the Downloads section of the IBM® Software Support Web site:

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

 When the Fix Pack 2 image is downloaded from the IBM Software Support Web
 site, these rules apply:

 * You may locally install the fix pack only on a system that already hosts
   a licensed copy of IBM Tivoli Monitoring.  Similar to other upgrade
   software, the fix pack image cannot be locally installed on a computer
   where the product software is not already installed.

 * You may populate agents to the depot.

 * You may remotely deploy agents to existing or new installations.

 This fix pack image contains the following files:

 Fix pack file name                          Description
 ---------------------------------------     -----------------------------------
 6.2.0-TIV-ITM_TMV-Tools-FP0002.tar          Contains the IBM Tivoli Monitoring
                                             5.1.2 Migration Toolkit, the
                                             Distributed Monitoring Upgrade
                                             Toolkit, the Agent Builder and the
                                             Tivoli Event Integration event
                                             synchronization component.
 6.2.0-TIV-ITM_TMV-Unix-Linux-FP0002.tar     Contains the IBM Tivoli Monitoring
                                             base product components, the
                                             operating system agents for both
                                             Unix and Linux, as well as
                                             application support for the
                                             operating system agents and a
                                             selected set of IBM Tivoli
                                             Monitoring 6.x based distributed
                                             monitoring agents.
 6.2.0-TIV-ITM_TMV-Windows-FP0002.zip        Contains the IBM Tivoli Monitoring
                                             base product components, the
                                             operating system agents for Windows
                                             as well as application support for
                                             the operating system agents and a
                                             selected set of IBM Tivoli
                                             Monitoring 6.x based distributed
                                             monitoring agents.


6.0 KNOWN PROBLEMS AND WORKAROUNDS
==================================

 Symptom:
   APAR IZ22232 INTEL EM64T IS LABELLED AS AMD64 IN INSTALLER

   Intel EM64T machines are displayed by the installer as AMD64.

   Workaround:
   Select the option to install Linux AMD64 when the installer is running
   on Intel EM64T machines.  This will install the x86_64 binaries which
   are appropriate for both AMD64 and EM64T architectures.


 Symptom:
   APAR IZ17449 UNABLE TO DEPLOY OS AGENT INTO C:\PROGRAM FILES ON 64-BIT
   MACHINE

   On 64-bit machines the Windows program directory is named "Program Files
   (x86)".  Remote deploy can not handle the parenthesis and will fail to
   install agents to this directory.

   Workaround:
   Use the graphical installation program to install agents on Windows 64-bit
   machines to the "Program Files (x86)" directory.


 Symptom:
   Custom settings and variables located in configuration files may be lost
   when upgrading IBM Tivoli Monitoring 6.1 or 6.2 using a Fix Pack.  These
   files would include .INI files, .CONFIG files, .ENV files, and more.

   Workaround:
   Reference technote 1307768 which can be located at the following URL:

   http://www.ibm.com/support/docview.wss?uid=swg21307768

   This technote explains what configuration files are preserved during an
   upgrade, what configuration files are not preserved, and behavior of
   custom settings in configuration files.  This note affects both Windows
   and Unix / Linux users.


 Symptom:
   Some agents are compiled with Java 1.5, so won't be able to run on
   platforms not supporting Java 1.5.

   Workaround:
   None.


 Symptom:
   The browser client does not start with the Firefox browser on Windows 2008
   Server.

   Workaround:
   Use Internet Explorer 7 to run the Tivoli Enterprise Portal browser
   client on Windows 2008 Server.


 Symptom:
   Using silent installation to upgrade a running TEMS on a Windows system
   fails to upgrade the TEMS.  After reporting a successful completion the
   TEMS remains at the previous level (EM 06.10.06.00) as reported by 'tacmd
   listsystems' command.

   Workaround:
   If the TEMS is stopped before the silent upgrade, the upgrade is
   successful.  This does not apply to GUI upgrades.


 Symptom:
   Reconnecting to TEPS fails if you connect your pre-Fix Pack 1 TEPS to more
   than one TEMS and have chosen option "Yes" in MTEMS prompt: "Do you wish to
   create a snapshot of the existing TEP Server data (User IDs, queries,
   workspace, navigators, terminal scripts) which can be used when the
   connection to the current TEMS is restored, and use a previous snapshot
   for the new TEMS connection?"

   Workaround:
   You must manually run buildpresentation.bat to upgrade the restored TEPS
   database to the Fix Pack 1 level when you switch back to the saved TEMS
   after upgrading TEPS to Fix Pack 1.


 Symptom:
   Upgrading from a previous version or fix pack level sometimes fails with
   error messages about locked files.  The reason for the failure is that
   attempts to stop running IBM Tivoli Monitoring process by the upgrade
   installer can fail to shutdown one or more processes leaving certain files
   used by those processes in a locked state.  While any IBM Tivoli
   Monitoring process can fail to shutdown and lock files, this failure has
   been mostly encountered when the Eclipse Help Server or Summarization and
   Pruning Agent fail to shutdown as expected.

   Workaround:
   To prevent these errors, it is best to shutdown all running IBM Tivoli
   Monitoring processes prior to performing an upgrade.  If any process fails
   to shutdown, the system should be restarted prior to resuming with the
   upgrade process.


 Symptom:
   The TEMS may crash during shutdown on Linux systems running glibc-2.3.4
   because of a possible race condition in the Linux Native Posix Thread
   Library.  A core file may be produced but is not always created.

   The TEMS messages log will end with shutdown in progress messages such as:

   KO4SRV018 Stopping Tivoli Enterprise Monitoring Server (TEMS) situation monitor.
   KO4SRV020 Stopping Tivoli Enterprise Monitoring Server (TEMS) data collection server.

   However, TEMS shutdown completion messages will be missing:

   KO4SRV030 Tivoli Enterprise Monitoring Server (TEMS) shutdown completed.
   KO4SRV030 Tivoli Enterprise Monitoring Server (TEMS) shutdown completed.
   KO4SRV020 Stopping Tivoli Enterprise Monitoring Server (TEMS) data collection server.
   KDSMA003 Tivoli Enterprise Monitoring Server (TEMS) data collection server ended successfully.
   KO4SRV021 Data collection server stopped.
   KO4SRV033 Tivoli Enterprise Monitoring Server (TEMS) no longer active.

   Workaround:
   This issue is corrected in Linux systems running glibc-2.5.


 Symptom:
   IBM Tivoli Monitoring DB2 V6.1.0.1 database agents that are not upgraded
   to the IBM Tivoli Monitoring V6.2.0.0 DB2 agent level may experience
   problems when stopping and starting the database agent (remotely or
   locally).

   $ ./itmcmd agent -o db2inst2 stop ud
   Sourcing db2profile for user db2inst2
   Stopping Monitoring Agent for DB2 ...
   Product ud was not stopped. You can use option -f to force stop product ud.
   Using this option you may lose/corrupt data! See help for more information.
   KCIIN0205E Unable to stop agent or process...

   Workaround:
   Installation of 'DB2 agent V6.1.0.1 LA0003' or later is needed.


 Symptom:
   When the TEPS is configured to use an external http server, the URL
   formulated by the TEP browser client when attempting to access pages from
   the Eclipse Help server does not include the proper port number (which, by
   default, should be 9999).  The resulting URL fails with a 404 "resource
   not found" error.

   Workaround:
   Correct the URL shown in the browser's location field after the 404 error
   has been displayed.  The correct URL is:

   http://<TEPS_hostname>:9999/classes/candle/fw/resources/help/contents.htm

   To invoke the Eclipse help system, the correct URL is

   http://<teps_hostname>:9999/help/index.jsp.


 Symptom:
   If Agent KNT is added to the depot by Install, the release will be
   040000100.  This may cause Deploy to reject the release as an upgrade to
   6.2 GA, or any IBM Tivoli Monitoring 6.1 release.

   Workaround:
   Do not use the installation program to populate the depot for IBM Tivoli
   Monitoring 6.2.0 Fix Pack 1.  Instead, Use the 'tacmd addbundles' command
   to add the nt bundle to the depot.  If the installation program was used
   to update the depot, first remove the nt bundle using the 'tacmd
   removebundles' command and then use the 'tacmd addbundles' command to add
   the nt bundle to the depot correctly.


 Symptom:
   After upgrading from IBM Tivoli Monitoring 6.1 to IBM Tivoli Monitoring
   6.2 and subsequent fix packs, the Warehouse Proxy and the Summarization
   and Pruning Agent configurations are not updated to the new default
   settings.  The Summarization and Pruning Agent Java log (*_sy_java_*.log)
   will contain information similar to this:

   == 1 t=Thread-0 Summarization and pruning agent started
   == 2 t=Thread-0 Loading driver : (COM.ibm.db2.jdbc.app.DB2Driver)
   == 3 t=Thread-0 Attempting connection with URL : (jdbc:db2:Warehous) user : (ITMUser)
   == 4 t=Thread-0 For connection: (con1) dbProdName: (DB2/NT) dbType: (DB2)
   == 5 t=Thread-0 For manager: (mgr1) created connection: (con1)
   == 6 t=Thread-0 Summarization and pruning agent ended with errors

   Workaround:
   Reconfigure the Warehouse Proxy and the Summarization and Pruning Agents
   to use the DB2 Universal Driver (JCC):

   KSY_WAREHOUSE_URL=jdbc:db2://<server>:<port>/<database>
   KSY_WAREHOUSE_DRIVER=com.ibm.db2.jcc.DB2Driver

   The DB2 Universal driver jars need to be added to the classpath for S&P to
   work correctly.  Those JARs are db2jcc.jar and db2jcc_license_cu.jar and
   are found in the same directory as the legacy db2java.zip was found.  It
   can also be downloaded from the IBM website.  Follow the IBM Data Server
   Driver for JDBC and SQLJ link:

   http://www.ibm.com/software/data/db2/java/


 Symptom:
   UA functions as a socket server that binds to local ports and listens for
   client connections, which primarily come from UA's own Data Providers.  If
   UA's TCP/IP address is changed or disappears while UA is running, then a
   whole series of communication errors and disconnects will occur, and UA
   will shut down because it cannot function without a usable TCP/IP
   environment.

   Workaround:
   The Universal Agent will need to be restarted when the network is
   available again.


 Symptom:
   While installing on AIX 6.1, the installer does not appear to have a
   correct entry for AIX 6.1 (64bit), and therefore defaults to AIX R5.3 (64
   bit) .

   Workaround:
   This was an oversight in the installer.  The installer chooses the correct
   default package to install.  The user should accept this default package
   and continue the installation.


 Symptom:
   When opening the TEP browser client without setting the Java Plugin Options
   to the recommended values, the following message will be displayed:

   KFWITM474E The settings specified for the Java plug-in component are
   different then those recommended for the Tivoli Enterprise Portal.  Press
   "Help" to review the documented procedure for setting the recommended
   values, or press "Continue" to complete your logon to the Tivoli
   Enterprise Portal.

   Selecting Continue will bring up the client logon panel and allow you to
   successfully login.  Selecting the Help button will open a new browser
   window which will be redirected to on-line help on the Java plugin
   options.  However, this option will also have the side effect of
   terminating the TEP client.

   Workaround:
   Follow the instructions on the help page to set the correct values to
   avoid the message from being displayed and then reload the browser client
   to display the logon panel.


 Symptom:
   At the end of the installation, there is a prompt asking if the user would
   like to add product support packages and providing the options Y or N.
   However, the installation program is not waiting for a user response.  The
   installation continues and eventually completes without errors.

   The problem is intermittent and has been observed in the following
   conditions:

   - on zLinux and xLinux machines

   - when installing IBM Tivoli Monitoring 6.2.0 Fix Pack 1 or upgrading to IBM
     Tivoli Monitoring 6.2.0 Fix Pack 1 or IBM Tivoli Monitoring 6.2.0 Fix
     Pack 1 Interim Fix 1

   - the installation ALL option is used

   Workaround:
   Install the desired product support packages one at a time after
   completing the upgrade.  Alternatively, use silent installation to perform
   the upgrade and specify the desired product support packages as
   silent installation options.


 Symptom:
   When upgrading IBM Tivoli Monitoring from 6.1 to 6.2, the WPA and S&P
   navigator items may not display properly in Navigation tree and the
   history configuration panel when you click on the time span button.

   Workaround:
   In order to display the WPA and S&P properly in TEP, you may have to
   reinstall WPA and S&P support files and reconfigure TEPS, then restart
   TEPS, WPA and S&P.


 Symptom:
   The TEP browser client on Firefox will only load once.  Attempts to load
   a second instance via a secondary tab or Firefox instance will not load
   the second instance of the TEP client.

   Workaround:
   None.


 Symptom:
   When connected to a Linux machine via some implementations of XWindows
   servers running on Windows, the Tivoli Enterprise Portal desktop client
   window does not display.

   Workaround:
   On your Windows machine, connect to the Tivoli Enterprise Portal server
   using a supported web browser client.


 Symptom:
   When configuring TEPS with the LDAP repository from the Manage Tivoli
   Enterprise Management Services (MTEMS) graphical user interface, the
   LDAP section of the configuration panel is disabled, preventing the
   configuration of the LDAP repository from MTEMS.

   Workaround:
   Use the command line interface to configure the TEPS LDAP repository.


 Symptom:
   On a Windows TEPS, when configuring the LDAP repository, the corresponding
   LDAP entry is not generated in the eWAS ISC console.

   On the Federate Configuration Panel, there should be an entry like the
   following.

   Base Entry: o=ITMSSOEntry
   Repository: ITM TEPS LDAP

   This problem does not appear on an AIX TEPS.

   Workaround:
   Manually create the LDAP entry in eWAS using the eWAS infocenter.


 Symptom:
   If two users with the same name but different case (e.g. MIKE and mike)
   are created in
   the Tivoli Portal Server and mapped to unique LDAP users, only the
   first TEPS user is recognized and allowed to login to the TEP.

   Workaround:
   Ensure that all users created in the TEPS are unique.  (e.g. MIKE1,
   mike2).


 Symptom:

   After upgrading from IBM Tivoli Monitoring 6.1 to IBM Tivoli Monitoring
   6.2 on AIX and Linux platforms, the cinfo command might report two
   versions for the ax, ui and uf components.  For example:

   AIX:
   ax    IBM Tivoli Monitoring Shared Libraries
            aix513  Version: 06.10.07.02
            aix516  Version: 06.10.07.02
            aix523  Version: 06.20.02.00
            aix526  Version: 06.20.02.00

   ui      Tivoli Enterprise Services User Interface
            aix513  Version: 06.10.07.02
            aix516  Version: 06.10.07.02
            aix523  Version: 06.20.02.00
            aix526  Version: 06.20.02.00

   uf      Universal Agent Framework
            aix516  Version: 06.10.07.02
            aix526  Version: 06.20.02.00

   Linux:
   ax    IBM Tivoli Monitoring Shared Libraries
            li6243  Version: 06.10.07.02
            li6263  Version: 06.20.02.00

   ui     Tivoli Enterprise Services User Interface
            li6243  Version: 06.10.07.02
            li6263  Version: 06.20.02.00

   uf     Universal Agent Framework
            li6243  Version: 06.10.07.02
            li6263  Version: 06.20.02.00

   Workaround:
   None.  This is expected behavior when upgrading from IBM Tivoli Monitoring
   6.1 to IBM Tivoli Monitoring 6.2 as a result of deprecated platform
   support.  In the example above, platforms aix513, aix516 and li6243 have
   been deprecated and replaced with aix523, aix526 and li6263 respectively.


 Symptom:
   IBM Tivoli Monitoring 6.2 requires Java 1.5.  In the IBM Tivoli Monitoring
   6.2 Problem Determination Guide, section Tivoli Enterprise Portal
   troubleshooting, subsection Tivoli Enterprise Portal has high memory usage
   and poor response time, the instructions incorrectly describe setting the
   Java heap parameters for Java Plug-in for IBM Java V1.4.2.

   Workaround:
   The correct instructions for configuring the Java heap are included in the
   IBM Tivoli Monitoring 6.2 Installation and Setup Guide, section
   Installation and initial configuration of base components and agents,
   subsection Configuring clients, browsers, and JREs.


 Symptom:
   After creating a user group and assigning restricted permissions, views
   or applications to the group, adding a user may not result in the user
   being restricted to the specified permissions, views or applications.

   Workaround:
   None.  This is defined behavior as a user's authorization is a union of
   all user specific and group authorizations.  If a user's authorizations
   should be restricted to the authorizations for a particular group, it is
   necessary to remove any undesired permissions, views and applications from
   the user's specific authorizations.


 Symptom:
   After upgrading from IBM Tivoli Monitoring 6.1 to IBM Tivoli Monitoring 6.2,
   a customized banner image becomes distorted or appears truncated in the
   TEP browser client.

   Workaround:
   The banner image in IBM Tivoli Monitoring 6.2 is limited to a 38 pixel
   high frame.  For best results, the banner image should be less than
   38 pixels in height.  To correct the display, either use a smaller
   image or edit the existing image and resize it to be less than 38
   pixels high.


 Symptom:
   After modifying bannerimage.html to use a customized image in the TEP
   browser as described in the Administrator's Guide, the TEP client does not
   show the customized image as expected.

   Workaround:
   The method for customizing the banner image changed in IBM Tivoli
   Monitoring 6.2.  The following procedure should be used to
   customize the banner in IBM Tivoli Monitoring 6.2.

   1.  On the computer where you installed the Tivoli Enterprise Portal
       Server, open the following file in a text editor:

         <itm_install_dir>\cnb\banner.js

       The file contains the following lines:

       var URL    = "http://www.ibm.com/software";
       var IMAGE  = "logo_bar_tiny.gif";

   2.  Modify the URL and IMAGE variables for your organization's URL and
       logo graphic file.

       For best results, use an image that is less than 38 pixels in height.

   3.  Save the file and exit the editor.

   4.  Copy the logo graphic named in step 2 to the <itm_install_dir>\cnb\
       directory.

   Users will now see the customized logo on the right-hand side of the
   banner the next time they start the browser client.


 Symptom:
   When starting TEP browser client in Firefox, after the authentication
   window, Firefox doesn't load TEP workspace and there is nothing that can
   be displayed.

   Workaround:
   Clean the Firefox cache first, if it still doesn't work.  Try
   to delete the following directory and restart Firefox:

   C:\Documents and Settings\Administrator\.webrendererswing


 Symptom:
   Occasionally, attempts to stop the Unix Log Agent using the 'tacmd
   stopagent' command will report a failure.  In some instances, the agent
   does stop and in other instances, the agent is not stopped.  The
   root cause of this failure also affects the 'tacmd updateagent' command
   which also attempts to stop the agent using the same code path.

   Workaround:
   Use the -f force option to stop the Unix Log Agent.


 Symptom:
   The IBM Tivoli Monitoring documentation, references SYSADMIN (all
   uppercase), sysadmin (all lower case) or sysAdmin (mixed-case) as the
   default user for TEPS.  However the TEMS authentication on some platforms,
   such as UNIX, is case-sensitive.  So when the default user is authenticated
   against TEMS platforms where the Validate Users option has been enabled,
   the login will fail due to the fact that on those platforms, the default
   user is converted to all lower case.  A line like the following will be
   logged in the TEMS log when this situation is encountered:

   Fri Oct 10 10:31:41 2008 KDSPA004   Logon validation failed. User sysadmin ip.pipe:#x.xx.xxx.xxx(xxxx)

   Workaround:
   1. Ensure that the default user ID does not contain any uppercase letters.
   2. Disable the Validate Users option, which will disable password
      authentication altogether.


 Symptom:

   When SSL is enabled on the IBM Tivoli Monitoring HUB TEMS, login to the
   TEMS using the tacmd command fails with an authentication error.  For
   example:

   C:\>tacmd login -s server -u username -p password

   Validating user...

   KUIC00006E: The specified user name or password is incorrect.

   You are not logged in because you specified an incorrect user name or
   password or you do not have permission to log in.

   Verify the correct user name and password and that you have permission to
   log in.

   Workaround:
   1. Check the GSKit support information in the Installation Guide and
      ensure that the target operating system is supported and has the correct
      patch(es).
   2. Ensure that the user exists in the user registry such as the local
      operating system user registry or the LDAP directory.


 Symptom:
   When attempting to use remote deploy to install the Universal Agent on
   Windows 2003 SP2 64-bit systems using the addsystem option, the deploy
   eventually times out.  On the target system, a dialog box is displayed
   waiting for input of the location of the TMV620.msi file.

   Workarounds:

   1.  In the dialog box on the the target system, enter the correct location
       of the TMV620.msi file (by default this would be
       c:\ibm\itm\tmaitm6\agentdepot\UM\062002000).
   2. Install the Universal Agent by running the IBM Tivoli Monitoring
      installation program on the target system.


6.1 LIMITED SUPPORT FOR WINDOWS SERVER 2008
-------------------------------------------

 This fix pack provides limited support for the Windows Server 2008
 environment.

 - Windows Server 2008 (32 bit) Operating System
 - TEMA and OS Agent (32 bit) supported
 - TEMS support for IP.PIPE only
 - TEPS no support
 - TEP java client and Internet Explorer supported, Firefox is not supported
 - WPA supported
 - Summarization and Pruning supported, with workaround
 - Remote deploy of the Windows OS agent and the Universal Agent to Windows
   2008 64-bit machines is not supported


 The following are the known issues and workarounds related to Windows Server
 2008 support.

 Symptom:
   When installing and configuring the TEMS on Windows Server 2008 a number
   of error popup windows are displayed.

   To install and configure the TEMS on Windows Server 2008 there are a
   number of manual steps and workarounds that must be performed.  The TEMS
   component of IBM Tivoli Monitoring 6.2.0 Fix Pack 1 Interim Fix 1 and later
   can be installed, configured, and run on Windows Server 2008 with the
   following restrictions:

   - The Windows Firewall must be disabled before the monitoring server is
     installed.
   - IP.SPIPE cannot be used as the communications protocol for the
     monitoring server or any components that connect to it.
   - The TEMS must be configured to work correctly with Windows User Account
     Control (UAC).

   Workaround:
   -  Before installing the product, disable the Windows firewall:
      1. Login to Windows Server 2008, and start the Server Manager.
      2. In the Security Information section, click "Go to Windows Firewall"
      3. In the Overview section, click "Windows Firewall Properties"
         The "Windows Firewall with Advanced Security" dialog box should now be
         displayed.
      4. To completely disable the firewall, it must be turned
         off in three (3) different places in the dialog box:
         Domain Profile
         Private Profile
         Public Profile

        Each of these tabs must be individually selected in the dialog box,
        and the Firewall state: must be changed to Off.

        Each time you change the state to Off, click Apply.

      5. After you have changed the Firewall state in all of the profiles,
         click OK.

   - During configuration, do not configure the monitoring server or any
     components that connect to it to use IP.SPIPE.

   - Following installation, configure the monitoring server to work
     correctly with Windows User Account Control (UAC).

     1. Using Windows Explorer, navigate to the IBM Tivoli Monitoring product
        installation directory (default is c:\IBM\ITM).
     2. Navigate to the appropriate subdirectory, right-click one of the
        executable files listed below, and select Properties.
        <itm_install_dir>\CMS\cms.exe
        <itm_install_dir>\CMS\kdsmain.exe
        <itm_install_dir>\CMS\kdstsns.exe
        <itm_install_dir>\InstallITM\kinconfg.exe
     3. When the Properties dialog box appears, select the Compatibility tab.
     4. In the Privilege Level section, check the box next to "Run this
        program as an administrator"
     5. Click OK.
     6. Repeat this procedure for each of the files listed.


 Symptom:
   A failure occurs when trying to install and start the Summarization and
   Pruning Agent on Windows 2008.

   Start MTEMS, select S&P agent and choose "configure using defaults".
   Reply yes to "Would you like to configure this Summarization and Pruning
   agent?".  A Windows pop-up menu opens with the message "ksycfg.exe has
   stopped working" and configuration fails.

   Workaround:
   Create the file c:\IBM\ITM\InstallITM\GetJavaHome.bat with the following
   content:

   @echo C:\Program Files\IBM\Java50\jre

   Please Note: the location of your IBM Tivoli Monitoring installation files
   and system JRE may vary so the location for the GetJavaHome.bat file and
   the contents will need to be tailored for your system configuration.


 The following are other issues or problems that currently have no
 workaround on Windows Server 2008:

 Symptom:
   The Tivoli Enterprise Portal fails to display specific operating system
   metrics for Windows 2008.  Explanation: Windows Counters are unique
   identifiers that the operating system uses to track system activity.  IBM
   Tivoli Monitoring references these counters to provide monitoring data for
   the Windows OS Agent.  Some of the counters that are used in Windows 2008
   differ from the counters used in previous versions of Windows.

 Symptom:
   The Windows OS Agent can not retrieve Windows network address.  Open
   "Windows Systems" workspace, in Windows Systems Summary view, the network
   address is "000.000.00.00".

 Symptom:
   The Windows OS Agent attributes "Available Bytes" and "Commit
   Limit(Bytes)" in Memory Allocation query show "Unknown".

 Symptom:
   The attributes Available Bytes and Commit Limit show "Unknown".

 Symptom:
   The Windows OS Agent attributes "FTP Server Statistics" and "HTTP Service"
   are empty.

 Symptom:
   The following counters are not changed with new names:

   - MSMQ Sessions is now MSMQ Session
   - TCP is now TCPv4
   - IP is now IPv4 (and IPv6)


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

 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 Web sites are provided
  for convenience only and do not in any manner serve as an endorsement
 of those Web sites. The materials at those Web sites are not part of
 the materials for this IBM product and use of those Web sites 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.


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

 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 might 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 Web sites are provided for
 convenience only and do not in any manner serve as an endorsement of those
 Web sites.  The materials at those Web sites are not part of the materials
 for this IBM product and use of those Web sites 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:

 IBM Corporation
 2Z4A/101
 11400 Burnet Road
 Austin, TX  78758 	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 document 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.

 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.

 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.

 COPYRIGHT LICENSE:
 ------------------

 This information contains sample application programs in source language,
 which illustrate programming techniques on various operating platforms.
 You may copy, modify, and distribute these sample programs in any form
 without payment to IBM, for the purposes of developing, using, marketing
 or distributing application programs conforming to the application
 programming interface for the operating platform for which the sample
 programs are written.  These examples have not been thoroughly tested
 under all conditions.  IBM, therefore, cannot guarantee or imply
 reliability, serviceability, or function of these programs.

 This product contains copyright material licensed from THOUGHT inc.


 A.1 Trademarks
 --------------

 IBM, the IBM logo, and ibm.com® 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 (®
 or ™), 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.  A
 current list of IBM trademarks is available on the Web at "Copyright and
 trademark information" at http://www.ibm.com/legal/copytrade.shtml.

 AIX, CICS, CICSPlex, DB2, developerWorks, DFSMShsm, Domino, eServer, IMS,
 Informix, iSeries, Lotus, MQSeries, MVS, NetView, Nways, OS/390, Passport
 Advantage, pSeries, RACF, Rational, Redbooks, RMF, SecureWay, Tivoli, the
 Tivoli logo, Tivoli Enterprise Console, Tivoli Management Environment,
 TME, VTAM, WebSphere, z/OS, and zSeries are trademarks or registered
 trademarks of International Business Machines Corporation in the United
 States, other countries, or both.

 Intel, the Intel Inside logos, and Pentium are trademarks of Intel
 Corporation in the United States, other countries, or both.

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

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


                                 | Java and all Java-based
                                 | trademarks and logos are
                                 | trademarks or registered
                                 | 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.

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