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 Serviceability
Created by Guest
Created on Feb 10, 2015

de-cluttering of db2diag.log(RIMS)

[This requirement originates from JPMC EDW/RTC group] The db2diag.log is an extremely useful reference for both customers and db2support persons. We are able to identify milestones events, find errors, and gather clues to their issues, all before engaging DB2 Support. Over the past few releases, the db2diag.log has become cluttered with informational messages (even at diaglvl 3) which makes examining the db2diag.log for milestones and clues very very difficult if not impossible. For example, in v10, this HADR message litterally clutters the db2diag.log 2013-02-08- I3432132512A534 LEVEL: Info PID : 7864458 TID : 10966 PROC : db2sysc 0 INSTANCE: vpcinp01 NODE : 000 HOSTNAME: EDUID : 10966 EDUNAME: db2lfr.0 (VPCDB) 0 FUNCTION: DB2 UDB, data protection services, sqlplfrFMRefreshXhdr, probe:5233 DATA #1 : LFR Scan Num = 80721764 LFR Scan Caller's EDUID = 22791 Refreshing Xhdr for log S0002480.LOG with page count of 499984 and extent size of 499984 The purpose of this requirement is to generate visibility/change within the DB2 Development teams to use precaution when adding db2diag.log entries: use diaglvl 4 when possible, be aware of repetitious entries, be user friendly. Alternately, if the db2diag.log is to be used as an ibm-internal mechanism, then this requirement is to add more value to the notify .nfy log file. Currently the notify .nfy log file is not useful to customers or support persons.