Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Feb 2, 2017

To have a easy way to know which targets in scope were unreachable during the discovery

In our environment we usually run discoveries on big scopes. It could happen that some targets included in the scope were unreachable through ping. We are looking for a simple way to have a list of scoped targets, for each of them having the simple information if during the discovery it was possible to ping it or not.

After involving TADDM support on this request, we were informed that there is not any simple way for that. The information about ping failures is only traced in ping sensor log files, but anyway it is not possible to explore them in a simple way, considering that most discoveries include anchors and the ping logs are present both on TADDM DS and on any single anchor (eventually chained).

Idea priority Urgent
RFE ID 100439
RFE Product Tivoli Application Dependency Discovery Mgmt (TADDM)
  • Guest
    Apr 16, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Operations Management
    Product - Tivoli Application Dependency Discovery Mgmt (TADDM)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Operations
    Product - Tivoli Application Dependency Discovery Mgmt (TADDM)

  • Guest
    Feb 3, 2017

    You could base a report on differences between on differences between BB_COMPUTERSYSTEM40_V and BB_OPERATINGSYSTEM62_V.

    Whenever a Ping discovery is run, BB_COMPUTERSYSTER40_V receives an update when the DNS entry still exists, but as long as the OSSensor is not run, the lastmod date of BB_OPERATINGSYSTEM62_V is not updated.

    We use this to identify login problems, but it could work for your purpose as well, assuming you're using L2 discovery. Good luck!

    ps. I'm not an IBM employee or representative :)

    The query:
    from cmdb.bb_operatingsystem62_v A1
    join cmdb.BB_COMPUTERSYSTEM40_V A2 on a1.PK_C = A2.PK__OSRUNNING_C
    -- Time difference between system update and os update is more than 2 days:
    A1.osconfidence_c = 100
    -- where not interested in systems that haven't been seen at all for 21 days.
    A2.LASTMODIFIEDTIME_C >= (((TRUNC(sys_extract_utc(SYSTIMESTAMP),'MI') - to_date('01-JAN-1970','DD-MON-YYYY')) * (86400) * (1000)) - (21*3600*24*1000))