| I agree with Dominique, I spoke with several customer in the St. Louis area a few
weeks ago and they all had the same need to know (by an event not a poll) if a
Terminal Server has crashed. They were pretty unhappy with the inability of any
DEC products to track TSs. In many cases, these customers have very large populations
attached via terminal servers and when one goes down they experience major outages
and user idle time. They were also very unhappy with the downline load scenrios
created by a building power failure where the TSs can not be loaded fast enough due
to limitations in VMS/NETACP/MOM. That is not an DECmcc issues, it is a DECnet-VAX
issue, but may affect customer perception of the effectiveness of DECmcc to
manage the Terminal Server environment (or any thing requiring DLL).
So please put events high on your futures list.
Thanks, Claudia
|
|
You must be using DECwindows VAXnotes, Claudia... Your text is wrapping past
the 80 column boundary and it's not readable from an 80-column DECterm.
(I've noticed this in a couple of replies from you today.)
This can be kind of a nuisance if they're not running DECwindows notes,
(or have a horizontal scrollbar on their DECterms) as people will either
need to infer what you typed or set their terminals to 132-column mode.
I _did_ say it was a nit.
Mea culpa.
/doug
|
|
re: .1
Again, the request for the functionality has been added to the
wish-list for TSAM enhancements.
If you are asking for new functionality in the terminal servers
themselves, I would suggest entering a note in either the LAT
or the new TOOK::TERMINAL_SERVERS notes conferences. The
TSM notes file also discusses management of terminal servers.
Lynne
|