Date:    June 17, 2002

Patch:  3.6.2-INV-0043

Component: Tivoli Inventory

General Description:  
  
  This patch fixes a variety of defects on Managed Nodes and TMA
  endpoints.  This patch depends on Framework 3.6.1, Inventory 3.6.2,
  and Inventory Patches 3.6.2-INV-0004,3.6.2-INV-0005, 3.6.2-INV-0022,
  3.6.2-INV-0030, 3.6.2-INV-0031, 3.6.2-INV-0033 and 3.6.2-INV-0040.


Problems Fixed:

     
     Internal CMVC Defect 128946
     Symptoms: The bios model data for machines with no specific model 
               information in SMBIOS is incorrectly identified as IBM 
               with a number appended.


     APAR IY25990
     Symptoms: Software Signatures cannot be loaded via the Web when 
               using DB2 V6.1 on OS/390 as the Inventory repository.
     Solution: This problem is related to the fact that DB2 6.1 on 
               OS/390 does not support the UCASE function in the ORDER
               BY clause.  In order to load the signatures via the 
               command line without using UCASE in the sql clause, the 
               new switch "-U" was added to the wfilesig command.  In 
               order to manage the indirect invokation of wfilesig 
               through the web interface, we look for the presence of 
               a flag file "dont_use_ucase" under the directory /tmp . 
         Note: If the TMR server is installed on a Windows platform, 
               then the flag file must be placed in the 
               <tmr_installation_drive>:\tmp directory.



     APAR IY27264
     Symptoms: An error message is reported on Windows systems when 
               using the wfilesig -a command to insert two signatures 
               with the same description. 
     Solution: The column SOFTWARE_ID is the primary key of the 
               SOFTWARE table.  This column is filled by the field 
               description coming from the wfilesig command or INI 
               file, so when trying to insert 2 entries with the same 
               description a unique contstraint violation occurs. So we
               added the -D flag to the wfilesig command which will 
               modify the SOFTWARE_ID value to include the field
               description with the version concatenated.
         Note: We recommend using the new -D flag only for signatures 
               you are loading with the same descriptions.


     APAR IY27864
     Symptoms: When scanning a Siemens Scenic XB 1219 using mrmbios,
               the attributes MANUFACTURER_ID, BIOS_MODEL and 
               BIOS_SER_NUM are not reported.


     APAR IY28752
     Symptoms: The BIOS_MODEL field contains the correct model number, 
               but it is also followed by several random characters 
               after the installation of Patch 3.6.2-INV-0038.


     APAR IY29119
     Symptoms: Scans of Netvista machines returns a 4-number model 
               (i.e. 6579) for the BIOS_MODEL attribute instead of 4 
               numbers plus 3 characters (i.e. 6579NBG).


     APAR IY31118
     Symptoms: The bios scanner fails to retrieve the bios serial 
               number and bios model from smbios compatible NCR brand 
               systems.


Architecture(s): Managed Node: Solaris 2, HP-UX 10, AIX 4, NT
                 Endpoint: NT, Win95/98, Solaris 2, HP-UX 10, AIX 4, 
                           Netware 3 & 4, OS/2
      
Managed Node Dependencies: 

   TME 10 Framework, Version 3.6.1
   TME 10 Inventory, Version 3.6.2
   Inventory Patch, 3.6.2-INV-0004
   Inventory Patch, 3.6.2-INV-0005
   Inventory Patch, 3.6.2-INV-0022
   Inventory Patch, 3.6.2-INV-0030
   Inventory Patch, 3.6.2-INV-0031
   Inventory Patch, 3.6.2-INV-0033
   Inventory Patch, 3.6.2-INV-0040

Gateway Dependencies:

   TME 10 Inventory Gateway, InventoryGW_3.6.2
   Inventory Gateway Patch, 3.6.2-INVGW-0004
   Inventory Gateway Patch, 3.6.2-INVGW-0005
   Inventory Gateway Patch, 3.6.2-INVGW-0022
   Inventory Gateway Patch, 3.6.2-INVGW-0030
   Inventory Gateway Patch, 3.6.2-INVGW-0031
   Inventory Gateway Patch, 3.6.2-INVGW-0033
   Inventory Gateway Patch, 3.6.2-INVGW-0040

Files Replaced or Added by this Patch:

  Managed Nodes:

  (for aix4-r1, hpux10, solaris2)
  
   bin/wfilesig
   TAS/HTTPd/cgi-bin/Inventory/t_wfilesig.cgi

  (for w32-ix86)

   bin/mrmbios.exe


  Gateways:

  (for all values of $INTERP)

   bin/w32-ix86/inv/SCANNER/mrmbios.exe
   bin/win95/inv/SCANNER/mrmbios.exe
   bin/os2-ix86/inv/SCANNER/mrmbios.exe


Patch Contents:

        - This README file
        - A cdrom image for this patch

