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.
See this idea on ideas.ibm.com
The QSYS2.USER_INFO SQL View is nice to have. However, the performance on systems with thousands or even hundreds of User Profiles means a lot of waiting. Providea faster version of USER_INFO that returns only the User Profile Info and not the OBJECT_STATISTICS stuff.
I rarely need the info provided with the extra data from OBJECT_STATISTICS that is returned with USER_INFO and yet I still have to wait for it.
Certainly when there are "20 or fewer" User Profiles on the system, the performance seems great, but with hundreds or more, it can sit for 20 to 30+ seconds before responding.
I assume this is because of a LATERAL join to the OBJECT_STATISTICS UDTF is performed for each returned User Profile. Ironically you use OBJECT_STATISTICS to build the *ALLSIMPLE list of USRPRF objects but then do the lateral join to pull in the full object information. This is on top of the LATERAL join to the internal UDTF that returns the User Profile info.
This request asks that a 2nd VIEW be created that avoids calling and avoids returning OBJECT_STATISTICS information for each user profile.
My actual preference would be to expose the internal UDTF used by the UDTF as a published/documented "Services" UDTF rather than spend centuries waiting on a VIEW to return information.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This enhancement was delivered in spring 2021 with IBM i 7.4 PTF Group level 13 and IBM i 7.3 PTF Group level 24.
A new view, QSYS2.USER_INFO_BASIC, returns the key information from USER_INFO while eliminating the additional information gathered from OBJECT_STATISTICS. For a system with many user profiles, this view is significantly faster.
IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.