tme 10 inventory release notes version 3.2.1 july...

TME 10 Inventory Release Notes

Version 3.2.1

July 16, 1998

TME Inventory Version 3.2.1 Release Notes (July 9, 1998)Copyright NoticeCopyright © 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 orAddendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication maybe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, orotherwise, without prior written permission of Tivoli Systems. The document is not intended forproduction and is furnished “as is” without warranty of any kind.All warranties on this document arehereby 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 ordisclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe 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 ofMicrosoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively throughX/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 orservicemarks of others.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply thatthey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theseproducts, 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 otherlegally protectable right, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunctionwith other products, except those expressly designated by Tivoli Systems or IBM, are the responsibilityof the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue,Thornwood, New York 10594.

TME 10 Inventory 3.2 Maintenance Release 1 Release Notes i

TME 10 InventoryRelease 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 3.2.1 and the Inventory

PC Scanning Program 3.2.1............................................................... 10

From the Desktop...................................................................... 10

From the Command Line Interface (CLI)................................. 11

Upgrading the Configuration Repository .......................................... 12

Preparing to Run the Configuration Repository Upgrade. ....... 13

Running the Upgrade Script ..................................................... 15

Upgrading the Inventory Queries from Inventory 3.2. ............. 18

Upgrading the Software Signatures. ......................................... 18

Patches Included in 3.2.1............................................................................ 19

Defects Fixed for 3.2.1........................................................................................ 19

3.2.1 Software Defects, Limitations, and Workarounds..................................... 21

ii Version 3.2.1

Product Notes....................................................................................................... 22

Use of Wildcard in Software Scan Configuration ..................... 22

Updated Scripts.......................................................................... 23

Upgrade Scripts Added by Inventory 3.2.1. .............................. 23

TME 10 Inventory 3.2 Maintenance Release 1 Release Notes 1

1Release Notes

This Release Notes document provides important information aboutInventory 3.2.1. These notes are the most current information for theproduct and take precedence over all other documentation.

Please review these notes thoroughly before installing or using thisproduct.

These release notes include the following topics:

■ New Features

■ System Requirements

■ Installation Notes

■ Patches Included in 3.2.1

■ Defects Fixed for 3.2.1

■ 3.2.1 Software Defects, Limitations, and Workarounds

■ Product Notes

New Features

The Configuration Repository

The schema for the configuration repository has been changed forInventory 3.2.1. The Inventory 3.2.1 configuration repositoryincludes several new tables and views. All tables and views, with thecolumns included in each, are listed in Appendix C, “ConfigurationRepository” in theTME 10 Inventory User’s Guide. The followingtables and columns are new in the configuration repository schemafor Inventory 3.6. An asterisk denotes columns in the primary key (* ).The following tables and their associated columns have been addedto the configuration repository:

New Features

2 Version 3.2.1

Policy Region Tables

The policy region tables listed below were added to allow you toperform 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 aboutthe BIOS (Basic Input/Output System) chip on each client orendpoint that is scanned.

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 withthe 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 followingcolumns are now part of the primary key:

• SOFTWARE_COMPONENT_NAME

• SOFTWARE_COMPONENT_VERSION

New Features

4 Version 3.2.1

■ In the INSTALLED_OS_DETAILS table, the length of theDESCRIPTION column was changed from 32 characters to 64characters.

■ In the following tables, the length of theCONFIG_CHANGE_TYPE column has been changed from 32characters to 12 characters:

• INSTALLED_OS_DETAILS

• INSTALLED_PRINTER

• INSTALLED_RWOPTICAL_DRIVE

■ In the table NETWORK_CARD, the length of the columnNETWORK_CARD_MODEL has changed from 32 charactersto 64.

■ The view INSTALLED_OS_DET_VIEW has been added.

■ The query INVENTORY_OS_DETAILS uses the viewINSTALLED_OS_DET_VIEW.

New Features


■ The view PC_BIOS_VIEW now includes the followingcolumns:

• 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, theNW_SERIAL_NUMBER column (12 characters, null) hasbeen added.

New Features

6 Version 3.2.1

■ The table PROCESSOR has the following new columns. All ofthe columns that are one character in length and have either a Yor 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 columnsadded to the PROCESSOR table described above.

