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

Date: 03/09/2007

Patch: 6.1.0.4-TIV-ITM-IF0011

IBM(R) Tivoli(R) Monitoring, Version 6.1.0: Interim Fix 011


Table of contents:

1.0 GENERAL DESCRIPTION
2.0 PROBLEMS FIXED
3.0 PREREQUISITES
4.0 INTERIM FIX IMAGE DIRECTORY CONTENTS
5.0 KNOWN PROBLEMS AND WORKAROUNDS
6.0 NOTICES


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

This is a cumulative interim fix for IBM Tivoli Monitoring,
Version 6.1.0.  This interim fix supersedes IBM Tivoli Monitoring,
Version 6.1.0 fix pack 004.


For installation information for IBM Tivoli Monitoring, 6.1.0, Interim Fix 011,
see the "IBM Tivoli Monitoring, 6.1.0, Fix Pack 004 Readme and Documentation
Addendum", available at

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


2.0 PROBLEMS FIXED
===================
The following APARs have been addressed in this interim fix.

INST Component APARs
--------------------

APAR IY93274

 Symptom:

 Settings for TEMS, TEPS, and Agents return to pre-FP4 upgrade
 settings. During upgrade to FP4, the [Override Local Settings] section 
 was not processed correctly for NULL values for a key [Key=value 
 value=null as Key=] causing these values to return to pre-upgrade 
 settings instead of being deleted. Only the [Override Local Settings] 
 Section is migrated from pre-FP4 install to FP4 upgrade.

APAR IY93626

 Symptom:

 Account settings for TEMS, TEPS, and Agents return to pre-FP4 upgrade
 settings. During upgrade to FP4, service Account information was not
 processed. This caused components to return to the Local Systems Account
 for Service Logon.

APAR IY95379

 Symptom:

 On some workstations/servers, the operating system failed to convert
 HOME\BACKUP\DATE TIMESTAMP to a short path. They retained the blank 
 between "DATE TIMESTAMP". This failure caused the migration from old 
 TEMS data (pre-FP4) to new TEMS data (FP4) to fail. Situations and
 any other persisted data for TEMS could be missing.

APAR IY92495

 Symptom:

 On Unix/Linux systems, the itmpatch tool returns a message stating a
 prereq is missing even though the prereq is installed.


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

APAR IY90863

 Symptom:

 System Commands ITM Automation are not executed. System Command 
 activities that are configured to "Continue after a non-zero return 
 code is received" are terminated after the first error is 
 encountered. 

APAR IY92023

 Symptom:

 Running updateAgent over a period of time will result in a TEMS 
 crash. Doing simultaneous deployments will hasten this condition.

APAR IY93646

 Symptom:

 Nodes are shown incorrectly as down at the HTEMS, while the RTEMS 
 correctly reports the node status as up

APAR IY93582

 Symptom:

 GSKiT IP.SPIPE high cpu and connectivity errors. This defect is present 
 in FP2 and later. External symptoms include loss of connectivity during 
 which no other network outage or anomaly is present.
     
APAR IY95346

 Symptom:

 Situation status state changes can be missed because updates to the 
 local situation status end in error, causing no status to be sent.


APAR IY95560

 Symptom:

 During long periods of deploying updates to endpoints the TEMS 
 executable kdsmain terminates.

APAR IY95108

 Symptom:

 After installing FP4, the hub and remote TEMS lose connection. 

APAR IY95438

 Symptom:

 AIX 5.3 TEMS shuts down on SOAP requests. Issuing a SOAP request to 
 view the attribute group KUDDB2APPLGROUP00 causes the TEMS to shutdown.

APAR IY95440

 Symptom:

 An unserialized reference to KDE buffer pool structure member 
 bpbNumReserved can potentially lead to destructive reuse of buffers 
 in the reserved list. The external symptoms are unpredictable and 
 varied.

APAR IY93294

 Symptom:

 Direct broker lookups (performed by the HUB for remote TEMS addresses) 
 are always made with a NULL partition ID. If the remote TEMS registers
 in a broker partition (ie the remote TEMS has variable KDC_PARTITION 
 configured to the desired remote TEMS partition name) the HUB will fail 
 to distribute requests to that remote because the address lookup for 
 that remote will fail. The lookup failure is due to the absence of the 
 correct partition ID on the direct lb_lookup call.

APAR IY95441

 Symptom:

 With TEMS V6.1, a memory leak occurs when you remove any agent 
 managed system name from the ITM V6.1 enterprise. Managed system names 
 can be removed via the TEP Enterprise 'Managed System Status' view 
 using the option 'Clear Offline Entry'. Some of the memory associated 
 with an active situation for this removed managed system name is not 
 properly freed.

APAR IY94094

 Symptom:

 The Energy Policy Act of 2005 changed the rules for Daylight Saving
 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 and JRE 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 IY89335

 Symptom:

 When FTO is enabled at the remote (but not necessarily the hub), if the
 hub is recycled, then reports for agents connected to the remote will
 fail in error message KFWITM220E.

APAR IY93238

 Symptom:

 TEC events are not translated using attribute table mapping even
 if the attribute table event mapping file is supplied.


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

APAR IY94100

 Symptom:

 See TEMS APAR IY93582 for details.

APAR IY95114

 Symptom:

 See TEMS APAR IY95108 for details.

APAR IY95439

 Symptom:

 See TEMS APAR IY95438 for details.

