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 updateson 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
we have done a network installation of iACS inside our IFS with restricted access for functions like "run SQL-Scripts". Our Users can only see the 5250-Emulator and their SPLFs. We have entered the restrictions inside the AcsConfig.properties-file. So far so good. When the users then open a 5250-Session (=HOD-Session) from the iACS-headmenu they find a toolbar with all icons and with access to functions we have restricted in the AcsConfig.properties-file !? Additionally the restricted functions can be also clicked inside an HOD-Session via the Menue Actions ! To restrict the access to this security-relevant functions you must additionally edit the .hod-file. To check if everything is fine we looked for a documentation of the key-val-pairs inside the hod-file. But it seems there is nothing available for customers, but only for IBM-Developers. To restrict the access to the menubar, we found out that this can be done by entering the hod-DEVD-files with the iACS Session Manager. Our RFE would be to synchronize the Restrictions of AcsConfig.properties-file with HOD and other related entry-functionality of iACS. But one point is really missing: a documentation of the key-val-pairs inside the hod-file. We made a lot of try-error changes inside the hod-file and from my point of view this is all but not productive.
Do not place IBM confidential, company confidential, or personal information into any field.