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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Feb 9, 2015

Method to prevent DB2 from modifying operating system tunables; print diag msg instea(RIMS)

Goldman Sachs deploys hundreds of db2 database instances. Many of these instances are configured to consume predefined resources in a system shared with other instances or dbms' or applications. In many cases, these instances are duplexed via QReplication and there are sanity checks to assure that both the Primary and contingency system remain identical in configuration. DB2 has the ability (during startup) to modify both kernel and user operating system tunables (for example, 'shmmax' just to name one). This poses two problems for Goldman Sachs; Firstly they do not want DB2/STMM to decide what share of free system resources should be consumed by DB2 versus other applications (they have already calculated this during capacity planning). Secondly, in duplexed environments this causes Primary and contingency system configurations to go out of sync. Goldman would prefer a means (ie. db2 registry variable or configuration setting) to prevent DB2 from modifying kernel or user tunables. Instead it would be ideal if DB2 just printed a db2diag.log warning message with the tuning recommendation. [Goldman Sachs would like this to be available in Galileo, especially to compliment the DB2_CPU_BINDING functionality which will see more customers using multiple instances on the same hardware]