RE: QSYS/QQQOOOPLNC

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

He can look at the access path recommendations but can't actually build
indexes over some of the files native security restricts him from, right?

If that's the case, I'd stick with whatever your business rules are.  If
he's not supposed to access PAYROLL, don't give him access to it just to
build indexes.  He can submit a request to system DBA or system Admin to
build them at night or something (index builds on large files takes a while
and may take significant resources).

Non-sensitive files... he can't do much harm by building indexes (other than
resource consumption for index builds).

Elvis

-----Original Message-----
Subject: QSYS/QQQOOOPLNC

I have a developer on our production machine that is trying to use iNav to 
look at suggested access paths to build.  However he can't because he 
doesn't have access to this file.
Any reasons why I wouldn't want to let them?

Only remote thing I can think of is the old "security by obscurity" 
concept that if he browses this file then he may see a recommendation to 
build an access path over a file named WAGES in a library called PAYROLL 
and that might inspire him to look harder at a way to get into that file.

Rob Berendt