<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Unclassified

                 IBM Tivoli License Compliance Manager
            Readme File for  Fix Pack 2.3.0-TIV-TLCM-FP0001

Version 2.3

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

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

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



This edition applies to the fix pack 2.3.0-TIV-TLCM-FP0001 for version
2, release 3 of IBM Tivoli License Compliance 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, 2007. All 
rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure 
restricted by GSA ADP Schedule Contract with IBM Corp.


Contents

1.0 Readme File for fix pack 2.3.0-TIV-TLCM-FP0001
  1.1 About this fix pack
    1.1.1 Hardware inventory collection
    1.1.2 Agent installation size check
    1.1.3 Support for partitioning technologies
    1.1.4 Product fixes
    1.1.5 Documentation fix history
    1.1.6 Backward compatibility
    1.1.7 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 Upgrading agents
    1.2.4 Reverting to the previous version
2.0 Notices
  2.1 Trademarks

1.0 Readme File for fix pack 2.3.0-TIV-TLCM-FP0001

This readme provides important information about the fix pack
2.3.0-TIV-TLCM-FP0001 for IBM(R) Tivoli License Compliance Manager,
version 2.3. 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 fix
pack.

This readme includes the following topics:

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

Note: To install the fix pack, you must be logged on as Administrator
      (on Windows(R)) or root (on UNIX(R)) to the computer where Tivoli
      License Compliance Manager is installed .

1.1 About this fix pack

Fix pack 2.3.0-TIV-TLCM-FP0001 includes support for the new Hardware
Inventory scan functionality and for additional agent platforms. It also
includes fixes for reported APARs and defects.

This section includes the following topics:

*  New functionality. See 1.1.1, "Hardware inventory collection".
*  1.1.2, "Agent installation size check"
*  1.1.3, "Support for partitioning technologies"
*  1.1.4, "Product fixes"
*  1.1.4.2, "Problems and workarounds"
*  1.1.5, "Documentation fix history"
*  1.1.6, "Backward compatibility"
*  1.1.7, "Other changes as a result of this fix pack"

1.1.1 Hardware inventory collection

Hardware inventory collection is an optional feature that enables Tivoli
License Compliance Manager to collect and store hardware configuration
information for hardware reconciliation processing by IBM Maximo Asset
Management for IT.

You can use commands, available from the administration command line
interface, to perform the following tasks: 
*  Enable the hardware inventory scan feature. This feature is disabled
   by default. See 1.1.1.1, "Enabling the hardware inventory scan
   feature".
*  Define rules for the generation of a Globally Unique Identifier
   (GUID) for each monitored computer. Use of a GUID simplifies the
   reconciliation of hardware information with the system to which it
   relates. See 1.1.1.2, "Defining the rule for generating GUIDs".
*  Configure hardware inventory scanning. This includes scheduling scans
   and determining whether to collect information in virtualized
   environments. See 1.1.1.3, "Configuring the hardware inventory scan".
*  Check the current values for the hardware inventory scan
   configuration. See 1.1.1.4, "Checking the configuration".
*  Check the status of hardware inventory scans. See 1.1.1.5, "Checking
   the scan status".

Notes: 
1. You cannot activate hardware inventory collection if you are using
   either Tivoli License Compliance Manager for IBM software or IBM
   Tivoli(R) Configuration Manager License Manager extension.
2. Hardware inventory scanning is not implemented on i5/OS(R) platforms
   or on Linux(R) platforms running on zSeries(R).

An initial hardware scan is automatically performed as soon as the agent
is deployed. Changes that imply a migration of the agent, for example
changing disks or upgrading the CPU do not trigger an automatic scan. To
obtain consistently updated information about changes in hardware
configuration, you must schedule scans to run on a regular basis or
request a one-off scan after you have made changes.

To issue any of these commands, start the administration server command
line interface, as follows: 

Windows  Open the Start menu and click Tivoli License Compliance Manager
         &gt;Admin CLI.

UNIX     
         1. Open a shell window and change to the directory: 

            &lt;INSTALL_DIR&gt;/admin/cli

         2. Enter the command: 

            . ./tlmcli

1.1.1.1 Enabling the hardware inventory scan feature

Following installation of the fix pack, the hardware inventory scan
feature is disabled by default. You can enable the feature using the
hwscanenable command.

Command syntax
         hwscanenable {-d | -e}

         To enable the feature, issue the command:

         hwscanenable -e

1.1.1.2 Defining the rule for generating GUIDs

You can configure Tivoli License Compliance Manager to generate a GUID
for each monitored computer using a specified rule. The following
options are available: 

None     Do not generate a GUID

	CSProduct
         Generate a GUID by concatenating the values for manufacturer,
         model, and serial number.

PrimaryMACAddress
         Generate a GUID using the Media Access Control (MAC) address of
         the first network card discovered on the computer.

Note: Neither method is able to generate unique GUIDs for systems
      running inside virtual containers or LPARs.

Use the hwscanguidrule command to set rule for generating a GUID. The
default value is None.

Command syntax
         hwscanguidrule {None | CSProduct | PrimaryMACAddress}

         For example, to set the rule to CSProduct, , issue the command:

         hwscanguidrule CSProduct

Note: Any change you make to the rule takes effect the next time a
      hardware scan is performed on each agent.

1.1.1.3 Configuring the hardware inventory scan

Configuration of the hardware inventory scan includes specifying whether
agents running in virtualized environments are to perform the scan and
defining the scan schedule. Both types of configuration can be applied
to all the agents for a specified organization or limited to those
within a specified division of the organization.

Command syntax
         The command for configuring hardware inventory scans is
         hwscanconf. It has the following syntax:

         hwscanconf {-organization | -division} {-n &lt;name&gt; | -i &lt;ID&gt;}
         [-S &lt;start_time&gt; -N {1 | 7 | 30} -R &lt;repetitions&gt;] [{-e | -d}]

         where: 

         -organization
                  specifies that the type of target for which the
                  configuration is being defined is an organization. The
                  organization name is specified using the -n parameter.

         -division
                  specifies that the type of target for which the
                  configuration is being defined is a division. The
                  division name is specified using the -n parameter. If
                  you have multiple organizations that include divisions
                  with the same name, you can uniquely identify the
                  division by specifying the ID, using the -i parameter.

         -n name  specifies the name of the organization or division.

         -i ID    specifies the unique ID of the division.

         -S start_time
                   Specifies the date and time when the first or only
                  occurrence of a hardware scan is start. The format
                  start_time must be YYYY-MM-DD-hh.mm.ss. When the
                  command is used to schedule a hardware scan, this
                  parameter is required.

         -N       Specifies the number of days included in the repeating
                  period for a regular scan. Possible values are 1, 7,
                  and 30. This parameter can only be specified if -S and
                  -R are also specified.

         -R repetitions
                  specifies the number repeating period that separate
                  consecutive occurrences of the scan. The length of
                  each repeating period is defined by the -N parameter.
                  This parameter can only be specified if -S and -N are
                  also specified.

         -e       specifies that the hardware scan is enabled in
                  virtualized environments.

         -d       specifies that the hardware scan is disabled in
                  virtualized environments.


Specifying the rules for running the hardware scan in virtualized 
environments
         Once the hardware inventory scan feature is enabled, the
         default configuration enables collection of information from
         both physical and virtual environments. However, when the
         hardware scan runs in a virtualized environment, it collects
         information related to the virtual machine rather than
         information about the physical hardware on which the virtual
         machine is running and this information is not required by IBM
         Maximo Asset Management for IT. You can collect and store this
         information for your own use or you can use the configuration
         command to define rules that disable the scan on agents running
         in virtualized environments. 

         The following supported environments are considered to be
         virtualized: 
         *  HP Integrity VM guests
         *  HP vPar
         *  VMware guests
         *  Microsoft(R) Virtual Server guests
         *  Solaris Containers (Zones) guests

         Note: LPAR is not treated as a virtualized environment.

         To specify that agents of the Sales division that are running
         in virtualized environments are not to perform the scan, issue
         the following command:

         hwscanconf -division -n Sales -d

         If your environment includes multiple organizations and more
         than one organization has a Sales division, a message is shown,
         listing each Sales division with the name of the organization
         to which it belongs and its unique division ID. Reissue the
         command, using the division ID, as follows:

         hwscanconf -division -i &lt;ID&gt; -d

         To reenable scanning of virtualized environments, issue the
         command replacing the -d parameter with -e.


Scheduling hardware inventory scans
         Using the configuration command, you can schedule a single
         hardware inventory scan or set up a series of regularly
         repeating scans. 

         To set up the schedule, you must specify the date and time on
         which the first or only scan is to be performed. The scheduled
         time is the agent system time at which the scan is to be
         completed.

         When setting up a repeating schedule you must also define the
         frequency of scans.

         To schedule a single occurrence of a hardware inventory scan
         for agents in the Sales division, at the agent system time of
         midnight on 1st June 2007, issue the following command:

         hwscanconf -division -n Sales -S 2007-06-01-00.00.00

         Scans can be scheduled to repeat at regular intervals that are
         multiples of 1, 7, or 30 days. To schedule a series of hardware
         inventory scans for agents in the Sales division, to start at
         agent system time of midnight on 1st June 2007 and repeat every
         4 weeks, issue the following command:

         hwscanconf - division -n Sales -S 2007-06-01-00.00.00 -N 7 -R 4

         If there is more than one Sales division, the command fails.
         Reissue the command, specifying -i parameter and the division
         ID.

