Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components Monitoring
Created by Guest
Created on Sep 4, 2019

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 little in place to allow for the active management of these thresholds.   At best, you can display DDF DETAIL and get some "current" numbers and the system provides a message when you reach a certain percentage (like 80% or 90%)  of some of these setting and/or there is a high water mark kept for some of these settings.   This does not provide for monitoring and trending of these resources.   For example, the high water mark for IDBACK is only reset when DB2 is bounced, in today's continuous availability world,  that could be many months; QUEDBAT is an ever rolling counter and does not show what you really want to know which is how deep the queue got.  More granularity is needed.  We need to be able to chart/monitor the the ebs and flow of these resources over time to identify peeks and be able to set these parameters more intelligently and plan accordingly.

Needed by Date Sep 4, 2019