This portal is to open public enhancement requests for IBM Sterling products and services. 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.
See this idea on ideas.ibm.com
CDz does issue SVTM082I when CDz as node hit the node specific SESS.SNODE.MAX. However, it doesn't issue any message when it reached Max PARSESS. Could you add a corresponding message for this so that we can easily figure out it hit the limit?
It means these process will be put in wait queue without any messages letting us know why it's there, so how could we tell it's because of the reason that it passed Max PARSESS if the user came to ask us their file was not delivered on time. Am I supposed to count the number of active sessions and check PARSESS? It deserves at least a informational message telling us it hits the limit and process put in wait queue.
What is your industry? | Financial Markets |
How will this idea be used?
It will be used for problem determination. |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for your patience as we worked on this request. I'm pleased to announce that we have delivered this enhancement with the C:D v6.1.0 release which became generally available on 06/05/20. Please consider upgrading to start gaining the benefits of this and other enhancements that we've made in the latest release.
Sincerely,
Chris Sanders
Connect:Direct Offering Manager
An alternate solution to this is now available in Connect Direct for z/OS 6.1.
A process that is waiting for PARSESS is now put in the WAit queue, with a status of WP (Wait for Parsess/class availability) instead of WC (Wait for Connection)
It would be helpful to know when CDz is approaching the max threshold - perhaps at 80%.
Thank you for opening this enhancement request with IBM. I have reviewed it with my team and we believe that improvements could be made to improve the visibility into why a process has been placed in the WA WC queue. We will accept this as an uncommitted candidate and will look to add it to our roadmap moving forward.
Sincerely,
Chris Sanders
Connect:Direct Offering Manager
chrissanders@us.ibm.com