1.1.1.4 Checking the configuration

You can use the hwscanshow report to request a report of the rules and
schedules you created using the hwscanconf command. The report can
include an entire organization or can be limited to a specified
division. It can be produced in either XML or CSV format.

Command syntax
         The hwscanshow command has the following syntax:

         hwscanshow &lt;format&gt; &lt;filename&gt; {-organization | -division} {-n
         &lt;name&gt; | -i &lt;ID&gt;}

         where: 

         format   is the format in which the report is to be produced.
                  Possible values are CSV and XML.

         filename is the name of the output file to be produced.

         -organization
                  specifies that the type of target for which the
                  configuration is being shown is an organization. The
                  organization name is specified using the -n parameter.

         -division
                  specifies that the type of target for which the
                  configuration is being shown is a division. The
                  division name is specified using the -n parameter. If
                  you have multiple organizations that include divisions
                  with the same name, you can uniquely identify the
                  division by specifying the ID, using the -i parameter.

         -n name  specifies the name of the organization or division.

         -i ID    specifies the unique ID of the division.


Checking the hardware inventory scan configuration for a specified 
organization
         To produce a report, in XML format, of the rules and schedules
         set up for the SafeBank organization, issue the following
         command:

         hwscanshow XML invrules.xml -organization -n SafeBank



1.1.1.5 Checking the scan status

You can use the hwscanstatus command to request a report detailing when
the last scan was scheduled and when the scan was actually last
performed for each agent. The report can include agents for an entire
organization or can be limited to a specified division. It can be
produced in either XML or CSV format. You can request that the report
include only those agents where the last scheduled scan was not
performed, that is, agents where the last scan time is earlier than the
last scheduled scan time.

Command syntax
         The hwscanstatus command has the following syntax:

         hwscanstatus &lt;format&gt; &lt;filename&gt; [-p] {-organization |
         -division} {-n &lt;name&gt; | -i &lt;ID&gt;}

         where: 

         format   is the format in which the report is to be produced.
                  Possible values are CSV and XML.

         filename is the name of the output file to be produced.

         -p       If specified, the report includes only agents where
                  the last scheduled scan was not performed.

         -organization
                  specifies that the type of target for which the status
                  is being shown is an organization. The organization
                  name is specified using the -n parameter.

         -division
                  specifies that the type of target for which the status
                  is being shown is a division. The division name is
                  specified using the -n parameter. If you have multiple
                  organizations that include divisions with the same
                  name, you can uniquely identify the division by
                  specifying the ID, using the -i parameter.

         -n name  specifies the name of the organization or division.

         -i ID    specifies the unique ID of the division.


Checking the hardware inventory scan status for a specified organization
         To produce a report, in CSV format, of the agents in the
         SafeBank organization that did not successfully perform the
         last scheduled hardware inventory scan, issue the following
         command:

         hwscanstatus CSV hwinvstatus.csv -p -organization -n SafeBank

1.1.1.6 Database changes

The hardware inventory scan feature adds the following tables to the
administration server database:
*  1.1.1.6.1, "The TLMHW.COMPONENT table": Stores common system
   information about monitored systems.
*  1.1.1.6.2, "The TLMHW.COMPUTER table": Stores common system
   information about monitored systems.
*  1.1.1.6.3, "The TLMHW.COMPUTER_SYS_MEM table": Stores information
   about installed memory on monitored systems.
*  1.1.1.6.4, "The TLMHW.HDISK table": Stores information about storage
   devices on monitored systems.
*  1.1.1.6.5, "The TLMHW.INST_MODEM table": Stores information about
   modems installed on monitored systems.
*  1.1.1.6.6, "The TLMHW.INST_MOUSE table": Stores information about
   pointing devices on monitored systems.
*  1.1.1.6.7, "The TLMHW.INST_PARTITION table": Stores information about
   disk partitions on monitored systems.
*  1.1.1.6.8, "The TLMHW.INST_PRINTER table": Stores information about
   printers attached to monitored systems.
*  1.1.1.6.9, "The TLMHW.INST_PROCESSOR table": Stores information about
   processors on monitored systems.
*  1.1.1.6.10, "The TLMHW.INST_SMBIOS_DATA table": Stores general SMBIOS
   information for monitored systems.
*  1.1.1.6.11, "The TLMHW.INST_USB_DEV table": Stores information about
   USB devices on monitored systems.
*  1.1.1.6.12, "The TLMHW.INST_VID_CARD table": Stores information about
   video cards on monitored systems.
*  1.1.1.6.13, "The TLMHW.IP_ADDR table": Stores information about IP
   addresses on monitored systems.
*  1.1.1.6.14, "The TLMHW.IPX_ADDR table": Stores information about IPX
   addresses on monitored systems.
*  1.1.1.6.15, "The TLMHW.MEM_MODULES table": Stores information about
   all memory modules installed in a monitored system.
*  1.1.1.6.16, "The TLMHW.MODEM table": Stores the details for types and
   models of modem.
*  1.1.1.6.17, "The TLMHW.MONITOR table". Stores information about all
   monitors connected to monitored systems.
*  1.1.1.6.18, "The TLMHW.MOUSE table". Stores the details for types and
   models of pointing device.
*  1.1.1.6.19, "The TLMHW.NET_ADAPTER table": Stores information about
   network adapters on monitored systems.
*  1.1.1.6.20, "The TLMHW.PCI_DEV table": Stores information about
   peripheral component interconnect (PCI) devices on monitored systems.
*  1.1.1.6.21, "The TLMHW.PC_SYS_PARAMS table": Stores BIOS information
   for monitored PCs.
*  1.1.1.6.22, "The TLMHW.PRINTER table": Stores the details of types
   and models of printer.
*  1.1.1.6.23, "The TLMHW.PROCESSOR table": Stores the details of types
   and models of processor.
*  1.1.1.6.24, "The TLMHW.SMBIOS_SYS_DATA table": Stores information
   SMBIOS configurations.
*  1.1.1.6.25, "The TLMHW.STORAGE_DEV table": Stores information about
   storage devices on monitored systems.
*  1.1.1.6.26, "The TLMHW.UNIX_SYS_PARAMS table": Stores system
   parameter information for monitored UNIX systems.
*  1.1.1.6.27, "The TLMHW.USB_DEV table": Stores information about types
   of USB device.
*  1.1.1.6.28, "The TLMHW.VID_CARD table": Stores information about
   types of video card.

Additions have been made to several tables in the administration server
database to support the hardware inventory scan feature. See 1.1.1.6.29,
"Changed tables".

1.1.1.6.1 The TLMHW.COMPONENT table

Stores information about hardware components.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| ID            | The component ID             | bigint     | no |
+---------------+------------------------------+------------+----+
| MODEL         | The component model.         | varchar    | ye |
|               |                              | (128)      | s  |
+---------------+------------------------------+------------+----+
| SERIAL_NUMBER | The serial number of the     | varchar    | ye |
|               | component.                   | (64)       | s  |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer of the      | varchar    | ye |
|               | component                    | (64)       | s  |
+---------------+------------------------------+------------+----+
| VERSION       | The component version.       | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| TYPE          | The component type.          | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| MODEL_CLASS   | The model class of the       | varchar    | ye |
|               | component                    | (64)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.2 The TLMHW.COMPUTER table

Stores common information about a computer system. One entry exists for
each system scanned.

