I had the same problem under OS/2. When the ADSM scheduler is continual
run without a start stop anywhere the log doesn't get pruned. An easy
workaround was to schedule a batch file (on a very quiet Sunday) that
made a back-up copy of the log and then deleted it. Works just fine
(killing the schedule process was not an option, far too dirty).

Walter Ridderhof                                            Mainland
Sequoia, Netherland



Alex Fagioli wrote:

> You can try stopping the scheduler service and then deleting the log
> file and then starting the scheduler sevice again
>
> Alex