TME 10 Inventory Release Notes Version 3.6.1

Transcription

1 TME 10 Inventory Release Notes Version April 1999

2 TME 10 Inventory Release Notes (April 1999) Copyright Notice Copyright 1999 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli Management Environment, TME 10, TME 10 Framework, TME 10 Software Distribution AutoPack, TME 10 Inventory, and TME 10 Software Installation Servic. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System s or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A.

3 TME 10 Inventory Release Notes New Features... 2 Changes to the Configuration Repository... 2 New View and Query... 2 Improved Installation of Software Signatures... 3 Support for DB2 on OS/ Support for DB2 on Windows NT RIM Hosts... 3 Support for Informix... 4 Improved DMI Scanning... 4 System Requirements... 4 Software Requirements... 5 RDBMS and RIM Hosts... 5 Web Browsers... 7 Hardware Requirements... 7 TMR Server and Managed Nodes... 7 PC Managed Nodes... 8 Endpoint Files... 9 Installation Notes... 9 Prerequisites... 9 Installation Directories Before You Begin Installing Upgrading to Upgrading TMR Servers & Managed Nodes Upgrading the PC Scanner Upgrading Gateways Upgrading the Inventory 3.6 Configuration Repository to Upgrading Inventory 3.6 Queries to Upgrading Software Signatures Patches Included in Version Defects Fixed for Version Version Software Defects, Limitations, and Workarounds TME 10 Inventory Release Notes vii

4 Version 3.6 Documentation Defects...29 Internationalization...32 Enabling Language Support...33 RDBMS Interface Module...33 International Defects Fixed in Version International Defects, Limitations, and Workarounds...34 Product Notes...36 Appendix A Creating an Informix Configuration Repository Prerequisites... A-1 Creating a RIM Object for Informix... A-2 Creating the Informix User and the Inventory Database... A-4 Installing the Configuration Repository Schema... A-4 Informix Table, Column, and View Names... A-4 viii Version 3.6.1

5 1Release Notes This Release Notes document provides important information about TME 10 Inventory, Version (Inventory 3.6.1). These notes are the most current information for the product and take precedence over all other documentation. Please review these notes thoroughly before installing or using this product. These release notes include the following topics: New Features System Requirements Installation Notes Patches Included in Version Defects Fixed for Version Version Software Defects, Limitations, and Workarounds Version 3.6 Documentation Defects Internationalization Product Notes Tivoli frequently updates the Tivoli Customer Support home page with new information about configuring and using Tivoli products. This information includes the following: Updated versions of these release notes Updated versions of Tivoli documentation Searchable support databases Additional product patches Access to training schedules Access to the Inventory Software Signature Collection for TME 10 Inventory Release Notes 1

6 New Features quarterly updates of software signature files. Visit the site for this information and additional customer services. After you link to and submit the customer registration form, you will be able to access these services on the Web. You will notice that both Tivoli and TME 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. We will be removing references to TME 10 in future product releases. This section briefly describes changes and enhancements included with Inventory Changes to the Configuration Repository With Inventory 3.6.1, a number of changes have been made to the configuration repository and related files and components. New View and Query The INVENTORY_NOSIGMATCH_FILES query uses the view NOSIG_FILES_VIEW to identify software files for which there are no software signatures installed in the configuration repository. Both the query and the view include the following columns: HARDWARE_SYSTEM_ID INSTALLED_FILE_NAME INSTALLED_FILE_SIZE TME_OBJECT_LABEL TME_OBJECT_ID Refer to Upgrading Inventory 3.6 Queries to 3.6.1, on page 1-17 for the procedure to create the new query. Refer to Upgrading the Inventory 3.6 Configuration Repository to 3.6.1, on page 1-15 for the procedure to upgrade the Inventory configuration repository, which adds the new view. 2 Version 3.6.1

7 Improved Installation of Software Signatures The software signatures provided with Version have been sorted in case-sensitive, alphabetical order, and the wfilesig command has been redesigned to take advantage of the sorted signatures. Customers who have not yet installed the Inventory 3.6 software signatures will experience a significant improvement in the speed at which the software signatures are installed. If you have already installed the Inventory 3.6 software signatures, you can still see an improvement in speed when you install new software signatures from later releases or from quarterly updates of the Software Signatures Collection Web page at Also, the software signature file provided with Inventory are significantly better quality than that provided with Inventory 3.6. The file no longer contains obsolete or redundant software signatures. Refer to Upgrading Software Signatures, on page 1-18 for the procedure to install the software signatures. Support for DB2 on OS/390 With Inventory 3.6.1, you can create and configure an Inventory configuration repository for a DB2 RDBMS on an OS/390 server. To configure your DB2 RDBMS, follow the instructions provided in Chapter 3, Installing Inventory, Version 3.6 of the TME 10 Inventory User s Guide, Version 3.6. To create the DB2 configuration repository on an OS/390 server, follow the instructions in Chapter 4, Creating the Configuration Repository, in the section titled Creating a DB2 Configuration Repository. However, instead of running the tivoli_db2_schema.sql script, you should run the tivoli_db2_mvs_schema.sql script. The tivoli_db2_mvs_schema.sql script is a template for your DB2 database administrator (DBA). The DBA must edit the file to add tablespace information. Refer to your RDBMS documentation for more information. Support for DB2 on Windows NT RIM Hosts With Inventory 3.6.1, you can create a RIM host for a DB2 relational database management system (RDBMS) on a Windows NT server. TME 10 Inventory Release Notes 3