Table 1.  The TLMHW.COMPUTER table
+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| COMPUTER_SCAN | The date and time of the     | timestamp  | ye |
| TIME          | most recent hardware scan in |            | s  |
|               | Greenwich Mean Time.         |            |    |
+---------------+------------------------------+------------+----+
| COMPUTER_MODE | The model of the system.     | varchar    | ye |
| L             |                              | (128)      | s  |
+---------------+------------------------------+------------+----+
| COMPUTER_BOOT | The date and time that the   | timestamp  | ye |
| _TIME         | system was last restarted.   |            | s  |
+---------------+------------------------------+------------+----+
| COMUTER_ALIAS | The host name of the system. | varchar    | ye |
|               |                              | (255)      | s  |
+---------------+------------------------------+------------+----+
| SYS_SER_NUM   | The serial number of the     | varchar    | ye |
|               | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| OS_NAME       | The specific operating       | varchar    | ye |
|               | system that is installed,    | (128)      | s  |
|               | for example Windows Server   |            |    |
|               | 2003 Standard Edition.       |            |    |
+---------------+------------------------------+------------+----+
| OS_TYPE       | The type of operating system | varchar    | ye |
|               | that is installed, for       | (32)       | s  |
|               | example Windows Server 2003. |            |    |
+---------------+------------------------------+------------+----+
| OS_MAJOR_VERS | The major version of the     | integer    | ye |
|               | operating system.            |            | s  |
+---------------+------------------------------+------------+----+
| OS_MINOR_VERS | The minor version of the     | integer    | ye |
|               | operating system.            |            | s  |
+---------------+------------------------------+------------+----+
| OS_SUB_VERS   | The sub-version of the       | varchar    | ye |
|               | operating system.            | (32)       | s  |
+---------------+------------------------------+------------+----+
| OS_INST_DATE  | The date when the operating  | varchar    | ye |
|               | system was installed.        | (32)       | s  |
+---------------+------------------------------+------------+----+
| REGISTERED_OW | The name of the owner of the | varchar    | ye |
| NER           | system                       | (255)      | s  |
+---------------+------------------------------+------------+----+
| REGISTERED_OR | The name of the organization | varchar    | ye |
| G             | to which the system belongs. | (255)      | s  |
+---------------+------------------------------+------------+----+
| KEYBOARD_TYPE | A description of the type of | varchar    | ye |
|               | keyboard assigned to the     | (255)      | s  |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| FUNCTION_KEYS | The number of function keys  | integer    | ye |
|               | on the keyboard.             |            | s  |
+---------------+------------------------------+------------+----+
| TZ_LOCALE     | The locale of the time zone  | varchar    | ye |
|               | in which the system is       | (32)       | s  |
|               | located.                     |            |    |
+---------------+------------------------------+------------+----+
| TZ_NAME       | The name of the time zone in | varchar    | ye |
|               | which the system is located. | (64)       | s  |
+---------------+------------------------------+------------+----+
| TZ_DAYLIGHT_N | The name of the daylight     | varchar    | ye |
| AME           | saving time zone in which    | (64)       | s  |
|               | the system is located.       |            |    |
+---------------+------------------------------+------------+----+
| ON_SAVINGS_TI | Indicates whether the system | char (1)   | ye |
| ME            | is on daylight saving time.  |            | s  |
+---------------+------------------------------+------------+----+
| TZ_SECONDS    | The number of seconds        | integer    | ye |
|               | difference between the       |            | s  |
|               | system time zone and         |            |    |
|               | Greenwich Mean Time.         |            |    |
+---------------+------------------------------+------------+----+
| TIME_DIRECTIO | Indicates whether the time   | char (1)   | ye |
| N             | zone is early or later than  |            | s  |
|               | Greenwich Mean Time.         |            |    |
+---------------+------------------------------+------------+----+
| OS_ARCH       | The operating system         | varchar    | ye |
|               | architecture for the system. | (24)       | s  |
+---------------+------------------------------+------------+----+
| OS_KERNEL_MOD | The operating system kernel  | varchar    | ye |
| E             | mode                         | (32)       | s  |
+---------------+------------------------------+------------+----+
| OS_LANG_VERS  | The operating system         | varchar    | ye |
|               | language version identifies  | (64)       | s  |
|               | the default language for the |            |    |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| OS_LCID       | The operating system locale  | varchar    | ye |
|               | identifier                   | (64)       | s  |
+---------------+------------------------------+------------+----+
| CURRENT_LCID  | The current locale           | varchar    | ye |
|               | identifier                   | (64)       | s  |
+---------------+------------------------------+------------+----+
| VM_CHAIN_HASH | The hash of the virtual      | char (24)  | ye |
|               | layer that hosts the agent.  |            | s  |
+---------------+------------------------------+------------+----+
| VIRTUAL_COMP_ | Indicates whether the        | smallint   | no |
| TYPE          | monitored system is          |            |    |
|               | virtualized. Possible values |            |    |
|               | are 0 (not virtualized) or 1 |            |    |
|               | (virtualized).               |            |    |
+---------------+------------------------------+------------+----+
| COMPUTER_GUID | The Globally Unique          | char (32)  | ye |
|               | Identifier (GUID) of the     |            | s  |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| COMPUTER_GUID | Indicates the rule for       | integer    | ye |
| _TYPE         | generation of the GUID that  |            | s  |
|               | was in use when the current  |            |    |
|               | information was collected.   |            |    |
|               | Possible values are:         |            |    |
|               | 1                            |            |    |
|               | Concatenate the values for   |            |    |
|               | manufacturer, model, and     |            |    |
|               | serial number.               |            |    |
|               | 3                            |            |    |
|               | Use the Media Access Control |            |    |
|               | (MAC) address of the first   |            |    |
|               | network card discovered on   |            |    |
|               | the system.                  |            |    |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.3 The TLMHW.COMPUTER_SYS_MEM table

Stores information about the physical and virtual memory installed on a
system. One entry exists for each system scanned.

+----------------+---------------------------------+--------------+---+
| Columns        | Description                     | Type         | N |
|                |                                 |              | u |
|                |                                 |              | l |
|                |                                 |              | l |
+----------------+---------------------------------+--------------+---+
| COMPUTER_SYS_I | Unique identifier of the        | bigint       | n |
| D              | system.                         |              | o |
+----------------+---------------------------------+--------------+---+
| PHYSICAL_TOTAL | The total physical memory in    | bigint       | y |
| _KB            | KB.                             |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| PHYSICAL_FREE_ | The amount of free physical     | bigint       | y |
| KB             | memory in KB                    |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| TOTAL_PAGES    | The total number of physical    | bigint       | y |
|                | memory pages                    |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| FREE_PAGES     | The number of free physical     | bigint       | y |
|                | memory pages.                   |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| PAGE_SIZE      | The size of a page.             | bigint       | y |
|                |                                 |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| VIRT_TOTAL_KB  | The total amount of virtual     | bigint       | y |
|                | memory in KB                    |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| VIRT_FREE_KB   | The amount of free virtual      | bigint       | y |
|                | memory in KB.                   |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| CREATE_TIME    | The date and time when the      | timestamp    | n |
|                | entry was added to the          |              | o |
|                | database.                       |              |   |
+----------------+---------------------------------+--------------+---+
| UPDATE_TIME    | Date and time when the entry    | timestamp    | n |
|                | was last updated.               |              | o |
+----------------+---------------------------------+--------------+---+

1.1.1.6.4 The TLMHW.HDISK table

Stores information about storage devices, for example hard disks and CD
ROM on monitored systems. One record exists for each hard disk
discovered on each system scanned.

+----------------+---------------------------------+--------------+---+
| Columns        | Description                     | Type         | N |
|                |                                 |              | u |
|                |                                 |              | l |
|                |                                 |              | l |
+----------------+---------------------------------+--------------+---+
| HDISK_ID       | Unique identifier of the        | varchar (32) | n |
|                | storage device.                 |              | o |
+----------------+---------------------------------+--------------+---+
| HDISK_CYLINDER | The number of cylinders in the  | integer      | y |
| S              | device.                         |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| HDISK_SECTORS  | The number of sectors in the    | integer      | y |
|                | device.                         |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| HDISK_HEADS    | The number of heads in the      | integer      | y |
|                | device.                         |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| HDISK_SIZE_MB  | The size of the device in MB.   | bigint       | y |
|                |                                 |              | e |
|                |                                 |              | s |
+----------------+---------------------------------+--------------+---+
| CREATE_TIME    | The date and time when the      | timestamp    | n |
|                | entry was added to the          |              | o |
|                | database.                       |              |   |
+----------------+---------------------------------+--------------+---+
| UPDATE_TIME    | Date and time when the entry    | timestamp    | n |
|                | was last updated.               |              | o |
+----------------+---------------------------------+--------------+---+

1.1.1.6.5 The TLMHW.INST_MODEM table

Stores information about the type of modem installed and the settings
that relate to it. One record exists for each modem discovered on each
system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| MODEM_ID      | The modem identifier.        | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| INST_MODEM_ID | Identifies the specific      | integer    | no |
|               | modem installed on the       |            |    |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| PORT          | The port used by the modem.  | varchar    | ye |
|               |                              | (16)       | s  |
+---------------+------------------------------+------------+----+
| PORT_SPEED    | The speed of the port that   | integer    | ye |
|               | the modem is using.          |            | s  |
+---------------+------------------------------+------------+----+
| PORT_SETTINGS | The port settings of the     | varchar    | ye |
|               | modem.                       | (16)       | s  |
+---------------+------------------------------+------------+----+
| USER_INIT     | The user-specified           | varchar    | ye |
|               | initialization string for    | (128)      | s  |
|               | the modem.                   |            |    |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.6 The TLMHW.INST_MOUSE table

Stores information about the type of pointing device installed and the
settings that relate to it. One record exists for each pointing device
discovered on each system scanned.

+----------------+---------------------------------+--------------+---+
| Columns        | Description                     | Type         | N |
|                |                                 |              | u |
|                |                                 |              | l |
|                |                                 |              | l |
+----------------+---------------------------------+--------------+---+
| COMPUTER_SYS_I | Unique identifier of the        | bigint       | n |
| D              | system.                         |              | o |
+----------------+---------------------------------+--------------+---+
| MOUSE_ID       | The mouse identifier.           | varchar (32) | n |
|                |                                 |              | o |
+----------------+---------------------------------+--------------+---+
| INST_MOUSE_ID  | Identifies the specific mouse   | integer      | n |
|                | installed on the system.        |              | o |
+----------------+---------------------------------+--------------+---+
| CREATE_TIME    | The date and time when the      | timestamp    | n |
|                | entry was added to the          |              | o |
|                | database.                       |              |   |
+----------------+---------------------------------+--------------+---+
| UPDATE_TIME    | Date and time when the entry    | timestamp    | n |
|                | was last updated.               |              | o |
+----------------+---------------------------------+--------------+---+

1.1.1.6.7 The TLMHW.INST_PARTITION table

