ITCAM for Microsoft (R) App : SQL Server 6.3.1-TIV-ITM_SQL-IF0001

Download Description

Copyright International Business Machines Corporation 2013.
All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:
Microsoft(R) SQL Server Agent, Version 6.3.1

Component ID: 5724B96MO

Interim Fix 0001, (6.3.1-TIV-ITM_SQL-IF0001)

Date: November 13, 2013

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
==================
2.1 APARS:
-------------------
APAR: IV49992
Abstract: Collector stops for blocked query details.
Additional Information: Collector gets stopped while fetching
data for Blocked Query Details attribute group when
query which is blocking has very long query text.

2.2 Defects:
-------------------
Defect: 97871
Abstract: Memory leak observed while collecting data for Process
Detail Attribute group.
Additional information : While fetching the data for Process Details
MS SQL Server Agent collector process produces memory
leak. This happens only when the Agent Instance is
configured with 'Support Long Lived database connection’
as ‘Disabled’.

Defect: 97014
Abstract: Data not populated for "Customized SQL Query Results"
attribute group.
Additional information : While navigating through "Customized SQL
Query Results" linkable workspace, the Data is not
populated for "Customized SQL Query Results" view.

2.3 Superseded fixes
--------------------
None

2.4 APARs and defects included from superseded fixes
----------------------------------------------------

Enhancements
------------
None

3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Microsoft SQL Server agent prerequisites Document,
version 6.3.1 or from the following link:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp


The following link is for the Tivoli operating system 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 V6.23 Fix Pack 3.
- ITCAMMA: Microsoft SQL Server Agent, Version 6.31

As this fix is cumulative, it can be installed on any fix level
for this version, release and mod level above the prerequisite.


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

- 6.3.1-TIV-ITM_SQL-IF0001.README.README - This README file
- 6.3.1-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format
- 6.3.1-TIV-ITM_SQL-IF0001.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.3.1-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar
6.3.1-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip
6.3.1-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab
6.3.1-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab
6.3.1-TIV-ITM_SQL-IF0001/KOQWINNT.dsc
6.3.1-TIV-ITM_SQL-IF0001/KOQWIX64.dsc
6.3.1-TIV-ITM_SQL-IF0001/oq_dd.properties
6.3.1-TIV-ITM_SQL-IF0001/oq_dd_063100001.xml
6.3.1-TIV-ITM_SQL-IF0001/itmpatch.exe


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

- Refer to section 7.0 entitled "Known problems and workarounds"
before installation.

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.3.1-TIV-ITM_SQL-IF0001.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 systems, this path includes the drive letter.

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. Use the "itmpatch" command to install the fix for that agent
platform. For more information on the "itmpatch" command, see
section 6.2.

On Windows systems, if the fix was expanded to
<TEMP>\6.3.1-TIV-ITM_SQL-IF0001, the install command is:

For 32 bit Agent:
> <TEMP>\6.3.1-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1-TIV-ITM_SQL-IF0001\KOQ_winnt_tema_if0001.cab

For 64 bit Agent:
> <TEMP>\6.3.1-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1-TIV-ITM_SQL-IF0001\KOQ_wix64_tema_if0001.cab

Note : Use "itmpatch" command from <TEMP>\6.3.1-TIV-ITM_SQL-IF0001\
temporary directory.
5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.3.1-TIV-ITM_SQL-IF0001.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 systems, this path includes the drive letter.

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. 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.3.1-TIV-ITM_SQL-IF0001:
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/6.3.1-TIV-ITM_SQL-IF0001

On Windows systems,
if the fix was expanded to <TEMP>\6.3.1-TIV-ITM_SQL-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\6.3.1-TIV-ITM_SQL-IF0001
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 "tacmd updateAgent" commands, see "IBM Tivoli
Monitoring Command Reference".

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 OQ
-n <Managed system name>
-v 063100001