8 To configure your DB2 RIM host on Windows NT, follow the instructions provided in Chapter 3, Installing Inventory, Version 3.6 of the TME 10 Inventory User s Guide, Version 3.6. Support for Informix With Inventory 3.6.1, you can create and configure an Inventory configuration repository with the Informix RDBMS. See Appendix A, Creating an Informix Configuration Repository of the TME 10 Inventory User s Guide, Version 3.6 for information about creating and configuring your Informix configuration repository. Improved DMI Scanning The DMI scanner has changed for Inventory to help you construct a valid, complete dmiscan.ini file. The new options is as follows: d file_name.ini The d option automatically creates an INI file (where file_name.ini is the name you choose for the file) that includes every DMI attribute in the DMI service layer of a target system. Once you have created this INI file, edit the file to include the custom table and column names where the information will be stored in the configuration repository. Use this option for each type of system you want to scan for DMI information. Then combine all the files into a single dmiscan.ini file to complete a thorough DMI scan on all target PCs in your environment. The following is a sample usage statement that creates an INI file called fulldmi.ini: dmiscan d fulldmi.ini For more information about the DMI scanner, see Chapter 7 of the TME 10 Inventory User s Guide, Version 3.6 and Version 3.6 Documentation Defects, on page System Requirements This section describes the software and hardware requirements for Inventory A list of supported operating systems is provided in a table in the TME 10 Framework Release Notes, Version Version 3.6.1

9 Software Requirements This section contains information about Inventory requirements for applications and operating systems. RDBMS and RIM Hosts An RDBMS must be installed and configured. Refer to your RDBMS documentation for database installation instructions and requirements. Also, see Using RIM and the RDBMS in Chapter 3 of the TME 10 Inventory User s Guide, Version 3.6 for more information about configuring the RDBMS and the RDBMS Interface Module (RIM) host. In addition to installing the RDBMS, you must designate a managed node as the RIM host in the TMR. The following table provides the supported RIM hosts and each supported RDBMS for each type of RIM host RIM Host Supported RDBMS AIX 4.2.x DB , Oracle 7.3.1, 7.3.2, 7.3.3, Sybase , , , Informix 7.24, 7.30 AIX 4.3.x DB , Oracle 7.2.2, 7.2.3, 7.3.1, 7.3.2, 7.3.3, Sybase , , , Informix 7.24, 7.30 Solaris 2.5.x DB , Oracle 7.3.1, 7.3.2, 7.3.3, Sybase , , , Informix 7.24, 7.30 Solaris 2.6 DB , Oracle 7.2.2, 7.2.3, 7.3.1, 7.3.2, 7.3.3, Sybase , , , Informix 7.24, 7.30 HP-UX DB Oracle 7.3.1, 7.3.2, Sybase , TME 10 Inventory Release Notes 5

10 RIM Host Supported RDBMS HP-UX DB , Oracle 7.2.2, 7.2.3, 7.3.1, 7.3.2, 7.3.3, Sybase , , , Informix 7.24, 7.30 HP_UX Oracle 7.2.2, 7.2.3, 7.3.1, 7.3.2, 7.3.3, Sybase , , , Windows NT 3.5 Windows NT 4.0 DB Microsoft SQL Server 6.5 Oracle 7.2.2, 7.2.3, 7.3.1, Sybase , , DB , Microsoft SQL Server 6.5 Oracle 7.2.2, 7.2.3, 7.3.1, 7.3.2, 7.3.3, Sybase , , Note: The following notes apply: In addition to the normal Oracle client installation, you must also install the 7.1.x Support Files on a Windows NT RIM host. For more information, see Chapter 3, Installing Inventory 3.6 in the TME 10 Inventory User s Guide, Version 3.6. The TNS_ADMIN and LOCAL environment variables are not supported. If you need to store your tnsnames.ora file in a location other than $ORACLEHOME/network/admin, create a link to the file in that directory. RIM requires the DB2 instance be named the same as the DB2 user name. Furthermore, if the DB2 client and DB2 server are on separate systems, the DB2 user must exist on both the DB2 client and server systems. The DB2INSTANCE system environment variable must be set to the RIM DB2 instance on Windows NT servers. HP-UX patch PHCO_5826 must be installed for DB2. This patch fixes an NIS defect that can prevent the use of 6 Version 3.6.1

11 the db2, db2icrt, and db2instance commands. DB2 fixpacks for Solaris, HPUX 10, and AIX are currently not certified for use with RIM on TME 10. Web Browsers To access the Inventory Web pages, you must have a Web browser that supports HTML 1.0 and Java 1.1.x. You can access the UserLink for TME 10 Inventory Web pages with Netscape 3.x, 4.x, or Microsoft Internet Explorer (MSIE) 4.x. To access the administrator s Inventory Web pages, you must have Netscape 4.x or MSIE 4.x. Note: Inventory Web functions support only HTTP 1.0. Users who want to use the Inventory Web functions on MSIE 4.x must disable HTTP 1.1. For more information, see APAR-IX76457 in Version Software Defects, Limitations, and Workarounds, on page Hardware Requirements This section provides the additional disk space requirements to install Inventory on Inventory components. For more information about disk space requirements to install Inventory 3.6, see the TME 10 Inventory Release Notes,Version 3.6. If the table cell contains an N/A, Inventory requires no additional disk space for that item. If a particular Inventory component is not included in this section, no additional disk space is required to upgrade to Inventory TMR Server and Managed Nodes PC Managed Nodes Endpoint Files Note: Use the space requirements that follow as general guidelines rather than absolute totals or even averages. The actual space required for each item depends on the size and configuration of your TMRs. TMR Server and Managed Nodes The following table lists the additional disk space required to install Inventory on managed nodes. The estimated disk space includes TME 10 Inventory Release Notes 7

