This document describes the new features, changes and enhancements for Entire Connection Version 4.5.3. The following topics are covered:
Entire Connection Version 4.5.3 is a 32-bit application. When installed on a 64-bit Windows operating system, Entire Connection will run under WOW64. WOW64 is an x86 emulator that allows 32-bit Windows-based applications to run seamlessly on 64-bit Windows.
Entire Connection can be installed on the following operating systems:
Microsoft Windows XP Professional.
Microsoft Windows Server 2003 Standard Edition or Enterprise Edition.
Microsoft Windows Vista.
Microsoft Windows Server 2008.
Microsoft Windows 7 Professional.
Windows Terminal Services are supported with the following exceptions: they are not supported for the session types VTxxx serial port and HLLAPI.
For further information, see Prerequisites in the Installation section.
It is now possible to uninstall Entire Connection in silent mode and to do update installations in silent mode. See Silent Installation and Uninstallation in the Installation section.
Internet Protocol version 6 (IPv6) is now supported. You can enter TCP/IP addresses in the IPv6 format in the Communication dialog boxes which appear for the session types TN3270(E) (display sessions and printer sessions), Telnet VTxxx and BS2000 TCP/IP. For further information, see Communication Parameters in the Overview of Object Properties.
Telnet SSH for sessions of type Telnet VTxxx is now supported. This allows a secure connection between Entire Connection and a server. For information on how to set up SSH in your environment, see Telnet SSH Support in the Installation section.
You can specify all required information (such as the SSH authentication methods) in the Communication dialog box which appears for the session type Telnet VTxxx. See the description for Telnet VTxxx in Communication Parameters in the Overview of Object Properties.
When you start a secure host session in the terminal application, a dialog box appears in which you have to enter your user ID and password. See also Starting a Host Session in the section Terminal Emulation.
When you are working with a secure host session in the terminal application, a lock icon is shown in the status bar. See also Displaying Security Information for an SSL or SSH Session in the section Terminal Emulation.
It is now possible to edit a key scheme in a more comfortable way, using a graphical representation of a keyboard. See Key Schemes in the Overview of Object Properties.
In addition, it is now also possible to manage the key schemes for the current session directly in the terminal application. See Modifying the Key Scheme for a Host Session in the section Terminal Emulation.
It is now possible to change the translation settings for the current session directly in the terminal application. See Changing the Translation Settings for a Host Session in the section Terminal Emulation.
When specifying a file name using the SET command, it is now possible to use an environment variable which contains a part or all of filename. For example, SET PCFILE 7 DOWN DATA %TEMP%\mydata.ncd. For further information, see
Specifying a File Name Using the SET Command in the section Terminal Emulation.
The section Other Events, Key Codes and Return/Error Codes now lists the key codes that can be passed using the PutData function, and the possible return/error codes.
The error messages have been revised and are now listed (with explanation and action) in the new Error Messages section.
The session type VT100 Protocol Converter is no longer supported. All references to this session type have been removed from
this documentation. This also includes the description of the system variable UPLPSIZE.
The option Disable data transfer enhancements on the Data Transfer page of the session properties will no longer be supported in the next version.
The option Interpret as Entire Connection 3.1 translation table on the National page of the session properties will no longer be supported in the next version.
Entire Connection Version 4.5.3 is the last version to support the Multiplan file format. This file format will no longer be supported in future versions.