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.
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...
Getting the Accessplans at the Routine level for the Database LUW
Db2 performance issues in one of the major area to look for, Whenever there is performance issue in the database, one of the major point we look is for the queries how they are behaving in the database.
Db2 LUW provides lot of options to get the ...
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.
event monitor tables (activity/actitivtystmt/activitymetrics) should support range partitioning
event monitor tables do not support range partitioning. In addition, you can not create expression based indexes on them. This makes them more difficult to manage and query.create event monitor wlm_activity_mon for activitieswrite to table acti...
Display row stats ( rows_read, rows_written, tq_rows_sent, tq_rows_recv) for each sub-section in MON_GET_AGENT
Currently, there is no equivalent of getting row level information ( TQ_ROWS_SENT/RECV, Rows Read, Rows written ) for each agent running within a sub-section which was readily available in snap_get_subsection or db2 get snapshot for application ag...
In the case of a hang, we only have the material for root-cause analysis if we were able to collect db2fodc information before the system became fully unusable. A small moving window of such information written out to disk on a regular basis would...
Do not place IBM confidential, company confidential, or personal information into any field.