Stores information about a disk partition on a drive on the system. One
record exists for each partition for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| FS_ACCESS_POI | The location where the       | varchar    | no |
| NT            | partition is mounted.        | (254)      |    |
+---------------+------------------------------+------------+----+
| DEV_NAME      | The device name.             | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| PARTITION_TYP | Identifies the type of       | varchar    | ye |
| E             | partition.                   | (32)       | s  |
+---------------+------------------------------+------------+----+
| MEDIA_TYPE    | The media type of the        | varchar    | ye |
|               | partition.                   | (32)       | s  |
+---------------+------------------------------+------------+----+
| PHYSICAL_SIZE | The physical size of the     | bigint     | ye |
| _KB           | partition in KB              |            | s  |
+---------------+------------------------------+------------+----+
| FS_TYPE       | The type of file system in   | varchar    | ye |
|               | the partition.               | (64)       | s  |
+---------------+------------------------------+------------+----+
| FS_MOUNT_POIN | The mount point of the file  | varchar    | ye |
| T             | system.                      | (254)      | s  |
+---------------+------------------------------+------------+----+
| FS_TOTAL_SIZE | The total size of the file   | bigint     | ye |
| _KB           | system in KB                 |            | s  |
+---------------+------------------------------+------------+----+
| FS_FREE_SIZE_ | The amount of free space in  | bigint     | ye |
| KB            | the file system in KB        |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.8 The TLMHW.INST_PRINTER table

Stores information about the type of printer installed, the driver
software, and port settings. One record exists for each printer for each
system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| PRINTER_ID    | Identifies the type of       | varchar    | no |
|               | printer.                     | (32)       |    |
+---------------+------------------------------+------------+----+
| INST_PRINTER_ | Identifies the specific      | integer    | no |
| ID            | printer.                     |            |    |
+---------------+------------------------------+------------+----+
| PRINTER_NAME  | The name of the printer.     | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| PRINTER_LOCAT | The physical location of the | varchar    | ye |
| ION           | printer.                     | (254)      | s  |
+---------------+------------------------------+------------+----+
| PRINTER_IS_LO | Specifies whether or not the | char (1)   | ye |
| CAL           | printer is local.            |            | s  |
+---------------+------------------------------+------------+----+
| DRV_NAME      | The printer driver name.     | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| DRV_VERS      | The printer driver version.  | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| PORT_NAME     | The name of the printer      | varchar    | ye |
|               | port.                        | (254)      | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.9 The TLMHW.INST_PROCESSOR table

Stores information about the type of processor or processors installed.
One record exists for each processor for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| PROCESSOR_NUM | The processor number         | integer    | no |
+---------------+------------------------------+------------+----+
| PROCESSOR_ID  | Identifies the type of       | varchar    | no |
|               | processor                    | (32)       |    |
+---------------+------------------------------+------------+----+
| SER_NUM       | The processor serial number. | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| PROCESSOR_BOA | The number of processor      | integer    | ye |
| RD            | boards.                      |            | s  |
+---------------+------------------------------+------------+----+
| PROCESSOR_MOD | The number of processor      | integer    | ye |
| ULE           | modules.                     |            | s  |
+---------------+------------------------------+------------+----+
| IS_ENABLED    | Indicates whether the        | char (1)   | ye |
|               | processor is enabled.        |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.10 The TLMHW.INST_SMBIOS_DATA table

Stores general SMBIOS information for monitored systems. One entry
exists for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| SMBIOS_ID     | The SMBIOS ID                | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| BIOS_DATE     | The date the system BIOS was | varchar    | ye |
|               | created.                     | (16)       | s  |
+---------------+------------------------------+------------+----+
| SYS_SER_NUM   | The serial number of the     | varchar    | ye |
|               | system                       | (64)       | s  |
+---------------+------------------------------+------------+----+
| SYS_UUID      | The universal unique ID of   | varchar    | ye |
|               | the system                   | (36)       | s  |
+---------------+------------------------------+------------+----+
| BOARD_SER_NUM | The serial number of the     | varchar    | ye |
|               | system board.                | (64)       | s  |
+---------------+------------------------------+------------+----+
| CASE_SER_NUM  | The serial number of the     | varchar    | ye |
|               | case for the system.         | (64)       | s  |
+---------------+------------------------------+------------+----+
| CASE_ASSET_TA | The asset tag number of the  | varchar    | ye |
| G             | case for the system.         | (64)       | s  |
+---------------+------------------------------+------------+----+
| POWERON_PASSW | Determines whether the power | varchar    | ye |
| ORD           | on password is set.          | (64)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.11 The TLMHW.INST_USB_DEV table

Stores information about the type of USB devices installed. One record
exists for each USB device for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| USB_ID        | Identifies the type of USB   | varchar    | no |
|               | device.                      | (32)       |    |
+---------------+------------------------------+------------+----+
| INST_USB_ID   | Identifies the specific USB  | integer    | no |
|               | device.                      |            |    |
+---------------+------------------------------+------------+----+
| HOST_CNTRL    | The host controller for the  | varchar    | ye |
|               | USB device.                  | (64)       | s  |
+---------------+------------------------------+------------+----+
| DEV_ADDR      | The device address for the   | varchar    | ye |
|               | USB device.                  | (16)       | s  |
+---------------+------------------------------+------------+----+
| SER_NUM       | The serial number for the    | varchar    | ye |
|               | USB device.                  | (64)       | s  |
+---------------+------------------------------+------------+----+
| PORT_NUM      | The port number used by the  | varchar    | ye |
|               | USB device.                  | (16)       | s  |
+---------------+------------------------------+------------+----+
| PARENT_ADDR   | The parent address used by   | varchar    | ye |
|               | the USB device.              | (16)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.12 The TLMHW.INST_VID_CARD table

Stores information about the type of video card installed and the
operating system settings. One record exists for each video card for
each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| VID_CARD_ID   | Identifies the type of video | varchar    | no |
|               | card.                        | (32)       |    |
+---------------+------------------------------+------------+----+
| INST_VID_CARD | Identifies the specific      | integer    | no |
| _ID           | video card.                  |            |    |
+---------------+------------------------------+------------+----+
| VID_HORIZNTL_ | The horizontal resolution    | integer    | ye |
| RES           | setting of the installed     |            | s  |
|               | video card.                  |            |    |
+---------------+------------------------------+------------+----+
| VID_VERTICAL_ | The vertical resolution      | integer    | ye |
| RES           | setting of the installed     |            | s  |
|               | video card.                  |            |    |
+---------------+------------------------------+------------+----+
| VID_COLORS    | The color setting of the     | integer    | ye |
|               | installed video card.        |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.13 The TLMHW.IP_ADDR table

Stores information about the IP address for the monitored system. One
record exists for each IP address for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| IP_ADDR       | The IP address of the        | varchar    | no |
|               | system.                      | (40)       |    |
+---------------+------------------------------+------------+----+
| INST_IPADR_ID | Identifies the specific IP   | integer    | no |
|               | address                      |            |    |
+---------------+------------------------------+------------+----+
| IP_HOSTNAME   | The IP host name for the     | varchar    | ye |
|               | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| IP_DOMAIN     | The IP domain name for the   | varchar    | ye |
|               | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| IP_SUBNET     | The IP subnet for the        | varchar    | ye |
|               | system.                      | (40)       | s  |
+---------------+------------------------------+------------+----+
| IP_GATEWAY    | The IP gateway name for the  | varchar    | ye |
|               | system.                      | (254)      | s  |
+---------------+------------------------------+------------+----+
| IP_PRIMARY_DN | The primary domain name      | varchar    | ye |
| S             | service (DNS) for the        | (40)       | s  |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| IP_SECONDARY_ | The secondary DNS for the    | varchar    | ye |
| DNS           | system.                      | (40)       | s  |
+---------------+------------------------------+------------+----+
| IS_DHCP       | Indicates whether the        | char (1)   | ye |
|               | Dynamic Host Configuration   |            | s  |
|               | Protocol (DHCP) is in use.   |            |    |
+---------------+------------------------------+------------+----+
| PERM_MAC_ADDR | The permanent MAC address of | varchar    | ye |
| ESS           | the system.                  | (64)       | s  |
+---------------+------------------------------+------------+----+
| IPV6_ADDRESS  | The IPV6 address of the      | varchar    | ye |
|               | system                       | (64)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.14 The TLMHW.IPX_ADDR table

Stores information about the IPX address for the monitored system. One
record exists for each IPX address for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| IPX_ADDR      | The IPX address of the       | varchar    | no |
|               | system.                      | (40)       |    |
+---------------+------------------------------+------------+----+
| NET_NUM       | The network number of the    | varchar    | ye |
|               | system.                      | (40)       | s  |
+---------------+------------------------------+------------+----+
| NODE_ADDR     | The node address of the      | varchar    | ye |
|               | system.                      | (40)       | s  |
+---------------+------------------------------+------------+----+
| LINK_SPEED    | The link speed of the        | integer    | ye |
|               | system.                      |            | s  |
+---------------+------------------------------+------------+----+
| MAX_PACKET_SI | The maximum package size     | integer    | ye |
| ZE            | that the system can handle.  |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.15 The TLMHW.MEM_MODULES table

