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).
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.
IBM has no plans to invest in updates to IPFilter in the future, as AIX has other firewall capabilities that are supported. IBM has added the ported IPFilter source code to the AIXOSS Github area at https://github.com/aixoss/ipfilter. You may open an issue there to discuss this problem.
We have many customers waiting for this issue to get resolved and hence need it (atleast the ETA) as early as possible.
Hi Dave,
Can you please let us know the ETA for this fix?
-Shreyas
The YACC compiler issue was concluded by IBM support team in PMR:41779082000
On running ippool -f /tmp/ippool.conf -dnv, the stack overflow message is thrown for YACC compiler
Hi. I don't understand how you've decided this relates to YACC. Do you believe this is a bug in the YACC parsing, or YACC using a buffer that's too small?