With the 5.3 baclient, a new parameter was introduced to limit the size of the logs
schedlogmax errorlogmax Also, previous parameters pruned the size of the logs in terms of days schedlogretention errorlogretention The juicy nuggets are generally in the dsmerror.log. Using a pattern searching tool like 'grep' or 'find' will ease your trawling through the logs. However, I am not aware of any method to control the verbosity of the dsmsched.log. Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Angus Macdonald Sent: 29 September 2006 09:59 To: [email protected] Subject: [SPAM: 4.000] [ADSM-L] Is it possible to limit what goes into the schedule log? I'm just implementing TSM 5.3. Is it possible to limit what goes into the BA client log file (dsmsched.log)? I really don't need to know every single file that is processed successfully. Exceptions or folders only would be fine. A typical client log is over 100MB a day so I either have to rollover a lot or trawl through a vast mass of irrelevance to get to the juicy nuggets. Angus
