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.
Db2 Profile Concurrency Limit at the Data-Sharing Level
A DB2 profile WARNING and EXCEPTION values for MONITOR THREAD and MONITOR CONNECTIONS limit concurrency at the member level. If I specify a MONITOR THREAD EXCEPTION value of 10 and leave GROUP_MEMBER blank, the EXCEPTION value of 10 is per member. If I have 10 members and the cloud app has access to all 10 members in my alias, it could technically be able to get 100 ADBATs. We would like a way to make the EXCEPTION value of 10 at the DSG. This way a cloud application can only have 10 concurrent ADBATs no matter how many members are in a DSG. Is there a way to put profile concurrency in the CF so concurrency values will be at the DSG level?
Needed by Date
Dec 31, 2019
Do not place IBM confidential, company confidential, or personal information into any field.