ITCAM for Microsoft (R) App : SQL Server 6.2.3-TIV-ITM_SQL-IF0003

Copyright International Business Machines Corporation 2011.

All rights reserved.

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

Component ID: 5724B96MO

Interim Fix 0003, (6.2.3-TIV-ITM_SQL-IF0003)

Date: NOVEMBER 16, 2011

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. 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: IV07344
Abstract: ATTRIBUTE AGE OF LAST ERROR(MIN) SHOWS INCORRECT
VALUE ON PORTAL. 
Additional Information: Attribute Age of Last Error(Min) from Alert
Summary attribute group shows the wrong value on Portal. 
Detailed Recreation Procedure: 
1) Go to the ErrorLog Alerts Navigator item.
2) Verify the Age of Last Error(min) attribute value from
Alert Summary attribute group on Portal.
APAR: IV08062
Abstract: Attributes Log Max Growth Size(MB) shows incorrect value
on Portal.
Additional Information: Attribute Log Max Growth Size(MB) from Database
Details attribute group shows the wrong value on Portal.
Detailed Recreation Procedure: 
1) Go to the Databases Navigator item 
2) Verify the Log Max Growth Size(MB) attribute value from 
Database Details attribute group on Portal.

APAR: IV09025
Abstract: AGENT SHOWS NO DATA ON PORTAL WHEN ANY DATABASE IS LOCKED
Additional Information: Whenever agent try to get the data from 
locked database, its keep on waiting & no data is seen
on portal (TEP).


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

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

2.4 Superseded fixes
--------------------
6.2.3-TIV-ITM_SQL-IF0002
6.2.3-TIV-ITM_SQL-IF0001

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

6.2.3-TIV-ITM_SQL-IF0002
--------------------------
APAR: IV00459
Abstract: Agent doesn’t show all instances in server list while
configuring the agent locally.
Additional Information: Generally all the instances of SQL server
of same version should be displayed in server list.
But due to incorrect registry key path of the instance,
the problematic instance and next coming instances of same
version doesn't show in server list.

APAR: IV01570
Abstract: AGENT CONFIGURATIONS LOST.
Additional Information: When you close the dialog to configure the
templates, all the custom variables for the previously
defined instances get lost, and they disappear from both
the .ini files for the instances and the registry.

6.2.3-TIV-ITM_SQL-IF0001
--------------------------
APAR: IZ99911 
Abstract: COLLECTOR CRASHES WHEN JOB RUNS MORE THAN 99 HOURS. 
Additional Information: Create a job in SQL server and keep it
running for more than 99 hours. 

APAR: IZ95858
Abstract: KOQOS.EXE CRASHES IF NOT ABLE TO COLLECT DATA FROM PERFMON. 
Additional Information: koqos.exe crashes if it not able to collect
data from perfmon. Following popup message may appears: 
"koqos.exe encountered a problem and needed to close." 

APAR: IZ98919 
Abstract: MEMORY LEAK OBSERVED IN KOQCOLL.EXE WHEN SQL QUERY FAILS. 
Additional Information: Memory leak observed when one or more 
databases are not accessible or any SQL query fails.
koqcoll.exe gets crash because of memory allocation error.

APAR: IZ98901 
Abstract: SQL SERVER CRASHES AND PROVIDE STACK DUMPWHEN MS SQL AGENT 
RUNS SP_REPLCOUNTERS. 
Additional Information: Microsoft Event viewer for SQL Server crash and
stack dumps:
1) Install SQL server agent 6.2.3 on system 
2) Configure agent 
3) Start the agent 
4) Make sure that few databases are not published 
5) Observe the SQL Server ERRORLOG as well as Microsoft 
Event viewer for SQL Server crash and stack dumps. 

APAR: IV00339 
Abstract: SQL SERVER AGENT ALERTS THE FALSE VALUE ON SITUATION 
"MS_SQL_STATUS_INACTIVE". 
Additional Information: The situation is triggering when the SQL 
Server is busy and the value of the attribute which is 
responsible to trigger the situation is showing value
as Inactive.

APAR: IV00420 
Abstract: SOME ATTRIBUTES SHOWS WRONG DATA IN MS SQL DATABASE DETAIL
ATTRIBUTE GROUP FOR PUBLISHED DATABASES. 
Additional Information: 
1) Install SQL server agent 6.2.3 on system 
2) Configure agent 
3) Make more than 1 databases published 
4) Start the agent 
5) Observer value of replication related attributes in
Databases Information workspace 
Related Files and Output: 
Verify the values of replication related attributes for 
published databases on Databases Information workspace. 

