Re: *ALLOBJ authority

I like that, just tell'em what they want to hear.  I do that to my wife all the 
time.   
 
 
-----Original Message-----
From: SIngvaldson@xxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Wed, 3 Jan 2007 4:47 PM
Subject: *ALLOBJ authority


One trick that I have used is to create an "Owner" profile that owns all
of the objects in an application.  Then when a programmer thinks that
they need *ALLOBJ authority you can add the "Owner" profile to theirs as
a supplemental group, giving them pseudo *ALLOBJ authority to only the
application objects.

Regards,
 
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company


-----Original Message-----
date: Wed, 3 Jan 2007 16:18:26 -0500
from: "Wilt, Charles" <CWilt@xxxxxxxxxxxx>
subject: RE: Is DFU capability a part of the *ALLOBJ privlidge or can
    DFUbeseparately denied?

Yes I know.

John Earl pointed out another way around it.

I wouldn't try this method myself <grin>  Just wanted to throw it out
there for the OP.  Hopefully, the user with *ALLOBJ who shouldn't have
it but from whom it can't be taken away isn't experienced enough to
figure out how to get around it.

Which means the OP better hope the user isn't on this list!

On the other hand, its been my experience that you can often take
*ALLOBJ away from a non-expert user without the user realizing it.


Charles Wilt
--
iSeries Systems Administrator / Developer Mitsubishi Electric Automotive
America