InfoConnect for Unisys
TelnetKeepAlive Property


Attachmate.Reflection.Emulation.IbmHosts Namespace > IIbmTerminal Interface : TelnetKeepAlive Property
Gets or sets a value indicating whether to periodically poll the host to determine if Telnet connections remain active during intervals when you are not sending data to the host.
Syntax
'Declaration
 

Property TelnetKeepAlive As KeepAlivePacketsOption
'Usage
 

Dim instance As IIbmTerminal
Dim value As KeepAlivePacketsOption
 
instance.TelnetKeepAlive = value
 
value = instance.TelnetKeepAlive
KeepAlivePacketsOption TelnetKeepAlive {get; set;}
Exceptions
ExceptionDescription
Attachmate.Reflection.SecuredSettingException This exception is thrown when you modify a property that was secured via the Permissions Manager or that can only be modified by an Administrator.
Remarks
Normally, InfoConnect becomes aware of Telnet communication problems only after a significant delay, or when it attempts to send data to the host. Because of this, you can lose your connection to the host and not be immediately aware of it. This can cause problems if you enter a large amount of data on one screen, or if you keep your connection open during periods of inactivity.

To become aware of connection problems as they occur, you can configure InfoConnect to send Keep Alive packets.

  • InfoConnect does not send any keep alive packets to the host. (The default.)
  • InfoConnect periodically sends a No Operation (NOP) command to the host. The gateway and host are not required to respond to these commands, but the TCP/IP stack can detect if there was a problem delivering the packet. Use KeepAliveTimeout to control the interval between requests.
  • The TCP/IP stack keeps track of the host connection. This value requires less system resources than KeepAliveTimingMark or KeepAliveNOP, but most TCP/IP stacks send Keep Alive packets infrequently.
  • InfoConnect periodically sends a Timing Mark Command to the host to determine if the connection is still active. The gateway or host should respond to these commands. If InfoConnect does not receive a response or there is an error sending the packet, it will shut down the connection. Use KeepAliveTimeout to control the interval between requests.
See Also