RE: Op's nav - Graphical UPDDTA

John,

Have you forgotten about select/omit logicals?  Row level security is normally
based on some value in the row, for example a plant identifier.  A logical for
each plant, appropriately secured to each plant's authorized users, can do this
job.  It might be so complex to maintain that it's impractical, but in principle
it's possible.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: John Earl [mailto:johnearl@400security.com]
> 
> Mark,
> 
> "M. Lazarus" wrote:
> > 
> > John,
> > 
> > At 09:09 PM 3/28/00 -0800, you wrote:
> > 
> > > (Example: With AOA, how do you provide ability to view
> > > transactions with a VB application,
> > > but restrict the ability to download the entire file with
> > > FTP?)
> > >
> >  One way to handle this is w/ logical files.  Another way (in
> > the later versions of OS/400) is column level security.
> 
> Thanks for the only reply on this inquiry.
> 
> But a logical file will still allow you to view all records
> (transactions) in the view.  Unless you want to create (and
> secure) a separate logical file for every record in the PF (how
> ugly!!), logicals won't help.
> 
> Also, column level authority does not work for reads....  only
> updates.   And still, it seems like what people are really looking
> for is row level security, or a combination of row/column level
> security.  I still don't see how OS/400 object level security
> helps here.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---