IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
This item is not in our plans but is being kept in our backlog.
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/OS Communications Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Networking
Product - z/OS Communications Server
This requirement is being accepted as a candidate, but as noted in a previous comment, if we address this requirement, we would probably do so by adding a SAF resource identifier to our IP filtering support.
--- the second time, because my comment was not visible / shown to me ---
Hi team,
We would prefer to use NETACCESS because it has very clear and simple to use configuration statements. It can be implementated very fast e.g. in emergency cases.
In our environments where we have Policy Agent (QoS) running, the configuration is shared / used by all LPARs of the Sysplex.
Our largest production Sysplex has 12 LPARs. In such a large environment it is more complex to define filters, which should be valid only for a view (maybe one) system only.
A misconfiguration in this case might harm the whole Sysplex because the rules would get loaded automatically on all systems (refresh time specified on the TCPIMAGE statement of Policy Agent).
Kind Regards,
Rene
Hi Rene. There are a couple of ways we could do something like this. One approach would be to add capability to NETACCESS as you described. Another is to add a SAF resource identifier to our IP filtering support, which would open all of the features of IP filtering (including ports, connection direction, time ranges, and so forth) to the SAF checks that you are looking for. We would prefer to implement such a solution on IP filtering, but that involves the use of policy agent, just like QoS. Would an approach based on IP filtering meet your needs, or does the use of policy agent put this in the same category as the QoS approach in your mind?