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.
To monitor system resource usage at database level in a pureScale environment
All current monitoring facilities can not meet customer requirements to monitor overall system resource consumed for a specific database, in a database consolidation scenario of pureScale. PMR#: TS000078803
Ref TS000003442, PMR 68950,664,706Ref PMR 67845,664,706In case a deadlock occurs on MDC tables on BID index, diagnostic from Locking Event Monitor is not sufficient to understand deadlock. We need to understand data in conflict pages to check acce...
Add session-level reset for monitoring metrics in the MON_GET* table functions
There is no way to reset the metrics reported in the MON_GET* table functions. Please add functionality for resetting these at the session level, much like "RESET MONITOR" does for snapshot monitoring. Yes, there are a dozen ways to code this your...
Please add Firstlsn to the MON_GET_CONNECTION table function
The firstLSN is only available using db2pd. It is the ninth column reported from: db2pd -transactions It does not appear to be anywhere else. I would like to be able to query it using the MON_GET* table functions.
Lock event monitor does not log hex values of prepared statements
When using the lock event monitor to track prepared statements involved in lock timeouts/deadlocks, it was observed that parameter marker values for hex entries are not logged even though the option for history and values is enabled. This works fi...
db will be blocked and hang after mon_heap is run out
agents will be blocked and will hang after mon_heap is run out when database turns on event monitor. Now it is works as design, yet customer hope we can change the design and decouple between event monitor and the agents executing some SQLs. So ag...
Invoke the DB2 call-out scripts (COS) for ALL First Occurrence Data Collection (FODC) events
Currently the DB2 call-out scripts (COS) will not be invoked for all ALL First Occurrence Data Collection (FODC) events. For instance the only time that FODC_AppErr% events will invoke the db2cos script is when the condition happens on a sub-agent...
Do not place IBM confidential, company confidential, or personal information into any field.