IBM Tivoli Monitoring: Linux(R) OS Agent 6.2.3.3-TIV-ITM_LINUX-IF0007

Download Description

Copyright International Business Machines Corporation 2016.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: Linux(R) OS Agent,
Version 6.2.3 Fix Pack 3

Component ID: 5724C04LN

Interim Fix 0007 (6.2.3.3-TIV-ITM_LINUX-IF0007)

Date: September 30, 2016

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices


1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


2.0 Problems fixed
==================
The following problems are addressed by this fix.

2.1 APARs
---------
APAR: IV71612
Abstract: Monitoring Agent for Linux OS randomly crashes during Disk data collection
Additional Information: Due to a lack of synchronization with the internal thread that
collects data for the "Disk Usage Trends" attribute group it may happen that the agent crashes while responding to a query or a situation on the "Linux Disk" attribute group, as the two groups share the same filesystems' cache. The event is rare because the "Disk Usage Trends" thread runs only once per hour by default.

APAR: IV78033
Abstract: Monitoring Agent for Linux OS randomly hangs during Disk data collection
Additional Information: Due to a lack of synchronization with the internal thread that
collects data for the "Disk Usage Trends" attribute group it may happen that the agent hangs while responding to a query or a situation on the "Linux Disk" attribute group, as the two groups share the same object. The event is rare because the "Disk Usage Trends" thread runs only once per hour by default.

APAR: IV80542
Abstract: Monitoring Agent for Linux OS core dumps while monitoring disks.
Additional Information: The Monitoring Agent for Linux OS can randomly crash during Disk attribute group data collection. This is due to a memory corruption caused by a timing condition between two agent internal threads. This condition may occur when one or more filesystems do not respond within the 2 seconds default timeout for the statfs64 system call.

APAR: IV56917
Abstract: Monitoring Agent for Linux OS does not have a way to disable the monitoring of cifs file system
Additional Information: Monitoring Agent for Linux OS does not have a way to disable the monitoring of cifs file system for the Linux Disk attribute group. A new environment variable has been added, KBB_SHOW_CIFS. Set the environment variable KBB_SHOW_CIFS in the lz.ini file with value TRUE or FALSE to allow or exclude the cifs file system. The default value is TRUE.


2.2 Defects
-----------
None.

2.3 Enhancements
----------------
None.

2.4 Superseded fixes
--------------------
6.2.3.3-TIV-ITM_LINUX-IF0006
6.2.3.3-TIV-ITM_LINUX-IF0005
6.2.3.3-TIV-ITM_LINUX-IF0004
6.2.3.3-TIV-ITM_LINUX-IF0003
6.2.3.3-TIV-ITM_LINUX-IF0002
6.2.3.3-TIV-ITM_LINUX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.3.3-TIV-ITM_LINUX-IF0006
----------------------------
APAR: IV87359
Abstract: Wrong statistical percentages reported
Additional Information: This is a follow-up of APAR IV73936 that fixed a temporary
condition where the Monitoring Agent for Linux OS was awakened by signals while
sleeping between two consecutive samples for the Linux CPU attribute group, thus
reporting invalid processors' CPU percentages. This APAR also fixes a condition
where signals are permanently interrupting the polling threads and applies to the
following attribute groups in addition to the Linux CPU one: Linux System Statistics,
Linux Swap Rate, Linux Process, Linux Network, Linux Disk IO, Linux IO Ext, Linux TCP
Statistics.

6.2.3.3-TIV-ITM_LINUX-IF0005
----------------------------
APAR: IV73936
Abstract: Incorrect processors' CPU percentages in the Linux CPU attribute group.
Additional Information: The Monitoring Agent for Linux OS may temporarily incorrectly
report 0% or 100% for all of the CPU percent attributes in the Linux CPU attribute
group, like User CPU (Percent), System CPU (Percent) or Busy CPU (Percent). This is
the effect of a failure in waiting for the expected time between two consecutive
samples. This behavior is not permanent and normal values are restored within few
minutes.

6.2.3.3-TIV-ITM_LINUX-IF0004
----------------------------
APAR: IV58803
Abstract: The Monitoring Agent for Linux OS may crash while monitoring processes.
Additional Information: Due to the usage of a non thread-safe system call in a code
that can be run in parallel by two threads, an agent crash can randomly occur
depending on the timing of the two threads.

