IBM Support

IV98715: SHALLOW DISCOVERY OF VIRTUAL CENTER CAUSES RECONCILIATION PLUGINNOT TO RUN AND CS NAME AND OS LMT ARE UPDATED.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When using Shallow VM discovery(shallowVMdiscovery=true) with
    Virtual Center Sensor the reconciliation plugin does not run.
    This causes the CS name to be overwritten by the Virtual Center
    sensor and the LMT on the OS to update.
    
    There was issue while merging of Operating System and Computer
    System when VMID is false which is the
    case of shallow discovery. Merging issue was occurring while
    doing reconciliation and caused by the plugin not firing when
    shallow VM discovery is true.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * TADDM User                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using Shallow VM discovery (shallowVMdiscovery=true)    *
    * with Virtual Center Sensor, the reconciliation plugin does   *
    * not run.                                                     *
    * This causes the CS name to be overwritten by the Virtual     *
    * Center sensor and the LMT on the OS to update.               *
    *                                                              *
    * There was issue while merging of Operating System and        *
    * Computer System when shallowVMdiscovery=true. We were not    *
    * setting the VMID in case of shallowVMdiscovery=true which    *
    * was causing the issue.                                       *
    *                                                              *
    * In new implementation we are setting the VMID irrespective   *
    * of shallowVMdiscovery.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages:
    | Fix Pack | 7.3.0-TIV-ITADDM-FP0004
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV98715

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2017-10-09

  • Last modified date

    2017-10-09

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

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

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

  • R730 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
09 October 2017