12 space for the binaries (Bins, Generic Bins), temporary installation configuration files (Cfg Files), manual pages (Man Pages), and message catalogs (Msg Cats). Platform Bins Generic Bins Cfg Files Man Pages Msg Cats AIX 4.x N/A 10 KB 2 KB N/A 4 KB HP-UX 10.x,11.x 10 KB 10 KB 2 KB N/A 4 KB Windows NT 3.51, 4.0 N/A 10 KB 2 KB N/A 4 KB Solaris N/A 10 KB 2 KB N/A 4 KB SunOS N/A 10 KB 2 KB N/A 4 KB PC Managed Nodes The following table lists the additional disk space required to install the TME 10 Inventory PC Scanning Program, Version (PC scanner 3.6.1) on PC managed nodes. Platform NetWare 3.x, 4.x Windows 3.11, Windows for Workgroups 3.11 PC Scanner 38 KB 3 KB Note: The following platforms require no additional disk space to install the PC scanner: Windows NT 3.51, 4.0 OS/2 Windows 95 and 98 8 Version 3.6.1

13 Endpoint Files The Inventory software that is necessary to scan endpoints is installed on the gateway. When you distribute an Inventory profile to an endpoint, the Inventory files that are required for that type of endpoint are sent from the gateway to the endpoint. The following table provides the additional disk space requirements for files that are downloaded to the endpoints during an Inventory scan. Windows 3.x Platform HPUX 10.x, 11.x Endpoint Files 16 KB 8 KB Note: The following platforms require no additional disk space to download endpoint files from a Inventory Gateway: Windows NT 3.51, 4.0 Windows 95 and 98 NetWare 3.x, 4.x AIX OS/2 Solaris SunOS Installation Notes Prerequisites This section summarizes the procedure, including prerequisite steps, for installing Inventory Satisfy the following requirements before installing or upgrading: TME 10 Framework, Version must be installed in your TMR. The or higher version of the TME 10 PC agent must be TME 10 Inventory Release Notes 9

14 installed on all PC managed nodes in your TMR. Note: The version of the PC agent has a defect that affects UserLink for TME 10 Inventory and several other Tivoli applications. Either use version or version Refer to the TME 10 Framework Release Notes for instructions on installing and using the Framework, PC agent, gateways, and endpoints. Refer to your RDBMS documentation, Chapter 3 Installing Inventory and Chapter 4 Creating the Configuration Repository in the TME 10 Inventory User s Guide, Version 3.6 for RDBMS installation instructions and requirements. Installation Directories The following table lists the file types that are included with an installation of Inventory and the directories in which those file types are installed. The Inventory files are installed into several directories under the TME 10 directory structure. The environment variable $BINDIR is the path to the Framework and Inventory executables. $DBDIR is the path to the object database directory that is also created during installation of the Framework. See the TME 10 Framework Planning and Installation Guide, Version 3.6 for more information about these variables. Note: Upgrade scripts for each applicable Inventory component are located in the same directory as the installation scripts. Some Inventory 3.6 files will be replaced with Inventory files. File Type Executable files Tivoli object database updates Man pages (UNIX only) Location $BINDIR/TME/INVENTORY $BINDIR/../generic/TME/INVENTORY $BINDIR/bin $DBDIR The man directory in the directory where the Framework is installed. 10 Version 3.6.1

15 CLI_INV.hlp, POL_INV.hlp files (PCs only) HTML files and Java applets CGI scripts File Type RDBMS configuration repository scripts Inventory queries scripts Software signatures files Gateway files The help directory in the directory where the Framework is installed. $BINDIR/../generic/HTTPd/Inventory $BINDIR/../generic/HTTPd/Inv $BINDIR/../generic/HTTPd/UserLink $BINDIR/TAS/HTTPd/cgi-bin/Inventory $BINDIR/TAS/HTTPd/cgi-bin/Inv $BINDIR/TAS/HTTPd/cgi-bin/UserLink $BINDIR/TME/INVENTORY/SCRIPTS/RDBMS $BINDIR/TME/INVENTORY/SCRIPTS/QUERIES $BINDIR/TME/INVENTORY/SCRIPTS/SIGNATURES $BINDIR/../lcf_bundle Location Before You Begin Installing The procedure that you follow to upgrade to Inventory depends on the version of Inventory you currently have installed. Note: If you are going to be using the Informix RDBMS for your configuration repository, read Appendix A, Creating an Informix Configuration Repository before installing Inventory. If you have Inventory 3.6 installed currently, refer to Upgrading to 3.6.1, on page 1-12 of this document. If you are doing a fresh installation of Inventory, you must install Inventory 3.6 first. Refer to the TME 10 Inventory User s Guide, Version 3.6, Chapter 3, Installing Inventory, Version 3.6 and Chapter 4, Creating the Configuration Repository. Next, turn to Upgrading to 3.6.1, on page 1-12 of this document. TME 10 Inventory Release Notes 11

