|
But is some smart security officer added QSECOFR *EXCLUDE, well private authorities over ride every thing else. On a brand new install of V5R3 QSECOFR has *all as well as QSYS and public is *EXCLUDE -----Original Message----- Chris Bipes wrote: > David I have run into this. Make sure Qsecofr has *use authority to Qsecofr > profile. You must have *use authority to your own profile to use the api. Wouldn't you have that authority regardless? When I do a DSPOBJAUT OBJ(QSECOFR) OBJTYPE(*USRPRF) on my system here (problem is happening on a customers system) the only authority QSECOFR has is *PUBLIC *EXCLUDE.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.