× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Once you've written one it isn't that difficult. The devil is in writing that first one to industrial grade standards.

Gary Monnier


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Wednesday, June 20, 2012 8:26 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: How to audit users of strsql?


Luis, I'm not sure how to work with exit points, how involved a pgm would be needed?


-----Original Message-----
From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wed, Jun 20, 2012 9:56 am
Subject: Re: How to audit users of strsql?


Frank,
IIRC, working with SQL sessions is a real PITA. Also, a user could bypass t easily using RUNSQLSTM, SQLRPGLE, etc.
What happens if you try to work with SQL's exit points?

est Regards,
Luis Rodriguez
BM Certified Systems Expert — eServer i5 iSeries
-


n Wed, Jun 20, 2012 at 9:14 AM, <fbocch2595@xxxxxxx> wrote:

Hi Y'all, for you folks that allow programmers to use strsql, how do you audit them? My interest is in knowing the statements they run and what data is changed via their strsql sessions. Is it possible to force session info to be generated upon their every use of strsql? I'd like to force an sql session upon every strsql usage and then make sure that session can not be deleted. I think there's 3rd party software that will help but we'll go the native OS route for now.

Any suggestions/recommendations?

Thanks, Frank
--
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.


-
his is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list o post a message email: MIDRANGE-L@xxxxxxxxxxxx o subscribe, unsubscribe, or change list options,
isit: http://lists.midrange.com/mailman/listinfo/midrange-l
r email: MIDRANGE-L-request@xxxxxxxxxxxx efore posting, please take a moment to review the archives t 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.