Line Mode in Telnet-and Why

Do you know that OutsideView Offers you a Choice of Telnet “Flavors” and your Selection is Important?

By default, OutsideView comes configured to use Telnet, a standard networking transport protocol. However, Tandem developed a proprietary form of Telnet for their NonStop hosts – Telnet 6530 (also known as line mode). Although NonStop hosts support both Telnet variations, there are some significant differences between Telnet and TN6530!

Standard Telnet is a character at a time protocol; each keystroke travels to the host independently. Bottom-line is that Telnet is a faster protocol – but does not do as well with type-ahead, and shouldn’t be used when data is being entered during conversational mode.

TN6530 uses local buffering and error-checking routines. This makes it more reliable, but slower. Bottom line here is that you should use TN6530 (AKA Line mode) for better type-ahead support, don’t mind a slight hit in performance, or if you do any form of data entry within conversational mode.

There are a variety of ways to specify which transport to use.

• You may set the default value for all future sessions by going to Session New Session Settings, and setting the check box for “Allow Negotiation of Line Mode”. Check this box for TN6530, or leave it unchecked for Telnet.
• You may also set this value while defining individual new sessions by selecting the category ‘Protocol’ and checking or unchecking the “Allow negotiation of Line Mode” switch.
• Finally, you may modify this setting in existing session (.cps) files, by going to Session, Session Settings, Protocol Category and setting or resetting the “Allow negotiation of Line Mode” switch. (Don’t forget to save the redefined session!)