×
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.
Hi Ken,
<snip>
If Larry and I worked at the same company, and he used his utility to take
over one of my jobs and had it delete an object, then *I* deleted the
object. If object auditing is turned on and you looked the audit record for
the deletion, it would show deleted by me. There would be no clue that Larry
was the one who instigated it, except the program name might show the name
of his exit program, but even then there would be no way to know from that
audit record who it was that actually used the utility.
</snip>
...and the deletion of the object caused the application to crash, and the
company lost $millions? Would you still insist that "you" deleted the
object? :-)
I agree with you about the way it works, I wont argue that point - on a
system level it's the user running the job that performs the action. Or
rather, the action is performed under the user profile that runs the job.
I've never argued otherwise. The problem here, as you pointed out, is that
the audit trail is broken - that's the big security concern for me. You'd
have to prove it "wasn't" you that deleted the object when all evidence
indicates that you did.
Having said all that, it's been a really useful tool for me over the years
(whichever way it works). It can still bel useful, even if it's only used as
a development tool - to help debugging batch jobs.
This is quite a good topic. Makes you think.
Have a good weekend.
Cheers
Larry Ducie
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.
midrange.com