Stores the details of memory modules installed. One entry exists for
each memory module for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| INST_MEM_ID   | The index number for the     | integer    | no |
|               | memory module.               |            |    |
+---------------+------------------------------+------------+----+
| MODULE_SIZE_M | The size of the installed    | integer    | ye |
| B             | memory module in MB.         |            | s  |
+---------------+------------------------------+------------+----+
| MAX_MODULE_SI | The maximum supported memory | integer    | ye |
| ZE            | module size in MB.           |            | s  |
+---------------+------------------------------+------------+----+
| SOCKET_NAME   | The name of the socket in    | varchar    | ye |
|               | which the memory module is   | (24)       | s  |
|               | installed                    |            |    |
+---------------+------------------------------+------------+----+
| PACKAGING     | The physical packaging of    | varchar    | ye |
|               | the memory, such as single   | (16)       | s  |
|               | in-line memory module (SIMM) |            |    |
|               | or dual in-line memory       |            |    |
|               | module (DIMM).               |            |    |
+---------------+------------------------------+------------+----+
| MEM_TYPE      | The type of memory           | varchar    | ye |
|               | installed.                   | (48)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.16 The TLMHW.MODEM table

Stores the details for one particular type and model of modem. It
contains one record for each unique modem in use in the monitored
environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| MODEM_ID      | The modem identifier.        | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| MODEM_DESC    | The description of the       | varchar    | no |
|               | modem.                       | (64)       |    |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer of the      | varchar    | ye |
|               | modem.                       | (64)       | s  |
+---------------+------------------------------+------------+----+
| PROVIDER_NAME | The maker of the software    | varchar    | ye |
|               | driver for the modem.        | (32)       | s  |
+---------------+------------------------------+------------+----+
| MODEM_TYPE    | The type of modem.           | varchar    | ye |
|               |                              | (32)       | s  |
+---------------+------------------------------+------------+----+
| INF_FILE      | The name of the description  | varchar    | ye |
|               | file for the modem driver.   | (32)       | s  |
+---------------+------------------------------+------------+----+
| INF_SECTION   | The details of the driver    | varchar    | ye |
|               | file for the modem.          | (32)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.17 The TLMHW.MONITOR table

Stores the details of monitors connected to systems in the monitored
environment. One entry exists for each monitor for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| INST_MONITOR_ | Identifier of the installed  | integer    | no |
| ID            | monitored.                   |            |    |
+---------------+------------------------------+------------+----+
| MANUFACT_CODE | Identifies the manufacturer  | varchar    | ye |
| _NAME         | of the monitor.              | (64)       | s  |
+---------------+------------------------------+------------+----+
| NAME          | The name of the manufacturer | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| WEEK_MANUFACT | The week in which the        | integer    | ye |
| URED          | monitor was manufactured.    |            | s  |
+---------------+------------------------------+------------+----+
| YEAR_MANUFACT | The year in which the        | integer    | ye |
| URED          | monitor was manufactured.    |            | s  |
+---------------+------------------------------+------------+----+
| SERIAL_NUMBER | The serial number of the     | varchar    | ye |
|               | monitor.                     | (64)       | s  |
+---------------+------------------------------+------------+----+
| SIZE_INCHES   | The size of the monitor in   | integer    | ye |
|               | inches                       |            | s  |
+---------------+------------------------------+------------+----+
| MIN_V_SCAN_FR | The minimum vertical scan    | integer    | ye |
| EQ            | frequency of the monitor.    |            | s  |
+---------------+------------------------------+------------+----+
| MAX_V_SCAN_FR | The maximum vertical scan    | integer    | ye |
| EQ            | frequency of the monitor.    |            | s  |
+---------------+------------------------------+------------+----+
| MIN_H_SCAN_FR | The minimum horizontal scan  | integer    | ye |
| EQ            | frequency of the monitor.    |            | s  |
+---------------+------------------------------+------------+----+
| MAX_H_SCAN_FR | The maximum horizontal scan  | integer    | ye |
| EQ            | frequency of the monitor.    |            | s  |
+---------------+------------------------------+------------+----+
| PIXEL_CLOCK_M | The rate at which pixels are | integer    | ye |
| HZ            | drawn on the screen.         |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.18 The TLMHW.MOUSE table

Stores the details for one particular type and model of pointing device.
It contains one record for each unique pointing device in use in the
monitored environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| MOUSE_ID      | The mouse identifier.        | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| MOUSE_MODEL   | The model of mouse.          | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| MOUSE_TYPE    | The type of pointing device  | varchar    | ye |
|               | for example mouse,           | (32)       | s  |
|               | trackball.                   |            |    |
+---------------+------------------------------+------------+----+
| BUTTONS       | The number of buttons on the | integer    | ye |
|               | mouse.                       |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.19 The TLMHW.NET_ADAPTER table

Stores information about the network adapter installed on a system. One
record exists for each network adapter for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| INDEX         | The net adapter index.       | integer    | no |
+---------------+------------------------------+------------+----+
| PERM_MAC_ADDR | The permanent Media Access   | varchar    | ye |
|               | Control (MAC) address of the | (64)       | s  |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| CURRENT_ADDR  | The current network address  | varchar    | ye |
|               | of the system.               | (64)       | s  |
+---------------+------------------------------+------------+----+
| ADAPTER_TYPE  | The network adapter          | varchar    | ye |
|               | installed on the system.     | (32)       | s  |
+---------------+------------------------------+------------+----+
| ADAPTER_MODEL | The model of the network     | varchar    | ye |
|               | adapter                      | (254)      | s  |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer of the      | varchar    | ye |
|               | network adapter.             | (128)      | s  |
+---------------+------------------------------+------------+----+
| INST_DATE     | Network adapter installation | varchar    | ye |
|               | date.                        | (32)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.20 The TLMHW.PCI_DEV table

Stores information about a PCI device installed in or connected to a
system. One record exists for each PCI device for each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| INST_PCI_ID   | Identifies the installed     | integer    | no |
|               | peripheral component         |            |    |
|               | interconnect (PCI) device.   |            |    |
+---------------+------------------------------+------------+----+
| PCI_DEV_NAME  | The name of the PCI device.  | varchar    | no |
|               |                              | (180)      |    |
+---------------+------------------------------+------------+----+
| PCI_REVISION  | The revision of the PCI      | char (8)   | ye |
|               | device.                      |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.21 The TLMHW.PC_SYS_PARAMS table

Stores BIOS and other system information for a PC. One entry exists for
each system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| USER_NAME     | The Windows user name for    | varchar    | ye |
|               | the system.                  | (254)      | s  |
+---------------+------------------------------+------------+----+
| DOMAIN_NAME   | The Windows domain name for  | varchar    | ye |
|               | the system.                  | (128)      | s  |
+---------------+------------------------------+------------+----+
| WORKGROUP_NAM | The Windows workgroup name   | varchar    | ye |
| E             | for the system.              | (128)      | s  |
+---------------+------------------------------+------------+----+
| BIOS_ID       | Identifies the BIOS that is  | varchar    | ye |
|               | in use on the system.        | (128)      | s  |
+---------------+------------------------------+------------+----+
| BIOS_ID_BYTES | Hexadecimal values from the  | varchar    | ye |
|               | BIOS.                        | (16)       | s  |
+---------------+------------------------------+------------+----+
| BIOS_DATE     | The revision date of the     | varchar    | ye |
|               | BIOS.                        | (32)       | s  |
+---------------+------------------------------+------------+----+
| BIOS_STRING   | The BIOS string.             | varchar    | ye |
|               |                              | (128)      | s  |
+---------------+------------------------------+------------+----+
| BIOS_MANUFACT | Identifies the manufacturer  | varchar    | ye |
| URER          | of the BIOS.                 | (64)       | s  |
+---------------+------------------------------+------------+----+
| MANUFACTURER_ | Identifies the manufacturer  | varchar    | ye |
| ID            | of the PC.                   | (64)       | s  |
+---------------+------------------------------+------------+----+
| BIOS_MODEL    | The BIOS model.              | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| BIOS_SER_NUM  | The BIOS serial number.      | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| UPTIME        | The current uptime of the    | bigint     | ye |
|               | system. Indicates the level  |            | s  |
|               | of reliability of the        |            |    |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| IE_VERS       | The version of Microsoft     | varchar    | ye |
|               | Internet Explorer that is    | (64)       | s  |
|               | installed.                   |            |    |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.22 The TLMHW.PRINTER table

Stores the details for one particular type and model of printer. It
contains only one record for each unique printer in use in the monitored
environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| PRINTER_ID    | Unique identifier of the     | varchar    | no |
|               | printer type.                | (32)       |    |
+---------------+------------------------------+------------+----+
| PRINTER_MODEL | A description of the printer | varchar    | ye |
|               | model.                       | (254)      | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.23 The TLMHW.PROCESSOR table