16 If you have Inventory 3.2, 3.2.1, or installed currently, you must upgrade to Inventory 3.6 first. Refer to the TME 10 Inventory User s Guide, Version 3.6, Chapter 2, Upgrading to Inventory 3.6 for instructions. Next, turn to Upgrading to 3.6.1, on page 1-12 of this document. Upgrading to The procedure to upgrade from Inventory 3.6 to includes the following steps: 1. Upgrading TMR Servers & Managed Nodes, on page Upgrading the PC Scanner, on page Upgrading Gateways, on page Upgrading the Inventory 3.6 Configuration Repository to 3.6.1, on page Upgrading Inventory 3.6 Queries to 3.6.1, on page Upgrading Software Signatures, on page 1-18 Note: If you are using the Informix RDBMS for your configuration repository, read Appendix A, Creating an Informix Configuration Repository before completing the upgrade procedure. Upgrading TMR Servers & Managed Nodes Complete the following steps to install Inventory on your TMR server and managed nodes from either the desktop or the command line: Desktop 1. Select Install > Install Patch. 2. Click Select Media, and set the directory to where the CD-ROM is mounted. 3. Select TME 10 Inventory Upgrade Version 3.6 to Version Select all targets on which to install the Inventory This must include the TMR server and all managed nodes that have Inventory installed on them. 12 Version 3.6.1

17 5. Click Install. Command Line To install Inventory from the command line, use the wpatch command. See the TME 10 Framework Reference Manual, Version 3.6 for information about the wpatch command. The following example installs Inventory on the managed nodes alien, happy, babel, elvis, and sleepy. wpatch c /cdrom i INV_361 alien happy babel elvis sleepy where: c /cdrom Specifies the directory to the CD-ROM. i INV_361 Specifies the name of the patch being installed. alien happy babel elvis sleepy Specifies the list of managed nodes on which Inventory is to be installed. Upgrading the PC Scanner Complete the following steps to install the PC scanner on your PC managed nodes from either the desktop or the command line: Note: The PC scanner must be installed in the same location over the previous PC scanner on each PC managed node. Otherwise, Inventory will try to run the software in the original location. Desktop 1. Select Install > Install Product. 2. Click Select Media, and set the directory to where the CD-ROM is mounted. 3. Select TME 10 Inventory PC Scanning Program, Version Select the PC managed nodes on which you want to install the PC scanner Click Install. TME 10 Inventory Release Notes 13

18 Command Line To install the PC scanner 3.6.1, use the winstall command. See the TME 10 Framework Reference Manual, Version 3.6 for documentation on the winstall command. The following example installs the PC scanner on the PC managed nodes winntpc1, winntpc2, winntpc3, and george. winstall c /cdrom i SCAN winntpc1 winntpc2 winntpc3 george where: c /cdrom Specifies the directory to the CD-ROM. i SCAN Specifies the name of the product being installed. winntpc1 winntpc2 winntpc3 george Specifies the list of PC managed nodes on which the PC scanner is installed. Upgrading Gateways Complete the following steps to install TME 10 Inventory Gateway, Version (Inventory Gateway 3.6.1) on gateways from either the desktop or the command line: Note: You may encounter warning messages if you install the Inventory Gateway on OS/2 systems. Reference Version Software Defects, Limitations, and Workarounds, on page 1-23 for more information. Desktop 1. Select Install -> Install Patch. 2. Click Select Media, and set the directory to where the CD-ROM is mounted. 3. Select TME 10 Inventory Gateway, Upgrade Version 3.6 to Select all targets on which to install the maintenance release. 5. Click Install. Command Line To install the Inventory Gateway 3.6.1, use the wpatch command. See 14 Version 3.6.1

19 the TME 10 Framework Reference Manual, Version 3.6 for documentation on the wpatch command. The following example installs the Inventory Gateway on the gateways thor, odin, and njal. wpatch -c /cdrom -i LCF_361 thor odin njal where c /cdrom Specifies the directory to the CD-ROM. i LCF_361 Specifies the name of the product being installed. thor odin njal Specifies the list of gateways on which the Inventory Gateway is to be installed. Upgrading the Inventory 3.6 Configuration Repository to This procedure upgrades your Inventory 3.6 configuration repository to by creating the NOSIG_FILES_VIEW in your configuration repository. If you are installing the Inventory configuration repository for Informix, you do not need to read this section. See Appendix A, Creating an Informix Configuration Repository for installation instructions. If you have a DB2, MS SQL Server, Oracle, or Sybase configuration repository, copy the xxx_nosig_files.sql script (where xxx depends on your RDBMS. Options are db2, ms_sql, ora, and syb) from the $BINDIR/TME/INVENTORY/SCRIPTS/RDBMS directory on the TMR server to a temporary directory. The next step or steps depend on your RDBMS. Refer to the following sections for more information. DB2 Complete the following steps to upgrade a DB2 configuration repository: 1. Create a connection to the DB2 server database before running the script. Enter the following command at the command line: db2 connect to database_name user user_name using password where: database_name TME 10 Inventory Release Notes 15

20 Specifies the name or alias name of the Inventory database. user_name Specifies the name of the user who owns the Inventory database. This is the login name of the DB2 instance owner. password Specifies the password of the user referred to by user_name. 2. Run the db2_nosig_files.sql script from the command line. Enter the following command: db2 -f db2_nosig_files.sql -o -t -z db2_nosig_files.log The view NOSIG_FILES_VIEW is created on your configuration repository. MS SQL Server To upgrade an MS SQL Server configuration repository, run the ms_sql_nosig_files.sql script as user tivoli. Enter the following command: isql -U tivoli [-P password] -i ms_sql_nosig_files.sql \ -o ms_sql_nosig_files.log where password is the RDBMS password that is set for the RDBMS user tivoli. The view NOSIG_FILES_VIEW is created in your configuration repository. Oracle Complete the following steps to upgrade an Oracle configuration repository: 1. From the directory that contains the ora_nosig_files.sql script, start an SQL*Plus session and log in to the RDBMS server as the RDBMS user tivoli. Enter the following command: sqlplus tivoli/password where password is the RDBMS password that is set for the Oracle user tivoli. 16 Version 3.6.1

