RE: Allowing power users to re-enable users

I said *ALLOBJ and *SECADM.  You can do the RTVUSRPRF SPCAUT(&SPCAUT) and 
then search &SPCAUT for SECADM or ALLOBJ
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/apis/qclscan.htm


Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/26/2003 01:16 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Allowing power users to re-enable users


I wish I could do one, but <cough> we can't. About 70% of the users have 
at
least *SPLCTL AND *JOBCTL. This is from before I became admin. We are 
going
through a cleanup currently and getting rid of these will be a step in the
process.

As far as #2, yes I did that per Raul's suggestion. The manager has to
approve the person to use it.

-----Original Message-----
From: rob@xxxxxxxxx 

Trust?

Don't let the program change any user profile with certain special 
authorities like *ALLOBJ, *SECADM.  Just happens to be the second 
parameter on RTVUSRPRF, therefore I believe it indicates it is a popular 
request.

On the program, and the command that runs it, make sure you *EXCLUDE 
*PUBLIC and add just the 'trusted' individuals.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.