Tony,

The ADSM Scheduler service stopping, sounds like a problem. As others have
stated, the logs may give you some insight  as to what the problem is.

The ADSM Remote Client Agent stopping is "working as designed". With the
ADSM Web client, the ADSM Client Acceptor service will start the ADSM
Remote Client Agent when it is needed, and the ADSM Remote Client Agent
will stop when it is no longer needed (after a specified amount of idle
time). Also, you should not set the ADSM Remote Client Agent to start
automatically... only the ADSM Client Acceptor service should be started
automatically.

Regards,
       Robert Edwards                                 TSM Development
       rob AT us.ibm DOT com


Larry Way <Larry.Way AT TRW DOT COM>@VM.MARIST.EDU> on 02/24/2000 11:18:31 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: ADSM Client on NT



What does the NT event log say about the ADSM scheduler service stopping?

Larry Way
SL09/100D
408-743-4242  voice
408-743-4201  fax

>>> JULEST AT OLYMPUS DOT COM 02/24/00 05:33AM >>>
I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4
Servers. I noticed that both the ADSM Remote Client Agent and ADSM
Scheduler services stop by themselves. Their Startup option is Automatic in
case the Servers had to be reboot. Any idea why this is happening?

Any help will be greatly appreciate.
Thank you

Tony Jules
Olympus America Inc.
ITS Department
516-844-5887
julest AT olympus DOT com