APAR: IV56049
Abstract: String attributes in Linux Process User Info attribute group are not
converted to UTF-8.
Additional Information: The following attributes in the Linux OS Agent
Process User Info attribute group are defined as UTF-8 strings but are not
actually converted to UTF-8:
Real User Name, Effective User Name, Saved User Name, File System User Name,
Real Group Name, Effective Group Name, Saved Group Name, File System Group Name,
Process Command Name and Process Command Line.
As one of the consequences the Warehouse Proxy Agent treats them as UTF-8 strings,
but since non-UTF-8 characters are found an error like the following may result:
A value in the attribute Process Command Line after UTF-8 conversion has a
length(1029) greater than the column size(768)

APAR: IV54053
Abstract: The Linux OS agent crashes while collecting short term CPU process data.
Additional Information: When multiple processes with the same name are running on the
monitored server and a situation based on one the Short Term CPU attributes is
defined on such process name, the agent may crash while collecting data for the
Linux Process attribute group.

APAR: IV52375
Abstract: Incorrect rounding for attributes in the Linux OS Agent VM Stats attribute
group.
Additional Information: Most of the attributes in the Linux OS Agent VM Stats attribute
group like Swap Space Used (MB) and Swap Space Free (MB) are rounded up incorrectly.
For example they always show 0.50 when they should be 0.00 because no swap space is
defined at all.

Defect:211160
Abstract: Linux 'Process Command Line' value is getting truncated on portal.

6.2.3.3-TIV-ITM_LINUX-IF0003
----------------------------
APAR: IV47181
Abstract: Linux OS agent unable to monitor when approaching the maximum number of
processes
Additional Information: he Linux kernel defines configurable parameters for
the maximum number of threads that can run on the system, and for the highest process ID that
can be assigned to a process. The Linux OS agent should be able to report such values and the
percentage of currently running processes and threads with respect to these limits, as they
are important indicators that the system is approaching its maximum capacity.
Five new attributes have been added to the Linux System Statistics group:
Max_Process_ID,Max_Number_Threads,Total_Number_Threads,Number_Processes_Pct,Number_Threads_Pct
The collection of Max_Number_Threads,Total_Number_Threads and Number_Threads_Pct can be disabled
setting KLZ_DISABLE_THREADS_COUNT=Y in the lz configuration file. On zLinux this is the default.

6.2.3.3-TIV-ITM_LINUX-IF0002
----------------------------
APAR: IV43959
Abstract: Processes that exceed 4096 bytes for the command string are not filtered correctly
Additional Information: The Linux OS agent Process Filter feature allows regular expressions to be applied for selecting the relevant portion of a long process command line. This is so that it can fit into the "Command Line" attribute which is 768 characters long and cannot be further expanded due to architectural limitations. However, this feature is currently based on an internal 4096 byte long buffer, so applying the filter does not properly work for processes whose command line is longer than 4096 characters. Inconsistent results in the "Command Line" attribute may occur in such a case. Moreover the length of the process command line that the kernel exposes to the Linux operating system (in the /proc/PID/cmdline pseudo file, to the ps command or other commands) is always limited to the defined page size of the system. So only servers with a page size greater than 4096 bytes can benefit of this improvement.

6.2.3.3-TIV-ITM_LINUX-IF0001
----------------------------
APAR: IV33441
Abstract: Short term process cpu attributes user and system are exchanged
Additional Information: In the Process attributes group for the Linux OS
agent, the values have been exchanged for the attributes:
- Process Short Term Avg User CPU (Percent)
- Process Short Term Avg System CPU (Percent)
The above attributes are available only inside situations, therefore the
problem is experienced when situations on those attributes are started.

APAR: IV33846
Abstract: Not available values for short term process cpu attributes
Additional Information: In Linux OS Agent, when running situations for Process
Short Term Avg CPU metrics, the time used to calculate the averages is not
properly calculated and the resulting metrics are not available for the
attributes:
- Process Short Term Avg User CPU (Percent)
- Process Short Term Avg System CPU (Percent)
- Process Short Term Avg Busy CPU (Percent)
The above attributes are available only inside situations, therefore the
problem is experienced when situations on those attributes are started.

