--> With your v5 clients you could try using the new client acceptor service ...

Maybe I am sticking to the word but both web client (with its
corresponding dsmcad binary) and managedservices option (with its
"schedule" value) were available before v5. I can find them in v4.2, v4.1
but no enough spare time to dig down since which version they were
introduced.

Maybe the memory leaks can contribute to restarts of the TSM Client
Scheduler sometimes. However we have Windows clients where the scheduler
is not restarting too often.
Have you verified isn't the restart of the service intentional?! When
schedules are managed by client acceptor you have two services - Client
Acceptor and Client Scheduler. The former is always running and
starts/stops the latter on each scheduled event. From there fake "stops"
can come (of course they can be due to other reasons).

Zlatko Krastev
IT Consultant






Stackwick <Stephen.Stackwick AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
31.07.2003 22:57
Please respond to Stephen.Stackwick


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Restarts of TSM services


Yeah, it happens all the time. Rumor has it that memory leaks are to blame
but who knows. The w2k
service restarts are a good work around. With your v5 clients you could
try using the new client
acceptor service which can manage the scheduler but maybe that will have
similar problems; still too
soon to tell IMHO.

Henrik Wahlstedt wrote:
> Hi,
>
> We are monitoring our w2k sp3 with pre-hotfixes sp4 servers with MOM (MS
> Operation Manager). And of course, we monitor TSM scheduler services
which
> generates an alert in MOM if a TSM service goes down. And they do that a
> little bit too frequently..  use repeat count in MOM.
>
> I am aware of w2k recovery of services i.e restart of services if it
fails,
> and I use it. I also use a simple registry setting to have TSM services
to
> be dependent on dnscache. But that are only work arounds to get it
working,
> not a solution that ends my minor problem.
>
> I would be happy if I found something in Eventviewer or dsmerror.log
> explaining why TSM services restart, but I dont.
>
> Have anyone else experienced this?
>
> Uhh I almost forgot, TSM client 4.1.2.12, 4.2.2.0, 5.1.6.0 and some
other
> flavours. TSM servers 5.1.7.0, 5.1.5.4, 4.2.2.8, 4.2.1.9.
>
> tia
> Henrik
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of
the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and
delete
> this message.
> Thank you.
>

--
Stephen Stackwick
The Johns Hopkins University
Applied Physics Laboratory
11100 Johns Hopkins Road
Laurel, MD 20723
Stephen.Stackwick AT jhuapl DOT edu