|
Edwin, Hopefully you have change control procedures that mitigate your SQL embedded in applications. I would just upgrade to Operations Navigator or DB Visualizer for SQL and then you are covered. It may take a while to get used to but I wouldn't trade either of these tools for STRSQL. If you set the authority to RUNSQL to exclude QSECOFR with auditing, you should be able to detect if it was used. David Morris >>> EDavidson@xxxxxxxxxxxx 11/23/2004 12:09:31 PM >>> Wow, you've opened up our eyes. Thank you. That is a major issue. With that product, the goal is to lock down your system. While we see individual SQL commands in the log, your are right. STRSQL and SQLRPGLE is not logged. We are checking with the vendor. If I find anything out that says it WILL/CAN do this I will post back. Edwin Davidson
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
