Unclassified

                       IBM Tivoli License Manager
             Readme File for  Fix Pack 2.1.0-TIV-TLM-FP0003

Version 2.1

+---- Note ------------------------------------------------------------+

Before using this information and the product it supports, read the
information in 2.0, "Notices".

+----------------------------------------------------------------------+

First Edition (September 2005)

This edition applies to the fix pack 2.1.0-TIV-TLM-FP0003 for version 2,
release 1 of IBM Tivoli License Manager (program number 5724-D33).

IBM welcomes your comments.

Address your comments to:


IBM License Management Information Development 
Rome Tivoli Lab 
IBM Italia S.p.A. 
Via Sciangai, 53 
00144 Rome 
Italy

Fax Number: (+39) 06 5966 2077

Internet ID: LMPUBS@IT.IBM.COM

When you send information to IBM, you grant IBM a non-exclusive right to
use or distribute the information in any way it believes appropriate
without incurring any obligation to you.

Copyright International Business Machines Corporation 2004, 2005. All 
rights reserved.


Contents

1.0 Readme File for fix pack 2.1.0-TIV-TLM-FP0003
  1.1 About this fix pack
    1.1.1 New in fix pack 2.1.0-TIV-TLM-FP0003
    1.1.2 New agent platforms
    1.1.3 Monitoring J2EE applications running in WebSphere Application 
          Server 6.0
    1.1.4 Product fix history
    1.1.5 Documentation fix history
    1.1.6 Problems fixed
    1.1.7 Backward compatibility
    1.1.8 Other changes as a result of this fix pack
  1.2 Installation, migration, upgrade, and configuration information
    1.2.1 Hardware and software requirements
    1.2.2 Installing the fix pack
    1.2.3 After installing the fix pack
    1.2.4 Upgrading agents
    1.2.5 Reverting to the previous version
  1.3 General information
    1.3.1 Publications
    1.3.2 Accessibility
    1.3.3 Tivoli technical training
    1.3.4 Contacting software support
    1.3.5 Conventions used in this readme file
2.0 Notices
  2.1 Trademarks

1.0 Readme File for fix pack 2.1.0-TIV-TLM-FP0003

This readme provides important information about the fix pack
2.1.0-TIV-TLM-FP0003 for IBM(R) Tivoli(R) License Manager version 2.1.
This readme is the most current information for the fix pack and takes
precedence over all other documentation.

Please review this readme thoroughly before installing or using this
interim fix.

This readme includes the following topics:

*  1.1, "About this fix pack"
*  1.2, "Installation, migration, upgrade, and configuration
   information"
*  1.3, "General information"

1.1 About this fix pack

Fix pack 2.1.0-TIV-TLM-FP0003 includes support for additional agent
platforms and extends monitoring of J2EE applications to those running
within the WebSphere(R) Application Server version 6.0 and WebSphere
Portal containers, as well as providing fixes for reported APARs and
defects.

This section includes the following topics:

*  1.1.1, "New in fix pack 2.1.0-TIV-TLM-FP0003"
*  1.1.2, "New agent platforms"
*  1.1.3, "Monitoring J2EE applications running in WebSphere Application
   Server 6.0"
*  1.1.4, "Product fix history"
*  1.1.5, "Documentation fix history"
*  1.1.6, "Problems fixed"
*  1.1.7, "Backward compatibility"
*  1.1.8, "Other changes as a result of this fix pack"

1.1.1 New in fix pack 2.1.0-TIV-TLM-FP0003

Fix packs are cumulative, so this fix pack includes functionality, APARs
and defects fixed in the previous fix packs and in interim fixes for
Tivoli License Manager, version 2.1. This subsection provides a summary
of the functionality and fixes that have been added for fix pack
2.1.0-TIV-TLM-FP0003. It aims to help users who have installed the
previous fix pack, 2.1.0-TIV-TLM-FP0002 to understand what changes they
can expect from this fix pack.

The following items are introduced in this fix pack:
*  Tivoli License Manager agent on the Red Hat Enterprise Linux(R)
   ES/AS/WS 4.0 platform. See 1.1.2, "New agent platforms".
*  Monitoring of J2EE applications that run inside WebSphere Application
   Server, version 6.0 and WebSphere Portal containers. See 1.1.3,
   "Monitoring J2EE applications running in WebSphere Application Server
   6.0"
*  Fixes for APARs IY69278, IY68803, IY72259, IY72870, IY73904, IY73923,
   IY73952, IY74433, IY70999, IY75483, IY75676, IY75757, IY75919, and
   IY76003. See 1.1.4, "Product fix history".
*  Fixes for documentation APARs IY73958, and IY75360. See 1.1.5,
   "Documentation fix history"
*  Fixes for agent defects. See 1.1.6.3, "For the agent".
*  Fix for an agent deployment defect. See 1.1.6.4, "For agent
   deployment".

This fix pack does not change the Catalog Manager nor the Agent for
OS/400. The most recent versions of these components are those provided
with the previous fix pack, 2.1.0-TIV-TLM-FP0002.

1.1.2 New agent platforms

The fix pack introduces support for agents on the following new versions
of currently supported platforms:
*  AIX(R) 5.3
*  SUSE LINUX Enterprise Server, version 9
*  Red Hat Enterprise Linux, version 3.0 update 3
*  Red Hat Enterprise Linux, version 3.0 update 4
*  Red Hat Enterprise Linux ES/AS/WS 4.0

Note:  To support Sub-Capacity licensing on Power 5 processors on AIX
      5.3 and SUSE LINUX Enterprise Server 9 you need to have the
      following system levels:
      *  AIX 5.3 maintenance level 2
      *  SUSE LINUX Enterprise Server 9 SP1

The new agents are supported on all hardware that was supported at GA
level for the earlier versions of the same platforms.

1.1.2.1 Dynamic reassignment of logical partitions (LPARS)

AIX 5.3, SUSE LINUX Enterprise Server, version 9, and Red Hat Enterprise
Linux, version 3.0 Update 4 provide support for new partitioning
technologies on IBM POWER5(TM) series hardware platforms. You can use
the Hardware Management Console (HMC) to define LPARs and allocate
resources to them. On AIX 5.3 and SUSE LINUX Enterprise Server, version
9, you can dynamically reassign resources between LPARs without the need
to restart the affected LPARs.

In the case of Red Hat Enterprise Linux, version 3.0 Update 4,
reassignment of resources requires a restart of the LPAR before the
changes take effect. HMC provides several options for restarting an
LPAR. If the Tivoli License Manager agent is monitoring the LPAR, you
must not use the Immediate restart option, because this could cause the
agent to lose data.

1.1.2.2 Software use monitoring

The agents for SUSE LINUX Enterprise Server, version 9, and for Red Hat
Enterprise Linux, version 3.0 Update 4 do not have a kernel extension.
Software use monitoring of products running on these platforms is
achieved by using the process list which is maintained by the operating
system and comprises a list of all currently active processes. The agent
retrieves the process list from the operating system at five minute
intervals. It is able to determine which products have started or
stopped during the interval between two retrievals by comparing the
contents of two consecutive snapshots. The consequences of using this
method of software use monitoring are the following:
*  The high setting for license compliance is not usable because, in the
   absence of a kernel extension, it is not possible to detect the
   process before the application starts and prevent it from starting if
   necessary.
