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
There are application installation procedure that requires the creation of "/etc/rc.d" entries to automate the application startup and shutdown. e.g. http://docs.oracle.com/cd/B28359_01/server.111/b32009/strt_stp.htm # ln -s /etc/dbora /etc/rc.d/rc2.d/S99dbora # ln -s /etc/dbora /etc/rc.d/rc2.d/K01dbora
In IBM AIX RBAC environment, it is not possible to create/modify/delete a file or a symbolic link within these /etc/rc.d directories, using a RBAC non-root UserID. Even if the RBAC non-root UserID was assigned with these RBAC roles in AIX 7.1; auditadm, fsadm, isso, pkgadm, sa, secadm, so, svcadm, sysop, and useradm.
In PMR 73011,000,834 IBM AIX Development Support Specialist advised us that, the non-root RBAC UserID will need to have "PV_ROOT" privilege assigned to it, before the UserID is able to perform the above mention activities. Even though a solution works, unfortunately it also gives the RBAC non-root UserID the privileges to edit system related files e.g. /etc/security/passwd files which is undesirable.
IBM development team will need to develop an alternate solution to the above use case without compromising the design of RBAC.
Do not place IBM confidential, company confidential, or personal information into any field.