hi, what about the missing "D" (as for days) behind 7 ?
goran ----- Original Message ----- From: "Large, M (Matthew)" <[EMAIL PROTECTED]> To: <ADSM-L@VM.MARIST.EDU> Sent: Tuesday, September 12, 2006 1:48 PM Subject: Re: Log prune on non-standard log names? Hi Richard, The filename is as it states in the first mail - dsmsched_1yr.log - unfortunately they've deleted it as they needed to free up space. It was definitely the schedule log, and besides, wouldn't the setting ERRORLOGRETENTION manage the dsmerror.log file? (which is also set to 7 days) I think we'll upgrade to 5.3.x soon so we'll just use the SCHEDLOGMAX setting along with the SCHEDLOGRETENTION to ensure that these file sizes to not become unreasonably sized. Cheers, Matthew -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 12 September 2006 12:05 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Log prune on non-standard log names? On Sep 12, 2006, at 3:27 AM, Large, M (Matthew) wrote:
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
.. Matthew - Get the specifics ... the file name, and latest timestamp (for context). What they're looking at may be a dsmerror.log file, which can be large as it accumulates endlessly over time - ignored until it gets huge. If some other log, its timestamp will provide evidence as to what is writing to it, in terms of scheduled or invoked events. Richard Sims _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________
