Fix pack file name

Description of what is contained in each package

6.3.0-TIV-ITM_TMV-Linuxx-FP0003.tar.gz

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux® x86, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Linuxx64-FP0003.tar.gz

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux® x86_64, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Linuxz-FP0003.tar.gz

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux® on System z, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Unix-FP0003.tar.gz

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Unix®, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Windows-FP0003.zip

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 32-bit Windows®, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Windows64-FP0003.zip

Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 64-bit Windows®, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents.

6.3.0-TIV-ITM_TMV-Agents-FP0003.tar.gz

Contains the IBM Tivoli Monitoring base agents. This includes the following: Agentless Monitor (multiplatforms), i5/OS® agent, Windows OS agent, Linux OS agent, UNIX OS agent, UNIX Logs agent, IBM Tivoli Universal Agent.

6.3.0-TIV-ITM_TMV-Tools-FP0003.tar.gz

Contains the IBM Tivoli Monitoring 5.1.2 Migration Toolkit, the Distributed Monitoring Upgrade Toolkit and the Tivoli Event Integration event synchronization component.

6.3.0-TIV-ITM_TMV-Agent-Reports-FP0003.tar.gz

Contains the IBM Tivoli Monitoring OS Agents Reports.

IBM Tivoli Enterprise Monitoring Server APARs

IV48076

Some forwarded events may be truncated when situations that have overrides use columns that contain numeric values.

IV49070

When a situation reset update alert is received in OMNIbus, and the original event has already been marked as reset, a synchronization error alert was generated.

IV49660

The "tacmd deleteappinstallrecs" command fails if the managed system name contains the hash symbol (#). The problem is caused by a bad regular expression used for input validation. This affects all tacmd commands with a managed system name parameter. This includes the following commands: - deleteappinstallrecs - histstartcollection - histstopcollection - listappinstallrecs - managesit - refreshCatalog - clearAppSeedState

IV50143

The format of the packet "If-Modified-Since" field does not include the day like Sat, 29 Oct 1994 19:43:31 GMT which is required by RFC1122, and RFC2616.

IV50167

The monitoring server is crashing after upgrading from IBM Tivoli Monitoring 6.30 to 6.30 Fix Pack 2. The crash occurs when event forwarding is enabled with Msg Slot customization.

IV51026

When any IBM Tivoli Monitoring component does a logon or a logoff to the monitoring server, the respective KDSMA009 and KDSMA011 messages are recorded in MSG2/Operation log file. There can be use cases that result in large numbers of these KDSMA009 and KDSMA011 messages being recorded to MSG2/Operation log file. The large volumes of KDSMA009 and KDSMA011 messages result in excessive growth of MSG2/Operation log file and this can be an undesirable effect on the log file. In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details.

IV52909

If a sampled situation event is cleared/deleted in OMNIbus, and the situation is not resolved in IBM Tivoli Monitoring, an acknowledgement expiration update is sent to OMNIbus. The synchronization cache triggers restore the data for the situation while checking to see if the Summary is equal to the situation name, which is true for default behavior. If the Summary is customized, the check fails, and the triggers fail to restore the data from the situation.

IV54339

Add serviceability enhancements, in the form of additional tracing statements, to the KPX/KRA components of IBM Tivoli Monitoring. Problems related to the use of recursive locks in the Tivoli Enterprise Monitoring Proxy are difficult to resolve with the current trace statements.

IV54386

Changing the fh.maxFileSize and/or fh.maxFiles parameters in the properties file does not affect the behavior of the operations log (KOL) component of the monitoring server or the portal server.

IV54577

When the Situation Update Forwarder (SUF) restarts, it locates its marker for the last event read using the lastread file in the cache file directory. The SUF is checking for the wrong value for cache file name in the lastread file, so it assumes the file didn't exist and starts from the beginning.

IV56654

Contents of the group member table can get out of sync between the hub monitoring server and the mirror monitoring server. The problem occurs when deleting a situation that is assigned to one or more groups. This leaves orphaned group members at the mirror monitoring server. The orphaned group member records can make their way back to the hub monitoring server during fail over operations. The orphaned group members are typically harmless, though can become relevant if the deleted situation is recreated.

IV59320

Contents of the access list table can get out of sync between the hub monitoring server and the mirror monitoring server . The problem occurs when deleting a endpoint that has direct distributions with overlapping group distributions. This may leave orphaned access list records at the mirror monitoring server. The orphaned access list records can make their way back to the hub monitoring server during fail over operations. The orphaned access list records are typically harmless, though can become relevant if the endpoint re-registers.

IV59338

If SQL is used to alter or repair records in table EVNTMAP, they can become damaged by having the TYPE column value changed from x'20' (blank) to x'00'. When the monitoring server is restarted, these records will not be processed and then situation events associated with these records will no longer contain the correct customized slot data.

IV59613

The hub monitoring server shuts down after I/O error attempting to open table index QA1DGRPI.IDX. An I/O error after attempting to open QA1DDYST.IDX and QA1CSITF.IDX also causes the TEMS to shut down.

IV59807

Linux_High_Zombies and Linux_High_Zombie_2 situations may produce excessive workload on the server. Because of the usage of the COUNT function in the formulas of these two out-of-the-box situations their evaluation takes place on the Tivoli Enterprise Management Server (TEMS), instead that on the agent side, and this can cause overheads in CPU, memory and network especially in case of large environments. Linux_High_Zombies in particular is an autostarted situation and the above risks are present by default.

IV60288

There are rare circumstances where a delete request fails to be performed at the mirror monitoring server. This can result in contents of the various tables being out of sync between the hub monitoring server and the mirror monitoring server. Records that were not deleted at the mirror monitoring server can make their way back to the hub monitoring server during fail over operations.

IV62579

This problem only occurs in IBM Tivoli Monitoring 6.30 release stream. For a situation that has a defined Reflex Action, the Reflex Action will not be executed if one or more of the following situation settings is defined ... 1) Persistence > 1    2) Formula contains embedded situation  3) Formula contains function, such as COUNT, SUM, AVG ...    When the problem occurs, the following messages may also be seen in the monitoring server RAS1 log file: KO41041, KFAA009W, KFAA092I, and KFAA001W.

