If ATS was launched as an application, you can shut it down from its user interface just as you would for any normal Windows program.
Shutting down the ATSD server does not have any effect on A-Shell sessions which are currently active. It just prevents new ATS sessions from being accepted.
If you shut down ATSD and then wish to restart it, you may have to first close all the A-Shell sessions that were started by the prior instance of ATSD. Failure to do this will not affect your ability to restart ATSD, but it may prevent new sessions from becoming connected. This is due to a peculiarity of Windows NT, and possibly of W2000 and XP, in which the socket used to accept connections is not actually freed up until all the child processes that were accepted via that socket have exited. The new instance of ATSD will open up the socket (e.g. 23) and listen for connections, but the operating system may still be routing incoming data for that socket to a still-active handle left by the previous instance of ATSD. (You could, however, workaround that problem by changing the port # used by ATSD, but that would of course require reconfiguring the client Telnet connections as well.)
If you launch ATSD as a service, then you should use the Services Applet to shut it down. The comments above about the effect on existing sessions and the ability to restart it apply here as well.
Note that even if you launch ATSD via the Services Applet, that doesn’t prevent you from shutting down ATSD.EXE directly from the ATSD.EXE user interface (assuming that UserInterface=Yes in the ATSDSRV.INI file.) If you shut down ATSD.EXE in that way, the Services Applet will not realize that the service has been stopped. To avoid that confusion, always use the Services Applet to start and stop the service.