3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in Chapter 2 of
the IBM Tivoli Monitoring: Microsoft SQL Server Agent User's Guide,
version 6.2.3.

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.22 Fix Pack 2.
- IBM Tivoli Monitoring for Microsoft Applications:
Microsoft SQL Server Agent, Version 6.23.0 

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.2.3-TIV-ITM_SQL-IF0003.README - This README file
- 6.2.3-TIV-ITM_SQL-IF0003.tar - Fix archive .tar format
- 6.2.3-TIV-ITM_SQL-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.3-TIV-ITM_SQL-IF0003/koq_tems_teps_tepd_IF0003.tar
6.2.3-TIV-ITM_SQL-IF0003/koq_tems_teps_tepd_IF0003.zip
6.2.3-TIV-ITM_SQL-IF0003/koq_winnt_tema_IF0003.cab
6.2.3-TIV-ITM_SQL-IF0003/koq_wix64_tema_if0003.cab
6.2.3-TIV-ITM_SQL-IF0003/KOQWINNT.dsc
6.2.3-TIV-ITM_SQL-IF0003/KOQWIX64.dsc
6.2.3-TIV-ITM_SQL-IF0003/oq_dd.properties
6.2.3-TIV-ITM_SQL-IF0003/oq_dd_062300003.xml


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.2.3-TIV-ITM_SQL-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 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.2.3-TIV-ITM_SQL-IF0003, the install command is:

For 32 bit Agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.3-TIV-ITM_SQL-IF0003\
koq_winnt_tema_IF0003.cab
For 64 bit Agent:
> itmpatch -h <CANDLEHOME> 
-i <TEMP>\6.2.3-TIV-ITM_SQL-IF0003\
koq_wix64_tema_if0003.cab
5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.2.3-TIV-ITM_SQL-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 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.2.3-TIV-ITM_SQL-IF0003:
> $CANDLEHOME/bin/tacmd addBundles
-n -i <TEMP>/6.2.3-TIV-ITM_SQL-IF0003

On Windows systems,
if the fix was expanded to <TEMP>\6.2.3-TIV-ITM_SQL-IF0003:
> %CANDLE_HOME%\bin\tacmd addBundles
-n -i <TEMP>\6.2.3-TIV-ITM_SQL-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 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 Appendix A.
Commands reference of 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 OQ
-n <Managed system name>
-v 062300003

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 062300003

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.2.3-TIV-ITM_SQL-IF0003.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_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 
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) GUI or the silent
installation method to install the application support files. 

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>] 

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.3-TIV-ITM_ASI-IF0003:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0004.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> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt". 

-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.23.00.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
=======================================
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.23.00.03.

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

OQ Microsoft SQL Server Support
WINNT Version: 06.23.00.00 Build: 10811

OQ Microsoft SQL Server Support
WINNT Version: 06.23.00.03 Build: 201111151809

OQ Microsoft SQL Server Support
WINNT Version: 06.23.00.00 Build: 10811

OQ Microsoft SQL Server Support
WINNT Version: 06.23.00.00 Build: 10811


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\062300003\
XXX_winnt_tema_if0003.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
or update the patch locally
or apply the workaround provided in APAR:IZ84841 (not 
applicable for 64bit patch upgrade with 32bit OS agent and
a PMR:35628,999,744 is opened to track the issue)

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: Remote 64-bit patch upgradation fails with 32 bit 
OS agent
Problem: Remote patch upgradation fails on already
installed patch of (i.e. IF1 and IF2).If we are 
trying to upgrade SQL agent patch IF0003 remotely
from patch IF1/IF2 then it is showing the following
error message: Error Message : KDY0003E: The agent
bundle OQ with version 0623000XX (XX : 10/20) is 
already deployed to XXXX (Manage instace name).
An agent bundle cannot be deployed if it is 
already deployed.

Workaround: upgrade the patch locally. A PMR:35628,999,744 is opened to track
the issue and we can get any other workaround if the PMR get updated.



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 press OK
5. After few moment a message box will appear to ask about 
recycling of TEMS, press Yes
6. Now the TEMS database updated

2. APAR:IZ73254
A new environment variable has been added named 'QUERY_TIMEOUT'
which can be set by user. The variable has added with reference to
APAR:IZ73254.
The variable has introduce to set max time (in seconds) to execute
a query from agent to SQL Server. If query does not return within
specified time, the agent will skip the query (Hence there will
not be any data displayed on portal for this query result) and
will proceed further execution/operation. After setting the query
timeout, the agent will not wait for infinite time to execute 
a query and user will be able to see data of other databases,
workspace etc.

Following instructions should be followed while setting 
'QUERY_TIMEOUT'
1.The variable can be set by following menu selection:
“Action->Advanced -> Edit Variables”.
2.The QUERY_TIMEOUT value should be less than 45.
3.If number of locked database (or the databases which are not 
accessible to user at that time and causes long time to execute
query) are greater the value of 'QUERY_TIMEOUT' should be less.
4.If 'QUERY_TIMEOUT' is not set or set to zero, there will not be
any effect on query execution. 

3. 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:
“Action->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.


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.

-IBM Tivoli Monitoring, Version V6.22 Fix Pack 2.
-IBM Tivoli Monitoring for Microsoft Applications:
Microsoft SQL Server Agent, Version 6.23.0