TME 10 Inventory Release Notes. Version 3.2.1

Transcription

1 TME 10 Inventory Release Notes Version July 16, 1998

2

3 TME Inventory Version Release Notes (July 9, 1998) Copyright Notice Copyright 1998 by Tivoli Systems, 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. 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, and TME 10. 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. Java and Hot Java are trademarks of Sun Microsystems, Inc. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks or registered trademarks of Intel Corporation in the United States and other countries. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notice 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 Systems 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, 500 Columbus Avenue, Thornwood, New York

4

5 TME 10 Inventory Release Notes New Features... 1 The Configuration Repository... 1 Policy Region Tables... 2 INSTALLED_BIOS Table... 2 TAG Table... 3 Other Configuration Repository Changes... 3 BIOS Scanner... 6 Case Sensitivity... 7 New Inventory Hardware Scanner... 8 Limited Logging... 8 System Requirements... 9 Installation Notes... 9 Prerequisites... 9 Uninstalling or Reinstalling Inventory... 9 Installation... 9 Installing Inventory and the Inventory PC Scanning Program From the Desktop From the Command Line Interface (CLI) Upgrading the Configuration Repository Preparing to Run the Configuration Repository Upgrade Running the Upgrade Script Upgrading the Inventory Queries from Inventory Upgrading the Software Signatures Patches Included in Defects Fixed for Software Defects, Limitations, and Workarounds TME 10 Inventory 3.2 Maintenance Release 1 Release Notes i

6 Product Notes Use of Wildcard in Software Scan Configuration Updated Scripts Upgrade Scripts Added by Inventory ii Version 3.2.1

7 1Release Notes New Features This Release Notes document provides important information about Inventory 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 Defects Fixed for Software Defects, Limitations, and Workarounds Product Notes The Configuration Repository The schema for the configuration repository has been changed for Inventory The Inventory configuration repository includes several new tables and views. All tables and views, with the columns included in each, are listed in Appendix C, Configuration Repository in the TME 10 Inventory User s Guide. The following tables and columns are new in the configuration repository schema for Inventory 3.6. An asterisk denotes columns in the primary key (*). The following tables and their associated columns have been added to the configuration repository: TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 1

8 New Features Policy Region Tables The policy region tables listed below were added to allow you to perform queries specific to policy regions. POLICY_REGION REGION_ID (64 characters, not null)* TMR_LABEL (32 characters, not null)* REGION_NAME (64 characters, null) POL_REG_MEMBER REGION_ID (64 characters, not null)* TMR_LABEL (32 characters, not null)* HARDWARE_SYSTEM_ID (64 characters, not null)* POL_REG_STRUCTURE PARENT_REGION_ID (64 characters, not null)* PARENT_TMR_LABEL (32 characters, not null)* CHILD_REGION_ID (64 characters, not null)* CHILD_TMR_LABEL (32 characters, not null)* INSTALLED_BIOS Table The INSTALLED_BIOS table was added to store information about the BIOS (Basic Input/Output System) chip on each client or endpoint that is scanned. 2 Version 3.2.1

9 New Features INSTALLED_BIOS HARDWARE_SYSTEM_ID (64 characters, not null)* BIOS_ID (128 characters, not null) BIOS_ID_BYTES (16 characters, null) BIOS_DATE (16 characters, null) BIOS_STRING (128 characters, null) HW_MANUFACTURER (32 characters, null) BIOS_MANUFACTURER (32 characters, null) BIOS_MODEL (32 characters, null) CONFIG_CHANGE_TYPE (12 characters, not null)* CONFIG_CHANGE_TIME (32 characters, null) TAG Table The TAG table was added to store internal information for use with the Tivoli Application Management Specification (AMS) Product. TAG TAG_NAME (64 characters, not null)* TAG_TYPE (16 characters, not null)* STATUS (32 characters, null) Other Configuration Repository Changes Other changes to the configuration repository include the following: In the SOFTWARE_SIGNATURE_FILE table, the following columns are now part of the primary key: SOFTWARE_COMPONENT_NAME SOFTWARE_COMPONENT_VERSION TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 3

