IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Documentation problems and corrections contained in this fix pack

User’s Guide for Inventory

This section contains new and updated information for IBM Tivoli Configuration Manager User’s Guide for Inventory:

APAR IZ50799
In Chapter 3. Working with Inventory profiles in the "Software scan configuration options" section subsection "Scan Options" replace the current text:

Signature data includes the name, size, and usually the quick checksum value of the file used to identify the software product.

with the following text:

Signature data includes the name and the size of the file used to identify the software product.

APAR IZ50799
In Chapter 5. Collecting custom information with Inventory in the "Using signatures" section replace the current text:

Signature data includes the name, size, and usually the Quick checksum value of the file used to identify the software product.

with the following text:

Signature data includes the name and the size of the file used to identify the software product.

APAR IZ50799
In Appendix B. Commands in the "winvsig" section replace the current description for the -a command option with the following text:

Adds one or more signatures to the configuration repository, and modifies existing signatures. Each signature must have a unique file name and size. If the specified signature already exists, the information for the existing signature (for example, the description or version) is modified.

APAR IZ50799
In Appendix B. Commands in the "winvsig" section replace the current description for the -f command option with the following text:

Specifies the name of a file that contains the data for one or more signatures. The signature data in the file must be in the following format:

<I>,name,size,description,version

The signature file supports also the XML file format.

APAR IZ53312
At the end of Appendix E. Installing and uninstalling Common Inventory Technology (CIT) add the following new section:

Setting the CIT processes priority on Windows

On Windows platforms, you can specify locally on each endpoint the priority for the different CIT processes by editing the cit.properties file and adding for example the following priorities:

fscanner.changepriority=low
swscanner.changepriority=low
hwscanner.changepriority=low
vpdscanner.changepriority=low
If you want to add the priority settings directly to the CIT_win.spb package used to install CIT, perform the following steps:
  1. Get the CIT_win.spb package from a gateway. The package is located under the ..bin/lcf_bundle.41100/lib/w32-ix86/inv/CIT/SPB directory.
  2. Using the Software Package Editor disconnected command line, unbuild the CIT_win.spb package by running the command:
    wdubldsp.exe
    The command extracts a software package (.sp file) and the CIT files.
  3. Edit the unpacked cit.properties file and add, at the bottom of the file, the following lines:
    fscanner.changepriority=low
    swscanner.changepriority=low
    hwscanner.changepriority=low
    vpdscanner.changepriority=low
    Save the file.
  4. Build the CIT_win.spb again by running the command:
    wdbldspb.exe
    The new CIT_win.spb now includes the new cit.properties file with the priority settings you set.
  5. Save the original CIT_win.spb on the gateways and store the new CIT_win.spb under the same directory.
  6. During the next CIT installations, on the endpoints, are automatically included the CIT priority settings contained in the cit.properties file.
APAR IZ53836
In Appendix B. Commands in the "wqueryinv" section add the following note:

Note:
When using a Tivoli query containing views sharing the same TME_OBJECT_ID field and running the wqueryinv command against that query, the command fails with a parse error due to an ambiguous column reference. For example, if you are using an Oracle database the error message displayed is the following:
ORA-00918: column ambiguously defined
You can run the command only with Tivoli queries where only one table and view have the TME_OBJECT_ID field.

Database Schema Reference

This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:

Feature MR0808085933
Feature 235414
In Chapter 2. History tracking in section "Modifying history tracking for efficiency" replace the first bullet of the section with the following text:

APAR IZ48308
In Chapter 3. Configuration repository views in section "PHYSICAL_PROCESSOR_VIEW" add the following columns to the current table:
Table 81.
Column Name Description
MANUFACTURER Processor manufacturer. Examples: Intel, AMD, IBM, SUN, HP. If the manufacturer is not recognized (is not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown".
FAMILY Processor family. Examples: Pentium 4, Xeon, Athlon 64, POWER5, UltraSparc-T1, PA-RISC. If the family is not recognized (not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown".
TYPE Processor type. Examples: 170 for AMD Opteron 150, 670 for Intel Pentium 4 670. If Common Inventory Technology does not support type identification for the family of processors then this field has value of an empty string. If Common Inventory Technology supports type identification for the family of processors but the type of processor is not recognized then this field has value of "Unknown".
CPU_FREQ Processor frequency in MHz. This field is optional and vendor-specific. Depending on the processor family it might be nominal or current CPU frequency. CPU frequency might be interpreted differently across processor architectures and families. If not valid this field is 0.
L2_CACHE_SIZE Size of L2 cache in Kilobytes. This field is optional, 0 if not valid.
L3_CACHE_SIZE Size of L3 cache in Kilobytes. This field is optional, 0 if not valid or there is no L3 cache.
SIGNATURE Processor signature. This field is optional and platform- and vendor-specific. The value of this field might be taken from different sources on each platform and even for different processor families. If available this is processor model identifier as reported by CPUID instruction, BIOS or OS. This field is for internal Common Inventory Technology purposes only, the exploiter should make no assumption on contents nor format of this field.
APAR IZ51439
In Chapter 3. Configuration repository views, in the "NET_CARD_VIEW" section modify the following information:

APAR IZ53642
In Chapter 3. Configuration repository views, in the "PRINTER_VIEW" section replace the current description for the PRINTER_IS_LOCAL column with the following description:

If the printer is a local printer or a network printer, and is the default printer or not. This column can have one of the following values:

Y
The printer is not the default printer and is local.
N
The printer is not the default printer and is not local.
Z
The printer is the default printer and is local.
O
The printer is the default printer and is not local.

Patch Management Guide

This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:

Defect 65768
In Chapter 2. Installing the automated patch management solution, section "Installing the Patch Management component", subsection "Before you begin", in the "Files to download" table replace the current Web site for the WUA download with the following Web site:

http://download.windowsupdate.com/v6/windowsupdate/redist/standalone/WindowsUpdateAgent20-x86.exe

APAR IZ41238
In Chapter 7. Troubleshooting, section "Problems with the Tivoli Configuration Manager Automation Server silent installation", subsection named "Checks run during installation" replace the current step 4 of the procedure:

Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files and that Windows Instrumentation Service is not running to prevent the failure of the MQ Series component .

with the following text:

Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files.

APAR IZ41238
In Chapter 2. Installing the automated patch management solution, section "Installing and configuring Cygwin" add at the end of the current step 4 the following text:

The new output of the mount -m command will be:

mount -f -s -b "C:/cygwin/bin" "/usr/bin" mount -f -s -b
"C:/cygwin/lib" "/usr/lib" mount -f -s -b "C:/cygwin" "/"
APAR IZ41238
In Chapter 2. Installing the automated patch management solution, section "Installing and configuring Cygwin" add at the end of the current section the following new steps:

Reference Manual for Software Distribution

This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:

APAR IZ53412
In Chapter 1. Editing the Software Package Definition File, section "Structure of the SPD File" before the paragraph:

The sections where these stanzas are described show the structure in which you should define each stanza and provide examples.

add the following paragraph:

At installation time, the installation of a software package starts only if, during the check of the conditions specified in all software package stanzas, all these conditions are verified.

APAR IZ57893
In Chapter 1. Editing the Software Package Definition File, section "Attributes in the File System Stanzas" table "SPD File attributes in file system stanzas" in the row for the descend_dirs attribute:

add the following note:

Note: If you set this attribute to y when creating on UNIX platforms software packages, to which a directory is added containing backward slashes, performing the winstsp command on the software package fails. To successfully install the software package on UNIX platforms, do not add to the package a directory containing backward slashes.


[ Top of Page | Previous Page | Next Page | Contents ]