From: Charlotte Brooks
*** Resending note of 05/27/97 08:05
RISC System/6000 Specialist
Sydney, Ph 61-2-9353-3437, FAX 61-2-9353-3604
Subject: Schedule log pruning failed
Re:          Schedule log pruning failed

I saw this recently, where the options file had pointed the schedule
log at a particular directory, which didn't exist on the client. So,
the schedule log was created in the home directory of the user running
the scheduler (in this case /, as it was a UNIX system, and the root
user was running). But, the pruning process still looked for a file in
the directory specified in the options file, didn't find it and failed
with similar error messages to what you're seeing. So, check that the
directory you specified for location of the SCHEDLOG does exist, is
writeable etc.
Hope this helps ...
Regards - Charlotte

> Does anyone know what kind of thing causes this error:
> 05/23/1997 02:53:09 ANS4483I Schedule log pruning started.
> 05/23/1997 02:53:09 ANS4485E Schedule log pruning failed.
> I see it on both NT and OS/2 clients.
> Thanks..
> Julie Phinney
> JULPHINN @ EMPHESYS.E-MAIL.COM