On Windows systems:
> %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 OQ
-n <Managed system name>
-v 063100001

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (oq), not three characters (koq).
- 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
------------------------
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.3.1-TIV-ITM_SQL-IF0001.tar or .zip) to the Tivoli
Enterprise Monitoring Servers, Tivoli Enterprise Portal
Servers, or 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 (koq_tems_teps_tepd_if0001.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. Use the Application Support Installer(ASI) script to launch either
GUI installation or silent installation of the application
support files.

Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.

1. Aquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-TIV-ITM_ASI-IF0002 at
http://www-01.ibm.com/support/docview.wss?uid=swg24034924
for download and installation instructions.

2. Specify the '-j javahome' parameter with the path to
a java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.

GUI installation option
------------------------
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:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" 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.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0002 for ITM to be copied to
CD-ROM directory:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0002.README".

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

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Required. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and
modified as per your environment.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.

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, the check boxes should be set as follows:

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

Continue through the remaining GUI panels selecting the
Microsoft SQL Server 06.31.00.01 support to complete the
installation.

Note: When support is installed using CLI or GUI for any of the
above Tivoli Monitoring components, they are restarted.


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
=======================================
Any existing Microsoft SQL Server Agent instances should be restarted
after the installation of this fix.

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 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 systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, 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 log in 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 OQ

On Windows systems, 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 OQ

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

When the agent update is successful, the agent version is:
06.31.00.01.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.31.00.01.

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 displayed date of the build 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 Windows systems:
-------------------
To validate that all components have been installed, run the
following command:

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

>kincinfo -i
********** Thursday, October 31, 2013 12:18:08 PM ***********
User : sqladmin Group : NA
Host Name : WinboxInstaller Installer : Ver: 0NOVALUE00000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory

OQ TEMS App Support/Microsoft SQL Server Support
WINNT Version: 06.31.00.00 Build: 32681

OQ TEPS App Support/Microsoft SQL Server Support
WINNT Version: 06.31.00.01 Build: 201310230953

OQ TEPB App Support/Microsoft SQL Server Support
WINNT Version: 06.31.00.00 Build: 32681

OQ TEPD App Support/Microsoft SQL Server Support
WINNT Version: 06.31.00.00 Build: 32681


7.0 Known problems and workarounds
==================================
Abstract: Remote agent update fails for OS agent version
06.22.02.00 (IZ73759 : ADD 32-BIT WINDOWS APP
SUPPORT ON WIX64 TO ITMPATCH)
Problem: In case of Remote agent update using OS agent (version
06.22.02.00), the update of agent fails with the error:
KDY1031E: The agent installation command
<CANDLEHOME>\bin\itmpatch.exe -h <CANDLEHOME> -i
<CANDLEHOME>\tmaitm6\agentdepot\XX\062301000\
XXX_winnt_tema_FP0001.cab
returned an error with the return code 34 . The agent
was not installed because there is not enough disk
space on the server or you do not have permission to
install the agent.
Workaround: This is the problem with OS agent version 06.22.02.00
and has been fixed in version 06.22.03.00.
For successful remote agent update use OS agent version
06.22.01.00 or 06.22.03.00.

Abstract: Upgrading from an Interim Fix to an Interim Fix or
Provisional does not work (IZ84841)
Problem: Upgrading from an Interim Fix to an Interim Fix or
Provisional does not work and the following message is
displayed:
KDY0041E: The agent bundle XX is already updated to the
highest version 062101040 found in the depot and deployed
to <hostname>.
Workaround: The fix for this APAR is contained in the following
maintenance packages:
6.2.2-TIV-ITM-FP0004

Abstract: Applying 32-bit program updates with itmpatch on 64-bit
Windows systems fails (IZ73759)
Problem: Using the itmpatch utility to update 32-bit programs
fails to update machines running IBM Tivoli Monitoring
6.2.2 Fix Pack 1 on 64-bit Windows platforms. The
returned user message states that the update is not
applicable to the machines architecture.
Workaround: The fix for this APAR is contained in the following
maintenance packages:
6.2.2-TIV-ITM-FP0003

Abstract: The itmpatch command fails while upgrading agent fix pack.
Problem: When itmpatch command is executed, it fails while upgrading
agent fix pack. The following error message is
displayed:
The patch file <TEMP>\XXX_winnt_tema_IF0001.cab
can not be installed. Either the current platform architecture
or the installed components do not meet the prerequisites
of the patch.
Workaround: Run the itmpatch.exe provided in patch file
6.3.1-TIV-ITM_SQL-IF0001.zip or 6.3.1-TIV-ITM_SQL-IF0001.tar
file.

Abstract: English characters are getting displayed in Agent support
installer having Non-English language operating system.
Problem: In Non-English language operating system, when agent
support installer is executed it shows English characters.
Workaround: None

Abstract: Installing support for patch fails on ITM 6.3.0
Problem: When you try to install the support for this patch on ITM
6.3.0, the installation fails with following error:
The wizard cannot continue because of the following error:
could not load wizard specified in /wizard.inf (104)
Workaround: Use the pre-packaged binaries for itmasi available at:
http://www-01.ibm.com/support/docview.wss?uid=swg24034924


Abstract: Customized SQL queries does not work with SQL_Id length
greater than 19 characters.
Problem: Customized SQL queries does not work with SQL_Id length
greater than 19 characters.
Workaround: Specify the SQL_id having length less than 19 characters
in KoqCusSQL.properties file.



8.0 Additional product information
==================================
1. To get effect of TEMS support defects/APARs,
To update support at TEMS for defect 109023.2, First run
Application Support Installer (ASI) and follow steps given below:

1. Go to Manage Tivoli Enterprise Monitoring Service(MTEMS) window
2. Select Tivoli Enterprise Monitoring Server (TEMS)->right click->
Advanced->Add TEMS application support...
3. After selecting TEMS location click on OK
4. On next dialog select koq_upg.sql among list of 'Component'
column and click on OK
5. After few moment a message box will appear to ask about
recycling of TEMS, click on Yes
6. Now the TEMS database is updated

2. APAR:IV09025
A new environment variable has been added named 'COLL_DBCC_NO_LOCK'
which can be set by user. The variable has added with reference to
APAR:IV09025.
If the tables of the databases are locked then queries from the
agent to SQL Server goes to infinite loop (hang).If we set the
variable then agent will execute the query with "no lock" option and
the agent will not wait for infinite time to execute but it might not
be return the recent data.

Following instructions should be followed while setting the
'COLL_DBCC_NO_LOCK'.
1.The variable can be set by following menu selection:
right-click “Microsoft SQL Server agent ->Advanced -> Edit Variables”.
2.The COLL_DBCC_NO_LOCK value should be 0 or 1.
3.If number is 1 then Query will execute with "no lock” option.
4.If 'COLL_DBCC_NO_LOCK' is set to 0, then there will not be
any effect on query execution i.e. not set the "no lock" option.

3. The changes to be made in koqErrConfig.ini for other languages are
mentioned below:
A) For English version of SQL server there is no need to
update koqErrConfig.ini.
B) For Other languages of SQL server please follow the below
steps:
1) Go to path %CANDLE_HOME%\TMAITM6 for 32 bit agent and
%CANDLE_HOME%\TMAITM6_x64 for 64 bit agent.
2) Open the koqErrConfig.ini.
3) Move to the end of the file.
4) Move the new line and provide the Collation of installed
MS SQL Server. For example the collation for English is
"SQL_Latin1_General_CP1_CI_AS" and for French is
"French_CI_AS". Place the collation in the square bracket
(i.e. [ ]) in the koqErrConfig.ini e.g.
[SQL_Latin1_General_CP1_CI_AS].
5) Then we need to specify the keywords in the particular
language in the new line. To find a “Error” in English
the word we will be "Error:" and in the French it will
be "Erreur :" . Note that the colon symbol (i.e. “:” ) in
French and English is same but it may be different in
different languages.
6) Similarly map the keywords in other languages and provide
it in the koqErrConfig.ini file. As the keyword Severity
is mapped in the file by “Severity:” in English and
“Gravité :” in French. And the State is mapped in the
file by “State:” in English and “État :” in French.
7) If all the keywords are found then you will be able to
see the error messages if any, with the severity greater
than default severity (i.e. >17) on the TEP.

