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 (https://ideas.ibm.com).
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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
It display the important ZPARM of CONDBAT and MDBAT (zparm name of MAXDBAT)
These two values are “limits” and rarely change. The DISPLAY DDF shows us these ZPARM values to remind us of these limits.
The DISPLAY DDF DETAIL command gives us all the information to watch how we are approaching these limits but it is not obviously stated in the documentation (in my opinion).
MDBAT limit is relatively better documented then CONDBAT which really beats about the bush on what exactly to watch.
The DISPLAY DDF DETAIL command page (link above) should have clear statement that
“DISPLAY DDF DETAIL message DSNL090I shows MDBAT (value of system parameter MAXDBAT). Assuming DT=A, then watch DSNL092I ADBAT value as it approaches MDBAT. When ADBAT reaches MDBAT then connections will begin to queue while waiting to become active”
“DISPLAY DDF DETAIL message DSNL090I shows CONDBAT (value of system parameter CONDBAT). Assuming DT=A, then watch DSNL092I & DSNL093I. When the total of “INACONN +ADBAT-DSCDBAT” reaches CONDBAT then incoming connections cannot be made and the distributed application will experience a connection error (connection refused)”
In addition, or alternatively, you could make enhance the documentation for the actuall messages to be more clear for how to watch CONDBATT
The message documentation for DSNL092i does say for ADBAT that if MAXDBAT is reached then queuing occurs. In my opinion, the documentation does not emphasize enough that this is important… but OK… you say something
The message documentation for DSNLO93I does not say how to watch CONDBAT. I find the documentation vague on this important point! All the information is here… but it is not clearly stated
Why is this important to me?
We had an experience when CONDBAT was reached. It turns out that our CONDBAT was relatively low and the application introduced a new change that forgot to properly close connections… so we hit CONDBAT. We later raised CONDBAT and changed the application to properly close connections. Both actions addressed our problem at that point in time. My point is that we hit CONDBAT and it was not immediately obvious to me during this application incident. It was not immediately obvious to me what I needed to be checking and monitoring. Of course, I did figure it out… but it took a bit to read and re-read and really understand the information from DISPLAY DDF DETAIL
As further background. I opened IBM support CASE TS005127784 to ask IBM Support directly and clearly how to monitor CONDBAT. You can see that it took IBM support some thought to provide the proper answer.
Do not place IBM confidential, company confidential, or personal information into any field.