Hi Eric,

I know that SP 6 changed the start order of services. This sometimes caused
third party services, like the TSM Scheduler, to fail to start correctly on
boot. We resolved these issues by either migrating to Win2K or using scripts
after boot to check the services and start them. This is a "feature" of NT 4
SP 6 and it impacts a variety of software in my experience.

Eric W. Cowperthwaite
EDS

 -----Original Message-----
From:   Eric Winters [mailto:ewinters AT AU1.IBM DOT COM]
Sent:   Friday, July 19, 2002 1:33 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        TSM Scheduler on NT not autostarting

Good Day TSMers,

Has anyone seen problems in autostarting the TSM Scheduler on NT 4.00? It
starts fine manually but is not starting automatically on boot up (although
it is configured to do so).

TSM Server: 4.1.5.2 on AIX 4.3
TSM Backup client 4.2.2 on NT 4.00 SP 6.

There are two scheduler services, both pointing to the same TSM Server but
each one created by running dsmcutil in a different 'baclient' directory
(ie different dsm.opt files with different nodenames). As I say, these can
be started manually without any problem, but after a reboot they do not
start and there is nothing in the event viewer, nothing in the dsmerror log
or the dsmsched log. The services are run by the system user.

Any suggestions are very welcome.

Thanks team,

Eric Winters
Sydney Australia