BIOS Scanner

The PC Scanning Software for Inventory 3.2.1 includes a BIOSscanner, which can identify a predefined set of manufacturers andmodels. Entries can also be added to the bios scanner dictionary fileso that it will identify additional systems. The BIOS scanner, named

New Features


mrmbios, runs whenever a hardware scan of a PC is executed. It findsthe BIOS identification string of the PC and returns it in aManagement Information Format (MIF) file. It also returns the modeland manufacturer of the PC if the BIOS id is in the dictionary file onthat PC. To update the dictionary file for any unknown PCs, completethe following steps:

1. Tivoli recommends keeping a TMR wide copy of the dictionaryfile, bios.ini, in a central location from which the file can bedistributed to all PcManagedNodes.

2. Check for PCs that return UNKNOWN for manufacturer andmodel in the scan results. To do this follow these steps:

a. Query the INSTALLED_BIOS table or thePC_BIOS_VIEW view.

b. Look for the value UNKNOWN in the BIOS_MODELcolumn.

c. Use the HARDWARE_SYSTEM_ID from thePC_BIOS_VIEW, to find which PC this is by looking in theCOMPUTER_SYSTEM table.

3. Update the dictionary file, bios.ini, on the unrecognized PC byrunning themrmbios command so that it will prompt the userto enter the Manufacturer Name and the Manaufacturer Modelby running the following command:

mrmbios -d bios.ini -a

4. Merge this new bios.ini file with the TMR wide copy of the fileusing a text editor or script.

5. Distribute the file to all PC managed nodes. There should beonly 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. ForUNIX, case sensitivity depends on the scanning option, as describedin the following list:

New Features

8 Version 3.2.1

■ 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 viewssuch as INSTALLED_SOFTWARE_VIEW andINSTALL_PC_SOFTWARE_VIEW. The scanner does allother matching.

New Inventory Hardware Scanner

Inventory uses TIVHSCAN, a scanner designed and maintained byTivoli, to scan the hardware on all PC targets except Windows 3.xmachines. On Windows 3.x, Inventory 3.2.1 still uses the Intelscanner 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 3.2.1.

■ RIM Logging - Lists the SQL commands equivalent to whatInventory generates when inserting data into the RDBMS

■ Progress Logging - Lists the current stage of a scan.

■ Debug Log - Lists minimal debug information that you shouldprovide to Tivoli Support

To activate logging, use the new-l flag for thewsetiprf command.See the Inventory User’s Guide or the man page for more informationabout using thewsetiprf command. You should use the -l argument

System Requirements


to activate logging. The following options are available for thisargument:

■ RIM - RIM logging only, generates a file calledInventory_RIM_log in /tmp or on NT %DBDIR%/tmp

■ PROGRESS - Progress logging only, generates the log fileInventory_Progress_log in /tmp or on NT %DBDIR%/tmp

■ ALL - turns on RIM and Progress logging, in addition to theDebug log, which is Inventory_Debug_log

■ NORMAL - sets logging back to normal inventory logging,which means writing to notice groups.

System RequirementsThe 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 TME10 Inventory Version 3.2 Release Notes.

Installation NotesThis section summarizes the procedure, including prerequisite steps,for installing Inventory. This section also documents changes thathave developed since theTME 10 Inventory User’s Guide waspublished.

PrerequisitesInventory 3.2 must be installed before Inventory 3.2.1 can beinstalled.

Uninstalling or Reinstalling InventoryPlease contact Tivoli Customer Support for information onuninstalling Inventory 3.2.1.

Installation Notes

10 Version 3.2.1

InstallationThe ManagedNode code for Inventory 3.2.1 is installed as a patch toInventory 3.2. The new scan software for PC managed nodes areinstalled as a product, and should be installed over the existingInventory 3.2 scan software. For additional information on installingpatches and products in Tivoli, please refer to the application’s user’sguide, and the Framework User’s Guide, the Framework Planningand Installation Guide.

Installing Inventory 3.2.1 and the Inventory PC ScanningProgram 3.2.1

1. 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 thecommand line interface.

From the Desktop

Install Inventory 3.2.1.

1. Select Install Patch.

