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.
Add more criteria for MONITOR CONNECTIONS in DB2 PROFILE tables
Currently the DB2 PROFILE table only allows LOCATION as the selection criteria with the MONITOR CONNECTIONS keyword. We would like to restrict the number of connections a particular application can open, but the connections can:
1) come via a shared DB2 Connect gateway so location is always the same and any limit would be shared across all applications
2) come directly from shared application server infrastructure - so again the limit is shared across multiple applications coming from that server
3) come from Cloud locations, using dynamically assigned IP addresses that change frequently, or using one-time location ids that are never repeated. In this case the limit can not be applied at all.
We have had the situation of a runaway application that constantly added more and more connections to its connection pool (never using them) until CONDBAT was reached on multiple DSG members. We had no way to restrict their connections without impacting other applications.
Do not place IBM confidential, company confidential, or personal information into any field.