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

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

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