ADSMer's,

     I'm having a problem on an NT client (4.0).  Running V3R1L0.5.
Although I do NOT have the option set to save pruned entries from the
DSMSched.log or DSMError.log files, ADSM is creating a DSMPrune.pru anyway.
This file grows to 2 GB within a couple of days, until NT can no longer
write to the file.  Then the ADSM service hangs, and backups are not taken.
I have to stop the service to delete the file.  Has anyone seen this
before.  I do have other machine's running V3R1L0.5 and this is not
occuring on them.  Any help would be appreciated.

Thanks,

Rick