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,
Post an idea
Upvote ideas that matter most to you
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.
LOCK ESCALATION: Ability to specify table-level lock-escalation criteria.(RIMS)
Customer wants more granularity on lock-escalation semantics. currently, lock escalation occurs either when an application hit's the MAXLOCKS constraint, or when the database LOCKLIST becomes full. Since lock-escalation is more detrimental on tabl...
Allow a DBA connection even if maximum connections has been exceeded.(RIMS)
Note from customer: Jill, We need a feature enhancement, where there is a way for a DBA to always be able to connect to the DB (at least one connection), even if maxappls, maxagents, maxwhatever has been hit. DBAs shouldnt have ...
New access path for faster first fetch with a good global time
Firstly, I don't know if it is possible. We can encounter this following performance issue : select on a big table with an order by. Depending on the statistics, we can have list prefetchs on an index. If the index is very big, we have to wait a l...
Automatic propagation of a significant application name
When a java program connects to the database, the application name is usually db2jcc_application. This behavior can be overridden by setting the appropriate properties in the DB2 driver. Unfortunately, it is rarely done (from my experience). It co...
Session level LOCK TIMEOUT should apply to all lock types.(RIMS)
Currently, the session-level lock timeout only applies to SQLP_TABLE, SQLP_RECORD, SQLP_KEYVALUE, and SQLP_MDCBLOCK. Customer would like this to apply to all locks acquired by the application that set the session-level timeout value.[Michael Snowb...
Optimizer should account for bufferpool hit-ratio when estimated page access time.(RIMS)
In PMR 00962,7TD,000, Goldman Sachs had a scenario where optimizer was choosing a more expensive HSJN over a less expensive NLJN. Shu Lin summaries the problem well: 'In terms of CPU cost and number of IOs, we correctly estimate that NLJN is ...
Modifications to both the Tivoli APIs and the IBMLDAPgroups plugin(RIMS)
1.Write out more info in the db2diag.log as to what server we are hitting when doing group lookups in AD. This would probably require modifications to both the Tivoli APIs and the IBMLDAPgroups plugin. Today, we receive an error (Cant contact LD...
Since proc_priocntl is required to be documented in Installation;Upgrade;Solaris Pre-Reqs and(RIMS)
Headline cont.. outside of just WLM documentation Description-See PMR45988 Verizon took a performance outage because proc_priocntl was not set. They had no way of knowing that it should be. It is only mentioned under Workload Manager in the DB2 ...
Do not place IBM confidential, company confidential, or personal information into any field.