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

Date: 02/12/2007

Patch: 6.1.0.3-TIV-ITM_TEMS-IF0010

IBM(R) Tivoli(R) Monitoring
 Version 6.1.0: Tivoli Enterprise Monitoring Server
 interim fix 0010


Table of contents:

1.0 GENERAL DESCRIPTION
2.0 PROBLEMS FIXED
3.0 ARCHITECTURE
4.0 PREREQUISITES
5.0 FIX PACK IMAGE DIRECTORY CONTENTS
6.0 INSTALLATION INSTRUCTIONS
7.0 KNOWN PROBLEMS AND WORKAROUNDS
8.0 NOTICES


1.0 GENERAL DESCRIPTION
========================
This is an interim fix for the 6.1.0-TIV-ITM_TEMS-FP0003 fix pack.

For information about the IBM Tivoli Monitoring Version 6.1.0 Fix
Pack 3, see the "IBM Tivoli Monitoring, 6.1.0, Fix Pack 03 Readme and
Documentation Addendum," available from the IBM Support Web site.
This document provides installation information, as well as additional
information about new features in the overall fix pack and an updated
operating system support matrix.

This interim fix supersedes all previous patches.


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

APAR IY94094

 Symptoms:

 The Energy Policy Act of 2005 changed the rules for Daylight Savings
 Time in the United States. Clocks will be set ahead one hour on the
 second Sunday of March instead of the first Sunday of April. Clocks
 will be set back one hour on the first Sunday in November, rather
 than the last Sunday of October.

 You also need to apply any operating system updates related to the
 change in Daylight Savings Time rules. Refer to this web page for
 details:

 http://www-1.ibm.com/support/docview.wss?uid=swg21254621

APAR IY89086

 Symptom:

 High CPU utilization caused by a loop in the TEMS.

APAR IY88090

 Symptom:

 The Tivoli Enterprise Monitoring Server crashes when one situation fires.

 APAR IY89212

 Symptom:

 The Tivoli Enterprise Monitoring Server is not correctly setting the event type
 from the SOAP interface.

 Required user action:


 The CT_Alert, CT_Acknowledge, CT_Reset, and CT_Resurface methods were modified
 to support the <type> tag. The <type> tag specifies the event type and is
 optional. The value for the <type> tag can be any of the following:

 * "sampled" or "0" (default)
 * "pure" or "1"
 * "meta" or "2"

 You must verify the event type and specify the corresponding value with the
 <type> tag.

APAR IY89229

 Symptom:

 TEC events forwarded from ITM exceed 4K after expansion on the TEC server
 causing problems on the TEC server.  This fix requires the installation
 of the fix for the corresponding TEP APAR IY91305 available in LA fix
 6.1.0.3-TIV-ITM_TEP-LA0006 for desktop clients and 6.1.0.3-TIV-ITM_TEPS-LA0006
 for browser clients.

 Required user action:

 New WAS agent provided event mapping and baroc files are also needed to complete
 this fix. The new agent provided event mapping and baroc files can be downloaded
 from the opal site. The event mapping file must be placed in the TEMS TECLIB
 directory. The baroc file must be compiled/loaded at the TEC server. The TEMS and
 TEC server must be recycled in order to pick up the new event definitions.

APAR IY89584

 Symptom:

 The Tivoli Enterprise Monitoring Server crashes if agents do not provide the
 HOSTINFO and SYSNAME heartbeat column information.

APAR IY89913

 Symptom:

 Duper situations getting 1144 error code during Tivoli Enterprise Monitoring
 Server startup.

APAR IY89918

 Symptom:

 RKLVLOGs shows many 1136 status codes from different situations.

APAR IY89987

 Symptom:

 Very high CPU usage on hub Tivoli Enterprise Monitoring Server in scale
 configuration.

APAR IY89989

 Symptom:

 Remote Tivoli Enterprise Monitoring Server crashes immediately after startup.

APAR IY90255

 Symptom:

 PING response can result in no new connections to the HUB TEMS after
 application 6.1.0-TIV-ITM-FP0002 (d6173a).

APAR IY90352

 Symptom:

 During startup, the Warehouse Proxy Agent fails with error
 "USERID DECODE FAILED. STATUS = 29".

APAR IY90485

 Symptom:

 When a remote Tivoli Enterprise Monitoring Server with many agents attached
 to it is started before the hub Tivoli Enterprise Monitoring Server, the
 remote connection to the hub can be delayed as much as 40 minutes.

APAR IY90486

 Symptom:

 When a remote Tivoli Enterprise Monitoring Server reconnects to the hub
 Tivoli Enterprise Monitoring Server, stale situation status records can
 remain on the hub.

APAR IY90508

 Symptom:

 If the remote Tivoli Enterprise Monitoring Server comes up before the hub
 Tivoli Enterprise Monitoring Server, the agent status for agents attached
 to the remote may not propogate correctly.

APAR IY91123

 Symptom:

 This APAR addresses the following symptoms:

 1.  Policies using correlated-by-address mode and which are distributed to
     6.1 TEMS do not work.  The policy throws away all incoming events and
     does not process anything.

 2.  Policies using uncorrelated mode, and which start with
     Wait-on-Situations with pure event situations, do not process all pure
     events received.  For example, if 3 pure events arrive at about the same
     time, the policy may only process the first event and stop.

 3.  Reflex emulation is not working consistently.  When a situation has a
     action that's handled by TEMS rather than the agent, the action doesn't
     execute for all events.  The situation has be to a sampled type, and not
     pure event.  For example, if a situation is set up to fire when either
     notepad or wordpad.  If notepad is running, but wordpad is not, the reflex
     action should have taken place for notepad, but it does not.

 4.  Given two TEMS called A and B,  A is running a policy that, when
     fired, executes a command remotely on B.  If B recycles, and the policy on
     A fires again, the first remote command will fail, but subsequent commands
     will work.