10 New Features In the INSTALLED_OS_DETAILS table, the length of the DESCRIPTION column was changed from 32 characters to 64 characters. In the following tables, the length of the CONFIG_CHANGE_TYPE column has been changed from 32 characters to 12 characters: INSTALLED_OS_DETAILS INSTALLED_PRINTER INSTALLED_RWOPTICAL_DRIVE In the table NETWORK_CARD, the length of the column NETWORK_CARD_MODEL has changed from 32 characters to 64. The view INSTALLED_OS_DET_VIEW has been added. The query INVENTORY_OS_DETAILS uses the view INSTALLED_OS_DET_VIEW. 4 Version 3.2.1

11 The view PC_BIOS_VIEW now includes the following columns: New Features TME_OBJECT_ID (128 characters, null) TME_OBJECT_LABEL (32 characters, null) HARDWARE_SYSTEM_ID (64 characters, not null) BIOS_ID ( 128 characters, not null) BIOS_ID_BYTES (16 characters, null) BIOS_DATE (16 characters, null) BIOS_STRING (128 characters, not null) HW_MANUFACTURER (32 characters, null) BIOS_MANUFACTURER (32 characters, null) BIOS_MODEL (32 characters, null) CONFIG_CHANGE_TYPE (12 characters, not null) CONFIG_CHANGE_TIME (32 characters, null) In the NETWARE_SERVER table, the NW_SERIAL_NUMBER column (12 characters, null) has been added. TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 5

12 New Features The table PROCESSOR has the following new columns. All of the columns that are one character in length and have either a Y or N value: FEATURE (16 characters, null) STEPPING (8 characters, null) MODEL (8 characters, null) FAMILY (8 characters, null) VIR_MODE_EXT (1 character, null) PAGE_SIZE_EXT (1 character, null) TIME_STAMP_CNT (1 character, null) MODEL_SPEC_REG (1 character, null) PHYSICAL_ADDR_EXT (1 character, null) MACHINE_CHECK_EXCPT (1 character, null) CMPXCHG8B_INST_SUP (1 character, null) ON_CHIP_APIC (1 character, null) MEM_TYPE_RANGE_REG (1 character, null) PAGE_GLOBAL_ENABLE (1 character, null) MACHINE_CHK_ARCH (1 character, null) COND_MOVE_INST (1 character, null) MMX_TECHNOLOGY (1 character, null) The view PROCESSOR_VIEW includes the new columns added to the PROCESSOR table described above. BIOS Scanner The PC Scanning Software for Inventory includes a BIOS scanner, which can identify a predefined set of manufacturers and models. Entries can also be added to the bios scanner dictionary file so that it will identify additional systems. The BIOS scanner, named 6 Version 3.2.1

13 New Features mrmbios, runs whenever a hardware scan of a PC is executed. It finds the BIOS identification string of the PC and returns it in a Management Information Format (MIF) file. It also returns the model and manufacturer of the PC if the BIOS id is in the dictionary file on that PC. To update the dictionary file for any unknown PCs, complete the following steps: 1. Tivoli recommends keeping a TMR wide copy of the dictionary file, bios.ini, in a central location from which the file can be distributed to all PcManagedNodes. 2. Check for PCs that return UNKNOWN for manufacturer and model in the scan results. To do this follow these steps: a. Query the INSTALLED_BIOS table or the PC_BIOS_VIEW view. b. Look for the value UNKNOWN in the BIOS_MODEL column. c. Use the HARDWARE_SYSTEM_ID from the PC_BIOS_VIEW, to find which PC this is by looking in the COMPUTER_SYSTEM table. 3. Update the dictionary file, bios.ini, on the unrecognized PC by running the mrmbios command so that it will prompt the user to enter the Manufacturer Name and the Manaufacturer Model by running the following command: mrmbios -d bios.ini -a 4. Merge this new bios.ini file with the TMR wide copy of the file using a text editor or script. 5. Distribute the file to all PC managed nodes. There should be only one version of the dictionary file in a TMR. Case Sensitivity For PC targets, including managed nodes running Windows NT, software scanning and signature matching are not case sensitive. For UNIX, case sensitivity depends on the scanning option, as described in the following list: TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 7

