hamm@BIOVAX.RUTGERS.EDU (06/27/87)
Where I used to work, we had a simple all-DEC environment. Life was easy if not always good. Terminal servers spoke LAT, obeyed their VAXen, and IP packets were exotic creatures who lived far away. Now I'm in the real world, and have to futz around with terminal servers which use PCs to manage them, don't know much about VAXen, and certainly don't speak LAT. They do, however, speak IP, and so can speak (sort of) to VAXen and lots of other stuff, and I have to have this capability. This requires me to run ugly software (which shall remain nameless) on my VAX, though, and just generally doesn't work as well as the good old days. What I'd like to see is the 'DECserver-xxxx'. Like all the other DECservers, this would be loaded, managed, and monitored from VAXen, would support all the DEC native stuff like LAT - *but* it would also understand different protocols (specifically TCP/IP, possibly others) and would allow a system manager to specify which protocol should be used for each of the services offered. I'd buy several of these *tomorrow* if they existed. Is this for some reason a silly or impossible idea (in which case explain gently), or would others find this useful as well? Does anyone see any hope of such a product? Just wondering... Greg ------------------------------------------------------------------------------ Greg H. Hamm || Phone: (201)932-4864 Director, Molecular Biology Computing Lab || Waksman Institute/NJ CABM || BITNET: hamm@biovax P.O. Box 759, Rutgers University || ARPA: hamm@biovax.rutgers.edu Piscataway, NJ 08854 * USA || ------------------------------------------------------------------------------ ------