APAR IY91150

 Symptom:

 After application of 6.1.0-TIV-ITM-FP0002 (d6173a), transport layer
 defects can cause loops (High CPU usage) and/or hangs resulting in loss of
 connectivity.  Symptoms include messages IDE00074 and IDE00075:

 1DE00074=KDE1_STC_DATASTREAMINTEGRITYLOST

 and/or

 1DE00075=KDE1_STC_RETRYLIMITEXCEEDED

APAR IY91189

 Symptom:

 Access violation in SITMON when more than 999 data rows are returned for
 a duperized situation.

APAR IY91190

 Symptom:

 SITDB table does not get updated with new UADVISORY situations when
 when the user updates the history configuration.

APAR IY91689

 Symptom:

 ITM 6.1 communications infrastructure problem with the following
 symptoms:

 1. Intermittent LOOP when running TEMS under VMWare
 2. Intermittent LOOP under z/OS
 3. ABEND in BSS1_GetLock called from KDEBSMW
 4. Loss of comm activity requiring recycle

 These symptoms can occur in any ITM process, not limited to just TEPS or
 TEMS.

IY92036

 Symptom:

 RTE load fails - IDC3314I **RECORD OUT OF SEQUENCE


NOTE: Refer to Chapter 1 of the IBM Tivoli Monitoring Fix Pack 003 Readme
and Documentation Addendum for a complete list of problems addressed in
previous fixes.

   ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_6.1.0/6.1.0-TIV-ITM-FP0003/itmfp3_add.pdf


3.0 ARCHITECTURE
=================
This fix pack is supported on the following architectures:

   aix513, aix516,
   li6242, li6243, li6263,
   ls3243, ls3246, ls3263, ls3266,
   sol286, sol283, sol603
   winnt


4.0 PREREQUISITES
==================
The following fix pack must be installed prior to applying this
interim fix:

   6.1.0-TIV-ITM_INST-FP0003
   6.1.0-TIV-ITM_TEMA-FP0003

Also, the fix for APAR IY89229 also requires the installation of the fix
for TEP APAR IY91305 available in LA fix 6.1.0.3-TIV-ITM_TEP-LA0006 for
desktop clients and 6.1.0.3-TIV-ITM_TEPS-LA0006 for browser clients.



5.0 FIX PACK IMAGE DIRECTORY CONTENTS
=====================================
This fix pack image contains the following files:
- 6.1.0.3-TIV-ITM_TEMS-IF0010.README - This readme file.
- 6.1.0.3-TIV-ITM_TEMS-IF0010.tar
- 6.1.0.3-TIV-ITM_TEMS-IF0010.zip

NOTE: The tar and zip archive files are identical in content. Download the tar
file if you prefer working in a Linux or AIX environment or download the
zip file if you prefer working in a Windows environment.


6.0 INSTALLATION INSTRUCTIONS
==============================
1) Download and extract the interim fix files to a temporary
   location on your computer.  This temporary location will be referred to as
   patch_dir in this document.

2) Before installing the interim fix, stop the monitoring server
   (and portal server, if present) through the Manage Tivoli Enterprise
   Monitoring Services utility (CandleManage on Linux or AIX). Also stop
   the Manage Tivoli Enterprise Monitoring Services utility.

   On Linux or AIX computers, you can alternatively run the following command to
   stop the portal server:

      itmcmd server stop <server_name>

   where <server_name> is the name of the monitoring server.

3) Run the itmpatch command to install the 6.1.0-TIV-ITM_TEMA-FP0003 fix pack.

   For Windows computers:

      <ITMinstall_dir>\bin\itmpatch.exe -h <ITMinstall_dir> -i <patch_dir>\6.1.0-TIV-ITM_TEMA-FP0003

   where <ITMinstall_dir> is the IBM Tivoli Monitoring installation directory
   (C:\IBM\ITM, by default).

   For Linux or AIX computers:

      <ITMinstall_dir>/bin/itmpatch -h <ITMinstall_dir> -i <patch_dir>/6.1.0-TIV-ITM_TEMA-FP0003

   where <ITMinstall_dir> is the IBM Tivoli Monitoring installation directory
   (/opt/IBM/ITM, by default).

4) Run the itmpatch command to install the 6.1.0.3-TIV-ITM_TEMS-IF0010
   interim fix.

   For Windows computers:

      <ITMinstall_dir>\bin\itmpatch.exe -h <ITMinstall_dir> -i <patch_dir>\6.1.0.3-TIV-ITM_TEMS-IF0010

   where <ITMinstall_dir> is the IBM Tivoli Monitoring installation directory
   (C:\IBM\ITM, by default).

   For Linux or AIX computers:

      <ITMinstall_dir>/bin/itmpatch -h <ITMinstall_dir> -i <patch_dir>/6.1.0.3-TIV-ITM_TEMS-IF0010

   where <ITMinstall_dir> is the IBM Tivoli Monitoring installation directory
   (/opt/IBM/ITM, by default).

5) Start the monitoring server through the Manage Tivoli Enterprise
   Monitoring Services utility.

   On Linux or AIX computers, you can run the following command to start the
   monitoring server:

      itmcmd server start <server_name>

   where <server_name> is the name of the monitoring server.


7.0 KNOWN PROBLEMS AND WORKAROUNDS
===================================
 There are no known problems or workarounds.


8.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, Tivoli, and Tivoli Enterprise Console are registered trademarks
 of International Business Machines Corporation in the United States,
 other countries, or both.

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

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

 Other company, product, or service names may be trademarked.