21 2. In the SQL*Plus session, run the ora_nosig_files.sql script. Enter the following The view NOSIG_FILES_VIEW is created in your configuration repository. 3. To log out of SQL*Plus, when the script is finished, enter the following command: quit Sybase To upgrade a Sybase configuration repository, run the syb_nosig_files.sql script as user tivoli. Enter the following command: isql U tivoli P password i syb_nosig_files.sql o syb_nosig_files.log where password is the password set for the Sybase user tivoli. The view NOSIG_FILES_VIEW is created in your configuration repository. Upgrading Inventory 3.6 Queries to Complete the following instructions to upgrade your INVENTORY_QUERIES query library from Inventory 3.6 to 3.6.1: 1. Verify that your Tivoli environment is set. If it is not, run the etc/tivoli/setup_env.sh script for UNIX or %windir%\system32\drivers\etc\tivoli\.cmd script for Windows NT. 2. Copy the inventory_queries_to_361.sh script from the $BINDIR/TME/INVENTORY/SCRIPTS/QUERIES directory on the TMR server to a temporary directory. 3. Run the inventory_queries_to_361.sh script by entering the following: inventory_queries_to_361.sh <PolicyRegionName> [QueryLibraryName] where PolicyRegionName specifies the name of the policy region which owns the INVENTORY_QUERIES query library and QueryLibraryName specifies the name of the query library created TME 10 Inventory Release Notes 17

22 that contains the Inventory queries. Upgrading Software Signatures If you have installed the Inventory 3.6 software signatures, you can complete the procedure Upgrading 3.6 Signatures to 3.6.1, on page 1-18 to upgrade to Inventory signatures. This procedure removes signatures that are duplicate, obsolete, or ambiguous and adds the new signatures. If you did not install the Inventory 3.6 software signatures, you can simply follow the procedure Installing Software Signatures, on page 1-18 to add new signatures to your configuration repository. Upgrading 3.6 Signatures to Complete the following steps to upgrade Inventory 3.6 signatures to Inventory 3.6.1: 1. Open the Inventory Software Signature Collection Web page. The URL is 2. Follow the instructions provided on the Web page to access the Download Software Signature page. 3. Complete the required fields. In the list of available software signature files, select Inventory Signatures (Jan 1, 1999). 4. Click the Download button. This opens the Web page titled Instructions for Installing Inventory Signatures which includes information about downloading and using the DELETED_SIGS.INI and the ADDED_SIGS.INI files to upgrade your signatures to Complete the instructions on the Web page in the section Upgrading 3.6 Signatures to Installing Software Signatures If you have not installed 3.6 signatures, install the software signatures contained in the SWSIGS.INI shipped with Inventory Run the following command on your RDBMS server from the directory where the SWSIGS.INI file is located: wfilesig -a -f SWSIGS.INI 18 Version 3.6.1

23 Patches Included in Version The following table lists the patches included in Inventory 3.6.1, the defects those patches fixed, and the item number in Defects Fixed for Version 3.6.1, on page 1-19: Patch ID Defect Number Item Number in Defects Fixed 3.6-INV-0007 CMVC Item 21 on page INV-0008 CMVC Item 21 on page INV-0018 APAR-IX84236 Item 1 on page INV-0021 CMVC CMVC CMVC Item 30 on page 1-23 Item 29 on page 1-22 Item 24 on page INV-0023 APAR-IX85351 Item 2 on page 1-19 Defects Fixed for Version The following defects have been corrected for the release of Inventory. The APAR number (if available) precedes the description of each defect and the CMVC number (if available) follows the description. 1. APAR-IX84236: Hardware scans no longer fail on Micron PCs that have an IOMEGA zip drive. 2. APAR-IX85351: Hardware scans no longer fail on clients of NetWare-managed sites when trying to scan Netware network printers. 3. APAR-IX70300: Certain configuration repository tables now store accurate hardware information. Proper data is now inserted in the fields for the following tables: for Windows NT systems, the PAGING_SPACE_KB column of the COMPUTER_SYSTEM_MEMORY table and, for Solaris SPARC stations, the HARDDISK_SIZE_MB and the TME 10 Inventory Release Notes 19

