Our IT department is asking for an exit program (based in IBM's direction)
to block ODBC access from Run SQL Scripts and other programs and only allow
a 3rd party SQL tool and our application through. IBM pointed then to exit
points but will not be more specific without a services contract. The 3rd
part tool is basically Run SQL Scripts but with extra logging and user
control (i.e. read-only queries). Our application uses either JDBC from
Java or ODBC from PHP to access the database.

I've looked into the exit points and found one that may help. I've also
seen comments about using special registers to know which app is calling.

My Google skills are failing me in finding anything useful. Is there any
good all in one write up on this process?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.