|
Dean Asmussen (DAsmussen@aol.com) wrote: >This is how IBM defines field-level security, although other platforms >provide more economical means to do so. How would you disallow physical file >access by a program using embedded SQL? This can be done by placing physical files in their own library that has public authority *EXCLUDE. The logicals remain in a normal production library. Users can still see the logical files, but only IDs specifically authorised to the PF library can see the physicals. This technique can also be used to block the compiler's access to the physical files and therefore guarantee that programs can only be built over logical files. DBAs should love it. Power. Power. :-) The downside of this of course is that you now have a cross library dependency and you have to make sure that you restore libraries in the correct order. Dave Kahn - TCO, Tengiz, Kazakstan ========= e-mail: kahn@tengizchevroil.com (until September 30th) dkahn@cix.compulink.co.uk (from October 1st) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.