2. Choose Select Media, and set the path to where the CDROM ismounted.

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 thathave 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 ismounted.

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 previousrelease has been installed on a PC , the TME 10 InventoryPC Scanning Program, Version 3.2.1 must be installed inthe same location over the previous Inventory PCScanning Program. Otherwise Inventory will try to runthe software in the original location.

From the Command Line Interface (CLI)

Install Inventory 3.2.1

Use thewpatch command. See the TME 10 Framework ReferenceManual, Version 3.2 for documentation on the command wpatch.

Example:wpatch -c /cdrom -i INV_321 alien happybabel elvis sleepy

This is an exmaple of the wpatch command with the minimumoptions to install Inventory 3.2.1. 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 ofmanaged node Targets on which Inventory 3.2.1 is to beinstalled.

To install the Inventory PC Scanning Program 3.2.1 use thewinstallcommand. See the TME 10 Framework Reference Manual, Version3.2 for documentation on the commandwinstall.

Installation Notes

12 Version 3.2.1

Example:winstall -c /cdrom -i SCAN winntpc1winntpc2 winntpc3 george

This is an example of the winstall command with the minimumoptions to install Inventory PC Scanning Program 3.2.1. The flags areas 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 ofPC managed node Targets on which Inventory 3.2.1 is to beinstalled.

Upgrading the Configuration Repository

To upgrade the Inventory 3.2 Configuration Repository to Inventory3.2.1, some preliminary tasks must be completed. The primary stepin upgrading the Configuration Repository is executing the upgradescript,upgrade_to_321.sh. This script needs to be executed on theRIM host, or a machine that has access to all the necessary scripts andto the RDBMS Vendor's client software. These directions are writtenfor running the upgrade on the RIM host. If the upgrade process is notrun on the RIM host the required scripts must be copied to themachine on which the upgrade will be run. Otherwise the followingrequirements apply.

CAUTION: The configuration repository should be backed upbefore running the upgrade_to_321.sh script. Consult thedatabase administrator or the user’s guide for the RDBMS formore information about database back ups.

All RDBMS-related messages generated while the script executes arestored in output log files in the directory from which the script wasexecuted. The log file has the same name as the related script, except

Installation Notes


that the extension for the log file is.log. For example, the scriptora_sp3_patch.sqlgenerates the log fileora_sp3_patch.log.

Preparing to Run the Configuration Repository Upgrade.

Before Running the Upgrade Script the following tasks need to becompleted:

1. Install the Inventory 3.2.1 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 clientinstance owner.

3. Verify the values of the following environment variablesspecific to your RDBMS:

■ MS SQL

Ensure that the path to isql is set in the environment from whichthe upgrade script is to be run.

■ DB2

• If a db2profile script does not reside in the instance owner’shome directory that contains the settings for theDB2INSTANCE environment variable, setDB2INSTANCE to the login name of the instance owner.

• Ensure that the path to DB2 is set in the environment fromwhich the upgrade script is to be run.

Installation Notes

14 Version 3.2.1

■ Oracle

• Set the environment variable ORACLE_HOME to thedirectory where the Oracle RDBMS client or serversoftware is installed. This should correspond to the RIMvalue of DATABASE_HOME.

• If the RIM host is a different machine from the RDBMSserver, 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 fromwhich the upgrade script is to be run.

■ Sybase

• Set the SYBASE environment variable as the path to thedirectory where the Sybase RDBMS client or serversoftware is installed. This should correspond to the RIMvalue of DATABASE_HOME.

• Set the DSQUERY environment variable as identifier thatthe client uses to extract connection information from theinterfaces file. This should correspond to the RIM value ofSERVER_ID

• Ensure that the path to isql is set in the environment fromwhich the upgrade script is to be run.

4. Make sure the following scripts, as appropriate for yourRDBMS , are in the$BINDIR/TME/INVENTORY/SCRIPTS/RDBMS directoryon the RIM host, including the upgrade_to_321.sh script:

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

Theupgrade_to_321.sh script must drop some tables from theConfiguration repository. It copies the contents of these tables totemporary tables before dropping them. The following tables fromthe Inventory 3.2 configuration repository are copied to temporarytables during the upgrade:

■ INSTALLED_OS_DETAILS

