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.
CICS TG team does not have plans to implement this RFE in near future and so this requirement is being declined at this point. 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.
If an option is provided to reset HEALTH of a gateway to zero, then the new requests only get impacted during z/OS WLM routing. CICS TG uses zOS TCP/IP port sharing by providing gateway health dynamically to the z/OS Workload Manager(WLM). z/OS WLM will take routing decisions based on gateway healths for new connections only. So the existing connections will continue to use the same gateway until client application closes the connection or the connection is closed by the CICS TG after idletimeout. If the connections are used continuously, then the idletimeout scenario never happens. The way to influence the load balancing decisions is to recycle the connections from client connections (like agedtimeout setting in WebSphere application server connection pool settings). Let us know if it is possible to recycle the connections from client applications.