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.
Include failure / warning counts in mon_get_pkg_cache_stmt
It's currently not possible to monitor the failure rate of an SQL statement. For example, count of dupkey on INSERT. Likewise for 'soft' errors (warnings) like +100 - row not found on INSERT or DELETE. High rates of these can be a significant drain on system resources and typically indicate either an application problem, or a lack of understanding of the data set. The dupkey problem is particularly challenging since the system will continue to run, but unless the application captures and handles the error, it often goes unnoticed, except for issues such as excessive lock wait and contention, especially in high concurrency environments such as on pureScale.
What is proposed are two new columns in MON_GET_PKG_CACHE_STMT 1) NUM_EXEC_WITH_FAILURE - on the same scale as NUM_EXECUTIONS but only counting executions which returned a negative SQLCODE 2) NUM_EXEC_WITH_WARNING - likewise, but for positive SQLCODEs.
Additionally, LAST_ERROR_SQLCODE and LAST_WARNING_SQLCODE would help on drill-down.
There is precedent for these, since MON_GET_CONNECTION currently reports on the number of failed activities (ACT_ABORTED_TOTAL) but this is a the connection level, and isn't helpful for diagnosing failures at the statement level.
Do not place IBM confidential, company confidential, or personal information into any field.