APAR: IV33850
Abstract: Wrong values for short term process cpu attributes
Additional Information: In the Process attributes group for the Linux OS agent,
with operating system with a kernel at level 2.6.18, the attributes
- Process Short Term Avg User CPU (Percent)
- Process Short Term Avg System CPU (Percent)
don't retrieve properly the data from the proc/<pid>/stat system file.
The above attributes are available only inside situations, therefore the
problem is experienced when situations on those attributes are started.

APAR: IV38468
Abstract: ETHERNET WITH STATUS UP/NO-CARRIER IS NOT HANDLED CORRECTLY
Additional Information: The status of a network interface is reported by the
Linux OS agent in the Interface_Status attribute of the KLZ_Network group.
The status of a properly working Network Interface is indicated as UP. When
the network cable is unplugged the status is expected to become UP NOT RUNNING,
but this is not occurring. The status remains UP even if operating system
commands like "ifconfig" or "ip addr" show it as no longer running.


3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Linux OS Agent User's Guide, version 6.2.3, Fix Pack 3.

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html


3.1 Prerequisites for this fix
------------------------------
- IBM Tivoli Monitoring, Version 6.2.3 Fix Pack 3.


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

- 6.2.3.3-TIV-ITM_LINUX-IF0007.README - This README file
- 6.2.3.3-TIV-ITM_LINUX-IF0007.tar - Fix archive .tar format
- 6.2.3.3-TIV-ITM_LINUX-IF0007.zip - Fix archive .zip format

NOTE: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a Linux(R) environment; use the .zip file if
you are working in a Microsoft Windows(R) environment.

The fix archive file contains the following:
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_tems_teps_tepd_if0006.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_tems_teps_tepd_if0006.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_lpp266_tema_if0006.tar - Binaries for Linux on PowerPC®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_li6243_tema_if0006.tar - Binaries for Linux on Intel
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_li6263_tema_if0006.tar - Binaries for Linux (2.6 kernels) on Intel
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_ls3243_tema_if0006.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_ls3263_tema_if0006.tar - Binaries for 32-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_ls3246_tema_if0006.tar - Binaries for 64-bit Linux on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_ls3266_tema_if0006.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_lx8266_tema_if0006.tar - Binaries for Linux on AMD Opteron
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klz_lia266_tema_if0006.tar - Binaries for Linux on Itanium
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzlpp266.dsc - Descriptor file for Linux on Power
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzli6243.dsc - Descriptor file for Linux on Intel
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzli6263.dsc - Descriptor file for Linux (2.6 kernels) on Intel
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzls3243.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzls3246.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzls3263.dsc - Descriptor file for 32-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzls3266.dsc - Descriptor file for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzlx8266.dsc - Descriptor file for Linux on AMD/EM64T
- 6.2.3.3-TIV-ITM_LINUX-IF0007/klzlia266.dsc - Descriptor file for Linux on Itanium

Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.

5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on Linux systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on Linux systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.

- It is recommended to verify the "cinfo" commands are operating
correctly on the system prior to installing the patch. See
section "7.0 Known problems and workarounds" for the workaround
for the problem titled "Remote deploy of the patch fails"

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.2.3.3-TIV-ITM_LINUX-IF0007.tar) to a temporary directory
on the system that contains the agent code to be updated.
For the purpose of this README, the symbol <TEMP> represents
the fully qualified path to this directory.

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

3. Use the itmpatch command to install the fix for that agent platform.
For more information on the itmpatch command, see section 6.2

For example:
On a Linux system, if the fix was expanded to
<TEMP>/6.2.3.3-TIV-ITM_LINUX-IF0007, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.3-TIV-ITM_LINUX-IF0007/klz_xxxxxx_tema_if0007.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file would be klz_li6263_tema_if0007.tar
> ./cinfo -i
lz Monitoring Agent for Linux OS
li6263 Version: 06.23.03.00


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

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

3. To add the agent fix bundles into the remote deploy depot, use
the tacmd addBundles command found in $CANDLEHOME/bin on Linux
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the tacmd addBundles command, see the IBM Tivoli
Monitoring Command Reference Guide.

