Re: field level security - (Was Use of a trigger...? ....)

It depends on how you define traditional.
Logical files have been around for a long time.
SQL has been around for a long time.
And I have a Systems Analyst text book from college that recommended
staying away from upstart languages like RPG.

How would you have had them handle it?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Richard B Baird"
                    <rbaird@esourceconsu       To:     midrange-l@midrange.com
                    lting.com>                 cc:
                    Sent by:                   Fax to:
                    midrange-l-admin@mid       Subject:     field level 
security - (Was Use of a trigger...? ....)
                    range.com


                    01/24/2002 04:53 PM
                    Please respond to
                    midrange-l







Rob,

Like I said, I had never used field level security, nor seen it used.  only
heard it was available.  Just throwing it out there as a possibility.

so, you're saying that all traditional means of getting data from the file
would have a hard error trying to access that field without authority?

that's an elegant solution.....
not.

rick

--original message--

Richard,

Think of it this way.  You have a traditional RPG program.  You loathe
selecting fields with logical files or SQL.  Now you read a file which
contains a field of which you are not authorized to - by the way it is this
field for every record.  Therefore every read will be an error.  The
workaround is to either create a view or logical file which omits these
secured fields, or avoid traditional RPG i/o and use SQL to
if superuser;

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.