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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
DB2 sensor executes db2find.sh during discovery that uses list db directory command to find out the Databases. This command lists the contents of the system database directory. In the command output there is a "Directory entry type" showing the location of the database; Remote, Indirect, Home and LDAP. However, TADDM does not fully consider these values and therefore shows all database directory entries as potential found databases on respective server under a DB2 instance record.
As we use LDAP to store our data sources on a global level, ywe have many entries with "Directory entry type" = LDAP. We expect that TADDM does only consider the entries with Directory entry type = Remote or Home. Also there some additional logic must be provided by TADDM, to find out the real database hosted on a given server as the database directory might show various aliases for a single database.
Do not place IBM confidential, company confidential, or personal information into any field.