*  Processes that run for a very short time and start and stop within
   the five minute interval between one process list retrieval and the
   next are not detected.

1.1.2.3 Changes to agent prerequisites

The introduction of the new agents involves changes in the agent
prerequisites as described for Tivoli License Manager, version 2.1 in
IBM Tivoli License Manager: Planning, Installation, and Configuration.

The new agent versions, on all supported platforms, are deployed with
the bundled prerequisite GSKit 7c. In addition, agents for the following
platforms, which bundled GSKit 7b at the general availablity (GA) date
of Tivoli License Manager, version 2.1, are now deployed with GSKit 7c: 
*  Red Hat Enterprise Linux 3.0 Update 1
*  Red Hat Enterprise Linux 3.0 Update 2

1.1.2.4 Changes to agent deployment procedures

For most of the agent deployment methods, there is no visible change
from the deployment procedures described for Tivoli License Manager,
version 2.1 in IBM Tivoli License Manager: Planning, Installation, and
Configuration. However for the RSH/SSH and manual deployment methods
there are minor changes that are visible to the user, as detailed in the
following sections.

1.1.2.4.1 RSH/SSH deployment

In the RSH/SSH deployment wizard, the pull-down list for the OS field
has changed. Most of the values in the list cover more than one
platform. During deployment, information is retrieved from the target
node to determine which of the agents in the selected group is to be
deployed. Table 1 shows the values that can be selected at the OS field
and the corresponding platforms on which agents can be deployed.

Table 1. Operating system selection in the RSH/SSH deployment wizard
+---------------+-----------------------------------------------------+
| Value         | Platforms                                           |
+---------------+-----------------------------------------------------+
| aix           |   AIX 5.1 (32 and 64-bit)                           |
|               |   AIX 5.2 (32 and 64-bit)                           |
|               |   AIX 5.3 (32 and 64-bit)                           |
+---------------+-----------------------------------------------------+
| hpux          |   HP-UX 11i on PA-Risc (32 and 64-bit)              |
+---------------+-----------------------------------------------------+
| linux         |   Red Hat Enterprise Linux ES/AS/WS 2.1 for         |
|               | Intel(R) x 86 (Standard or Premium) Update 2        |
|               |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
|               | 86 (Standard or Premium) Update 1                   |
|               |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
|               | 86 (Standard or Premium) Update 3                   |
|               |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
|               | 86 (Standard or Premium) Update 4                   |
|               |   Red Hat Enterprise Linux ES/AS/WS 4.0 for Intel x |
|               | 86                                                  |
|               |   SUSE LINUX Enterprise Server, version 8 for Intel |
|               | x 86                                                |
|               |   SUSE LINUX Enterprise Server, version 9 for Intel |
|               | x 86                                                |
+---------------+-----------------------------------------------------+
| linux_ppc     |   Red Hat Enterprise Linux AS 3.0 for iSeries(TM)   |
|               | and pSeries(R) Update 2                             |
|               |   Red Hat Enterprise Linux AS 3.0 for iSeries and   |
|               | pSeries Update 3                                    |
|               |   SUSE LINUX Enterprise Server, version 8 for       |
|               | iSeries and pSeries                                 |
|               |   SUSE LINUX Enterprise Server, version 9 for       |
|               | iSeries and pSeries                                 |
+---------------+-----------------------------------------------------+
| linux_s390    |   Red Hat Enterprise Linux AS 3.0 for zSeries(R)    |
|               | and S/390(R) Update 1                               |
|               |   Red Hat Enterprise Linux AS 3.0 for zSeries and   |
|               | S/390 Update 3                                      |
|               |   Red Hat Enterprise Linux AS 3.0 for zSeries and   |
|               | S/390 Update 4                                      |
|               |   Red Hat Enterprise Linux AS 4.0 for zSeries and   |
|               | S/390                                               |
|               |   SUSE LINUX Enterprise Server, version 8 for       |
|               | zSeries                                             |
|               |   SUSE LINUX Enterprise Server, version 9 for       |
|               | zSeries                                             |
+---------------+-----------------------------------------------------+
| sun32         |   Sun Solaris 8 for SPARC platforms (32-bit)        |
|               |   Sun Solaris 9 for SPARC platforms (32-bit)        |
+---------------+-----------------------------------------------------+
| sun64         |   Sun Solaris 8 for SPARC platforms (64-bit)        |
|               |   Sun Solaris 9 for SPARC platforms (64-bit)        |
+---------------+-----------------------------------------------------+

For a full description of the RSH/SSH deployment wizard, see the Deploy
Agents chapter in IBM Tivoli License Manager: Planning, Installation,
and Configuration.

1.1.2.4.2 Manual deployment

The manual deployment scripts manualDeploy.bat and manualDeploy.sh
create a set of directories in a location that you specify when you run
the script. Each of the directories contains the files required by the
installagent command to install the agent on specific platforms. Table 2
shows the directories created by the scripts and the corresponding
platforms.

Table 2.  Directories created by the manualDeploy script
+---------------+-----------------------------------------------------+
| Directory     | Platforms                                           |
+---------------+-----------------------------------------------------+
| aix_51        |   AIX 5.1 (32 and 64-bit)                           |
+---------------+-----------------------------------------------------+
| aix_52        |   AIX 5.2 (32 and 64-bit)                           |
+---------------+-----------------------------------------------------+
| aix_53        |   AIX 5.3(32 and 64-bit)                            |
+---------------+-----------------------------------------------------+
| hpux          |   HP-UX 11i on PA-Risc (32 and 64-bit)              |
+---------------+-----------------------------------------------------+
| linux_sles8   |   SUSE LINUX Enterprise Server, version 8 for Intel |
|               | x 86                                                |
+---------------+-----------------------------------------------------+
| linux21       |   Red Hat Enterprise Linux ES/AS/WS 2.1 for Intel x |
|               | 86 (Standard or Premium) Update 2                   |
+---------------+-----------------------------------------------------+
| linux_sles9-r |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
| hel3          | 86 (Standard or Premium) Update 1                   |
|               |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
|               | 86 (Standard or Premium) Update 3                   |
|               |   Red Hat Enterprise Linux ES/AS/WS 3.0 for Intel x |
|               | 86 (Standard or Premium) Update 4                   |
|               |   SUSE LINUX Enterprise Server, version 9 for Intel |
|               | x 86                                                |
+---------------+-----------------------------------------------------+
| linux_ppc-sle |   SUSE LINUX Enterprise Server, version 8 for       |
| s8            | iSeries and pSeries                                 |
+---------------+-----------------------------------------------------+
| linux_ppc-sle |   Red Hat Enterprise Linux AS 3.0 for iSeries and   |
| s9            | pSeries Update 2                                    |
|               |   Red Hat Enterprise Linux AS 3.0 for iSeries and   |
|               | pSeries Update 3                                    |
|               |   Red Hat Enterprise Linux AS 3.0 for iSeries and   |
|               | pSeries Update 4                                    |
|               |   SUSE LINUX Enterprise Server, version 9 for       |
|               | iSeries and pSeries                                 |
+---------------+-----------------------------------------------------+
| linux_s390-sl |   SLES8 for zSeries                                 |
| es8           |                                                     |
+---------------+-----------------------------------------------------+
| linux_s390-sl |   Red Hat Enterprise Linux AS 3.0 for zSeries and   |
| es9-          | s/390 Update 1                                      |
| rhel3         |   Red Hat Enterprise Linux AS 3.0 for zSeries and   |
|               | s/390 Update 3                                      |
|               |   SLES9 for zSeries                                 |
|               |   Red Hat Enterprise Linux AS 3.0 for iSeries and   |
|               | pSeries Update 4                                    |
+---------------+-----------------------------------------------------+
| sun32         |   Sun Solaris 8 for SPARC platforms (32-bit)        |
|               |   Sun Solaris 9 for SPARC platforms (32-bit)        |
+---------------+-----------------------------------------------------+
| sun64         |   Sun Solaris 8 for SPARC platforms (64-bit)        |
|               |   Sun Solaris 9 for SPARC platforms (64-bit)        |
+---------------+-----------------------------------------------------+
| win32         |   2000 Professional for Intel x86(32-bit)           |
|               |   2000 Server for Intel x86(32-bit)                 |
|               |   2000 Advanced Server for Intel x86(32-bit)        |
|               |   Server 2003 for Intel x86(32-bit)                 |
|               |   XP Professional for Intel x86(32-bit)             |
+---------------+-----------------------------------------------------+