24 HARDDISK_CYLINDERS columns of the HARDDISK table. 4. Configuration files with spaces in the file name can now be saved as RCS format. (CMVC-32116) 5. APAR-IX75340: When you scan an OS/2 PC managed node, the elapsed time for the MIF files created during the scan is no longer reported as a negative value. (CMVC-35237) 6. APAR-IX76915: The Software Signatures Editor was not case-sensitive. If users attempt to edit a software signature by changing the case of a file name, the change is now reflected in the configuration repository. (CMVC-37404) 7. Swap space from Windows 3.x PC managed nodes is now reported correctly. (CMVC-38251) 8. Inventory now supports DB2 for Windows NT RIM host. See Support for DB2 on Windows NT RIM Hosts, on page 1-3 for more information. (CMVC-38271) 9. APAR-IX77985: If you attempt to distribute a profile owned by a profile manager with no subscribers, the following error message no longer occurs: Distribute of profile Profile_Name failed for some subscribers. An internal error occurred: method not found where Profile_Name is the name of the profile that failed. An error message that accurately describes the problem is displayed instead. (CMVC-39081) 10. When Inventory performs a hardware scan on Windows 3.1 and OS/2 systems, the value stored in the LOGICALDRIVE_SIZE_KB column of the LOGICALDRIVE table is now correct. The scanner now reports the size of the logical drive in kilobytes, although it had previously reported the value in megabytes. (CMVC-42384, 42383) 11. Scans of HP-UX systems no longer reports space usage for mounted CD-ROMS as if they were hard disks. (CMVC-42540) 12. Scans on Windows 95 and Windows NT systems no longer fails because the length of the path to an item in the Recycle Bin could 20 Version 3.6.1

25 be more than 256 characters long. The Recycle Bin is now listed in the Do Not Search These Directories list. (CMVC-43336) 13. The LOGICALDRIVE table now keeps configuration change history. When a profile is customized to Update with Differences, the information stored in LOGICALDRIVE is no longer replaced and an UPDATE record is now stored in the CONF_CHANGE_TYPE column. (CMVC-43345) 14. If you have a DB2 or an Informix configuration repository and you click the Table Description button of the Create Query dialog, the following error message is no longer displayed: No Column List Generated for the Table: Table_name where Table_name is the name of the table in the Table/View Name field. (CMVC-43405) 15. Inventory now populates the configuration repository with information about Ultrasparc 5 Solaris 2.6 disk drives. (CMVC-43480) 16. To capture log information while creating an Oracle configuration repository, you no longer have to run the SQL*Plus command spool tivoli_ora_*.log (where * was either admin or schema). Spooling is now part of the configuration repository scripts for Oracle. (CMVC-43567) 17. Endpoints in interconnected TMRs can now connect to the HTTP daemon in a connected TMR. Prior to 3.6.1, endpoints could only connect to the HTTP daemon in the TMR to which the endpoint belongs. (CMVC-43692) 18. The DMI scanner can now be used on Windows NT managed nodes. (CMVC-43828) 19. The default list of file extensions configured for Inventory profiles created with Inventory no longer includes both upper case versions of each extension because software scans for PCs and UNIX systems are case-insensitive. (CMVC-43830) 20. The Inventory hardware scanner now has the ability to pick up the hard disk serial number on AIX systems.(cmvc-43987) 21. You can now update tables populated by information from scalar TME 10 Inventory Release Notes 21

26 groups in custom MIF files. The first scan that read a scalar group could successfully add information to the configuration repository, but subsequent scans no longer fail when you chose the Update with Differences option. (CMVC-44104) 22. Scans on HP-UX 11 systems no longer include cross-mounted drives. This sometimes caused the scan to time out before completion. (CMVC-44135) 23. Software scans no longer collect both full file names and paths and truncated file names and paths. Only the full file names and paths are returned. The TMR server determines the truncated information based on the complete information. This saves network bandwidth because only one version of the file name and path is sent to the TMR server, instead of two. (CMVC-44710) 24. When scanning for software or configuration files on OS/2 endpoints or PC managed nodes, the scanner no longer searches network drives. If a drive contained a large directory structure, it no longer causes the following error: MIF PARSE ERROR This was a symptom of insufficient memory resources caused by inv_endpt_meths.exe traversing the large directory structure of a network drive. (CMVC-44739) 25. Inventory hardware scans now provide a more meaningful drive model for AIX systems. (CMVC-46597) 26. Hardware scans for certain types of HP-UX CD-ROMS no longer fail. (CMVC-46597) 27. Inventory now stores information about the operating system for Windows 98 systems. Therefore, you can right-click the icon of a Windows 98 system and get the correct information for the configuration repository. (CMVC-46725) 28. APAR-IX81629: Inventory can now handle MAC addresses correctly. (CMVC-47731) 29. You can now successfully distribute and execute scripts on OS/2 targets. (CMVC-48537) 22 Version 3.6.1

27 30. You can now perform Inventory hardware and software scans from OS/2 gateways. (CMVC-48539) 31. Inventory scans no longer fail if there was a significant difference (over 500 KB) between the MIF file of the most recent scan and MIF file of the previous scan. (CMVC-48654) 32. You can now log into a gateway from an endpoint while the Inventory scan is in progress. (CMVC-49200) 33. Inventory hardware scans no longer go into an infinite loop if the scanned system has an attached zip drive. (CMVC-49203) 34. The User Data Form fields now check to ensure that users enter strings of a length equal to or less than the string limit you set in the User Data Template. (CMVC-49379) Version Software Defects, Limitations, and Workarounds This section describes known defects in Inventory The APAR number (if available) precedes the description of each defect and the CMVC number (if available) follows the description. Where applicable and known, suggested workarounds are identified. 1. You may encounter warning messages when installing TME 10 Inventory Gateway Version 3.6 on an OS/2 gateway. When you use the TME 10 Desktop Install to install TME 10 Inventory Gateway Version 3.6, you will see the following message: Installing product: TME 10 Inventory Gateway, Version 3.6 The following problems were encountered: Host link.dev.tivoli.com: Could not find a valid Binaries media packet listed in the installation index (.IND) file for this type of platform.check that the cdrom image directory is set correctly for what you are trying to do. Ignore the message and proceed with the installation. The gateway will function correctly. You will not encounter this problem when upgrading to using Desktop Install. When you use TME 10 Software Installation System (SIS) to install TME 10 Inventory Gateway, Version 3.6 on an OS/2 TME 10 Inventory Release Notes 23

