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

I believe that is correct.  We are currently developing a similar scheme
here.  I don't think you need to set USEADPAUT to "*YES" to make this work,
though.  I believe that parameter refers to whether or not the authority of
the calling program is adopted.

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
We have all the files in a library set to allow a specific user profile to
have *ALL authority (lets call it FUSER) and *PUBLIC authority set to 
*EXCLUDE.  All of the programs that access the files are owned by FUSER and
the authority of those programs is set to USRPRF(*OWNER) and
USEADPAUT(*YES).  As far as I know that prevents anyone from accessing 
these files outside of using specific programs unless they have *ALLOBJ
authority (Correct?)

We need to access those same files through JDBC so we have a program that we
call when we establish the connection in Java that sets the library list and
file overrides (OVRSCOPE  (*JOB)).  That program is 
also owned by FUSER and is compiled USRPRF(*OWNER) and USEADPAUT(*YES).
This should prevent anyone who successfully connects through JDBC but 
doesn't call the program from getting access to the files (unless they have
*ALLOBJ authority) (Correct?)
<clip>