How do you set pruning on the logs mine are growing out of control!



> -----Original Message-----
> From: Mathew Warren [SMTP:MWarren AT TANDB.CO DOT UK]
> Sent: Thursday, October 01, 1998 11:59 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Schedlog pruning
>
> Hello people,
>
>
> I have a question on the schedule log pruning. We run backups
> triggered from a scheduled script. The script writes to the same file
> as the schedlogname parameter in the dsm.sys so the scheduler and the
> backup details are all in the same file.
>
> Now, for the last couple of weeks the logs have looked something like;
>
>
> 09/25/1998 02:30:12 Querying server for next scheduled event.
> 09/25/1998 02:30:12 Next operation scheduled:
>
> {Scheduled op details}
>
> Executing scheduled command now.
>
> {Output from backup script}
>
> 09/25/1998 02:38:24 Finished command.  Return code is:
>    0
> 09/25/1998 02:38:24 Scheduled event 'WGC20' completed successfully.
> 09/25/1998 02:38:24 Sending results for scheduled event 'WGC20'.
> 09/25/1998 02:38:25 Results sent to server for scheduled event
> 'WGC20'.
>
> 09/25/1998 02:38:25 ANS4483I Schedule log pruning started.
> 09/25/1998 02:38:25 Schedule Log Prune: 104 lines processed.  0 lines
> pruned.
> 09/25/1998 02:38:25 ANS4484I Schedule log pruning finished
> successfully.
> 09/25/1998 02:38:25 Querying server for next scheduled event.
> 09/25/1998 02:38:25 Next operation scheduled:
>
> etc...
>
>
>
> This morning though, there was no initial 'Executing Command Now'
> section, no output from the backup script, BUT there was this;
>
> 10/01/1998 02:38:47 Schedule Log Prune: 105 lines processed.  105
> lines pruned.
> 10/01/1998 02:38:47 ANS4484I Schedule log pruning finished
> successfully.
> 10/01/1998 02:38:47 Querying server for next scheduled event.
> 10/01/1998 02:38:47 Next operation scheduled:
>
> {details of next event}
>
>
> Does this mean that the lines I needed (Output from backup script)
> have been 'Pruned' out?  How is pruning controlled? what does it
> prune, and why did it prune out the details in this log and not any
> others?
>
>
> Any help much appreciated,
>
> Matthew Warren.
>
> (Sorry for the T&B Gubbins below. NMF)
>
>
>
>
>
>
> ** IMPORTANT INFORMATION **
> This message is intended only for the use of the person(s) ("the
> Intended Recipient")
> to whom it is addressed. It may contain information which is
> privileged and confidential
> within the meaning of applicable law. Accordingly any dissemination,
> distribution, copying
> or other use of this message or any of its contents by any person
> other than the Intended
> Recipient may constitute a breach of civil or criminal law and is
> strictly prohibited.
>
> If you are not the Intended Recipient please contact the sender and
> dispose of this email
> as soon as possible. If in doubt contact the Tibbett & Britten Group
> Network Administration
> Department on 01707 391010 (UK).