■ INSTALLED_PRINTER

■ NETWORK_CARD

■ INSTALLED_RWOPTICAL_DRIVE

■ PC_DEVICE_DRIVER

■ SOFTWARE_SIGNATURE_FILE

Installation Notes

16 Version 3.2.1

In addition, the script backs up the software signature information inthe SOFTWARE_SIGNATURE_FILE table.

WARNING: Make sure that there is sufficient free space in theRDBMS for copies of these tables, otherwise the upgrade of theSchema will fail. Make sure that there is enough free space for tohold a complete copy of the tables listed above. In general 20 to30MB of space should be enough. Also, make a backup of theConfiguration Repository before running the upgrade script.

For DB2, a connection to the DB2 database must be created beforerunning the script. Issue the following command at the commandline:

db2 connect to database_name user user_nameusing 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, andcolumns that are required for Inventory 3.2.1. This script calls theother scripts that are specific to your RDBMS. Enter the following atthe command line for your RDBMS server to run the script:

Installation Notes


■ For UNIX: upgrade_to_321.sh RDBMS_vendoruser_name password

■ For NT: sh upgrade_to_321.sh RDBMS_vendoruser_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 configurationrepository.

■ password

Specifies the password for owner of the configuration repository

Example:sh upgrade_to_321.sh Oracle tivolitivoli

This would upgrade the Schema on Oracle, where the Inventory useris tivoli and its password istivoli .

Note: Before you run a script on a DB2 database, you must createa connection to that database. See step 5.3.1

Optionally a new Inventory Schema could be created instead. Afterinstalling Inventory 3.2.1, the scripts, tivoli_*_schema.sql, in

Installation Notes

18 Version 3.2.1

$BINDIR/TME/INVENTORY/SCRIPTS/RDBMS are replacedby the Inventory 3.2.1 upgrade. So these SQL scripts create thecomplete 3.2.1 schema. The process of running these scripts is thesame as in Inventory 3.2, and is documented in the Inventory 3.2User’s Guide.

Upgrading the Inventory Queries from Inventory 3.2.

WARNING - running this script will delete any of the queriescreated by the 3.2 version of the inventory_queries.sh script thatare 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 3.2.1 and recreatethem with the settings for Inventory 3.2.1.

If the 3.2 Inventory queries were never created, then just run thescript inventory_queries.sh from a managed node on whichInventory 3.2.1 has been installed, as this script will create all of the3.2.1 queries. When Inventory 3.2.1 is installed, it over-writes the 3.2version of the script with the 3.2.1 version.

Upgrading the Software Signatures.

The file,SIGS_UPDATE.INI , contains all the signatures that havebeen added to Inventory 3.2.1. The upgrade process just adds the newsignatures.

Defects Fixed for 3.2.1


From the directory containing the signature files,$BINDIR/TME/INVENTORY/SCRIPTS/SIGNATURES run thefollowing command on a managed node that has Inventory 3.2.1.

■ wfilesig -a -f SIGS_UPDATE.INI

Patches Included in 3.2.1The following patches have been incorporated into this release ofInventory:

Defects Fixed for 3.2.11. IX73654 - LDISCAN REPORTS INCORRECT DATA (CMVC

32521)

2. X70300 - HARDWARE TABLES POPULATED WITHINACCURATE DATA. (CMVC 27591)

3. IX74362 - LDISCAN.EXE DOES NOT IDENTIFYNETWORK ADAPTER CARD. (CMVC 33698)

These defects addressed wrong of inaccurate information in theconfiguration repository.

4. IX74133 - MEMORY USAGE WITH INV_PROF_METHOD.(CMVC 33401)

The method ip_push leaked memory. The amount depended on theamount of software data returned.

5. IX74275 - THE CASE SENSITIVITY AND WILDCARDINGIS INCONSISTENT. (CMVC 33620)

3.2-INV-0001 3.2-INV-0002

Defects Fixed for 3.2.1

20 Version 3.2.1

On the PC operating systems supported by TME 10, file and directorymatching is not case sensitive. However software queries andsoftware scan configuration options were all case sensitive.

6. IX71762 - MIF PARSE ERROR SCANNING NT MANAGEDNODE. (CMVC 29790)

