IBM Tivoli Monitoring: Linux(R) OS Agent 6.2.2.1-TIV-ITM_LINUX-IF0003

Download Description

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

Component: IBM(R) Tivoli(R) Monitoring: Linux(R) OS Agent,
Version 6.2.2

Component ID: 5724C04LN

Interim Fix: 0003, 6.2.2.1-TIV-ITM_LINUX-IF0003

Date: 30 August 2010

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 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.


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

2.1 APARs
-------------
APAR: IZ69455
Abstract: LINUX OS AGENT SHUTS DOWN DUE TO CONTENT IN /PROC/<PID>/CMDLINE
Additional Information: The Agent Management Services watchdog utility that
is part of the OS Agent checks the cmdline files in the /proc/<pid>
directory to find the correct process it is monitoring. Invalid
characters in a cmdline file can cause the watchdog code to crash.

APAR: IZ74848
Abstract: LINUX OS AGENT TAKES HOURS TO START AND CONNECT
Additional Information: When starting the agent, it appears to start correctly,
however it can take several hours for the agent to actually
connect to the management server and display data. The watchdog
code that is part of the OS Agent issues a "find" command to
locate the /etc/SuSE-release or /etc/redhat-release file.
If the /etc directory is NFS mounted and large, the find command
can take a long time to complete.

APAR: IZ76377
Abstract: WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
Additional Information: The Agent Management Services watchdog utility which
is part of the OS Agent used the "cinfo -R" command to get the
status of running agents. Most of these calls originate from
the common agent package (CAP) files, such as klz_default.xml.
The "cinfo -r" call is quicker and uses less resources than
"cinfo -R". It also can reduce the risk of the RunInfo file
getting out-of-sync which can cause multiple agents to be started.
The fix also changes the checkFrequency default to 120 seconds for
the OS Agents and watchdog process.

Please see Section 8.2 under 'Additional product information' for
more information regarding this APAR fix.

APAR: IZ78695
Abstract: MULTIPLE COPIES OF OS AGENTS RUNNING
Additional Information: There are multiple kuxagent or klzagent processes
running from a single $CANDLEHOME. There can also be multiple
copies of other agents running that are being monitored by the
Agent Management Services watchdog utility of the OS Agent.