IV62585

Tivoli Monitoring agents fail to connect to the Monitoring server without attempting to retry the failing bind operation using the next derived port in the range of ports. This results in an agent connection failure with no attempt to retry the connect. This defect is observed most frequently on z/OS but can occur on all Tivoli Monitoring supported platforms.

IV62659

The monitoring server on z/OS abends during shutdown with an S0C1 when accessing a path object that has already been freed.

IBM Tivoli Enterprise Portal Client APARs

IV33958

On the portal client, an empty or incorrect view may be displayed if a 'Compare Date and Time' function is used to filter the result set on a time stamp value. An 'equal' comparison will almost always result in an empty view while 'less than' or 'greater than' comparisons may include more or less data rows than expected. A 'not equal' comparison will almost always be true for all data rows.

IV50910

In IBM Tivoli Monitoring 6.30 Fix Pack 2, the portal client Workflow Editor Select a Situation dialog displays no situations.

IV52550

IBM Tivoli Monitoring Portal Server EWAS java process consuming memory until an out of memory condition occurrs.

IV53529

After implementing ITCAM for Microsoft Application Active Directory version 6.3, new Active Directory agents are not shown in the available Managed Systems list any more so user cannot add the new agent. Custom Managed System List of Active Directory agent can't be customized by Tivoli Enterprise Portal Client.

IV53925

The portal client displays the 'KFWITM080I Rebuilding View...' message in the Navigator pane when any but the rightmost tab is removed. The Navigator pane becomes inoperable until the portal client is restarted. This behavior is only seen when using Java version 1.6 or above.

IV55598

Changes to the Tivoli Portal client in IBM Tivoli Monitoring 6.30 FP2 cause the "tacmd tepslogin" on Solaris and HP UNIX servers to fail. The tacmd (UI component) tepslogin uses the Tivoli Portal client code to login to the Tivoli Portal.

IV55992

When in admin mode, selecting a navigator node may display the wrong default workspace.

IV62689

Add support for launch-in-context to IBM SmartCloud(R) Analytics - Log Analysis (SCALA) from the portal client.

IBM Tivoli Enterprise Portal Server APARs

IV50764

A query defined with the STRSCAN function on a column returns data for real time and short term history, but fails with an error when used to retrieve long term history. An error message similar to the following will be seen in the portal server log: [IBM][CLI Drivcw.er] CLI0100E Wrong number of parameters. SQLSTATE=07001, GENERIC SQLSTATE: 07001, ERR: -99999

IV51010

