| Title: | DECtp Desktop for ACMS |
| Moderator: | UCROW::GIBSON |
| Created: | Mon Sep 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 859 |
| Total number of notes: | 3034 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 59.1 | Desktop ACMS won't provide failover, but you could | SOJU::QUINN | Tim - EIS/E Cross-Industry EIC | Mon Apr 15 1991 22:53 | 35 |
| 59.2 | Clarification of Routing Slide 17 | ACESMK::RLEE | Wed Jun 26 1991 12:28 | 10 | |
| 59.3 | ACMSDI$SERVER requires at min ACMS Remote kit | ACESMK::RLEE | Wed Jun 26 1991 16:14 | 7 | |
| 59.4 | Does the Server live on ?? | FUTURS::CROSSLEY | For internal use only | Wed Apr 02 1997 11:33 | 10 |
Does anyone have any information as to what happens to the server if
the client looses the use of one particular desktop ??
Does it die instantly, or does it continue processing then die ??
Regards,
Ian.
| |||||
| 59.5 | UCROW::GIBSON | Wed Apr 02 1997 13:10 | 8 | ||
If the server refers to the ACMS Desktop server, (the ACMS agent) and the
client is the PC. The server normally has a read posted to the client,
if it detects an error such as loss on network connection, it would log
the error to the SWL log, disconnect that client and continue
processing other clients. It should not die, but the "thread" that was
handling that particular client will shutdown.
/Tom
| |||||
| 59.6 | FUTURS::CROSSLEY | For internal use only | Thu Apr 03 1997 03:59 | 4 | |
Thanks Tom,
Ian.
| |||||