14 New Features Filename extension matching is not case sensitive Configuration file matching is not case sensitive. Directory inclusion and exclusion is case sensitive Signature matching is case sensitive. Note: Signature matching is performed in the RDBMS by the views such as INSTALLED_SOFTWARE_VIEW and INSTALL_PC_SOFTWARE_VIEW. The scanner does all other matching. New Inventory Hardware Scanner Inventory uses TIVHSCAN, a scanner designed and maintained by Tivoli, to scan the hardware on all PC targets except Windows 3.x machines. On Windows 3.x, Inventory still uses the Intel scanner LDISCAN. Limited Logging Inventory logs do not list error conditions because: RIM does not report enough error information. Other errors are already logged in other areas. There are 3 types of information that is logged in Inventory RIM Logging - Lists the SQL commands equivalent to what Inventory generates when inserting data into the RDBMS Progress Logging - Lists the current stage of a scan. Debug Log - Lists minimal debug information that you should provide to Tivoli Support To activate logging, use the new -l flag for the wsetiprf command. See the Inventory User s Guide or the man page for more information about using the wsetiprf command. You should use the -l argument 8 Version 3.2.1

15 System Requirements to activate logging. The following options are available for this argument: RIM - RIM logging only, generates a file called Inventory_RIM_log in /tmp or on NT %DBDIR%/tmp PROGRESS - Progress logging only, generates the log file Inventory_Progress_log in /tmp or on NT %DBDIR%/tmp ALL - turns on RIM and Progress logging, in addition to the Debug log, which is Inventory_Debug_log NORMAL - sets logging back to normal inventory logging, which means writing to notice groups. System Requirements The Inventory 3.2 Maintenance Release 1, requires Inventory 3.2. Otherwise the requirements are identical to those of Inventory 3.2. For the System Requirements for Inventory 3.2, please see the TME 10 Inventory Version 3.2 Release Notes. Installation Notes Prerequisites This section summarizes the procedure, including prerequisite steps, for installing Inventory. This section also documents changes that have developed since the TME 10 Inventory User s Guide was published. Inventory 3.2 must be installed before Inventory can be installed. Uninstalling or Reinstalling Inventory Please contact Tivoli Customer Support for information on uninstalling Inventory TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 9

16 Installation Notes Installation The ManagedNode code for Inventory is installed as a patch to Inventory 3.2. The new scan software for PC managed nodes are installed as a product, and should be installed over the existing Inventory 3.2 scan software. For additional information on installing patches and products in Tivoli, please refer to the application s user s guide, and the Framework User s Guide, the Framework Planning and Installation Guide. Installing Inventory and the Inventory PC Scanning Program Backup the Tivoli database of each TMR server to be upgraded, either from the Desktop or by using the wbkupdb command. 2. Mount the CDROM. 3. Decide whether to install from the Tivoli Desktop or the command line interface. From the Desktop Install Inventory Select Install Patch. 2. Choose Select Media, and set the path to where the CDROM is mounted. 3. Select TME 10 Inventory 3.2, Maintenance Release 1 4. Select all targets on which to install the Maintenance Release. This must include the TMR server and all Managed Nodes that have inventory installed on them. 5. Select Install, and verify the contents of the Install Popup. Install the Inventory PC Scanning Program. 1. Install the new scanners on all the PC Managed Nodes. 2. Select Install Product this time. 3. Choose Select Media, and set the path to where the CDROM is mounted. 10 Version 3.2.1

17 Installation Notes 4. Select TME 10 Inventory PC Scanning Program, Version 3.2.1, 5. Select the PC Managed Node targets 6. Select Install or Install & Close. Note: If the Inventory PC Scanning Program from a previous release has been installed on a PC, the TME 10 Inventory PC Scanning Program, Version must be installed in the same location over the previous Inventory PC Scanning Program. Otherwise Inventory will try to run the software in the original location. From the Command Line Interface (CLI) Install Inventory Use the wpatch command. See the TME 10 Framework Reference Manual, Version 3.2 for documentation on the command wpatch. Example: wpatch -c /cdrom -i INV_321 alien happy babel elvis sleepy This is an exmaple of the wpatch command with the minimum options to install Inventory The flags are as follows: -c /cdrom is the path to the CDROM. -i INV_321 is the name of the patch being installed alien happy babel elvis sleepy is the list of managed node Targets on which Inventory is to be installed. To install the Inventory PC Scanning Program use the winstall command. See the TME 10 Framework Reference Manual, Version 3.2 for documentation on the command winstall. TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 11

