Hot Diggety! Thomas Denier was rumored to have written:
>
> It depends on the purpose of the log files. Some applications append

When put in that way, does make a lot of sense why the TSM behavior would
be have options to control that.

Fortunately, the log files in question is non-database, and used for
accounting; works by continually appending entries.

> planning, or accounting. This type of log can usually be dealt with
> by using an include statement in the include/exclude file to bind the
> log to a management class whose backup copy group is defined with
> 'serialization=dynamic'. This will cause TSM to read the file once

Groovy, thanks. (Also appreciated the other poster whom also suggested
looking at the serialization options.)

-Dan Foster
IP Systems Engineering (IPSE)
IP Systems Engineering (IPSE)
Global Crossing Telecommunications