Re: WRKUSRPRF

A *USRPRF is just another object.  They must have access to it to modify 
it.  And, no, WRKUSRPRF does not analyze the current user profile, decide 
if they have *SECADM and then adopt authority to get at the user profiles. 
 You could submit a DCR to get it to do so.  But there's two concerns:
1 - I wouldn't hold your breath waiting for IBM to come out with such a 
fix for V4R4.
2 - There could be some obscure i5 shop out there that needs a user to 
have *SECADM authority to do something other than WRKUSRPRF and therefore 
hasn't given them *ALLOBJ.  And, IBM hates to open up a security door that 
someone wants closed.

Workaround:  Use your own custom WRKUSRPRF program that does not have a 
command line and adopts QSECOFR authority.
Or, just give them *ALLOBJ authority.

ps:  Scott Klement had a sample 'command exit point' program that checks 
to see if a user has certain authority and then automatically forces a 
joblog.
http://www.iseriesnetwork.com/artarchive/index.cfm?fuseaction=viewNewsletterArticle&articleID=51363&webID=1001&override=0


Rob Berendt