On certain NT managed nodes, scans failed because ldiscangenerated a MIF file that the target method, ip_discover, was unableto parse.

7. IX69995 - INVENTORY FAILURE TO PICK UP SERIALNUMBERS. (CMVC 26722)

LDISCAN did not report BIOS information or systems serialnumbers for most PC hardware.

8. IX74161 - LAST ENTRY IN SEARCH DIRECTORIESSCROLLING WINDOWS CANNOT BE DELETED. (CMVC33402)

In the Customize Inventory Profile dialog, the last entry in the SearchThese Directories and Do Not Search These Directories panels couldnot be deleted.

9. IX69425 - NEED A WAY TO REMOVE NODES FROMREPOSITORY. (CMVC 25541)

10. IX73627 - REMOVE DATA FROM INVENTORY DB AFTERNODE IS REMOVED. (CMVC 32520)

There was no way to remove data about a node from the configurationrepository after it had been removed from a TMR.

11. IX74121 - SCAN SOFTWARE FILES SETTING CHANGEDFOR PROFILE WHEN CLONED. (CMVC 33338)

3.2.1 Software Defects, Limitations, and Workarounds


Cloning an Inventory Profile did not preserve the settings of thesource profile.

12. IX78472 - INVENTORY ENDPOINT SCRIPT NOTINTERPRETED CORRECTLY ON WIN95. (CMVC 40134)

The batch file created for the custom script for Windows 95 targetswas created with UNIX style end of line characters rather than DOSEOL characters.

13. Internal - new lines in MIF tables causes inserts and deletes inthe database. (CMVC 41638)

This is a significant fix to how inventory determines the differencesbetween the results of subsequent scans when update with differencesis selected.

14. Internal - scan of Netware Managed Site generated a sequenceerror. (CMVC 42162

15. internal - Tivoli software scanner failed with a GPF when run byhand using the example INI file. Tivsscan could not be run byhand until after a scan of that target has completed, whichexecuted the software scanner. (CMVC 42349)

3.2.1 Software Defects, Limitations, andWorkarounds

1. Because mrmbios must run in 16 bit mode under Windows 95and NT, the path to the executable cannot have any elementsthat violate the DOS 8.3 naming convention. Also the pathleading to mrmbios.exe cannot be greater than 64 characters.This means that the path in which the PC Scanner Software is

Product Notes

22 Version 3.2.1

installed can only have 8.3 names and it cannot have more than59 characters. Do not include the drive letter or a terminating \separator when counting the number of character . (CMVC37437)

Ex: \tivoli\ can be counted as having 7 characters and not 8.

Ex: D:\TIVOLI can also be counted as having 7 charactersrather than 9.

2. Inventory scans will fail if the scan tries to retrieve aconfiguration file when the full path to that file is greater than255 characters. (CMVC 43014)

Product Notes

Use of Wildcard in Software Scan Configuration

In the Customize Inventory Profile dialog, standard PC or UNIXwildcarding does not apply when designating the directories toinclude 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 allsubdirectories of /winnt

■ In Do Not Search These Directories list, wildcards can be usedonly as an ending character.

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 arereplaced by the 3.2.1 version of the scripts after Inventory has beenupgraded to version 3.2.1.

The SQL scriptstivoli_*_schema.sql will create the Inventory 3.2.1Schema rather than the Inventory 3.2 schema.

The inventory_queries.sh script will create the Inventory 3.2.1versions of the Queries.

TheSWSIGS.INI file is the complete list of signatures for Inventory3.2.1 and not Inventory 3.2.

Upgrade Scripts Added by Inventory 3.2.1.

For the RDBMS portion, these areupgrade_to_321.sh, and*_sp3_patch.sql. The changes made by these scripts are detailedConfiguration Repository section of the TME 10 Inventory 3.2.1Release Notes.

For the queries, the upgrade script isinventory_queries_to_321.sh,which upgrades the Inventory 3.2 Queries to Inventory 3.2.1.

Product Notes

24 Version 3.2.1

For the signatures, the upgrade file isSIGS_UPDATE.INI which islist of signatures that are new to Inventory 3.2.1 from Inventory 3.2.

tme 10 inventory release notes version 3.2.1 july...

Documents