Stores the details for one particular type and model of processor. It
contains only one record for each unique processor in use in the
monitored environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| PROCESSOR_ID  | Unique identifier of the     | varchar    | no |
|               | processor type.              | (32)       |    |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer of the      | varchar    | ye |
|               | processor.                   | (128)      | s  |
+---------------+------------------------------+------------+----+
| PROCESSOR_MOD | The processor model.         | varchar    | ye |
| EL            |                              | (200)      | s  |
+---------------+------------------------------+------------+----+
| PROCESSOR_FEA | A bitmask within which each  | integer    | ye |
| TURES         | bit that is set identifies a |            | s  |
|               | feature that is available    |            |    |
|               | for the processor.           |            |    |
+---------------+------------------------------+------------+----+
| MAX_SPEED     | The maximum speed of the     | integer    | ye |
|               | processor in MHz.            |            | s  |
+---------------+------------------------------+------------+----+
| CURRENT_SPEED | The current speed of the     | integer    | ye |
|               | processor in MHz.            |            | s  |
+---------------+------------------------------+------------+----+
| BUS_SPEED     | The external bus speed of    | integer    | ye |
|               | the processor in megahertz   |            | s  |
|               | (MHz).                       |            |    |
+---------------+------------------------------+------------+----+
| CPU_INTERFACE | The external central         | varchar    | ye |
|               | processing unit (CPU)        | (32)       | s  |
|               | packaging interface.         |            |    |
+---------------+------------------------------+------------+----+
| ECACHE_MB     | The size of the processor    | varchar    | ye |
|               | ecache in MB                 | (16)       | s  |
+---------------+------------------------------+------------+----+
| CPU_IMPL      | The implementation (type) of | varchar    | ye |
|               | the processor                | (16)       | s  |
+---------------+------------------------------+------------+----+
| CPU_MASK      | The CPU mask for the         | varchar    | ye |
|               | processor.                   | (16)       | s  |
+---------------+------------------------------+------------+----+
| CHIP_FAMILY   | The chip family of the       | integer    | ye |
|               | processor.                   |            | s  |
+---------------+------------------------------+------------+----+
| CHIP_MODEL    | The chip model of the        | integer    | ye |
|               | processor.                   |            | s  |
+---------------+------------------------------+------------+----+
| CHIP_STEPPING | The chip stepping code for   | integer    | ye |
|               | the processor                |            | s  |
+---------------+------------------------------+------------+----+
| VIRT_MODE_EXT | Indicates whether virtual    | char (1)   | ye |
|               | mode extension is supported. |            | s  |
+---------------+------------------------------+------------+----+
| PAGE_SIZE_EXT | Indicates whether page size  | char (1)   | ye |
|               | extension is supported.      |            | s  |
+---------------+------------------------------+------------+----+
| TIME_STAMP_CO | Indicates whether time stamp | char (1)   | ye |
| UNTER         | counter is supported.        |            | s  |
+---------------+------------------------------+------------+----+
| MODEL_SPECIFI | Indicates whether            | char (1)   | ye |
| C_REG         | model-specific registers are |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| PHYSICAL_ADDR | Indicates whether physical   | char (1)   | ye |
| _EXT          | address extension is         |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| MACHINECHECK_ | Indicates whether            | char (1)   | ye |
| EXCPT         | machine-check exception is   |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| CMPXCHG8B_SUP | Indicates whether the        | char (1)   | ye |
| P             | compare exchange 8-byte      |            | s  |
|               | instruction is supported.    |            |    |
+---------------+------------------------------+------------+----+
| ON_CHIP_APIC  | Indicates whether the        | char (1)   | ye |
|               | integrated advanced          |            | s  |
|               | programmable interrupt       |            |    |
|               | controller (APIC) is         |            |    |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| MEM_TYPE_RANG | Indicates whether memory     | char (1)   | ye |
| E_REG         | type range registers are     |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| PAGE_GLOBAL_E | Indicates whether the page   | char (1)   | ye |
| NABLE         | global extension is enabled. |            | s  |
+---------------+------------------------------+------------+----+
| MACHINECHECK_ | Indicates whether the        | char (1)   | ye |
| ARCH          | machine-check architecture   |            | s  |
|               | is supported.                |            |    |
+---------------+------------------------------+------------+----+
| COND_MOVE_SUP | Indicates whether the        | char (1)   | ye |
| P             | conditional move instruction |            | s  |
|               | is supported.                |            |    |
+---------------+------------------------------+------------+----+
| MMX_TECHNOLOG | Indicates the Intel(R) MMX   | char (1)   | ye |
| Y             | features that are supported. |            | s  |
+---------------+------------------------------+------------+----+
| ON_CHIP_FPU   | Indicates whether the        | char (1)   | ye |
|               | floating processor unit is   |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| DEBUG_EXT_PRE | Indicates whether the        | char (1)   | ye |
| SENT          | debugging extension is       |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| FAST_SYS_CALL | Indicates whether fast       | char (1)   | ye |
|               | system call is supported.    |            | s  |
+---------------+------------------------------+------------+----+
| PAGE_ATTR_TAB | Indicates whether the page   | char (1)   | ye |
| LE            | attribute table extension is |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| PAGE_SIZE_EXT | Indicates whether the 36-bit | char (1)   | ye |
| 36            | page size extension is       |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| SER_NUM_ENABL | Indicates whether the        | char (1)   | ye |
| ED            | processor serial number is   |            | s  |
|               | enabled.                     |            |    |
+---------------+------------------------------+------------+----+
| FAST_FLOAT_SA | Indicates whether fast       | char (1)   | ye |
| VE            | floating point save and      |            | s  |
|               | restore instructions are     |            |    |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| SIMD_EXT_SUPP | Indicates whether the        | char (1)   | ye |
|               | streaming single             |            | s  |
|               | instruction, multiple data   |            |    |
|               | (SIMD) instruction set is    |            |    |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| NOW_3_D_ARCH  | Indicates whether the AMD    | char (1)   | ye |
|               | 3DNow! instructions are      |            | s  |
|               | supported.                   |            |    |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.24 The TLMHW.SMBIOS_SYS_DATA table

Stores general SMBIOS details. It contains only one record for each
unique SMBIOS configuration that is in use in the monitored environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| SMBIOS_ID     | SMBIOS ID.                   | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| BIOS_VENDOR   | The manufacturer of the      | varchar    | ye |
|               | system BIOS.                 | (64)       | s  |
+---------------+------------------------------+------------+----+
| BIOS_VERS     | The version number of the    | varchar    | ye |
|               | system BIOS.                 | (128)      | s  |
+---------------+------------------------------+------------+----+
| BIOS_SIZE     | The size of the system BIOS. | char (8)   | ye |
|               |                              |            | s  |
+---------------+------------------------------+------------+----+
| SYS_MANUFACTU | The manufacturer of the      | varchar    | ye |
| RER           | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| SYS_PRODUCT_N | The product name of the      | varchar    | ye |
| AME           | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| SYS_VERS      | The version number of the    | varchar    | ye |
|               | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| BOARD_MANUFAC | The manufacturer of the      | varchar    | ye |
| TURER         | system board.                | (64)       | s  |
+---------------+------------------------------+------------+----+
| BOARD_PRODUCT | The product name of the      | varchar    | ye |
|               | system board.                | (64)       | s  |
+---------------+------------------------------+------------+----+
| BOARD_VERS    | The version number of the    | varchar    | ye |
|               | system board.                | (64)       | s  |
+---------------+------------------------------+------------+----+
| CASE_MANUFACT | The manufacturer of the case | varchar    | ye |
| URER          | for the system.              | (64)       | s  |
+---------------+------------------------------+------------+----+
| CASE_TYPE     | The type of case for the     | varchar    | ye |
|               | system.                      | (64)       | s  |
+---------------+------------------------------+------------+----+
| CASE_VERSION  | The version number of the    | varchar    | ye |
|               | case for the system.         | (64)       | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.25 The TLMHW.STORAGE_DEV table

Stores the details for a particular storage device installed on a
system. One record exists for each storage device for each system
scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| INST_STORAGE_ | The index number for the     | integer    | no |
| ID            | installed storage device     |            |    |
+---------------+------------------------------+------------+----+
| STORAGE_TYPE  | The type of storage device.  | varchar    | ye |
|               |                              | (64)       | s  |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer of the      | varchar    | ye |
|               | storage device.              | (128)      | s  |
+---------------+------------------------------+------------+----+
| MODEL         | The model of storage device. | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| SER_NUM       | The serial number of the     | varchar    | ye |
|               | storage device               | (64)       | s  |
+---------------+------------------------------+------------+----+
| HDISK_ID      | The hard disk ID             | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.26 The TLMHW.UNIX_SYS_PARAMS table

Stores UNIX system parameters for a system. One entry exists for each
system scanned.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| COMPUTER_SYS_ | Unique identifier of the     | bigint     | no |
| ID            | system.                      |            |    |
+---------------+------------------------------+------------+----+
| BOOT_TIME     | The date and time that the   | timestamp  | ye |
|               | system was last restarted.   |            | s  |
+---------------+------------------------------+------------+----+
| UPTIME        | The current uptime of the    | integer    | ye |
|               | system. Indicates the level  |            | s  |
|               | of reliability of the        |            |    |
|               | system.                      |            |    |
+---------------+------------------------------+------------+----+
| RUN_LEVEL     | The run level of the system. | integer    | ye |
|               |                              |            | s  |
+---------------+------------------------------+------------+----+
| HOST_NAME     | The host name of the system. | varchar    | ye |
|               |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.27 The TLMHW.USB_DEV table

