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.
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 database , To migrate We couldn’t find equivalent alternative for STATUS_CHANGE_TIME in mon_get views/functions . unfortunately, we dont have similar one in mon_get_* table functions for the application. we have some entry timestamps for the activities however these are not same things.
We have db2pd =apinfo which only tells you the application connection time it does not tell you the status change time unfortunately."
For now we are using UOW_START_TIME column of TABLE(MON_GET_UNIT_OF_WORK(NULL,-1))
LOCK_WAIT_ELAPSED_TIME > 900 and UOW_START_TIME < (CURRENT TIMESTAMP - 900 SECONDS) with ur" LOCK_WAIT_ELAPSED_TIME > 900 and STATUS_CHANGE_TIME < (CURRENT TIMESTAMP - 900 SECONDS) with ur""
Also - we are looking for below enhancements
2. MON_GET_TABLE has metrics to find information about a table. But we can’t find its size. We are dependent on SYSIBMADM views to find table size. It will be good to add table size metrics to MON_GET_TABLE
3. We can’t monitor/know connection status using MON_GET_CONNECTION, whether connection is executing/locking/wating etc. Good to add connection status metrics column to MON_GET_CONNECTION view
Do not place IBM confidential, company confidential, or personal information into any field.