Lee Gunter wrote:
>
> If NM File Close events are being logged (event 105), you should be able to
> track purged files.  <plug> We use Vesoft's 'VeAudit' for this purpose
> </plug>, but HP's LOGTOOL utility should be able to return the same
> (albeit, more verbose) information ("CLOSE DISP."=Delete).
<snip>
> I agree with Doug that such a capability would be advantageous, though.

Me too. Does anyone know (just looking for ballpark percentages here)
how much more space this will take up by turning on logging for NM File
Close? My concern here is that every time someone runs a program or
executes a command file, might that count as an open/close combination?
And if so, do all those events get logged as well, or is logging
restricted to programmatic (other than the CI) closing/purging of files?

We do log console messages, but also get the occasional request such as,
"Is there any way to find out who deleted this file?" which until now I
didn't know *could* be logged.

Guess I'll turn on logging for events 105 (NM fclose) & 160 (CM fclose)
when I get a chance and watch for a while, we'll just see what we see...

Patrick
--
Patrick Santucci
Technical Services Systems Programmer
KVI, a division of Seabury & Smith
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If they try to rush me, I always say, 'I've only got
one other speed -- and it's slower.'"    ~ Glenn Ford