This portal is to open public enhancement requests against IBM Z Software products. 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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Enterprise Tooling
Product - CICS Transaction Gateway
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - CICS Transaction Gateway
Hi,
I agree with your suggestion to add a high-water-mark statistic for the value of CM_CWAITING.
We also need if possible the total number of Connection Manager waiting during the full interval, an 'CM_IWAITING'.
These value will help to determine if MaxWorker must be increased or if we have in case of short time peak.
To clarify, CM_CWAITING does indicate the number of connection managers that are actively waiting for a worker thread - and is included (as are all statistics) in each SMF record. However, I agree that value of value of CM_CWAITING might have returned to a low value by the end of the statistics interval, and so you do not know the maximum "depth" of the queue over the course of an interval.
Would you agree that CM_CWAITING already shows you how many connection managers are waiting for a worker thread, and that if a high-water-mark statistic for the value of CM_CWAITING was added - then this was provide you with the information you have requested?
Note that if such a statistic was made available, then in certain circumstances such as "start of day", it might validly show a high value, as a burst of client application all attach at 9am (for example).