Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

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.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Components Monitoring
Created by Guest
Created on Jun 8, 2015

DBM parameter just for DB2diag file

Currently we have db2diag files as part of dbm parameter (DIAGPATH) and all the files (db2diag.log, events,nfy,bin,stack,stmm,dump) going into the same directory. The challenge is in case of issues, we see huge dump files produced (sometimes 40gb dump files) and fill up diagpath. Any information on the error or the reason of the dump file gets lost since db2diag is unable to write (file system got full becuase of the 40gb dump file).

Request is to seperate out db2diag logs from rest of the files.

This will also help when we collect db2support and we can have a much smaller db2support if we exclude all the other files.