|
I missed the first part of the conversation so I apologize if this has already been covered. Wouldn't this be where journaling would come in? It's been a while since I looked into a receiver but I think it will tell you how the file changes were made. Rick -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Al Barsa Sent: Friday, July 08, 2005 9:11 AM To: Midrange Systems Technical Discussion Subject: Re: Auditing of SQL Statements via STRSQL Jim, There is no way to audit SQL, but on the other hand, there is no way to audit an RPG program. We could always ask IBM for a way to audit any database change, but how much would you be willing to pay for that? I don't think that this is a reasonable request. >From a SOX perspective, that could easily double the size of your system, and plausibly raise it to a high multiple. Strikes me that the SOX people are just nuts. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Norbut, Jim" <Jim.Norbut@Grubb -Ellis.com> To Sent by: "midrange-l" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s+barsa=barsacons cc ulting.com@midran ge.com Subject Auditing of SQL Statements via STRSQL 07/08/2005 09:09 AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I can see where I am able to turn on "auditing" of commands that a user types in QAUDJRN on a user by user basis. Is there a way to log/audit things done in SQL via STRSQL and typing in commands that way to update tables. (This is in response to a request re: Sarbanes/Oxley.....not for a rogue user who we are watching) Thanks, Jim -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
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.