28 gateway, or when you use SIS to upgrade to 3.6.1, you will see the following message: Interp not valid for product See the SIS Release Notes for special instructions on how to install TME 10 Inventory Gateway, Version 3.6 on an OS/2 Gateway using SIS. 2. Installation of Inventory fails if you indicate a non-existent RIM host in the Install Options dialog or the RIM arguments of the winstall command. (CMVC-43650) When you install, the following message is displayed in the status dialog: An instance named RIMhost of resource "ManagedNode" was not found. RDBMS_HOST_OID= completed with errors. where RIMhost is the name of the non-existent RIM host. The following error message is another signal that installation failed due to a non-existent RIM host: Could not find object s method implementation: method not found 3. Upgrading from Framework Version 3.6 to upgrades all queries in query libraries. If a query belongs to a connected TMR and cannot be accessed at the time of the upgrade, it will not get upgraded. WORKAROUND: Complete the following steps to upgrade the query: a. Create a temporary query library QL_temp. b. Copy the query to the query library QL_temp. To do so, select the query and drag it over the new QL_temp query library. c. Remove the query from the original library. Select the query and choose Edit->Remove. d. Copy the query back to the original library from QL_temp by dragging it to the original library. e. Remove the query from QL_temp by choosing 24 Version 3.6.1

29 Edit->Remove. 4. You cannot run the winvorphan command on a DB2 or Informix configuration repository. 5. If you have a Microsoft SQL Server configuration repository, you cannot run the winvorphan command unless you change the database default nullability option. WORKAROUND: Complete the following procedure: a. Log in into Microsoft SQL Server as user sa. Enter the following: isql -U sa -P password where password is the password for the user sa. b. In the Inventory configuration repository, change the default nullability option of the database by entering the following: use inventory go sp_dboption inventory, ANSI null default, true go 6. When the Sybase transaction log is full, Inventory scans do not complete, and you cannot perform any operations that require access to the Inventory configuration repository. No status, response, or error is provided. (CMVC-35663) WORKAROUND: Clear the Sybase transaction log. Contact your database administrator for assistance and other options. 7. APAR-IX76457: Inventory Web functions support only HTTP 1.0. (CMVC-36764) WORKAROUND: Users who want to use the Inventory Web functions must disable HTTP 1.1 on MSIE 4.x. Complete the following steps: a. On your MSIE Web browser, choose View->Internet Options. b. Click the Advanced tab. c. Click the HTTP 1.1 option to deselect it. Note: Netscape 4.x does not have this problem. TME 10 Inventory Release Notes 25

30 8. If you attempt to replace a software signature that you have deleted in the Software Signatures Editor, you see the following error message: You can only replace one item at a time in the list. This error message does not describe the problem. The problem is that you cannot replace a software signature that you have deleted. (CMVC-39112) WORKAROUND: Use the Add button to add the software signature. 9. When you add software signatures to the Inventory configuration repository, the signature file size must be greater than zero bytes. (CMVC-41670) 10. When Inventory saves information in the configuration repository about a Windows 3.x client of a NetWare managed site, and an error occurs, an incorrect error message is displayed in the error dialog. (CMVC-43519) 11. If you attempt to execute a script as part of a profile distribution on a Solaris or HP-UX target and the script fails, Inventory does not generate an error message. Furthermore, the Inventory notice group incorrectly states that the profile distribution succeeded. (CMVC-43649) 12. If you run the script to upgrade a Microsoft SQL Server configuration repository from an MS SQL client, it fails. The script does not specify the server on which to perform the upgrade. (CMVC-44228) WORKAROUND: Run the upgrade script from the Microsoft SQL Server machine. 13. If you have a DB2 or Informix configuration repository, you cannot run a query that creates a join between two tables. The first table in the From clause in the Create Query dialog does not get truncated to the required length for DB2 or Informix, causing the SQL statement to fail. (CMVC-44771) WORKAROUND: Use the truncated version of the table names when joining two or more tables. See the TME 10 Inventory User s Guide, Version 3.6, Appendix C, Configuration Repository for a 26 Version 3.6.1

31 list of DB2 and Informix abbreviations. 14. No view corresponds to the NW_VOLUMES table in the configuration repository. (CMVC-45366) WORKAROUND: Create a query that points to the NW_VOLUMES table. 15. An error message stating that a directory cannot reside in both the Do Not Search These Directories scrolling list and the Search These Directories scrolling list is displayed if you do the following: a. Delete a directory from the Do Not Search These Directories scrolling list. b. Add that directory to the Search These Directories scrolling list c. Save and close the profile. d. Open the profile again. e. Move the directory from the Search These Directories scrolling list to the Do Not Search These Directories scrolling list and try to save. (CMVC-46730) WORKAROUND: After you open the profile again in step d, do not move the directory to the Do Not Search These Directories scrolling list. Instead, delete the directory from the Search These Directories scrolling list. Next, click the Save button. Then, you can add the directory to the Do Not Search These Directories scrolling list. 16. You cannot run the query LASTSCAN_CONFIG_FILES_CHANGED on a DB2 or Informix configuration repository. This query uses the view LSCAN_CFG_FILE_VIEW which is too long to be compatible with DB2 because words FILE and VIEW do not get truncated by RIM. (CMVC-63215) WORKAROUND: Complete the following steps: a. Delete the query from the query library: TME 10 Inventory Release Notes 27