18 Installation Notes Example: winstall -c /cdrom -i SCAN winntpc1 winntpc2 winntpc3 george This is an example of the winstall command with the minimum options to install Inventory PC Scanning Program The flags are as follows: -c /cdrom is the path to the CDROM. -i SCAN is the name of the product being installed. winntpc1 winntpc2 winntpc3 george is the list of PC managed node Targets on which Inventory is to be installed. Upgrading the Configuration Repository To upgrade the Inventory 3.2 Configuration Repository to Inventory 3.2.1, some preliminary tasks must be completed. The primary step in upgrading the Configuration Repository is executing the upgrade script, upgrade_to_321.sh. This script needs to be executed on the RIM host, or a machine that has access to all the necessary scripts and to the RDBMS Vendor's client software. These directions are written for running the upgrade on the RIM host. If the upgrade process is not run on the RIM host the required scripts must be copied to the machine on which the upgrade will be run. Otherwise the following requirements apply. CAUTION: The configuration repository should be backed up before running the upgrade_to_321.sh script. Consult the database administrator or the user s guide for the RDBMS for more information about database back ups. All RDBMS-related messages generated while the script executes are stored in output log files in the directory from which the script was executed. The log file has the same name as the related script, except 12 Version 3.2.1

19 Installation Notes that the extension for the log file is.log. For example, the script ora_sp3_patch.sql generates the log file ora_sp3_patch.log. Preparing to Run the Configuration Repository Upgrade. Before Running the Upgrade Script the following tasks need to be completed: 1. Install the Inventory upgrade from the CD-ROM. 2. Log on to the RIM host. Note: For DB2, the scripts must be run on the RIM host as the client instance owner. 3. Verify the values of the following environment variables specific to your RDBMS: MS SQL Ensure that the path to isql is set in the environment from which the upgrade script is to be run. DB2 If a db2profile script does not reside in the instance owner s home directory that contains the settings for the DB2INSTANCE environment variable, set DB2INSTANCE to the login name of the instance owner. Ensure that the path to DB2 is set in the environment from which the upgrade script is to be run. TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 13

20 Installation Notes Oracle Set the environment variable ORACLE_HOME to the directory where the Oracle RDBMS client or server software is installed. This should correspond to the RIM value of DATABASE_HOME. If the RIM host is a different machine from the RDBMS server, you must set the environment variable TWO_TASK. This should correspond to the RIM value of SERVER ID. Ensure that the path to sqlplus is set in the environment from which the upgrade script is to be run. Sybase Set the SYBASE environment variable as the path to the directory where the Sybase RDBMS client or server software is installed. This should correspond to the RIM value of DATABASE_HOME. Set the DSQUERY environment variable as identifier that the client uses to extract connection information from the interfaces file. This should correspond to the RIM value of SERVER_ID Ensure that the path to isql is set in the environment from which the upgrade script is to be run. 4. Make sure the following scripts, as appropriate for your RDBMS, are in the $BINDIR/TME/INVENTORY/SCRIPTS/RDBMS directory on the RIM host, including the upgrade_to_321.sh script: 14 Version 3.2.1

21 Installation Notes DB2 db2_sp3_patch.sql MS SQL ms_sql_sp3_patch.sql cr_ms_sql_drop_pk.sql Oracle ora_sp2_patch.sql Sybase syb_sp3_patch.sql cr_syb_drop_pk.sql Running the Upgrade Script The upgrade_to_321.sh script must drop some tables from the Configuration repository. It copies the contents of these tables to temporary tables before dropping them. The following tables from the Inventory 3.2 configuration repository are copied to temporary tables during the upgrade: INSTALLED_OS_DETAILS INSTALLED_PRINTER NETWORK_CARD INSTALLED_RWOPTICAL_DRIVE PC_DEVICE_DRIVER SOFTWARE_SIGNATURE_FILE TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 15