Technote "Multiple copies of OS Agents running"
(http://www-01.ibm.com/support/docview.wss?uid=swg21445312) contains
the list of additional interim fixes related to this APAR as well as
updated CAP files for other IBM Tivoli Monitoring agents that can be
downloaded.

APAR: IZ78723
Abstract: "FILE READ FAILED" MESSAGES FILLING UP LOG
Additional Information: There are multiple "Error: file read failed" messages
in the OS Agent log file every 30 seconds which can fill up the log
file.

2.2 Defects
-------------

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

2.4 Superseded fixes
--------------------
6.2.2.1-TIV-ITM_LINUX-IF0002
6.2.2.1-TIV-ITM_LINUX-IF0001


2.5 APARS and defects included from superseded fixes
----------------------------------------------------

6.2.2.1-TIV-ITM_LINUX-IF0002
---------------------------
APAR: IZ74138
Abstract: WATCHDOG DOES NOT START IF ANOTHER ONE RUNNING ON SAME SYSTEM.
Additional Information: This occurs when a Solaris Zones system is defined
where a Local Zone has the same CANDLEHOME name as the Global Zone
(but different DASD). When the OS Agent in the Local Zone is
started before the OS Agent is started in the Global Zone, then
the watchdog process (kcawd) is not started for the the Global Zone.
This results in a Process ID of 0 being displayed on the on the Agent
Management Services workspace for the Proxy Agent Services Watchdog
process.

The same symptom occurs if more than one OS Agent is running on a
system in different CANDLEHOMEs, Once the kcawd is started in the
first CANDLEHOME on the system, the kcawd from all the other
CANDLEHOMEs do not start.

APAR: IZ74140
Abstract: INSTANCE NAME IS WRONG IN WATCHDOG WORKSPACE
Additional Information: In the Agent Management Services workspace, an extra
instance appears for an agent with an incorrect name.

APAR: IZ74143
Abstract: WATCHDOG CAN SEND SIGNAL TO INCORRECT PROCESS ID
Additional Information: The disarmWatchdog.sh sends a USR1 signal to the OS
Agent to signal watchdog monitoring is to stop. The script calls
the "cinfo -r" utility to determine if the OS Agent is running.
The results can return process IDs that are no longer running,
which can result in the script sending a USR1 signal to an
incorrect process id.

Defect: 119211
Abstract: Watchdog shows Process ID 0 after itmpatch of OS Agent
Additional Information: After installing an Interim Fix for the IBM Tivoli
Monitoring Agent for UNIX OS Agent or IBM Tivoli Monitoring Agent
for Linux OS Agent, the watchdog process is started with an extra
slash in the path name. This results in a Process ID of 0 being
displayed on the Agent Management Services workspace for the Proxy
Agent Services Watchdog process (kcawd).

6.2.2.1-TIV-ITM_LINUX-IF0001
---------------------------
APAR: IZ67524
Abstract: LINUX OS AGENT SUPPORT OF PROCESS GROUP LEADER ID
ATTRIBUTE
Additional Information: In both Linux and UNIX, process groups are
used to manage multiple related tasks. The Linux Process Group
ID is used to identify the leader of the process group. A new
Linux OS Agent attribute is needed to alert on the condition
when a process group leader is missing and the children are
still running.

Feature: 120683
Abstract: Added TCP Statistics attribute group for Unix and Linux OS Agents.
You can use TCP Statistics to monitor network traffic in the TCP protocol.
It contains the TCP data packets retransmitted per second attribute, that
measures the rate of failures in sending out TCP segments over the last
sampling interval. Sampling interval is 30 seconds by default, and it is
configurable by means of the KLZ_TCPSTAT_SAMPLE_SECS variable. You can set
it in the lz.ini file with a minimum of 5 seconds.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in Chapter 2 of
the IBM Tivoli Monitoring: Monitoring Agent for Linux OS User's Guide, version 6.2.2.

The following link is for the Tivoli platform and application support
matrix. Please refer to this matrix for the latest certification
information.

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

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

- IBM Tivoli Monitoring, Version 6.2.2 Fix Pack 1

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.1-TIV-ITM_LINUX-IF0003.README - This README file
- 6.2.2.1-TIV-ITM_LINUX-IF0003.tar - Fix archive .tar format
- 6.2.2.1-TIV-ITM_LINUX-IF0003.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 UNIX(R) environment; use the .zip file if
you are working in a Windows(R) environment.

The fix archive file contains the following files:
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_tems_teps_tepd_if0003.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers/Tivoli Enterprise Desktop Client
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_tems_teps_tepd_if0003.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers/Tivoli Enterprise Desktop Client
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_lpp266_tema_if0003.tar - Binaries for Linux on PowerPC®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_li6243_tema_if0003.tar - Binaries for Linux on Intel
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_li6263_tema_if0003.tar - Binaries for Linux (2.6 kernels) on Intel
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_ls3243_tema_if0003.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_ls3263_tema_if0003.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_ls3246_tema_if0003.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_ls3266_tema_if0003.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_lx8266_tema_if0003.tar - Binaries for Linux on AMD Opteron
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klz_lia266_tema_if0003.tar - Binaries for Linux on Itanium
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzlpp266.dsc - Descriptor file for Linux on Power
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzli6243.dsc - Descriptor file for Linux on Intel
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzli6263.dsc - Descriptor file for Linux on Intel
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzls3243.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzls3246.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzls3263.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzls3266.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.1-TIV-ITM_LINUX-IF0003/klzlx8266.dsc - Descriptor file for Linux on AMD/EM64T
- 6.2.2.1-TIV-ITM_LINUX-IF0003/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 UNIX systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX 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.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_LINUX-IF0003.tar
or .zip) 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. Note: On Windows, this includes the drive letter.

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

3. Use the itmpatch command to install the fix for the operating
system of that agent. For more information on the itmpatch command,
see section [6.2].

On UNIX systems, if the fix was expanded to <TEMP>/6.2.2.1-TIV-ITM_LINUX-IF0003,
the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.1-TIV-ITM_LINUX-IF0003/[klz_xxxxxx_tema_if0003].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_if0003.tar
> ./cinfo -i
lz Monitoring Agent for Linux OS
li6263 Version: 06.22.01.03


