IBM Power Ideas Portal
This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
IBM does not intend to provide a new solution or 5250 specific solution to this request, so it is being closed. The existing IBM i Intrusion Detection support provides a generic DoS solution.
IBM i Intrusion Detection provides built in support to notify and optionally deny connections exceeding a configured policy's threshold. You can create a traffic regulation policy including the remote IP address or range of remote IP addresses to monitor for clients offending your expected connection thresholds on a particular local server port. When the threshold is exceeded, audit records are created (optionally an e-mail or message to a message queue can also be sent) to warn you of the unexpected conditions. Intrusion Detection also provides built in prevention with variable dynamic throttling. A policy can enable throttling so that it starts to drop TCP connection attempts matching the throttled policy when the policy's threshold is exceeded. If the threshold is continually exceeded, throttling is variable in that it will increasingly deny more connection attempts until it throttles back connections to the desired connection rate for a policy's time interval. As connections slow down throttling backs off and is eventually disabled when thresholds are no longer exceeded. Note: If you decide to throttle, you should carefully consider your policy's settings because throttling could eventually result in total denial for connections matching the configured policy with throttling enabled if the connections are coming in at a rate that continues to exceed the policy's thresholds even with some connections throttled.
The following Knowledge Center link discusses the Intrusion Detection support available on IBM i.
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzaub/rzaubkickoff.htm
This link highlights variable dynamic throttling which is built in prevention available through Intrusion Detection.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzaub/rzaubthrottle.htm
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Networking
Operating system - IBM i
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Availability, Recovery
Operating system - IBM i
Source - Client
The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a “nice to have” LOW priority feature.
Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM
We use named sessions, but always append the '=' to the end of the name. Then each session is named with a "collision avoidance ID".
Having named sessions can let you know where someone's running something.
I agree with pnicolay and Jason. Unless you have a really good reason to have named 5250 sessions, I would just allow QPADEVxxxx names. I have seen a bigger need to have multiple connections for certain boxes and this need is hindered by used named sessions.
I agree with pnicolay. I've never understood the need to have named sessions in today's 5250 world. Plus, if you move to the web, that whole concept goes away anyway.
Jason
You could use the TELNET exit program to give the device a name (with an incremental session id)... so you don't need to do it in the emulator. Or just use QPADEVxxxx names instead of named sessions.