For a full description of the manual deployment procedure, see the
Deploy Agents chapter in IBM Tivoli License Manager: Planning,
Installation, and Configuration.

1.1.3 Monitoring J2EE applications running in WebSphere Application 
      Server 6.0

This fix pack includes a new version of the WebSphere Application Server
agent for all supported platforms. The new version adds monitoring of
J2EE applications running inside the WebSphere Application Server,
version 6.0 and WebSphere Portal containers.

If you have installed WebSphere Application Server, version 6.0 or
WebSphere Portal on a monitored computer, or are planning to do so, you
must redeploy the agent or use the agent self-update facility after
installing this fix pack to enable monitoring of the J2EE applications.

WebSphere Application Server version 5.x and version 6.0 can coexist on
the same system if the coexistence option was selected. In such a case,
the Tivoli License Manager will monitor the J2EE applications running
within both versions when this fix pack has been installed.



1.1.4 Product fix history

This is the third fix pack to be issued for Tivoli License Manager,
Version 2.1. It fixes the following APARs:

APAR IY76003
         

         Add the capability to remove duplicated agents.

         When a systems is reinstalled from scratch, and the tlmagent is
         also reinstalled, the agent shows up duplicated on the Web UI
         because, as part of the reinstallation, the agent_id is
         regenerated. A duplication occurs if an agent with the same
         hostname, operating system name and version is already present.
         Under these circumstances, the administration server can change
         the status of the old agent to inactive, so that the user can
         delete the agent from the Web UI. The status change is based on
         the plugin_time: the status of agents with an older plugin_time
         becomes inactive.

         This check needs to be esplicitely set by adding two new
         system.properties in the administrator server under the Admin
         Server section:

         inactivateDuplicatedAgentEnabled=[true/false]
         inactivateDuplicatedAgentPeriod=[minutes]

          If the property inactivateDuplicatedAgentEnabled is not
         defined, the default value is false. The default value of
         inactivateDuplicatedAgentPeriod is 2880 minutes (that is, 2
         days) while the minimum value is 1440 minutes (1 day). The
         second property is used only if the value of the first property
         is set to true.

         To enable this configuration change, the administration server
         has to be stopped and restarted.


APAR IY75919
         

         On Sun Solaris platforms, the installation of GSKit fails even
         if all required patches have been installed.

         With the fix pack, the problem is resolved.


APAR IY75757
         

         The characters in the Japanese version of the itlm_dict.xsl
         file are garbled.

         With the fix pack, the problem is resolved.


APAR IY75676
         

         An error occurs when importing a large update of the catalog.

         With the fix pack, the problem is resolved.

APAR IY75483
         

         On Linux there is no check that prevents the tlmagent
         executable file from being uploaded as an unknown file.

         With the fix pack, the problem is resolved.


APAR IY74433
         

         When logging to the Web UI, if the tlmsrv password has expired,
         a misleading error message is displayed.

         With the fix pack, the text of the message is changed.


APAR IY73952
         

         The hardware scan was performing a calculation of the CPU
         frequencies if the value of the CPU clock retrieved from
         Windows(R) Management Instrumentation (WMI) and the value
         retrieved from the System Management BIOS (SMBIOS) were
         different.

         This was generating a performance issue. After installing the
         fix pack, the calculation is only performed if neither WMI or
         SMBIOS is installed..


APAR IY73923
         

         The hardware scan was being performed every 10 minutes.

         This was generating a performance issue. After installing the
         fix pack, the interval between hardware scans is increased to
         30 minutes.


APAR IY73904
         

         The agent abends if the proxy is misconfigured.

         If the communication between the runtime server and the proxy
         uses a different security level than that used between the
         proxy and the agent, the agent may crash when a new version of
         the catalog is downloaded. With the fix pack, the problem is
         resolved.


APAR IY72870
         

         The installed software scan can take a long time on systems
         where Distributed File System (DFS(TM)) volumes are mounted.

         After installing the fix pack, DFS volumes are not included in
         the scan.


APAR IY72259
         

         A Java(TM) stack overflow error occurs on the administration
         server when attempting to update the database with software use
         information.

         With the fix pack, the problem is resolved.


APAR IY70999
         

         When importing a license using the dataimp command, if the
         Component name field is not defined in the component entity
         file an undocumented error is displayed.

         With the fix pack, the error message (with code CL7043E) is
         provided.


APAR IY69278
         

         When importing a license using the dataimp command, an error
         occurs if the total cost information, which is an optional
         value, is not provided for the procured license.

         With the fix pack, optional information are handled correctly.


APAR IY68803
         

         After the installation of a patch, customizations to the file
         unknownFiles.properties are not preserved.

         With the fix pack, the problem is resolved.


APAR IY68811
         

         When upgrading an agent from version 1.1.1 to version 2.1, the
         agent prerequisites for version 2.1 are not checked before the
         version 1.1.1 agent is uninstalled. This creates a situation
         where the version 1.1.1 agent has been removed but the version
         2.1 agent cannot be installed because of missing prerequisites.

         With the fix pack, the prerequisite check precedes the
         uninstallation of the version 1.1.1 agent. If prerequisites are
         missing, the upgrade does not continue, leaving the version
         1.1.1 agent installed.


APAR IY66394
         

         The agent is not able to communicate using port numbers higher
         than 32 000. This APAR was opened against Tivoli License
         Manager, version 1.1.1 but also impacts version 2.1.

         With the fix pack, the problem is resolved.


APAR IY68617
         

         The software package block for deploying Windows agents
         contains a corrupted info.exe file.

         With the fix pack, the problem is resolved.