Stores the details for one particular type of USB device. It contains
only one record for each unique USB device in use in the monitored
environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| USB_ID        | The USB ID                   | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| USB_VERS      | The USB version of the       | varchar    | ye |
|               | device.                      | (32)       | s  |
+---------------+------------------------------+------------+----+
| DEV_CLASS     | The device class of the USB  | varchar    | ye |
|               | device.                      | (32)       | s  |
+---------------+------------------------------+------------+----+
| DEV_SUBCLASS  | The device subclass for the  | integer    | ye |
|               | USB device.                  |            | s  |
+---------------+------------------------------+------------+----+
| VENDOR_ID     | The vendor ID of the         | integer    | ye |
|               | manufacturer of the USB      |            | s  |
|               | device.                      |            |    |
+---------------+------------------------------+------------+----+
| PRODUCT_ID    | The product ID for the USB   | integer    | ye |
|               | device.                      |            | s  |
+---------------+------------------------------+------------+----+
| MANUFACTURER  | The manufacturer for the USB | varchar    | ye |
|               | device.                      | (128)      | s  |
+---------------+------------------------------+------------+----+
| PRODUCT       | The type of product the USB  | varchar    | ye |
|               | device is.                   | (254)      | s  |
+---------------+------------------------------+------------+----+
| NUM_OF_PORTS  | The number of USB ports      | integer    | ye |
|               | present on the USB device.   |            | s  |
+---------------+------------------------------+------------+----+
| DEV_IS_HUB    | Indicates whether the USB    | char (6)   | ye |
|               | device is a hub.             |            | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.28 The TLMHW.VID_CARD table

Stores the details for one particular type of video card. It contains
only one record for each unique video card in use in the monitored
environment.

+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| VID_CARD_ID   | The video card ID            | varchar    | no |
|               |                              | (32)       |    |
+---------------+------------------------------+------------+----+
| VID_CARD_MODE | The video card model.        | varchar    | ye |
| L             |                              | (254)      | s  |
+---------------+------------------------------+------------+----+
| VID_CARD_BIOS | The BIOS information for the | varchar    | ye |
|               | video card.                  | (254)      | s  |
+---------------+------------------------------+------------+----+
| VID_DAC_TYPE  | The integrated               | varchar    | ye |
|               | digital-to-analog converter  | (254)      | s  |
|               | (DAC) for the video card.    |            |    |
+---------------+------------------------------+------------+----+
| VID_MEM       | The amount of memory for the | integer    | ye |
|               | video card.                  |            | s  |
+---------------+------------------------------+------------+----+
| VID_BIOS_RELD | The BIOS release date        | varchar    | ye |
| ATE           |                              | (32)       | s  |
+---------------+------------------------------+------------+----+
| VID_CHIP_TYPE | The chip type for the video  | varchar    | ye |
|               | card.                        | (254)      | s  |
+---------------+------------------------------+------------+----+
| CREATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was added to the database.   |            |    |
+---------------+------------------------------+------------+----+
| UPDATE_TIME   | Date and time when the entry | timestamp  | no |
|               | was last updated.            |            |    |
+---------------+------------------------------+------------+----+

1.1.1.6.29 Changed tables

Additions have been made to the following tables to support the hardware
inventory scan feature: 
*  ADM.AGENT. See Table 2.
*  ADM.CONTROL. See Table 3.
*  ADM.DIVISION. See Table 4.

Table 2. Additions to the ADM.AGENT table.
+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| HWSCAN_TIME   | The date and time of the     | timestamp  | ye |
|               | last hardware scan.          |            | s  |
+---------------+------------------------------+------------+----+

Table 3. Additions to the ADM.CONTROL table.
+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| HARDWARE_SCAN | Indicates whether the        | char (5)   | ye |
| _ENABLED      | hardware inventory scan      |            | s  |
|               | feature is enabled.          |            |    |
+---------------+------------------------------+------------+----+
| COMPUTER_GUID | Indicates the rule used to   | smallint   | ye |
| _RULE         | calculate the computer GUID. |            | s  |
|               | Possible values are:         |            |    |
|               | 1                            |            |    |
|               | Concatenate the values for   |            |    |
|               | manufacturer, model, and     |            |    |
|               | serial number.               |            |    |
|               | 3                            |            |    |
|               | Use the Media Access Control |            |    |
|               | (MAC) address of the first   |            |    |
|               | network card discovered on   |            |    |
|               | the system.                  |            |    |
+---------------+------------------------------+------------+----+

Table 4. Additions to the ADM.DIVISION table.
+---------------+------------------------------+------------+----+
| Columns       | Description                  | Type       | Nu |
|               |                              |            | ll |
+---------------+------------------------------+------------+----+
| HWINV_START_D | The date on which the        | timestamp  | no |
| ATE           | hardware scan schedule       |            |    |
|               | starts.                      |            |    |
+---------------+------------------------------+------------+----+
| HWINV_RATE_TY | Indicates the hardware scan  | smallint   | no |
| PE            | repeating period. Possible   |            |    |
|               | values are:                  |            |    |
|               | 0                            |            |    |
|               | No repetition                |            |    |
|               | 1                            |            |    |
|               | The repetition period is 1   |            |    |
|               | day.                         |            |    |
|               | 2                            |            |    |
|               | The repetition period is 7   |            |    |
|               | days.                        |            |    |
|               | 3                            |            |    |
|               | The repetition period is 30  |            |    |
|               | days.                        |            |    |
+---------------+------------------------------+------------+----+
| HWINV_RATE_VA | The number of repeating      | integer    | no |
| LUE           | periods that separate        |            |    |
|               | consecutive occurrences of   |            |    |
|               | the hardware scan.           |            |    |
+---------------+------------------------------+------------+----+
| HWINV_VIRTUAL | Indicates whether the        | smallint   | no |
| _DISABLED     | hardware scan is disabled in |            |    |
|               | virtual environments.        |            |    |
|               | Possible values are 0        |            |    |
|               | (scanning enabled), 1        |            |    |
|               | (scanning disabled).         |            |    |
+---------------+------------------------------+------------+----+

1.1.2 Agent installation size check

For all agent deployment methods, a space check is now made to ensure
that the installation will not start and then fail because of lack of
sufficient space in the agent installation directory. Before starting
the installation process, the following space requirement in the agent
installation directory must be satisfied: 

Windows agent
         38 MB

Linux agent
         50 MB

Solaris, AIX(R) and HP-UX agents
         65 MB

GSKit component
         30 MB

If the space available is insufficient, the installation fails with
return code -17.

1.1.3 Support for partitioning technologies

The fix pack introduces support for agents in Solaris Containers
non-global zones with resource pools enabled.

When an agent is deployed in a non-global zone and resource pools are
enabled, the agent details that are shown on the Web UI include
information about the processor set associated with the resource pool
for the zone where the agent is deployed. 

Note:  When agents are deployed in non-global zones, an agent must also
      be deployed in the global zone.

1.1.4 Product fixes

This is the first fix pack issued for Tivoli License Compliance Manager,
version 2.3. It fixes the following APARs:

APAR IY95336
         On Linux 390 platforms, the manual agent deploy setup fails in
         silent mode.

         The fix pack resolves the problem.


APAR IY95183
         On Windows systems, a noise is heard when the agent checks the
         presence of the floppy disk.

         The fix pack resolves the problem by installing a new version
         of the Common Inventory Technology (CIT) component.


APAR IY94558
         The initial scan performed at agent start up takes too long. 

         The problem was related to the collection of system storage
         information. This is no longer required and so has been
         removed.


APAR IY94123
         The Software Package Block (SPB) for agent configuration
         changes does not include the possibility to change the
         organization. 

         The fix pack adds the Organization parameter to the SPB
         change_agt_configuration_platform.spb. 

         The main objective of this change is to allow configuration
         errors to be corrected. If the name of the organization has
         been entered incorrectly, the agent is not able to plug in. You
         can use the software package block to distribute a correction
         to all affected agents.

         You can also use the SPB to transfer agents that are already
         active from one organization to another. However, be aware that
         all installed software and software use information that has
         already been collected by the agents will no longer be
         available. Before distributing the SPB, use the Manage
         Infrastructure &gt; Agents task on the Web UI to delete the agent.
         When the agent plugs in after the SPB has been applied, a new
         agent record is automatically created.


APAR IY93924
         The time on the agents is not in synch with the time on the
         server.

         The fix pack resolves the problem.


APAR IY93548
         No software use is detected for WebSphere(R) Commerce 5.6.x
         when the J2EE application has the same name as the application
         server. 

         The fix pack resolves the problem.


APAR IY93364
         If the administration and runtime servers are started using the
         Windows command line and, later on, the user logs off from
         Windows, the servers are also stopped. 

         The fix pack resolves the problem.


APAR IY93328
         Abend code on an i5/OS agent because of a variable overflow
         caused by an http connectivity problem with the runtime server.

         The fix pack resolves the problem.


APAR IY93251
         The agent cannot handle correctly 'Manufacturer' strings longer
         than 31 characters.

         The fix pack resolves the problem.

1.1.4.1 Problems fixed

The following problems were found since the general availability of
Tivoli License Compliance Manager, version 2.3 and fixed with this fix
pack:

The generateAgentId command does not work if fix pack 3 is applied to 
WebSphere Application Server, version 6.1
         This problem is caused because the update to the Java(TM) SDK
         introduced in fix pack 3 is not backward compatibile. At the GA
         version of Tivoli License Compliance Manager, version 2.3, the
         generateAgentId command will not work after you have applied
         fix pack 3 to WebSphere Application server. 

         When this fix pack has been applied, the command works both
         with and without fix pack 3.


Exceptions are generated when a division that has many connected agents 
is deleted. 
         When the fix pack has been applied, it is no longer possible to
         delete divisions that have connected agents.

1.1.4.2 Problems and workarounds