The Manage Situations window only shows stopped situations. This happens when the KFW_REPORT_ROW_LIMIT variable is set to a low value.

IV51545

Query against Summarization and Pruning agent tables is created incorrectly when (UNIT:ctreport detail) trace is on. It returns the following errors: KFWITM325E The Time Span request terminated with the following message: KFWIIM217E Request error: [IBM][CLI Driver]... An unexpected token ... SQLSTATE=42601 ERR: -104  SLexecDirect rc =-1 SQL_ERROR The log shows incorrect SQL was generated.

IV52938

Enhancements in IBM Tivoli Monitoring 6.30 FP2 were made to use a more secure SSL context. This causes the Tivoli Portal client to fail a connection to the Tivoli Portal server when the https protocol is used for client to server connection.

IV59081

Tivoli Monitioring attributes defined with a TYPE parameter that uses the kfw.unsignedinteger class for formatting do not show the correct number value in Tivoli Portal report workspaces.

Summarization and Pruning Agent APARs

IV51965

The Warehouse Summarization and Pruning agent does not process its UNIX/Linux start-up configuration file (sy.ini) for comments using the pound sign (#) character. It is using the asterick (*) that is for Windows only. Therefore, UNIX/Linux comments can be read as configuration statements and values. This causes the Warehouse Summarization and Pruning agent to fail at start-up or use invalid configuration settings.

IV52159

Agents that use the AGTIM column and not the default WRITETIME column for a historical collection table will find that the Warehouse Summarization and Pruning agent does not add partitions for that table when partitioning is enabled.

IV52163

On Linux, the classpath for the tdwschema tool is formed incorrectly and thus causes the tool not to work.

IV52191

When the operating system is booted and agent processes start, the Warehouse Summarization and Pruning agent throws a java.net.ConnectException: Connection refused errors and SQL State = 08001 , SQL Error Code=-4499.

Warehouse Proxy Agent APARs

IV50877

Using analytics on historical data is a new feature introduced in IBM Tivoli Monitoring 6.30 Fix Pack 2. This feature fails when KHD_HISTRETENTION=0 (normal historical collection) or RETAIN=0 (private historical collection) are set.

IV51380

The Summarization and Pruing Agent creates range partitions starting at the current date. If the Summarization and Pruning Agent is not running for any amount of time exceeding the KSY_PARTITIONS_UPWARD parameter, then partitions will not be created during that timeframe and inserting data into the table for that time will not be possible. As a result the table may still have missing partitions while the short-term history file may contain data for those missing partitions. This will result in the exception appearing in the Warehouse Proxy log file: 5243F456.83B9-AC8:khdxodbc.cpp,2476,"ODBCError") Error Msg = [IBM][CLIDriver][DB2/NT64] SQL0327N The row cannot be inserted into table "DB2ADMIN.KVM_RESOURCE_POOL_CPU" because it is outside the bounds of the defined data partition ranges. SQLSTATE=22525

Agentless OS Monitor APARs

IV52458,IV52459

IBM Monitoring Agent for Linux OS APARs

IV48002,IV51064,IV54053,IV56049,IV56705

IBM Monitoring Agent for Unix OS APARs

IV46733,IV47168,IV47625,IV51670,IV52312,IV52450,IV52558,IV53161,IV53168,IV53199,IV53503,IV54057,IV54290,IV54974,IV55187,IV57730,IV60498

IBM Monitoring Agent for Windows OS APARs

IV53227,IV54401,IV54934,IV54984,IV55053,IV55705,IV58658,IV62941

IBM Tivoli Enterprise Monitoring Agent APARs

IV62667

IBM Tivoli Enterprise Monitoring Installation APARs

IV50010,IV50033,IV50747,IV51014,IV51017,IV51424,IV52410,IV52806,IV52929,IV53302,IV54752,IV56542,IV57246,IV58966,IV59252,IV59268,IV62181,IV62183

IBM Monitoring Agent for Windows OS APARs

IV53227,IV54401,IV54934,IV54984,IV55053,IV55705,IV58658,IV62941

IBM Tivoli Enterprise Monitoring Installation APARs

IV50010,IV50033,IV50747,IV51014

Basic Services APARs

IV55866

Command Line Interface APARs

IV49958,IV55770,IV55978,IV56001,IV59038,IV62606

Performance Analyzer APARs

IV55653

Remote Deploy APARs

IV57076,IV58559