Telnet protocols

Telnet is the first and oldest TCP/IP terminal control protocol, originally defined in RFC854 back in 1983, to control a very primitive device. Telnet is a data stream protocol with the Telnet commands embedded in the data stream as escape sequences. Each side must merge its commands into the outgoing data stream. Each side must scan the incoming byte-stream looking for the Telnet commands.

TN3270, TN5250 and TNVIP are Telnet dialects. They are still basically the Telnet byte scanning protocol, with options that help overcome some of the disadvantages of using a byte-stream oriented protocol designed for dumb echo mode terminals, to control an intelligent block mode terminal device. They still require that a Telnet server be on the mainframe side, scanning the incoming byte stream, and decoding Telnet protocol.

Bull Protocols

For the Bull environment Glink Professional Edition supports the G&R/DSA gateway protocol connecting Glink to Bull mainframes via G&R/Ggate.
G&R DSA gateway protocol is by far the most efficient TCP/IP protocol for accessing Bull GCOS8, GCOS7 or GCOS6 mainframes. It maps directly into DSA, the GCOS internal protocol used by TP8, TSS, IOF, TDS and all other interactive GCOS applications, making G&R/Ggate the fastest and most efficient GCOS gateway on the market.

Ggate runs on UNIX, Linux and Windows server platforms making it uniquely scalable and adaptable in any network scenario.

Ggate connects directly into the Bull mainframes using the RFC1006 protocol over TCP/IP. It does not need to connect via a front-end, saving the cost of a MainWay.

For older Bull systems (or networks) Ggate can connect via a Datanet or MainWay using OSI Transport protocol over a LAN or X.25.