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.
See this idea on ideas.ibm.com
Today on a system we have 125,000 socket blocks defined, and we are reaching a peak of 90,000 active sockets through the day. We run with Keepalive active so we can ensure they are still valid, and currently have the TCPALIVE interval set to 360 seconds. While we won't have to send the keepalive for all 90,000 active sockets, there will be times where a lot of keepalives will be sent, maybe 20,000 or more in a given interval. The keepalive processing in CTLV does give up control after every 500th socket checked by doing a DLAYC, but going through the entire table is going to happen very fast. We have seen instances where keepalive processing seems to have exacerbated potential network issues, by flooding the network with a significant number of packets in a very short time frame.
We're wondering if there should be a limit on the number of keepalive messages sent at one time. An easy solution may be to change the DLAYC in CTLV to an EVNTC/EVNWC with a delay of a second. This may not be the best solution as it would delay every 500 sockets, regardless of if the keepalive is sent or not, but may not be an issue. A more elegant solution may be to add an additional counter, and only do the second delay if a specified number of keepalives (perhaps another CTK2 value) have been sent. Either way would limit the number of keepalives sent within a given time frame to a manageable and known amount.
Idea priority | Medium |
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/TPF
Component - z/TPF
Operating system - IBM z/TPF
Source - TPFUG
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/TPF
Component - z/TPF
Operating system - IBM z/TPF
Source - None
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/TPF
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - z/TPF