APAR IY92830

 Symptom:

 Memory leak in TEMA historical data collection code.


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

APAR IY92844

 Symptom:

 The heartbeat monitor in TEP can go into a tight loop due to a 
 timing issue in the background monitoring of the TEP/TEPS connection.

APAR IY93444

 Symptom:

 Can't view query definition if it uses certain attribute types
 with values.


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

APAR IY91846

 Symptom:

 When there are a large number of managed systems and a large number of 
 TEP clients logging in and out, editing navigators leaves memory behind.


APAR IY92269

 Symptom:

 Managed System Status situations do not always reset in the TEP 
 navigator or event console when the situations are restarted.  

APAR IY95442

 Symptom:

 The TEP query may return many more records than requested. If data is 
 requested from a short time span in the last week, all of the records 
 for the entire week are returned. In addition to being misleading, this
 could cause functional or performance problems for other OMEGAMON 
 components, such as the TEMS and TEMA, due to the large number of 
 records returned from the query.

APAR IY95443

 Symptom:
      
 BuildPresentation fails for MSSQL environment.

APAR IY94531

 Symptom:

 When following a link from one of the sysplex reports, the target 
 workspace displays data for all plexes. It should only show data 
 for the plex the link came from.

APAR IY93443

 Symptom:

 High CPU overhead and long response time when interacting with the
 history configuration user interface.


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

APAR IY92548

 Symptom:

 After a database shutdown or a database failure implying connection 
 errors, the WAREHOUSE PROXY AGENT can use 100% of CPU. Even if the 
 database is restarted, all the export of historical data may fail.

APAR IY93667

 Symptom:

 t=work1 java.sql.SQLException: ORA-12899: value too large for column 
 "ITMUSER"."WAREHOUSEMARKER"."ORIGINNODE" (actual: 128, maximum: 64)   
 This occurs when an ITM agent defines the OriginNode greater than 64 
 characters. For example, the ITCAM for Websphere agent uses 128 
 characters. The overflow SQLException is independent of the database
 being used by the warehouse.


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

APAR IY95959

 Symptom:

 Due to unpredictable TCP behavior whereby data packets are fragmented, 
 UA processing of incoming TCP data buffer did not look for the
 //END-DP-INPUT string being received separately from the socket 
 client. UA Socket DP was simply processing the data rows and never 
 looking for //END-DP-INPUT lagging behind in next data buffer.                                                

APAR IY92509

 Symptom:

 When network connectivity is lost between UA and TEMS/RTEMS at some 
 indeterminate time, UA can fall into an infinite loop and continually 
 log the same trace messages over and over, thereby consuming 
 significant CPU cycles and substantial disk space.

APAR IY94220

 Symptom:

 Using only ONE UA Instance that uses an MDL containing two source 
 statements for FILE data provider where the 2 files reside in 
 different directories, only one of the 2 files is being monitored 
 and thus only one Managed System occurs in the Managed Systems list.

APAR IY94579

 Symptom:

 When starting/restarting UA from TEP (rather than MTEMS) the subnode 
 labels were using an IP address that TEP/TEPS assigned to 
 KDCB0_HOSTNAME. As a result, the UA subnodes are then labeled using
 this IP address and not the desired hostname, as they originally used.

APAR IY91963

 Symptom:

 When using UA's Socket data provider with a socket client running on 
 z/OS, Universal Agent is not translating first record received from 
 EBCDIC to ASCII. This causes the corresponding first row of the TEPS 
 report/workspace to be blank.


Tivoli Enterprise Console APARs
-------------------------------

APAR IY92698

 Symptom:

 Enabling EIF tracing by inserting "ed_diag_config_file=..."  into the
 om_tec.config may lead to the issue documented in TEC apar IY92628.  As
 described in this apar a potential buffer overrun can lead to TEMS
 abending.


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



3.0 PREREQUISITES
==================
There are no prerequisites for this interim fix.


4.0 INTERIM FIX IMAGE DIRECTORY CONTENTS
=====================================
This interim fix image contains the following files:

Interim fix file name                             Platform
------------------------------------------------- ---------------------------------------------------------
6.1.0.4-TIV-ITM-IF0011.README                     This readme file
6.1.0.4-TIV-ITM_TMV-Windows-IF0011.zip            Windows® platforms
6.1.0.4-TIV-ITM_TMV-AIX-IF0011.tar                UNIX® platforms - AIX®
6.1.0.4-TIV-ITM_TMV-HPUXPARISC-IF0011.tar         UNIX platforms - HP-UX Integrity, HP-UX native processors
6.1.0.4-TIV-ITM_TMV-Solaris-IF0011.tar            UNIX platforms - Solaris
6.1.0.4-TIV-ITM_TMV-LinuxIA64-LinuxX64-IF0011.tar Linux® on Intel® Itanium® and AMD Opteron 64-bit processors
6.1.0.4-TIV-ITM_TMV-Linuxip-IF0011.tar            Linux on pSeries®
6.1.0.4-TIV-ITM_TMV-Linuxz-IF0011.tar             Linux on zSeries®
6.1.0.4-TIV-ITM_TMV-LinuxIA32-1-IF0011.tar        Linux Intel platforms (Part 1 of 2)
6.1.0.4-TIV-ITM_TMV-LinuxIA32-2-IF0011.tar        Linux Intel platforms (Part 2 of 2)


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


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