Although I manually "pruned" the log down to just a few days worth of info
yesterday (I only keep 10 days worth anyway, and QUIET is turned "on"), I
didn't delete it. I'll give this a try --- maybe this is a random bug with
the V3.1.0.0 scheduler...?

C.L.Cannam
Storage Management
GENAM/St. Louis, MO/USA
ccannam AT genam DOT com




Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG> on 07/15/98 09:10:54 AM

Please respond to dthorneycroft AT lacsd DOT org

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Cindy Cannam)
Subject:  Re: log pruning problem




We had this happen to one of our NT Clients. I deleted the dsmsched.log,
and during the next backup, a fresh copy was
created. The problem hasn't returned.


Cindy Cannam wrote:
>
> To all:
>
> Just in the last two days, one of ADSM's 3.1.0.0 clients has placed the
> following message in the SCHED.LOG:
>
> 07/13/1998 00:54:56 ANS1483I Schedule log pruning started.
> 07/13/1998 00:54:57 ANS1485E Schedule log pruning failed.
>
> The V3 Messages manual says to run the command with tracing on, but
doesn't
>  say which trace options are required,
> and what the syntax for the command would be to start log pruning on a
> specific client.
>
> Has anyone else seen this with NT/ADSM V3 clients so far? What did you do
> to resolve the problem? This is only one client
> out of three in this particular domain, but if this can happen to one,
it's
>  certainly waiting to happen to the other two!
>
> Thanks much!
>
> C.L.Cannam
> Storage Management
> GENAM/St. Louis, MO/USA
> ccannam AT genam DOT com