5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_LINUX-IF0003.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 UNIX systems or
an unzip utility on Windows systems. This 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 UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the tacmd addBundles command, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.2.1-TIV-ITM_LINUX-IF0003:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.1-TIV-ITM_LINUX-IF0003

On a Windows system,
if the fix was expanded to <TEMP>\6.2.2.1-TIV-ITM_LINUX-IF0003:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.1-TIV-ITM_LINUX-IF0003

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 login 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 Monitoring
Administrator's Guide.

On UNIX 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 062201003

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.

> %CANDLE_HOME%\bin\tacmd updateAgent -t lz
-n <Managed system name>
-v 062201003

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

5.4 Agent support update
------------------------------
Fix 6.2.2.1-TIV-ITM_LINUX-IF0001 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, or
Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_LINUX-IF0003.tar
or .zip) to the IBM Tivoli Enterprise Portal Servers.

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

3. Expand the archive file (klz_tems_teps_tepd_if0003.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 unzip utility
on Windows systems. This 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:
> $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar

On a Windows system:
> <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar

where <"C:\Program Files\IBM\Java142"> is the default drive
and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
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 would
like to add application support to. For this fix, the check boxes
should be as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the product
06.22.01.03 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.


6.0 Additional installation information
========================

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superceded 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 UNIX systems:
- 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 UNIX 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

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

When the agent update is successful, the agent version is:
[06.22.01.03].

2. To verify the agent support files were updated correctly, use the
kincinfo command on Windows systems or the cinfo command on Linux
or UNIX systems. The sample output below shows the versions of
the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, or Tivoli Enterprise Portal Desktop systems after this
fix has been successfully applied.

Note:
- The date of the build displayed might not be accurate. This is
a known problem.

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

./cinfo -i


On a Windows System:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

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



7.0 Known problems and workarounds
=========================
Abstract: Two kcawd processes displayed in Agent Management Services
workspace.
Problem: In the Agent Management Services workspace, the Watchdog
process (kcawd) is displayed twice, once with a correct
value for the Process ID and once with a Process ID of 0.
Workaround: Check the pas.dat file in the $CANDLEHOME/config/CAP
directory. If there are two entries for kcawd in the file,
then stop the OS Agent, delete the pas.dat file, and restart
the agent.


8.0 Additional product information
======================
8.1 IZ49762 - ITM IDML BOOK CONTAINS INVALID MAPPING - LINUX OS AGENT
---------------------------------------------------------------------
This APAR is addressing the case that Linux OS agents are in a private
network. It installs an updated version of the klz_tmsdla.xml file in the
TEPS directory structure. If you also have UNIX or Windows agents, you
must also install the corresponding maintenance vehicle with the updated
file for these environments (APARS IZ50834, IZ50835).

8.2 IZ76377 - WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
--------------------------------------------------------------
The fix for this APAR makes changes to the common agent package (CAP)
file, such as $CANDLEHOME/config/CAP/klz_default.xml, which is used by
the Agent Management Services watchdog utility. In the
<availabilityStatusScript> section of this file, instead of specifying the
command "cinfo -R" it now specifies either "agentInstanceCommand.sh" or
"cinfo -r" depending on the agent.

It is recommended to not use a CAP file that still contains "cinfo -R".

If you have copied the original CAP file in $CANDLEHOME/config/CAP, such as
<pc>_default.xml file to <pc>.xml to customize settings, it is recommended
to make a copy of the latest version of this file delivered as part of this
fix and make your customizations on the newly copied file.

The Agent Builder version 6.2.2.2 Interim Fix 01
(6.2.2.2.-TIV-ITM_ABLDR-IF0001) was updated to no longer specify "cinfo -R"
in the CAP files for single instance agents. Multi-instance agents created
by the Agent Builder did not previously specify "cinfo -R". If your agent
is a single instance agent and you will be using watchdog to monitor the
agent, it is recommended to use this version or later of the Agent Builder
to generate your agent.


9.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, the IBM logo, and ibm.com(R) 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 (R or TM), 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.

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

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

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.