22 Installation Notes In addition, the script backs up the software signature information in the SOFTWARE_SIGNATURE_FILE table. WARNING: Make sure that there is sufficient free space in the RDBMS for copies of these tables, otherwise the upgrade of the Schema will fail. Make sure that there is enough free space for to hold a complete copy of the tables listed above. In general 20 to 30MB of space should be enough. Also, make a backup of the Configuration Repository before running the upgrade script. For DB2, a connection to the DB2 database must be created before running the script. Issue the following command at the command line: db2 connect to database_name user user_name using password where: database_name Specifies the name or alias name of the Inventory database. user_name Specifies the name of the user who owns the Inventory database. password Specifies the password of the user referred to by user_name. Run the upgrade_to_321.sh script to add the views, tables, and columns that are required for Inventory This script calls the other scripts that are specific to your RDBMS. Enter the following at the command line for your RDBMS server to run the script: 16 Version 3.2.1

23 Installation Notes For UNIX: upgrade_to_321.sh RDBMS_vendor user_name password For NT: sh upgrade_to_321.sh RDBMS_vendor user_name password where: RDBMS_vendor Specifies the name of your RDBMS. The options are DB2, Oracle, MS_SQL, and Sybase. user_name Specifies the name of the owner of the Inventory configuration repository. password Specifies the password for owner of the configuration repository Example: sh upgrade_to_321.sh Oracle tivoli tivoli This would upgrade the Schema on Oracle, where the Inventory user is tivoli and its password is tivoli. Note: Before you run a script on a DB2 database, you must create a connection to that database. See step Optionally a new Inventory Schema could be created instead. After installing Inventory 3.2.1, the scripts, tivoli_*_schema.sql, in TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 17

24 Installation Notes $BINDIR/TME/INVENTORY/SCRIPTS/RDBMS are replaced by the Inventory upgrade. So these SQL scripts create the complete schema. The process of running these scripts is the same as in Inventory 3.2, and is documented in the Inventory 3.2 User s Guide. Upgrading the Inventory Queries from Inventory 3.2. WARNING - running this script will delete any of the queries created by the 3.2 version of the inventory_queries.sh script that are altered by the upgrade script. Run the script in $BINDIR/TME/INVENTORY/SCRIPTS/QUERIES On UNIX: inventory_queries_to_321.sh On NT: sh inventory_queries_to_321.sh This will remove the queries that are changed in and recreate them with the settings for Inventory If the 3.2 Inventory queries were never created, then just run the script inventory_queries.sh from a managed node on which Inventory has been installed, as this script will create all of the queries. When Inventory is installed, it over-writes the 3.2 version of the script with the version. Upgrading the Software Signatures. The file, SIGS_UPDATE.INI, contains all the signatures that have been added to Inventory The upgrade process just adds the new signatures. 18 Version 3.2.1

25 Defects Fixed for From the directory containing the signature files, $BINDIR/TME/INVENTORY/SCRIPTS/SIGNATURES run the following command on a managed node that has Inventory wfilesig -a -f SIGS_UPDATE.INI Patches Included in The following patches have been incorporated into this release of Inventory: 3.2-INV INV-0002 Defects Fixed for IX LDISCAN REPORTS INCORRECT DATA (CMVC 32521) 2. X HARDWARE TABLES POPULATED WITH INACCURATE DATA. (CMVC 27591) 3. IX LDISCAN.EXE DOES NOT IDENTIFY NETWORK ADAPTER CARD. (CMVC 33698) These defects addressed wrong of inaccurate information in the configuration repository. 4. IX MEMORY USAGE WITH INV_PROF_METHOD. (CMVC 33401) The method ip_push leaked memory. The amount depended on the amount of software data returned. 5. IX THE CASE SENSITIVITY AND WILDCARDING IS INCONSISTENT. (CMVC 33620) TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 19

