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
Today, the QSYLOBJP API documentation states that it creates: a list of objects that adopt an object owner's authority
In the classic way of thinking, this would be program/srvpgm objects that have USRPRF(*OWNER) set a creation time. However what is being produces is a list of objects that have the ADOPT(*YES) attribute regardless of the USRPRF setting.
In this context, that object's user profile parameter may be *USER or *OWNER.
The documentation for ADOPT(*YES) states that it Specifies whether program adopted authority from previous programs in the call stack will be used as a source of authority when this program is running.
I have programs with USRPRF(*USER) and ADOPT(*YES) and they appear in the list of objects generated by the QSYLOBJP API, along with USRPRF(*OWNER) ADOPT(*YES) objects.
Wouldn't it be more accurate to state that the API returns a list of objects that are Owned by the specified User Profile and have the Adopt Authority attribute set to *YES?
Do not place IBM confidential, company confidential, or personal information into any field.