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.
We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The introduction of SOTUNING in CICS V5.3 provides some support. If SOTUNING is active (which it is by default) then persistent connections are only actually persistent for 1000 requests.
The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
Hi Mike,
I think we may have addressed this with the introduction of SOTUNING in CICS V5.3. If SOTUNING is active (which it is by default) then persistent connections are only actually persistent for 1000 requests. After the 1000th request they are closed and so have to reconnect, which for your scenario would allow them to be balanced over any new port sharing regions just started up. Does this sound like it addresses this issue, is 1000 requests a low enough number to provide the function you need?
Regards, Alison