What is the generally accepted practice for QIBM_IOSYSCFG_VIEW?

What is the generally accepted practice for QIBM_IOSYSCFG_VIEW?

7.6 added QIBM_IOSYSCFG_VIEW.  Along with adding this they tightened up a
whole lot of stuff.  Stuff which was publicly available prior to 7.6.
Certain things now either require *IOSYSCFG or they user be added to
QIBM_IOSYSCFG_VIEW.

Adding all users to *IOSYSCFG allows a smooth transition from an earlier
version to 7.6 but has some SERIOUS consequences.

Just changing the default authority on QIBM_IOSYSCFG_VIEW to allow viewing
may be better.

Or you can piecemeal out users to QIBM_IOSYSCFG_VIEW as needed and leave
the default to *DENIED.

I am having vendor issues (GoAnywhere).  They recommended the
QIBM_IOSYSCFG_VIEW for the user profile associated with their software.

For this, and more fun stuff associated with 7.6, check out:
https://www.ibm.com/docs/en/i/7.6.0?topic=system-security-related-changes
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.