26 Defects Fixed for On the PC operating systems supported by TME 10, file and directory matching is not case sensitive. However software queries and software scan configuration options were all case sensitive. 6. IX MIF PARSE ERROR SCANNING NT MANAGED NODE. (CMVC 29790) On certain NT managed nodes, scans failed because ldiscan generated a MIF file that the target method, ip_discover, was unable to parse. 7. IX INVENTORY FAILURE TO PICK UP SERIAL NUMBERS. (CMVC 26722) LDISCAN did not report BIOS information or systems serial numbers for most PC hardware. 8. IX LAST ENTRY IN SEARCH DIRECTORIES SCROLLING WINDOWS CANNOT BE DELETED. (CMVC 33402) In the Customize Inventory Profile dialog, the last entry in the Search These Directories and Do Not Search These Directories panels could not be deleted. 9. IX NEED A WAY TO REMOVE NODES FROM REPOSITORY. (CMVC 25541) 10. IX REMOVE DATA FROM INVENTORY DB AFTER NODE IS REMOVED. (CMVC 32520) There was no way to remove data about a node from the configuration repository after it had been removed from a TMR. 11. IX SCAN SOFTWARE FILES SETTING CHANGED FOR PROFILE WHEN CLONED. (CMVC 33338) 20 Version 3.2.1

27 3.2.1 Software Defects, Limitations, and Workarounds Cloning an Inventory Profile did not preserve the settings of the source profile. 12. IX INVENTORY ENDPOINT SCRIPT NOT INTERPRETED CORRECTLY ON WIN95. (CMVC 40134) The batch file created for the custom script for Windows 95 targets was created with UNIX style end of line characters rather than DOS EOL characters. 13. Internal - new lines in MIF tables causes inserts and deletes in the database. (CMVC 41638) This is a significant fix to how inventory determines the differences between the results of subsequent scans when update with differences is selected. 14. Internal - scan of Netware Managed Site generated a sequence error. (CMVC internal - Tivoli software scanner failed with a GPF when run by hand using the example INI file. Tivsscan could not be run by hand until after a scan of that target has completed, which executed the software scanner. (CMVC 42349) Software Defects, Limitations, and Workarounds 1. Because mrmbios must run in 16 bit mode under Windows 95 and NT, the path to the executable cannot have any elements that violate the DOS 8.3 naming convention. Also the path leading to mrmbios.exe cannot be greater than 64 characters. This means that the path in which the PC Scanner Software is TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 21

28 Product Notes installed can only have 8.3 names and it cannot have more than 59 characters. Do not include the drive letter or a terminating \ separator when counting the number of character. (CMVC 37437) Ex: \tivoli\ can be counted as having 7 characters and not 8. Ex: D:\TIVOLI can also be counted as having 7 characters rather than Inventory scans will fail if the scan tries to retrieve a configuration file when the full path to that file is greater than 255 characters. (CMVC 43014) Product Notes Use of Wildcard in Software Scan Configuration In the Customize Inventory Profile dialog, standard PC or UNIX wildcarding does not apply when designating the directories to include or to exclude. In the Search These Directories list, wildcards do not work. Ex: /winnt/* is not valid. Ex: /winnt The scanner will scan /winnt on all drives, and all subdirectories of /winnt In Do Not Search These Directories list, wildcards can be used only as an ending character. 22 Version 3.2.1

29 Product Notes Ex: Using *foo does not match all directories ending in foo Ex: Using foo* excludes all directories beginning with foo. Updated Scripts All scripts in $BINDIR/TME/INVENTORY/SCRIPTS are replaced by the version of the scripts after Inventory has been upgraded to version The SQL scripts tivoli_*_schema.sql will create the Inventory Schema rather than the Inventory 3.2 schema. The inventory_queries.sh script will create the Inventory versions of the Queries. The SWSIGS.INI file is the complete list of signatures for Inventory and not Inventory 3.2. Upgrade Scripts Added by Inventory For the RDBMS portion, these are upgrade_to_321.sh, and *_sp3_patch.sql. The changes made by these scripts are detailed Configuration Repository section of the TME 10 Inventory Release Notes. For the queries, the upgrade script is inventory_queries_to_321.sh, which upgrades the Inventory 3.2 Queries to Inventory TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 23

30 Product Notes For the signatures, the upgrade file is SIGS_UPDATE.INI which is list of signatures that are new to Inventory from Inventory Version 3.2.1