For example:
On Linux systems,
if the fix was expanded to <TEMP>/6.2.3.3-TIV-ITM_LINUX-IF0007
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.3.3-TIV-ITM_LINUX-IF0007

On a Windows system,
if the fix was expanded to <TEMP>\6.2.3.3-TIV-ITM_LINUX-IF0007
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.3.3-TIV-ITM_LINUX-IF0007

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the tacmd
login and updateAgent commands, see the IBM Tivoli Command Reference Guide.

For example:
On Linux systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> $CANDLEHOME/bin/tacmd updateAgent -t lz
-n <Managed System Name>
-v 062303007

On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> %CANDLEHOME%\bin\tacmd updateAgent -t lz
-n <Managed System Name>
-v 062303007

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (lz), not three characters (klz).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5.4 Agent support update
------------------------
Fix 6.2.3.3-TIV-ITM_LINUX-IF0003 includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server,
and Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.3.3-TIV-ITM_LINUX-IF0007.tar
or .zip) to the IBM Tivoli Enterprise Portal Servers,
Tivoli Enterprise Portal Servers, and Tivoli Enterprise Portal
Desktops.

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

3. Expand the archive file (klz_tems_teps_tepd_if0007.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX systems or an extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java on your system might vary.

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.


5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)

Continue through the remaining GUI panels selecting the product
06.23.03.07 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
Browser was running when the update was installed, it must be
restarted.

7. Note that the version reported by cinfo command for the TEP Browser
(TEPB) App Support component will not be updated by the itmasi tool.

6.0 Additional installation information
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

6.1 Installation instructions for agent baroc file
--------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using itmpatch command
-----------------------------------------------------
The "itmpatch" command has the following syntax:

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch


For example, on Linux systems:
<CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
<TEMP> points to the temporary directory where the fix is located.

- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows, this must include the drive
letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, this must include the drive letter.

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

For example:
On Linux systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t lz

On a Windows system, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\ibm\itm'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t lz

When the agent update is successful, the agent version should now be:
06.23.03.07

Note:
- The component (-t) for the tacmd listSystems command is specified
as two characters (lz), not three characters (klz).


On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Mon Feb 11 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candle Installer Lvl:06.23.03.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

lz Monitoring Agent for Linux OS
li6263 Version: 06.23.03.07

.
.
.
2. To verify the agent support files were updated correctly run the cinfo
command on a Unix/Linux server, or the kincinfo command on Windows server,
and check LINUX OS Support version.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------

kincinfo -t lz
********** Friday, August 12, 2016 7:02:03 PM **********
User : Administrator Group : NA
Host Name : WIN2K3SP2-32BIT Installer : Ver: 062303000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory


PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

LZ TEMS App Support/Monitoring Agent for LINUX OS WICMS 06.23.03.07 201608300000 20160830 1101
LZ TEPS App Support/Monitoring Agent for LINUX OS WICNS 06.23.03.07 201608300000 20160830 1101
LZ TEPB App Support/Monitoring Agent for LINUX OS WIXEB 06.23.03.07 30241 20130624 1101
LZ TEPD App Support/Monitoring Agent for LINUX OS WIXEW 06.23.03.07 201608300000 20160830 1101

7.0 Known problems and workarounds
==================================
1. It can happen that the installation of this Interim Fix fails while
adding the agent supports for TEMS and TEPS if using Java 1.7,
giving an error as below:

"The wizard cannot continue because of the following error: could not
load wizard specified in /wizard.inf (104)
Trace log location: C:\Users\ADMINI~1\AppData\Local\Temp\2"

When this issue occurs, please choose another version for Java (JRE)
installed on the machine for running the setup.jar file.
Java version 1.5 or 1.6 are suggested

2. The Application Support Installer may fail to stop the Tivoli Enterprise
Monitoring Server, or the Tivoli Enterprise Portal Server, within the
timeout. The agent support update process does not proceed in such a case.
To avoid this issue it is suggested to manually stop the Tivoli Enterprise
Monitoring Server and/or the Tivoli Enterprise Portal Server before starting
the Application Support Installer.




8.0 Additional product information
==================================
None.


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.



10.0 Notices
=======
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 jurisdictions 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.

Microsoft, Windows, and Windows Server are 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 Oracle and/or its affiliates.

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

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

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

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.