IBM Z Software
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).
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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
In the scenario described it is the Gateway's problem to notify CICS that it the connection is closing, so that the CICS IPIC layers can tidy up and remove the autoinstalled IPCONN. If this is not happening during a normal close of a Gateway then this a defect which the CTG team need to address. If it occurs because a gateway has failed then again we would expect CICS to be notified that the sockets that an IPCONN was using are no longer open. That should be the responsibility of the TCP/IP Stack to notify CICS about, and so the problem rests with Comms Server if this is not happening.
When we have encountered this we set the ipconns to REL (not Out of Service) and then they reestablish themselves when a new request comes in. I am planning to do this release in an automated fashion trapping on message DFHIS1015.