|
For those "grandfathered" aps that you've used and trusted you can also compile them to have a special authority without compromising security. -------------------------------------------- Booth Martin MartinB@Goddard.edu 802-454-8315 x235 -------------------------------------------- -------Original Message------- From: rpg400-l@midrange.com Date: Wednesday, October 31, 2001 02:45:27 PM To: rpg400-l@midrange.com Subject: Re: Record level security Great idea. Just might take some tinkering on apps which currently access the data. Those vendor apps can be tricky. Rob Berendt "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Rusling, John B. (TC)" To: rpg400-l@midrange.com <JBRusling@taylor cc: corp.com> Fax to: Sent by: Subject: Re: Record level security rpg400-l-admin@mi drange.com 10/31/2001 02:29 PM Please respond to rpg400-l Use External Stored Procedures as the front end to the file. Allow only the procedure the authority to access teh file. The companies programs can call the procedure only not the file. Do your own filtering inside the stored procedure to allow who sees what. http://www.redbooks.ibm.com/redbooks/SG244249.html John B. Rusling (TC), 386-3183 _______________________________________________
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.