6530
Terminal Server Support FAQS
Yes, both block and conversational modes are fully supported.
Pathway applications are fully supported.
None whatsoever. The server process software emulates the standard Guardian terminal process. As a result, no application changes are required to utilize it.
Yes. Workstations running 6530 emulators may be connected to a terminal server and transact transparently with the host as a 6530 terminal.
Dial in users can be accommodated via TCP/IP terminal servers equipped with modems. The terminal server would provide the capability of encapsulating the terminal traffic into TCP/IP TELNET packets. The server software transparently delivers the transactions to application software.
You can entirely eliminate the requirement for the set of terminal servers at the host end as well as the requirement for all of those serial ports.
Terminal servers would still continue to be used at the terminal locations, but their traffic would go directly into the host using TCP/IP over Ethernet. Our server would handle the correct routing of traffic to application software.
Stated differently, all the host end terminal servers and serial ports are replaced by an Ethernet controller and host software.
Because competing products require the use of a specific manufacturers' terminal server equipment.
This product employs no proprietary technology whatsoever. Standard TCP/IP TELNET protocol is employed. As a result, virtually any terminal server manufacturer's product may be employed.
Our view has always been that Open Systems Standards should mean open products.
We have always supported UB products as well as others such as 3COM, XYPLEX, and others.
In other words, we believe that "Open Systems" means "open products" and the customer should be free to choose the specific products to be employed without concern as to proprietary traps.
A product demonstration at your site can be easily arranged.