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.
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...
Monitoring table function to display details on the application and its temp space usage
Often times, users would like to get a single view report on the application handles/ids, the corresponding process id and application usage of sys or user temp spaces and db2 does not have one monitoring table function to accomplish this. Users n...
Add a monitoring table function to return transaction ids along with their commit times.
Goldman Sachs needs to know all the insert/update/delete operations against all tables updated by 1000s of applications along with their commit times. They dont want to use a replication. They want to use triggers that will be triggered on I/U/D o...
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...
Allow better monitoring of DB2 Thread/Connection types
Currently there are various ZPARMs to "control" thread management (CTHREAD,MAXDBAT,CONDBAT,IDFORE,IDBACK,etc). These ZPARMS are upper bound limits of the number of each type of thread/connection that DB2 is configured with. There is very litt...
STATUS_CHANGE_TIME Colum doesnt exist in in mon_get views
We are currently working to migrate all our SNAP views to MON_GET views/Functions as SNAP views caused a response spike in our PROD environment recently.We are using STATUS_CHANGE_TIME columns of sysibmadm.applications to check lock waits on the ...
Application status change time is not available in any mon_get_* table functions
In snap admin views, users could see STATUS_CHANGE_TIME column for the application which was helpful in determining when exactly the application changed it status when investigating performance issues. This would help users to estimate or know how...
Warning error code for Db2 tablespace architecture limit
If Db2 tablespace reaches architecture limit of 90%, then there should be a Warning Message write into db2diag.log, so that before it is reaching 100% of Db2 tablespace architecture limit, this can be fixed.
Now we are monitoring through a SQ...
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.