The information is stored IN the file header (see the Stats region if you have access to the internal file documentation). And the performance hit comes when you close the file and all the numbers you collected over time (in memory) is added to the header values, which means you lock down the ENTIRE file (group 0) during that time. It's not meant to be kept on for long periods of time.

At 12:59 PM 11/18/2004, you wrote:
I've never used FILE.USAGE. Where can I find out more information such as where the information is stored, is there much of a performance hit while using it, etc...

Thanks

-------------- Original message --------------

> You can certainly collect statistics on the number of writes, deletes,
> clear-files, etc., using the FILE.USAGE group of commands.
> FILE.USAGE.CLEAR to reset statistics and enable collection
> FILE.USAGE.OFF to disable further collection
> FILE.USAGE to view statistics
>
> This does not identify the culprit. However, we once used it to prove that a
> file was being cleared (by a rogue ex-employee, as it turned out, who was
> successfully prosecuted) even though the owners of the application swore blind
> (and could prove) that nowhere in the application was the file cleared.
> -------
> u2-users mailing list
> [EMAIL PROTECTED]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to