32 b. Recreate the query using: wcrtquery -d "Config Files Changed in Last Scan" \ -r inventory -v LASTSCAN_CONFIG_FILES \ -c TME_OBJECT_LABEL \ -c CONFIG_FILE_NAME \ -c CONFIG_CHANGE_TYPE \ -c CONFIG_CHANGE_TIME \ -c CONFIG_FILE_PATH \ -c CONFIG_FILE_SIZE \ -c CONFIG_FILE_DATE \ -c CONFIG_FILE_TIME \ -w "order by TME_OBJECT_LABEL" \ "$query_lib" LASTSCAN_CONFIG_FILES_CHANGED where $query_lib is the variable containing the name of the Query Library for which this query should be created. By default, this value is set to INVENTORY_QUERIES. 17. If you use an Informix RIM host and errors occur, RIM always returns: PA_RESULT failed with code -1 : WORKAROUND: To see the specific error message, enable RIM error and information tracing. (CMVC-63414) 18. If the DB2 server is NT, the RIM host cannot be installed on the same system as the DB2 server. (CMVC-63480) WORKAROUND: The RIM host must be created on a separate DB2 client system. 19. The following problems exist with the wrminvnode command: The v and o options do not work. There are inconsistencies in the way wrminvnode reacts when the command includes an invalid node name versus an invalid node ID. When the node ID is invalid, wrminvnode returns an error message, but if a node-name is invalid, no error is generated.(cmvc-53835, 60983, 61279) WORKAROUND: The wrminvnode command works if you provide the target system name without any options. For example, the following command removes information about the tigger managed node: wrminvnode tigger 28 Version 3.6.1

33 Version 3.6 Documentation Defects This section describes documentation defects in the TME 10 Inventory User s Guide, Version 3.6, man pages, or online help. The APAR number (if available) precedes the description of each defect and the CMVC number (if available) follows the description. 1. In the TME 10 Inventory User s Guide, Version 3.6 and in the man pages, the description and argument definition for the o option of the wrminvnode command is incorrect. The o option requires the HARDWARE_SYSTEM_ID of the system you want to remove from the configuration repository, not the TME_OBJECT_ID. (CMVC-48849) In addition, the usage statement for this command is incorrect in the book, man pages, and online help. The following usage statement is correct: wrminvnode [-l rim_label] [-v] [-o node_id] [node_name1 node_name2...] where: rim_label Specifies the name of the RIM object. By default, the value is inventory. node_id Specifies the hardware system ID of the system you want to remove from the configuration repository. node_name1, node_name2 Specifies the TME_OBJECT_LABEL of the system or systems you wan to delete from the configuration repository. 2. In Chapter 7 of the TME 10 Inventory User s Guide, Version 3.6, the section titled Customizing PC Scans for DMI Information needs the following corrections: On pages 7-39 through 7-41, the book refers to the sample INI file for the DMI scanner as dmi.ini. The correct name for this file is dmiscan.ini. When you create DMI tables and columns for your configuration repository, you must carefully choose the TME 10 Inventory Release Notes 29

34 column lengths. At a minimum, each column must be seven characters long to store the value NO_DATA. NO_DATA is the value returned when the DMI scanner finds no information for the attribute in DMI service layer of a system. If a column is not large enough to hold the scanned data, the entire row will not be inserted. To estimate the necessary column length, run the DMI scanner once with no options checked in the Read Results column. Look at the contents of the resultant dmiscan.mif. In step 2 on page 7-39, when you edit the comprehensive dmiscan.ini file, organize entries by DMI attribute rather than by system type. This will prevent duplicate entries and overwriting of entries. The following examples is the correct way to organize the contents of dmiscan.ini: DMI_DATA SERIAL Compaq PC Systems MIF ComponentID Serial Number DMI_DATA SERIAL Dell Systems MIF ComponentID Serial Number DMI_DATA SERIAL PC Systems MIF ComponentID Serial Number DMI_DATA BIOS_VER Compaq PC Systems MIF ComponentID Version DMI_DATA BIOS_VER Dell Systems MIF ComponentID Version DMI_DATA BIOS_VER PC Systems MIF ComponentID Version The following example is the incorrect way to organize the contents of the dmiscan.ini: DMI_DATA SERIAL Compaq PC Systems MIF ComponentID Serial Number DMI_DATA BIOS_VER Compaq PC Systems MIF ComponentID Version DMI_DATA SERIAL Dell Systems MIF ComponentID Serial Number DMI_DATA BIOS_VER Dell Systems MIF ComponentID Version DMI_DATA SERIAL PC Systems MIF ComponentID Serial Number DMI_DATA BIOS_VER Compaq PC Systems MIF ComponentID Version DMI_DATA BIOS_VER PC Systems MIF ComponentID Version Step 4 on page 7-41 indicates that you should distribute the dmiscan.ini file to systems you plan to scan. This information is correct for managed nodes and PC managed nodes. However, to run the DMI scanner on endpoints, you must install the dmiscan.ini file on the gateway in the $BINDIR/../lcf_bundle/bin/os_dir/inv/SCANNER directory, where os_dir is either win95 or w32-ix The following corrections need to be made to Appendix C, Configuration Repository of the TME 10 Inventory User s Guide, Version Version 3.6.1