Applying the Patch:

 1)  Extract the patch:

     On a Unix system:

     Extract the contents into a scratch directory.  For the purpose
     of this release note, assume that the symbol $PATCH points to
     this directory.

        # cd $PATCH
        # tar xvf 3.6.2-INV-0043.tar

     On a Windows NT system:

     Extract the contents into a scratch directory. For the purpose
     of this release note, assume that the symbol %PATCH% points to
     this directory.

        > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
        > X:
          ^-- 'X' is drive letter where %PATCH% is found
        > cd %PATCH%
        > tar xvf 3.6.2-INV-0043.tar

     NOTE:  If you are extracting the tar image on a Windows NT
     system, you will find an executable for tar in the TME
     installation on Windows NT under bin/w32-ix86/tools/tar.exe.

 2)  Follow these instructions for using Software Installation 
     Service (SIS).  If you do not wish to use SIS skip to the 
     next step.

     NOTE: SIS can install Tivoli products on any hardware platform
     supported by Tivoli, but there are some hardware platforms on
     which SIS cannot be run. Please check your SIS User's Manual
     for the list of platforms on which SIS can be run.

     NOTE: You must have the install_product and super
     authorization roles to successfully install this patch.

     a)  From the Tivoli Desktop, pull down
         Desktop --> Install --> Software Installation Service.
     b)  SIS will initialize, and bring up the Get Installation
         Password Dialog.  Enter your Installation Password.
     c)  Click the Install Button on the dialog which contains
         the Tivoli image.
     d)  Click the Select Product Button on the Install Spreadsheet
         Dialog.
     e)  Click the Import Product Button on the Select Product
         Dialog.
     f)  Locate the media to 3.6.2-INV-0043 using the file browser, 
         and select the PATCHES.LST file by double-clicking it.
     g)  Select 3.6.2-INV-0043 in the Import Product Dialog, and  
         click the Import Button.
     h)  When the import is complete, click the OK Button on the
         Global Progress Dialog.
     i)  Select 3.6.2-INV-0043 in the Select Product Dialog, if 
         it is not already selected, and click the OK Button.
     j)  Now click the Select Machine Button on the Install
         Spreadsheet Dialog.
     k)  Select the machine(s) you would like to install 
         3.6.2-INV-0043 to, and click the OK Button.
     l)  Click the appropriate cell(s) in the Install Spreadsheet
         Dialog. (NOTE: This should yield an "X" in the cell(s)
         for the machines you want to install 3.6.2-INV-0043 to).
     m)  Click the Install Button.
     n)  Select the install algorithm you want to use on the
         Installation Algorithm Dialog, and click OK.
     o)  SIS will perform the installation(s) you designated
         in the Install Spreadsheet Dialog.
     p)  Installation is complete. Check the additional
         installation instructions section below.
     q)  Repeat for Gateway component 3.6.2-INVGW-0043.

 3)  Use the following steps to install the patch using the old
     Tivoli install mechanism.
     NOTE: You must have the install_product and super
     authorization roles to successfully install this patch.

     a)  Select the "Install -> Install Patch..." option from the
         "Desktop" menu to display the "Install Patch" dialog.
     b)  Press the "Select Media..." button to display the "File
         Browser" dialog.
     c)  Enter the path to the directory containing the patch, 
         $PATCH, in the "Path Name:" field.
     d)  Press the "Set Media & Close" button to return to the 
         "Install Patch" dialog.
     e)  The patch install list now contains the name of the 
         patch.  Select the patch by clicking on it.
     f)  Select the clients to install this patch on.
     g)  Press the "Install" button to install the patch.

 4) To install the patch on PC Managed Nodes you must install the
    patch as a product.

    To install the new PC scanning program:

    a)  Select the "Install -> Install Product..." option from the
       "Desktop" menu to display the "Install Product" dialog.
    b)  Press the "Select Media..." button to display the 
        "File Browser" dialog.
    c)  Enter the path to the directory containing the patch, 
        $PATCH, in the "Path Name:" field.
    d)  Press the "Set Media & Close" button to return to the 
        "Install Product" dialog.
    e)  The product install list now contains the name of the 
        product, Tivoli Inventory PC Scanning Program Patch 
        3.6.2-INV-0043.  Select the product by clicking on it.
        All PC managed nodes and NetWare managed sites will be 
        displayed in the "Clients to Install On" and "Available 
        Clients" lists.  Also, a dialog will be displayed prompting 
        for a path for the location of where the scanning program 
        is to be installed.
        (YOU MUST INSTALL TO THE SAME DIRECTORY WHERE THE ORIGINAL
        SCAN PACKAGE WAS INSTALLED)
    f)  Fill in the path to the location for the scanning program 
        and click on "Set".  (The prompting dialog is dismissed 
        at this point.)
    g)  Select the machines to receive the new scanning programs.
        All PC managed nodes that are Windows NT
        and NetWare managed sites, should be re-installed
        with new scanning programs.
    h)  Press the "Install & Close" button to install the patch.


Additional Installation Instructions (General):

  After installing any Tivoli patch it is recommended that you reexec
  the oservs on your TMR Server and managed nodes by running the 
  following commands on your TMR Server:

    odadmin shutdown clients
    odadmin reexec 1
    odadmin start clients


Known Issues: 

  None.