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.
Enhance Db2 WLM to enable it to prioritize access to physical I/O
We have a Db2 AESE 11.1 fp4a mixed use (but no column tables) data warehouse on an AIX 7.2 LPAR that is limited to 75K IOPS by NetApp. When the threshold is met, high priority OLTP queries submitted by our 1000 retail store POS systems can hang in...
We need an activity threshold to trigger an action whenever a specific activity consumes more than a given amount of transaction log space. I know that there is already some control mechanism by using DB CFG parameters MAX_LOG and NUM_LOG_SPAN , b...
WLM monitor and control total private sortheap usage
Concurrent private sortheap heavy queries run out of system memory and cause systems reboot. ISAS 7700 environment with DB2 v10.1 FP4 on AIX. There are 16 physical nodes running 122 database partitions. The catalog node and coordinator are on one ...
Lowering the limit for ACTIVITYTOTALTIME and UOWTOTALTIME
We should be able to trap the transaction that spent more than 10 seconds with a threshold. Can we change the low limit of the parameter ACTIVITYTOTALTIME and UOWTOTALTIME to allow a magnitude of milli second.
Do not place IBM confidential, company confidential, or personal information into any field.