The following describes a problem affecting interaction with IBM Tivoli
Configuration Manager. 

Incorrect agent installation return code reported in the Tivoli 
Configuration Manager logs.
         When the agent is deployed using Tivoli Configuration Manager
         and errors occur, incorrect agent installation return codes are
         written to the software package block log. 

         This problem is caused because the error return codes are
         negative integers and logging in Tivoli Configuration Manager
         does not handle them correctly. The correct return code is
         written in the file slmrc, which is stored in the directory on
         the target computer from which the agent installation was
         launched.


On HP-UX platforms, problems can occur accessing the Web UI after the 
server has been stopped and restarted.
         This problem is caused by a WebSphere transport problem that
         affects both the administration and runtime servers. The
         problem is resolved in fix pack 5 for WebSphere Application
         Server 6.1. 

         If you do not want to apply the WebSphere Application Server
         fix pack at this time, you can overcome the problem by stopping
         both the Tivoli License Compliance Manager server and the HTTP
         server and then restarting them.

1.1.5 Documentation fix history

This fix pack documents solutions for the following problems or errors
in the product documentation:

Missing information about installing the agent on VMware environments 
(APAR IY96544 for Tivoli License Compliance Manager version 2.2)
         Problem (found in
         IBM Tivoli License Compliance Manager: Planning, Installation,
         and Configuration): you can install the agent on VMware
         environments without running the CIT enabler. Agents installed
         in this manner will only be able to send inventory data: they
         will not send usage data, nor aggregated or hardware
         information. On agents running VMware ESX 3.0 (or later), APAR
         IY96549 for CIT version 2.3 must be installed. The CIT enabler
         in this fix pack includes the APAR.

Missing CIT required libraries for VMware environments (APAR IY95943 for 
Tivoli License Compliance Manager version 2.2)
         Problem: In Chapter 1 of
         IBM Tivoli License Compliance Manager: Planning, Installation,
         and Configuration, the information about libraries required by
         CIT for VMware environments is documented in Table 4 "Supported
         agent platforms", but is missing from page 20 where the CIT
         enabler specifications are documented. 

         Solution: The table that documents the CIT enabler software on
         page 20 of Chapter 1 should include the following new
         paragraph: "On hosts running Red Hat Linux, the enabler
         requires the compatibility packs documented in Table 4 on page
         11."


Instructions for configuring the WebSphere Application Server virtual 
host for secure communications are not clear. (APAR IY94284 for Tivoli 
License Compliance Manager version 2.2)
         Problem: In Chapters 2 and 3 of
         IBM Tivoli License Compliance Manager: Security Management, the
         instruction that describes the configuration of a secure port
         for all virtual host aliases does not make clear which virtual
         host should be selected. 

         Solution: In both chapters, the instruction is changed as
         follows:

         Ensure that the WebSphere Application Server has virtual
         aliases for the secure port.

         Logon to the WebSphere Application Server console and do the
         following: 
         1. On the Virtual Host settings page, select the virtual host
            instance called default_host.
         2. Configure a secure port for the virtual host and all its
            aliases. You can create a single definition that applies to
            all possible host aliases, setting the Host Name to * and
            Port to the secure port number (normally 443).
         3. Generate the Web Server plug-in.
         4. Propagate the Web Server plug.in.


Clarification for differences in the steps for configuring Java 2 
security depending on the WebSphere Application Server configuration.
         Problem: In Chapter 5 of
         IBM Tivoli License Compliance Manager: Security Management, the
         instructions for configuring Java 2 security do not reflect
         possible differences in the the WebSphere Application Server
         configuration.

         Solution: The following differences need to be stated: 
         *  In the document the directory where Java 2 policies are
            stored is given as: 

            

            &lt;WAS_INSTALL_DIR&gt;\profiles\default\config\cells\
            &lt;host_cell_name&gt;\applications\
SLM_&lt;server_type&gt;
            
            
            
            _Application.ear\deployments\
SLM_&lt;server_type&gt;_Application\META-INF

            The subdirectory \default is should be documented as a
            variable. The subdirectory name is the name of the default
            profile created when WebSphere Application server is
            installed. It could be "default", but it could also have
            other values.

         *  If you have installed the Tivoli License Compliance Manager
            server with an existing installation of WebSphere
            Application Server, for which Java 2 security was already
            configured, you need only to complete the task of replacing
            the profile file with the file in which you have defined the
            location of the Tivoli Common Directory. Steps 7, 8, and 9
            are not required.


The prerequisite for space in the /tmp directory during installation of 
the runtime server is too low (APAR IY93190 for Tivoli License 
Compliance Manager version 2.2)
         Problem: In Chapter 1 of
         IBM Tivoli License Compliance Manager: Planning, Installation,
         and Configuration, the table of prerequisites for servers
         specifies a requirement for 250 MB of free space on UNIX
         platforms in the /tmp directory. For runtime server
         installations, this is insufficient. In addition, the table of
         prerequisites for the runtime server should say that the
         WebSphere Application Server temporary directory
         (java.io.tmpdir) by default is set to the /tmp directory.

         Solution: The requirement is to have at least 700 MB of free
         space on UNIX platforms.


The syntax for the backupconf and restoreconf commands is incorrect.
         Problem: In IBM Tivoli License Compliance Manager: Commands,
         the syntax described for the command backupconf and restoreconf
         commands is incorrect. The documented syntax for the commands
         is: 
            backupconf [-d &lt;directory_name&gt;]
            restoreconf [-d &lt;directory_name&gt;]

         The correct syntax is:

            backupconf [&lt;directory_name&gt;]
            restoreconf [&lt;directory_name&gt;]

1.1.6 Backward compatibility

Dependencies:
   Tivoli License Compliance Manager, version 2.3

1.1.7 Other changes as a result of this fix pack

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

Agents deployed after this fix pack has been applied to the runtime
server will have a new version number of 2.3.0.10. 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 Compliance 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, "Upgrading agents"
*  1.2.4, "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

The following information supplements the supported platform information
documented in IBM Tivoli License Compliance Manager: Planning,
Installation, and Configuration: 

On the following platforms, changes are required to the required 
maintenance levels, service packs, patches or compatibility patches
         

         HP-UX 11i v2 running on rx7640 and rx8640.
                  Required patch: PHKL_35174 

                  This patch is required when agents are deployed in
                  partitioned environments.


         HP-UX 11i v2 on PA-RISC
                  Required patch: PHSS_35381

Limitation to the deployment of agents on Solaris x86 platforms (global 
and non-global zones)
         Agents cannot be deployed on hardware that supports
         hyper-threading functionality.

1.2.1.2 System requirements

The following are additions to hardware and software prerequisites
detailed in IBM Tivoli License Compliance Manager: Planning,
Installation, and Configuration.

The space in the agent installation directory required for agent 
installation is changed
         

         Windows agent
                  38 MB

         Linux agent
                  50 MB

         Solaris, AIX and HP-UX agents
                  65 MB

         GSKit component
                  30 MB

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.4,
"Reverting to the previous version".

The fix pack includes the following files:

2.3.0-TIV-TLCM-FP0001-servers-&lt;platform&gt;.zip
         For each supported platform, the compressed file contains the
         files for installing the fix pack on computers where an
         administration server, a runtime server, or an administration
         server database or runtime server database is installed.

2.3.0-TIV-TLCM-FP0001-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.3.0-TIV-TLCM-FP0001-agent-gateway.zip
         This file contains the software packages for each supported
         agent platform in PKT format.

2.3.0-TIV-TLCM-FP0001-RSH-SSH-&lt;platform&gt;.zip
         This contains the files needed to deploy agents on UNIX
         platforms using the RSH/SSH deployment wizard.

2.3.0-TIV-TLCM-FP0001-agentOS400.zip
         This contains the files needed to deploy agents on i5/OS
         platforms.

2.3.0-TIV-TLCM-FP0001-ManualDeploy-&lt;platform&gt;.zip
         This contains the files needed to install agents using a local
         wizard.

2.3.0-TIV-TLCM-FP0001-SPB-TOOLS.zip
         This contains the SPBs for agent configuration update that have
         been updated for APAR IY94123.



The fix pack must be applied to all server and database components of
Tivoli License Compliance Manager.

Notes: 
1. Before starting the installation, back up the administration and
   runtime server databases and the installation directories of
   administration server and runtime servers.
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
   Compliance Manager components is installed as Administrator (Windows)
   or root (UNIX).
2. Unpack the servers 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 Compliance Manager, version 2.3 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 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 Compliance Manager: Planning, Installation, and
Configuration.

Agents are supported only when they are registered to a runtime server
with the same, or a higher, Tivoli License Compliance Manager
maintenance level.

1.2.4 Reverting to the previous version

There is no automatic method for uninstalling this fix pack.

You must rollback 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.3.0-TIV-TLCM-FP0001 which contains a
   subset file structure for the Tivoli License Compliance 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 installation.

3. If this is the first fix applied to the GA version of the code,
   delete the file &lt;INSTALL_DIR&gt;\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.

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: 

AIX
DB2
DB2(R) Universal Database
 IBM
 i5/OS
 Tivoli
 WebSphere
 zSeries

Intel and Itanium are a trademarks of Intel Corporation in the United
States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the U.S., and other
countries.Microsoft and Windows are registered trademarks, of Microsoft
Corporation in the U.S. and other countries.

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

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

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

</pre></body></html>