This has happen to us every so often that the sched log does not get
prune.  Usually if I restart the Schedule process in the control panel
services panel, the log file will trim it self correctly.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David McClelland
Sent: Tuesday, September 12, 2006 2:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Log prune on non-standard log names?

Hi Matthew,

Is your customer's TSM client scheduled using the TSM Central Scheduler
(I guess so if it's growing to over 100MBs) for backup operations? This
kind of log pruning only happens during a TSM scheduled backup operation
Hi All,

One of my customers recently came to me to say that they had a 100MB log
file from TSM sitting in their file system, which confused me since the
setting clearly stated in the options file (Win2K) says    

SCHEDLOGRETENTION  7
schedlogname    dsmsched_1yr.log