Re: Edit Object Authority for Library, Program, File and User Security.....

[George Lopez <georgerl@xxxxxxxxxxxx>]

From my take from what others are telling me *EXCLUDE for file 
objects?  For the addlible command failing use *USE for library? Thanks

Rory Hewitt wrote:
> George,
>
> Limit the file authorities so the user can't view them - PUBLIC(EXCLUDE) can
> work, but may be a bit much. Could use the same authorities for the
> containing library - up to you. Create the program that accesses the file.
> Once it's compiled, change it so that it's owned by QSYS and has
> USRPRF(*OWNER).
>
> Rory
>
> On Tue, Apr 27, 2010 at 10:55 AM, George Lopez <georgerl@xxxxxxxxxxxx>wrote:
>
>   
> > I want a particular user to use the file in a program(CL/RPG) but not be
> > able to view all the files in a library outside of a program. I did the
> > below but it does not work.
> >
> > 1). I did EDTOBJAUT for a library and for a user to *EXCLUDE so this
> > user can not view these files. But I want the programs(CL/RPG) the user
> > uses to be able to read/write/update the file.
> >
> > 2). I changed the user's initial sign on CL to USRPRF(*OWNER). But when
> > this user signs on the user gets the below error for *EXCLUDE....
> >
> > Not authorized to library xxxx01
> > Not authorized to library xxxx02
> >
> > 3). If I use object authority to *USE then this user can view the
> > file(s) in these libraries using iSeries Data transfer, FTP or some
> > other utility which I do not want to happened.
> >
> >