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.
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...
Purescale - Event Monitor for Locking - Include member information
In Purescale environment, with currently commited enabled and CS isolation query, we can find situations where a "select" receives a locktimeout depending on which member the connection comes. But, event monitor for locking doesn't include this in...
Currently we have db2diag files as part of dbm parameter (DIAGPATH) and all the files (db2diag.log, events,nfy,bin,stack,stmm,dump) going into the same directory. The challenge is in case of issues, we see huge dump files produced (sometimes 40gb ...
Adjusting column status in syscat.tables by synchronizing with column AVAILABLE SYSIBMADM.ADMINTABINFO
Customer mentions that tables which are delivering aSQL1477N should have an inoperative status. But theyhave status 'N' (for normal) insyscat.tables. The only way to retrieve the status of anSQL1477N is to select the column AVAILABLE inSYSIBMADM.A...
Enhancement of View syscat.bufferpools to show alos stmm bufferpool sizes
When a bufferpool size is set to AUTOMATIC, -2 is being retrieved fromsyscat.bufferpools. But customer wants the current number of pages ofautomatic settings also displayed in syscat.bufferpools. Also a new column insyscat.bufferpools should indic...
DB2 listener not activated after DB process killed by OS and restarted automatically by TSA in HADR environment
We had DB2 HADR primary/standby configuration. Due to one application job,DB2 consumes all memory and OS killed db2sysc process. db2 restarted automatically by TSA but listener wasn't activated . There was no evidence in logs which process was usi...
Begin / End COMMIT instrumentation for DRDA, CICS/IMS
Complex CICS/IMS or DRDA transactions (involving multiple programs with an implicit Commit at the end) are incorrectly presented on the Omegamon Accounting Report/Trace. By design the costs of the tough SYNC (COMMIT) operation are added to the las...
Lack of information about Queries from Federated DBs - particulary from DB2 z/OS
From DSM we should be able to see the transactions from federated databases. In the case when we are having some federated transaction contention we are not able to see on the source database on DSM getting more difficulty to diagnose a performanc...
reduce I/O activity to /etc/services upon each connect
Using filemon, we see 191 accesses to /etc/services for each Connect statement. It seems this file should only be accessed once or twice. This has been verified by IBM personnel with ticket TS001677150.
Do not place IBM confidential, company confidential, or personal information into any field.