4. DEFECT:184566
A new environment variable has been added named 'COLL_JOB_DISABLED'
which can be set by user.
The variable has been introduced for not displaying the
information of the disabled jobs in the job details workspace.
After setting 'COLL_JOB_DISABLED' to 1, the agent will not
show the information about the disabled jobs.

Following instructions should be followed while setting
'COLL_JOB_DISABLED'
1.The variable can be set by following menu selection:
right-click “Microsoft SQL Server agent -> Advanced -> Edit Variables”.
2.The 'COLL_JOB_DISABLED' value should be 1.
3.If 'COLL_JOB_DISABLED' is not set or set to zero, there will not be
any effect on query execution and it will display the all the jobs.

5. APAR: IV22763
A new environment variable has been added named 'COLL_KOQDBD_INTERVAL'
which can be set by user.
If user has large number of databases, then the KOQDBD collection takes longer time,
in this case if user does not want frequent collection, he can set the interval time
between two consecutive collections by setting the above environment variable.

If this variable is not set then interval between two consecutive collection will
be bydefault 180 seconds.

Following instructions should be followed while setting
'COLL_KOQDBD_INTERVAL'
1.The variable can be set by following menu selection:
right-click “Microsoft SQL Server agent ->Advanced -> Edit Variables”.
2.The 'COLL_KOQDBD_INTERVAL' value should be 'n'Sec. depending
on user requirement.
3.If 'COLL_KOQDBD_INTERVAL' is not set then database
detail collection will resume after every 180 seconds.


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 are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
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.