APARs IY68390 and IY63893
         The software use monitoring functionality of the agent includes
         the capability to collect information about unknown executable
         files. When the agent detects the starting of an executable
         file it attempts to match it to a product in the catalog. If
         the executable file does not match a catalog entry, the agent
         adds it to the list of unknown modules to be sent to the
         runtime server and subsequently to the administration server,
         where they are stored in the administration server database and
         can be processed using the catalog manager tool. 

         This feature has caused performance problems when the agent is
         installed on a system where an application that generates a
         large number of transient executable files is running. In such
         a case, the agent and the runtime server are forced to store
         and process very large numbers of unknown modules. In addition
         to the storage and performance problems this causes to the
         agent and runtime server, it also populates the list of unknown
         modules with a large number of executable files that the user
         will not want to add to the catalog. This reduces the
         usefulness of the unknown modules list.

         The solution implemented in the fix pack is to exclude
         executable files that start in certain directories from the
         list of unknown modules. This is implemented partly on the
         agent and partly on the runtime server. The agent excludes the
         following relative paths from collection of unknown module
         information:

         Windows  
                  *  *\temp\*
                  *  *\TEMP\*
                  *  *\tmp\*
                  *  *\TMP\*


         UNIX(R)  
                  *  */tmp/*
                  *  */TMP/*

         On the runtime server, an additional configuration file,
         unknownFiles.properties is added. You can use this file to
         define other paths for which unknown module information is not
         of interest. The runtime server rejects any executable files
         that started in any of the directories specified in the
         properties defined in this file and they are not included when
         unknown modules are transmitted to the administration server.
         The properties file is stored in the following location:

         <INSTALL_DIR>/runtime/conf 

         It includes the following properties: 

         windowsPathToSkip
                  The relative paths that are to be excluded from
                  unknown module monitoring on Windows systems.

         unixPathToSkip
                  The relative paths that are to be excluded from
                  unknown module monitoring on UNIX systems. 

                  UNIX paths are case-sensitive.

Notes: 
         1. The wildcard character "*" can be used in the definition of
            paths to be skipped, as follows:
            *  To skip all paths that start with the a particular
               string, specify: <string>*
            *  To skip all paths that end with the a particular string,
               specify: *<string>
            *  To skip all paths that contain a particular string,
               specify: *<string>*
            *  To skip all paths that start with a specified string and
               end with a different specified string, specify:
               <string1>*<string2>

         2. If multiple paths are specified, you must form a
            concatenated string within which the relative paths are
            separated by the character ";".
         3.  The server must be stopped and restarted before the changes
            take effect.


APAR IY65790
         Closing of browser windows when logging on or off the Web UI is
         handled incorrectly.

         When the user logs on to the Web UI, the Web UI should open in
         a browser window in kiosk mode (without any browser control
         buttons or menus) and close the original window. When the user
         logs off, the browser should revert to normal mode and close
         the Window that is in kiosk mode. After the application of the
         Microsoft(R) Security path MS04-38, the automatic closing of
         browser windows is no longer correctly handled for Internet
         Explorer 6.x.

         With the fix pack, the correct behavior is restored.


APAR IY65521
         

         The statusinfo command cannot be performed on the
         administration server.

         With the fix pack, the problem is resolved.


APAR IY65295
         

         Errors occurred when using the catalog manager to add software
         use monitoring modules to products in the catalog.

         With the fix pack, the problem is resolved.


APAR IY65120
         On Windows platform, if the agent is not manually stopped
         before the system is shut down, information in the agent cache
         is lost.

         With the fix pack, the problem is resolved.


APAR IY63633
         If there is more than one instance of DB2(R) created on the
         computer where the administration server or runtime server
         database is installed and the default instance is active, the
         server or catalog manager is not able to access the database if
         it is not installed in the default DB2 instance.

         With the fix pack, the server or catalog manager will handle
         the DB2 instance correctly.


APAR IY69113
         On AIX platforms, the agent kernel extension is inactive after
         Fix pack 2.1.0-TIV-TLM-FP0001 is installed

         With the fix pack, the problem is resolved.

1.1.5 Documentation fix history

This fix pack documents solutions for the following documentation APARs:

APAR IY73958
         Problem (found in the IBM Tivoli License Manager: Data
         Dictionary): it is wrongly believed that AGENT_H.START_TIME is
         the time when the agent starts and the AGENT.PLUGIN_TIME the
         time when the agent plugs-in. So it is not clear why the
         PLUGIN_TIME is before the START_TIME.

         Solution: AGENT_H.START_TIME is the date and time at which the
         agent record is either inserted by the initial deployment of
         the agent or updated by the redeployment of the agent, as
         indicated by the value I (insert) or U (update) held in the
         AGENT_H.START_ACTION field. Following the date and time
         indicated by AGENT_H.START_TIME, the agent remains current
         until the agent is deleted or updated, as indicated by the
         value D (delete) or U (update) held in the AGENT_H.END_ACTION
         field. Therefore, the period of time between the
         AGENT_H.START_TIME and the AGENT_H.END_TIME is the period of
         currency of the agent parameters held in the agent history
         record.

         AGENT.PLUGIN_TIME is the date and time at which the agent last
         sent its plug-in information to the runtime server. The agent
         sends the plug-in information in the following circumstances:
         *  When the agent is initially deployed
         *  Whenever the agent is stopped and restarted
         *  Whenever the runtime server is stopped and restarted
         *  When the agent is redeployed or upgraded
         *  When the agent has detected a change in the hardware of the
            node it is monitoring
         *  When the tlmagent command is issued with the -p parameter

         Since the START_TIME and the END_TIME are updated by the
         Administration Server when the agent data come from the Runtime
         Server it is possible that the PLUGIN_TIME is before the
         START_TIME, because the PLUGIN_TIME is communicated by the
         agent itself, while the START_TIME is the time when the data
         are available on the server for the first time or are updated.


APAR IY75360
         Problem: an overview of the kernel extension functionality is
         missing from the documentation.

         Solution: The kernel extension is a subcomponent of the Tivoli
         License Manager agent. It is installed together with the agent
         and is a kernel module that functions as an extension of the
         operating system of the computer on which the agent is
         installed. The kernel extension detects the starting and
         stopping of applications in a real-time mode and so enables the
         agent to collect information about the use of the applications
         and to generate requests for the grant and release of licenses.

         The kernel extension is installed on all platforms of Tivoli
         License Manager 2.1 supported at GA time. None of the new
         platforms that have been introduced in fix packs, other than
         AIX 5.3, have kernel extensions.

1.1.6 Problems fixed

The following problems were found since the general availability of
Tivoli License Manager, version 2.1 and fixed with this fix pack:
*  1.1.6.1, "For the administration server"
*  1.1.6.2, "For the runtime server"
*  1.1.6.3, "For the agent"
*  1.1.6.4, "For agent deployment"

1.1.6.1 For the administration server

Wrong dialog displayed in Contracts task
         During use of the administration server Web UI to create or
         update contract information, the wrong dialog is displayed when
         the legal and business information tab is selected. 

         With the fix pack, the correct dialog is displayed.


Internal error generated in the Use Trend report
         An internal error occurred when the Use Trend report attempted
         to report the use of a license that had since been deleted. 

         With the fix pack, the use trend report correctly reports use
         of the license even if it has been deleted.


Wrong value reported for the high water mark in the Unlicensed Use 
report.
         The high water mark for unlicensed use of products was being
         incorrectly calculated.

         With the fix pack, the high water mark is correctly reported.

1.1.6.2 For the runtime server

Error message wrongly displayed in Current Use report
         In the Current Use report, when the License Use option is
         selected from the main report page, an error message is
         displayed before the correct information is shown.

         With the fix pack, the error message is not displayed.


Error message in the Distributed Licenses report cannot be closed
         In the Distributed Licenses report, the error message that is
         displayed if the query returns no results does not contain a
         Close Message link.

         With the fix pack, the error message contains a Close Message
         link.


A column header has the wrong label in the Distribute Licenses report
         The column that is headed Product Name in the Distributed
         License report should be headed License Name.

         With the fix pack, the correct column header is displayed.

1.1.6.3 For the agent

The agent hangs when requested to stop.
         In some circumstances the agent hangs (on Linux 390) or takes a
         core dump (on Sun Solaris). 

         After installing the fix pack, this problem is resolved.


The agent self-update process does not check that prerequisite fixes for 
GSKit have been installed.
         This problem occurs on Windows and Sun Solaris platforms. 

         After installing the fix pack, this problem is resolved.


On Solaris platforms, any system shutdown or reboot causes the agent to 
terminate abnormally.
         The agent terminates abnormally even if the system is shutdown
         or rebooted in a clean manner.

         After installing the fix pack, the agent is stopped correctly
         before system shutdown when the init 6 or init 0 procedures are
         used.


On OS/400(R) platforms, strings containing paths were not converted to 
UTF8.
         WebSphere Application Server paths discovered by the WebSphere
         Application Server agent controller were not converted to UTF8
         format.

         With the fix pack, the conversion of paths is performed. If
         there is a discrepancy between the input and output values of
         the conversion, a warning is generated.


During reboot, the tlm script causes the startpar command to hang.
         This problem affects Linux systems. With the fix pack, this
         problem is resolved.

Products are prevented from starting when hardware configuration 
information is not available.
         For some license types, the agent must retrieve hardware
         information from the monitored computer. If it was not possible
         to retrieve this information because of a missing or corrupt
         MIF file, the license was denied and the product was prevented
         from starting even if the compliance level was set to Low.

         With the fix pack, the product is allowed to start and an
         exception is returned. Use information is not transmitted to
         the server, as this could cause erroneous information to be
         included in reports.


The WebSphere Application Server agent command line ends unexpectedly in 
some cases.
         With the fix pack, this problem is resolved.

An agent warning message is shown on the console of a computer where the 
agent is running.
         The message: CCGBC0071W The logging method's parameter list is
         missing type markers is shown periodically on the console of a
         computer where the agent is running. 

         With the fix pack, this message no longer appears.


The help argument for the tlmagent command ends with an error message.
         When the tlmagent command is issued with the -h argument, the
         output ends with an error message.

         With the fix pack, this problem is resolved.


Incorrect memory size information detected by the agent on Linux 390 
platforms.
         The agent information shown on the administration server Web UI
         for Linux 390 agents, includes incorrect information about the
         memory size of the host computer. 

         With the fix pack, this problem is resolved.


First Failure Data Capture (FFDC) performed twice for agents on AIX 
platforms.
         The agent FFDC command, which is invoked automatically to copy
         problem determination information to the FFDC directories in
         the Tivoli Common Directory when the agent is stopped, is
         performed twice when an agent stops on an AIX computer.

         With the fix pack, this problem is resolved.


The WebSphere Application Server agent command line does not work with 
the IPv6 protocol.
         If the IPv6 protocol is enabled, the command line of the
         WebSphere Application Server agent does not work. 

         With the fix pack, this problem is resolved.


On Red Hat Linux platforms, the agent self-update fails with a disk 
space error, even though there is enough space available.
         This problem occurs when the self-update involves an upgrade of
         the WebSphere Application Server agent. 

         With the fix pack, this problem is resolved.


On Linux platforms, information is lost if the agent is not stopped 
before the system is shut down.
         On Linux platforms, if the agent is not manually stopped before
         the system is shut down, any information about license or
         software use currently held by the agent is lost. 

         With the fix pack, this problem is resolved.

1.1.6.4 For agent deployment

The manual agent deploy script for UNIX platforms does not work.
         After installing the fix pack, this problem is resolved.

The RSH/SSH deployment wizard allows multiple selection in list boxes 
when defining the topology on which agents are to be deployed.
         The panel in the RSH/SSH agent deployment wizard, in which you
         set up a list of nodes where agents are to be deployed,
         includes list boxes for the deployment parameters:
         Organization, Division, and Runtime address. These list boxes
         support multiple selection. This is not useful because the tool
         is designed to allow the deployment of a group of agents that
         all use the same deployment parameters (Organization, Division,
         Runtime address). For each deployment run, you must select one
         set of deployment parameters and then specify the nodes on
         which agents are to be deployed using these parameters.

         With the fix pack, the list boxes support single selection
         only.


Using the SSH agent deploy method, the agent installation logs a failure 
return code after a successful installation.
         When the SSH agent deploy method is used, the return code -8
         (agent failed to start) is logged and a corresponding trace
         message is written even though the agent has been successfully
         installed and started.

         With the fix pack, this problem is resolved.

1.1.7 Backward compatibility

All previous fix packs and interim fixes are superseded by this fix
pack.

Dependencies:
   IBM Tivoli License Manager, Version 2.1

1.1.8 Other changes as a result of this fix pack

This fix pack creates or updates a file called <INST_DIR>\product.xml
(where <INST_DIR> is the directory where Tivoli License Manager is
installed), which keeps track of the current Tivoli License Manager
version.

Agents deployed after this fix pack has been applied to the runtime
server will have a new version number of 2.1.0.30. The individual
agents' software will be updated only when you specifically reinstall
the agent software, or after you have used the agent self-update
facility in the agent configuration file, as described in
IBM Tivoli License Manager: Planning, Installation, and Configuration.

1.2 Installation, migration, upgrade, and configuration information

This section includes the following topics:
*  1.2.1, "Hardware and software requirements"
*  1.2.2, "Installing the fix pack"
*  1.2.3, "After installing the fix pack"
*  1.2.4, "Upgrading agents"
*  1.2.5, "Reverting to the previous version"

1.2.1 Hardware and software requirements

This section includes the following topics:
*  1.2.1.1, "Supported platforms"
*  1.2.1.2, "System requirements"

1.2.1.1 Supported platforms

Information about supported platforms at GA is detailed in
IBM Tivoli License Manager: Planning, Installation, and Configuration.

The fix pack introduces support for the following new versions of
currently supported agent platforms:
*  AIX 5.3
*  SUSE LINUX Enterprise Server 9
*  Red Hat Enterprise Linux 3.0 Update 3
*  Red Hat Enterprise Linux 3.0 Update 4
*  Red Hat Enterprise Linux ES/AS/WS 4.0

Note:  To support Sub-Capacity licensing on Power 5 processors on AIX
      5.3 and SUSE LINUX Enterprise Server 9 you need to have the
      following system levels:
      *  AIX 5.3 maintenance level 2
      *  SUSE LINUX Enterprise Server 9 SP1

1.2.1.2 System requirements

Hardware and software prerequisites are detailed in
IBM Tivoli License Manager: Planning, Installation, and Configuration.
See 1.1.2.3, "Changes to agent prerequisites" for information about
changes in the agent prerequisites caused by the introduction of the new
agent platforms.

1.2.2 Installing the fix pack

This section contains the instructions for installing the fix pack. Once
you have installed the fix pack, you cannot uninstall it automatically.
For details of how to revert to the previous version see 1.2.5,
"Reverting to the previous version".

The fix pack includes the following files:

2.1.0-TIV-TLM-FP0003_servers_<platform>.zip
         For each supported platform, the compressed file contains the
         files for installing the fix pack on computers where
         administration server, a runtime server, or a runtime server
         database is installed.

2.1.0-TIV-TLM-FP0003-SPB.zip
         This file contains the software package blocks for each
         supported agent platform, to be used when deploying agents
         using IBM Tivoli Configuration Manager.

2.1.0-TIV-TLM-FP0003-RSH-SSH-Win.zip
         This contains the files needed to deploy agents on UNIX
         platforms using the RSH/SSH deployment wizard.



The instructions for running the installation wizard are the same for
both installation types.

Notes: 
1. Before starting the installation, back up the administration server
   database and the installation directories of administration server,
   runtime servers, and the catalog manager.
2. During the installation of the fix on the administration server or a
   runtime server, the wizard stops and starts the server. If the server
   is running in a WebSphere Application Server secure cell, you will be
   asked to provide the user ID and password for the secure cell. Ensure
   that you have this information before you start.

To install the fix pack, complete the following steps on each computer
where a component is installed: 
1. Log on to the computer where one or more of the Tivoli License
   Manager components is installed as Administrator (Windows) or root
   (UNIX).
2. Unpack the servers or catalog manager compressed file into a
   temporary directory.
3. Launch the setup file for the platform on which you are installing
   the fix pack. 

   The installation wizard starts.

   Note: No license agreement panel is displayed. The fix pack is
         subject to the same terms and conditions under which Tivoli
         License Manager, version 2.1 is licensed.

4. Specify a directory where the wizard can create a backup of your
   server configuration and other files that are affected by the fix
   pack and click Next. 

   If the wizard is unable to create the backup, the installation cannot
   continue. Ensure that you have the correct permissions to write to
   the specified directory and that there is sufficient space to create
   the backup.

   Note: The wizard calculates the space required to create the backup
         based on the initial size of a server when it is installed.
         Under normal circumstances, the space occupied by the server
         directories should not increase very much. However, if other
         directories, for example directories required for manual agent
         deployment, have been created within the server file structure,
         the space required for the backup could be considerably more
         than anticipated. Under these circumstances, it is possible
         that the installation could fail because of lack of space. If
         this occurs, a message will be displayed informing you that the
         installation has failed, possibly because of insufficient
         permissions. You must then make more space available for the
         installation.

5. Check the summary panel for the installation and click Next to
   confirm that you want to install the fix pack.

   If you are applying the fix pack to a server that is running in a
   WebSphere Application Server secure cell, you will be prompted to
   supply a valid user ID and password when the wizard stops and starts
   the runtime server.

6. When the installation is complete, click Finish.

1.2.3 After installing the fix pack

After you have installed the fix pack, you must perform the following
tasks where appropriate:
*  If you are using DB2 UDB Enterprise Server Edition, version 8.2 for
   your runtime server databases, you may experience problems in
   updating the software catalog tables when a new catalog is imported
   and downloaded from the administration server following application
   of the fix pack. These problems can be avoided by using the following
   DB2 configuration settings:
   *  pckcachesz = 64000
   *  locklist = 2000
   *  dbheap = 20000

*  If you had applied fix pack 2.1.0-TIV-TLM-FP0001 and are already
   using the unknown file skipping functionality described in APAR
   IY63893, the installation of this fix pack will have overwritten the
   unknownFiles.properties configuration file where you have defined the
   paths to be skipped because of the introduction of wildcard character
   (APAR IY68390). You can restore the configuration file from the
   backup created during the installation of the fix pack on the runtime
   server.

1.2.4 Upgrading agents

To apply the fixes to agents that are already deployed, you must
redeploy or update the agent. For information about how to do this see
the sections Redeploying an agent and Agent self-update in
IBM Tivoli License Manager: Planning, Installation, and Configuration.

Note: On Solaris and Windows platforms, the agent deployment process
      does not check that the operating system has the required patches
      applied for the installation of GSKit. Before upgrading or
      deploying agents on these platforms, you should check that all
      necessary patches are applied.

After installing this fix pack the following version changes take
effect: 
*  The agent version for all platforms becomes 2.1.0.30.
*  The kernel extension version for Linux for Intel X86 and Linux for
   S/390 changes to 2_1_0_10.
*  The driver agent version for AIX changes to 2101.

1.2.4.1 WebSphere Application Server agents

Where WebSphere Application Server is installed on a node that is
monitored by Tivoli License Manager with a GA level agent, the agent
must be upgraded as soon as this fix pack is applied to the runtime
server with which the agent is registered. If the runtime server has the
fix pack applied and the agent does not, the WebSphere Application
Server agent will not work.

Where WebSphere Application Server is not installed, you can delay
upgrading the GA level agent to the fix pack level. However, if at any
point you install WebSphere Application Server on a node that is
monitored by an agent that has not been upgraded, you must immediately
upgrade the agent to this fix pack. If you do not, the agent will not be
able to download the WebSphere Application Server agent.

If you have WebSphere Application Server, version 6.0 or WebSphere
Portal installed on a monitored computer, you should upgrade to, at
least, fix pack 2.1.0-TIV-TLM-FP0002 to obtain monitoring of J2EE
applications running inside these containers. If you do not apply the
upgrade, the agent is unable to detect WebSphere Application Server,
version 6.0 or WebSphere Portal and so will not monitor the applications
that are running within them.

When WebSphere Portal is installed, the file itlm.product is installed
in the directory: <WebSphere_Portal_Home>\version. This file contains
commented entries that identify WebSphere Portal products and versions.
To enable Tivoli License Manager monitoring of the WebSphere Portal
product that you have installed, you must edit the file and uncomment
the lines that relate to your product. If the file is changed after the
Tivoli License Manager agent is upgraded to this fix pack, you must
restart the agent for the changes you made to the itlm.product file to
take effect.

1.2.5 Reverting to the previous version

There is no automatic method for uninstalling this fix pack.

You must back-out the changes on each computer where the fix pack has
been installed, as follows: 
1. Stop the server.
2. Manually replace the files that were changed by the installation of
   the fix pack with the backup copies taken during the installation.

   The backup directory specified during the installation of the fix
   pack contains a subdirectory 2.1.0-TIV-TLM-FP0003 which contains a
   subset file structure for the Tivoli License Manager components to
   which the fix pack has been applied. You must copy the files manually
   from each subdirectory of the backup to the corresponding directory
   of the server or catalog manager installation.

3. If this is the first fix applied to the GA version of the code,
   delete the file <INSTALL_DIR>\product.xml. 

   If previous fixes have been applied, the product.xml file is one of
   the files that you have restored from the backup directory.

4. Restart the server.

1.3 General information

This section contains the following general information that might have
changed since these products were made available:
*  1.3.1, "Publications"
*  1.3.2, "Accessibility"
*  1.3.3, "Tivoli technical training"
*  1.3.4, "Contacting software support"
*  1.3.5, "Conventions used in this readme file"

1.3.1 Publications

This section lists publications in the Tivoli License Manager library
and related documents. It also describes how to access Tivoli
publications online and how to order Tivoli publications.

1.3.1.1 Tivoli License Manager library

The Tivoli License Manager library consists of the following books: 
*   IBM Tivoli License Manager: Administration

   Provides an overview of Tivoli License Manager and gives information
   about how to use the product to set up a monitoring infrastructure,
   define licensing conditions, and produce reports.

*   IBM Tivoli License Manager: Planning, Installation, and
   Configuration

   Provides information about planning, installing, and configuring the
   Tivoli License Manager product

*  IBM Tivoli License Manager: Data Dictionary 

   Provides descriptions of the database tables and indexes maintained
   in the Tivoli License Manager administration server database.

*  IBM Tivoli License Manager: Problem Determination

   Provides information about Tivoli License Manager diagnostic
   information, including messages, traces, and event logs, and about
   tools and techniques for diagnosing problems.

*  IBM Tivoli License Manager: Catalog Management

   Describes how to use the software catalog management tool to maintain
   an up-to-date master catalog of products and the modules that are
   used to detect their presence and use on monitored computers.

*  IBM Tivoli License Manager, Version 2.1: Warehouse Enablement Pack,
   Version 2.1.0 Implementation Guide for Tivoli Data Warehouse, Version
   1.2

   Provides instructions and other information related to enabling the
   use of Tivoli Data Warehouse with Tivoli License Manager.

*  IBM Tivoli License Manager: Release Notes 

   Provides a summary of changes made in the release, lists the
   supported platforms for each component, documents known errors and
   workarounds, and includes the latest information about the product
   that could not be included in the main documentation. This document
   is not delivered on the publications CD, but is available from the
   Tivoli Software Information Center. Updated versions of the document
   may be placed on the Tivoli Software Information Center at any time.

   How to access the Tivoli Software Information Center is described in
   1.3.1.3, "Accessing publications online".

1.3.1.2 Related publications

The following document also provides useful information:

*  IBM DB2 Universal Database(TM): Quick Beginnings for DB2 Servers
*  IBM DB2 Universal Database: Quick Beginnings for DB2 Clients

   These Quick Beginnings guides provide an introduction to installing
   and configuring DB2 products.

*  www.ibm.com/software/webservers/appserv/infocenter.html provides
   access to WebSphere Application Server product information.
*  Redbook: DB2/UDB/WebSphere Performance Tuning Guide

   This Redbook contains useful information about tuning DB2 and
   WebSphere Application Server for performance. In particular, see
   Sections 2.7-2.10, Chapter 3, Sections 3.3-3.5; and Chapters 4 and,
   5.

*  Redbook: IBM WebSphere V5.0 Performance, Scalability, and High
   Availability: WebSphere Handbook Series

   This Redbook contains information about tuning WebSphere Application
   Server for performance. In particular, see chapter 18.

*  IBM WebSphere Application Server, version 5.0.2: Monitoring and
   Tuning Performance

   This is the tuning guide for WebSphere Application Server, version 5.

*  Redbook: IBM WebSphere Application Server, version 5.0 System
   Management and Configuration

   This Redbook contains information about configuring WebSphere
   Application Server, version 5.

The Tivoli Software Glossary includes definitions for many of the
technical terms related to Tivoli software. The Tivoli Software Glossary
is available, in English only, at the following Web site:

www.ibm.com/software/tivoli/library

Access the glossary by clicking the Glossary link on the left pane of
the Tivoli software library window.

1.3.1.3 Accessing publications online

The Tivoli License Manager documentation CD contains the publications
that are in the product library, other than the
IBM Tivoli License Manager: Release Notes, in all supported languages.
The format of the publications is PDF, HTML, or both. To access the
publications using a Web browser, open the allpubs.htm file. The file is
in the root directory on the documentation CD. Select the language of
your choice, and an Information Center for the product in that language
is displayed. Select the publication and the format in which you want to
view it.

Note: On Windows platforms, an autorun opens the allpubs.htm file in
      your default browser.

IBM posts publications for this and all other Tivoli products, as they
become available and whenever they are updated, to the Tivoli Software
Information Center Web site. Access the Tivoli Software Information
Center by first going to the Tivoli software library at the following
Web address:

www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link on the left pane of the
Tivoli software library window. In the Tivoli Technical Product
Documents Alphabetical Listing window, click the IBM Tivoli License
Manager link to access the product library at the Tivoli Information
Center.

Note:  If you print PDF documents on other than letter-sized paper, set
      the option in the File -> Print window that allows Adobe Reader to
      print letter-sized pages on your local paper.

1.3.1.4 Ordering publications

You can order many Tivoli publications online at the following Web site:


  www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pb
  i.cgi

You can also order by telephone by calling one of these numbers:

*  In the United States: 800-879-2755
*  In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone
numbers:

www.ibm.com/software/tivoli/order-lit/

1.3.2 Accessibility

Accessibility features help users with a physical disability, such as
restricted mobility or limited vision, to use software products
successfully. With this product, you can use assistive technologies to
hear and navigate the interface. You can also use the keyboard instead
of the mouse to operate all features of the graphical user interface.

This product is operated using a Web browser, which has certain built-in
accessibility features, and has been provided with specific shortcut
keys for navigating the Web interface, starting tasks, and performing
toolbar actions.

1.3.3 Tivoli technical training

For Tivoli technical training information, refer to the following IBM
Tivoli Education Web site:

www.ibm.com/software/tivoli/education/

1.3.4 Contacting software support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active
IBM software maintenance contract, and you must be authorized to submit
problems to IBM. The type of software maintenance contract that you need
depends on the type of product you have:
*  For IBM distributed software products (including, but not limited to,
   Tivoli, Lotus(R), and Rational(R) products, as well as DB2 and
   WebSphere products that run on Windows or UNIX operating systems),
   enroll in Passport Advantage(R) in one of the following ways:
   *  Online: Go to the Passport Advantage Web page and click How to
      Enroll . The Web address is the following:

      www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home

   *  By phone: For the phone number to call in your country, go to the
      IBM Software Support Web site
      (techsupport.services.ibm.com/guides/contacts.html) and click the
      name of your geographic region.

*  For IBM eServer(TM) software products (including, but not limited to,
   DB2 and WebSphere products that run in zSeries, pSeries, and iSeries
   environments), you can purchase a software maintenance agreement by
   working directly with an IBM sales representative or an IBM Business
   Partner. For more information about support for eServer software
   products, go to the IBM Technical Support Advantage Web page
   (www.ibm.com/servers/eserver/techsupport.html).

If you are not sure what type of software maintenance contract you need,
call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other
countries, go to the contacts page of the IBM Software Support Handbook
on the Web (techsupport.services.ibm.com/guides/contacts.html) and click
the name of your geographic region for phone numbers of people who
provide support for your location.

Follow the steps in this topic to contact IBM Software Support:
1. 1.3.4.1, "Determine the business impact of your problem"
2. 1.3.4.2, "Describe your problem and gather background information"
3. 1.3.4.3, "Submit your problem to IBM Software Support"

1.3.4.1 Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity
level. Therefore, you need to understand and assess the business impact
of the problem you are reporting. Use the following criteria:

+------------------+--------------------------------------------------+
| Severity 1       | Critical business impact: You are unable to use  |
|                  | the program, resulting in a critical impact on   |
|                  | operations. This condition requires an immediate |
|                  | solution.                                        |
+------------------+--------------------------------------------------+
| Severity 2       | Significant business impact: The program is      |
|                  | usable but is severely limited.                  |
+------------------+--------------------------------------------------+
| Severity 3       | Some business impact: The program is usable with |
|                  | less significant features (not critical to       |
|                  | operations) unavailable.                         |
+------------------+--------------------------------------------------+
| Severity 4       | Minimal business impact: The problem causes      |
|                  | little impact on operations, or a reasonable     |
|                  | circumvention to the problem has been            |
|                  | implemented.                                     |
+------------------+--------------------------------------------------+

1.3.4.2 Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include
all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently. To save time,
know the answers to these questions:

*  What software versions were you running when the problem occurred?
*  Do you have logs, traces, and messages that are related to the
   problem symptoms? IBM Software Support is likely to ask for this
   information.
*  Can the problem be recreated? If so, what steps led to the failure?
*  Have any changes been made to the system? (For example, hardware,
   operating system, networking software, and so on.)
*  Are you currently using a workaround for this problem? If so, please
   be prepared to explain it when you report the problem.

The problem determination toolkit includes commands for assembling
problem determination information for all product components. For more
information see IBM Tivoli License Manager: Problem Determination.

1.3.4.3 Submit your problem to IBM Software Support

You can submit your problem in one of two ways:

*  Online: Go to the "Submit and track problems" page on the IBM
   Software Support site (www.ibm.com/software/support/probsub.html).
   Enter your information into the appropriate problem submission tool.
*  By phone: For the phone number to call in your country, go to the
   contacts page of the IBM Software Support Handbook on the Web
   (techsupport.services.ibm.com/guides/contacts.html) and click the
   name of your geographic region.

If the problem you submit is for a software defect or for missing or
inaccurate documentation, IBM Software Support creates an Authorized
Program Analysis Report (APAR). The APAR describes the problem in
detail. Whenever possible, IBM Software Support provides a workaround
for you to implement until the APAR is resolved and a fix is delivered.
IBM publishes resolved APARs on the IBM product support Web pages daily,
so that other users who experience the same problem can benefit from the
same resolutions.

For more information about problem resolution, see 1.3.4.4, "Searching
knowledge bases" and 1.3.4.5, "Obtaining fixes".

1.3.4.4 Searching knowledge bases

If you have a problem with your IBM software, you want it resolved
quickly. Begin by searching the available knowledge bases to determine
whether the resolution to your problem is already documented.

1.3.4.4.1 Search the information center on your local system or network

IBM provides extensive documentation that can be installed on your local
machine or on an intranet server. You can use the search function of
this information center to query conceptual information, instructions
for completing tasks, reference information, and support documents.

1.3.4.4.2 Search the Internet

If you cannot find an answer to your question in the information center,
search the Internet for the latest, most complete information that might
help you resolve your problem. To search multiple Internet resources for
your product, expand the product folder in the navigation frame to the
left and select Support on the Web. From this topic, you can search a
variety of resources including:
*  IBM technotes
*  IBM downloads
*  IBM Redbooks(TM)
*  IBM DeveloperWorks
*  Forums and newsgroups
*  Google

1.3.4.5 Obtaining fixes

A product fix might be available to resolve your problem. You can
determine what fixes are available for your IBM software product by
checking the product support Web site:
1. Go to the IBM Software Support Web site
   (www.ibm.com/software/support).
2. Under Products A - Z, select your product name. This opens a
   product-specific support site.
3. Under Self help, follow the link to Search all Downloads, where you
   will find a list of fixes, fix packs, and other service updates for
   your product. For tips on refining your search, click Search tips.
4. Click the name of a fix to read the description and optionally
   download the fix.

To receive weekly e-mail notifications about fixes and other news about
IBM products, follow these steps:
1. From the support page for any IBM product, click My support in the
   upper-right corner of the page.
2. If you have already registered, skip to the next step. If you have
   not registered, click register in the upper-right corner of the
   support page to establish your user ID and password.
3. Sign in to My support.
4. On the My support page, click Edit profiles in the left navigation
   pane, and scroll to Select Mail Preferences. Select a product family
   and check the appropriate boxes for the type of information you want.
5. Click Submit.
6. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support
Handbook (techsupport.services.ibm.com/guides/handbook.html).

1.3.4.6 Updating support information

Information centers typically include one or more support information
plug-ins. These plug-ins add IBM technotes and other support documents
to the information center. The following steps describe how to update
your support information plug-ins:
1. Go to the IBM Software Support Web site
   (www.ibm.com/software/support).
2. Under Products A - Z, select your product name. This opens a
   product-specific support site.
3. Under Search support for this product, type the keyword phrase:
   com.ibm.support. Click the Download check box, and click Submit.
4. Check the search results for updates to support information plug-ins.
   All support information plug-ins follow the naming convention,
   "com.ibm.support.product.doc." If an update is available, select it
   from the list and view the download instructions.
5. Save the attached zip file to a temporary location on your hard
   drive.
6. Unzip the downloaded file, making sure that you retain the
   subfolders.
7. From the location where you unzipped the file, copy the support
   information plug-in folder to your Eclipse plug-ins folder. For
   example, if your IBM software product is installed at
   c:\IBM\WebSphere\, copy the updated plug-in folder
   (com.ibm.support.product.doc) to c:\IBM\WebSphere\eclipse\plugins.
8. To see the updated support information, start the information center
   (or shut it down and restart it), and expand the Support information
   node in the navigation tree.

1.3.5 Conventions used in this readme file

This readme file uses the following typeface conventions:

Bold              
                  *  Lowercase commands and mixed case commands that are
                     otherwise difficult to distinguish from surrounding
                     text
                  *  Interface controls (check boxes, push buttons,
                     radio buttons, spin buttons, fields, folders,
                     icons, list boxes, items inside list boxes,
                     multicolumn lists, containers, menu choices, menu
                     names, tabs, property sheets), labels (such as
                     Tip:, and Operating system considerations:)
                  *  Column headings in a table
                  *  Keywords and parameters in text


Italic            
                  *  Citations (titles of books, diskettes, and CDs)
                  *  Words defined in text
                  *  Variables and values you must provide


Monospace         
                  *  Examples and code examples
                  *  File names, programming keywords, and other
                     elements that are difficult to distinguish from
                     surrounding text
                  *  Message text and prompts addressed to the user
                  *  Text that the user must type
                  *  Values for arguments or command options


<text>            
                  *  Indicates a variable in a path name. For example in
                     the path <INSTALL_DIR>/admin/conf, INSTALL_DIR
                     depends on the location where you have installed
                     the component, while /admin/conf is constant.

2.0 Notices

This information was developed for products and services offered in the
U.S.A. 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 give 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-178, U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

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

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own
risk.

IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged,
should contact:



IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX  78758 	U.S.A.

Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.

Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related
to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.

2.1 Trademarks

The following terms are trademarks of the IBM Corporation in the United
States or other countries or both: 

IBM
The IBM logo 
AIX
 DB2
 DB2 Universal Database
 eServer
 IBM
 iSeries
 Lotus
 OS/400
 Passport Advantage
 pSeries
 Rational
 Redbooks
 Tivoli
 WebSphere
 zSeries

Microsoft, Windows, and the Windows logo are registered trademarks, of
Microsoft Corporation in the U.S. and other countries.

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

Intel is a trademark of Intel Corporation in the United States, other
countries, or both.

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

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

