RE: Do I understand USRPRF *OWNER USEADPAUT *YES correctly?

Pete,

The overrides don't carry any authority.

The user's authority to the overridden-to object will be checked when the file 
is opened for I/O.  The standard OS/400 authority checking is used with the 
target being the overridden-to file.

So, if your JDBC user didn't have authority prior to the overrides, he's not 
going to have authority after the OVRDBF is done.

(Note, I put together a quick test of this to confirm ;-)


HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pete Helgren
> Sent: Friday, April 08, 2005 2:00 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Do I understand USRPRF *OWNER USEADPAUT *YES correctly?
> 
> 
> I'll know in a bit if it IS working.  But here is what I thought was 
> happening:
> 
> We set the overrides at *JOB scope using this program at entry time.  
> The overrides DO persist, I can use the wonderful WRKODBCJOB by Bryan 
> Dietz and see them all there as long as the job persists.  I assumed 
> (perhaps wrongly) that because it was the program owned by 
> FUSER the set 
> the overrides that all transactions using the overrides were 
> under the 
> FUSER authority.  I guess my question would be, if the 
> overrides set by 
> the program owned by FUSER don't carry FUSER's authority, 
> then, at that 
> point, who's authority do the overrides carry?
> 
> Always dangerous to assume things...That is why I went to the list.  
> I'll know a bit later after we make some changes and bounce Tomcat.
> 
> Pete
> 
>