IBM Support

OA46675: INCORRECT VERSION IDENTIFIED WHEN MULTIPLE VERSIONS THAT ARE THE SAME EXIST IN THE GKB.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a product that has multiple versions in the GKB and the
    modules are the same, the last version added to the GKB is
    always used in the identification.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IBM Tivoli Asset Discovery for z/OS      *
    *                 V8.1 customers.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Incorrect release identifications    *
    *                      for some products.                      *
    *                                                              *
    *                      2. Detailed module usage is lost on     *
    *                      module identification change.           *
    *                                                              *
    *                      3. Some products are not marked         *
    *                      deleted although they have no active    *
    *                      modules.                                *
    *                                                              *
    *                      4. For some scans, USS modules are      *
    *                      matched incorrectly as UNKNOWN.         *
    ****************************************************************
    * RECOMMENDATION: N/A                                          *
    ****************************************************************
    1. The Match Engine uses statistical sampling of module names
    and sizes to determine the best matching release. When module
    names and sizes do not change much between releases or when
    the sample size is small, there is not enough differentiation
    for the Match Engine to pick the correct release.
    
    2. Module usage is assigned to the module identification that is
    in effect at the time the module usage is processed. It is only
    adjusted later when the usage is attached to unidentified
    modules that are subsequently identified. This behavior is
    acceptable if the identification change is due to a recent
    upgrade, but could be incorrect if the identification change is
    due to GKB/LKB upgrades and corrections.
    
    3. During previous FULLREMATCH=N processing, libraries and
    products are not marked deleted since they may not be processed.
    However, libraries are processed if they have changed. If some
    modules are now identified to new products, the old products
    are still shown as active in these libraries even though they
    may no longer have any active modules.
    
    4. The IQ Import process assumes that all modules collected
    by the Inquisitor for z/OS UNIX are always sorted.
    

Problem conclusion

  • 1. For some products which do not change much between releases,
    the Inquisitor will now identify and store a specific product
    release for the product with a new Inquisitor identification
    record. This change will now correctly identify products with
    multiple identical versions of the same product.
    
    The Match Engine will take into account this new Inquisitor
    identification when finalizing matching outcomes.
    GKB scorecards that match Inquisitor identification records
    will be favored.
    
    Inquisitor identification will be displayed with messages in
    the Inquisitor Import job log.
    
    The Inquisitor identification will only take effect for recent
    scans performed with the latest maintenance levels of the
    Inquisitor. This only applies to products that the Inquisitor
    tries to identify.  In addition, the GKB maintenance level
    must also be up to date and contains scorecards of these
    Inquisitor identified releases for the Inquisitor
    identification to be chosen.
    
    Identification will be possible for products with a small
    number of modules when Inquisitor identification is provided
    for these products.
    
    2. Usage will now be assigned to the latest module
    identification and will be adjusted following each Inquisitor
    Import run. This identification will include any new vendor
    and product names. This adjustment can only take place if
    the following conditions apply:
    
    (a) The detailed usage is still active and has not been deleted
        either by usage deletion, or by previous re-identifications
        that preceded this maintenance.
    
    (b) IQ Import must be run with FULLREMATCH=Y to force all
        libraries to be processed. Otherwise, libraries that do
        not change and are therefore not processed under
        FULLREMATCH=N will not have their usage adjusted.
    
    (c) The Aggregator must be run at least once with
        COUNTUSAGEFULL=Y in effect to adjust all usage counts.
    
    The adjustment will take place over time as new IQ scans are
    done.
    
    The Usage Summary program has also been changed to generate
    unique module names.
    
    3. The Match Engine will now mark libraries that it will
    process as deleted even when FULLREMATCH=N is in effect.
    The Aggregator has also been modified to mark any products
    deleted when the libraries they reside in are marked deleted,
    or when no active modules belong to these products.
    
    It is still best to run the IQ Import with FULLREMATCH=Y to
    ensure all libraries are re-matched, particularly if the
    GKB or LKB has changed, or if IQ Imports are run infrequently
    on the same system.
    
    4. The IQ Import will now no longer assume that modules
    collected by the Inquisitor are sorted.
    
    
    HOLD ACTION follows:
    
    *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ***
    
    COMMENT
    (***************************************************************
     * FUNCTION AFFECTED: Tivoli Asset Discovery for z/OS          *
     ***************************************************************
     * DESCRIPTION      : Installation notes                       *
     ***************************************************************
     * TIMING           : POST-APPLY                               *
     ***************************************************************
     **************************************************************)
     This PTF must be applied before using GKB build
     '8.1.0 Tiv-TADZ-zOS-LV150331' or later.
     Failure to do so will result in corruption of data in the
     Repository.
     ***************************************************************
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA46675

  • Reported component name

    TIV ASSET DISC

  • Reported component ID

    5698B39TD

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-12-02

  • Closed date

    2015-03-04

  • Last modified date

    2015-04-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA76489

Modules/Macros

  •    HSICIQIM HSICTLAG HSICUSUM HSIPINQ
    

Fix information

  • Fixed component name

    TIV ASSET DISC

  • Fixed component ID

    5698B39TD

Applicable component levels

  • R810 PSY UA76489

       UP15/03/10 P F503

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBLR8","label":"Tivoli Asset Discovery for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"810","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
18 July 2023