Release Notes: DynaComm Connectivity Series 9 Release Version: 9.3.0 Release Date: March 31, 2010 ================================================================================ Please review this document carefully, these notes contain last-minute product information that may affect your use of the product. ================================================================================ Contents This document contains the following sections: 1.0 Product Overview 2.0 New In DynaComm Connectivity Series 9 3.0 System Requirements 4.0 Notes on DynaComm Connectivity Series 9 5.0 Updated, Implemented or Fixed in This Release 6.0 Technical Support ================================================================================ 1.0 Product Overview These Release Notes include information relevant to DynaComm Connectivity Series * Key Features Multi-session capabilities; custom keyboard mapping; OLE compliance; custom toolbar editor; web-to-host connectivity; custom menu editor; ActiveX support; custom hotspot editor; standalone FTP component; event-driven scripting language; Euro symbol support; HLLAPI programming language support; URL user file addressing; Visual Basic(r) Interface (VBI) * Emulations Base Product: ADDS Viewpoint/60; TeleVideo 925/950; ANSI/TTY/SCO-ANSI; Digital VT 52/100/102/220/320/420; AT&T 605/705; Wyse 50/60; AT&T 4425; IBM TN3270; HP 700/94; IBM TN5250; Tandem 6530 Client Options: IBM TN3270; IBM TN5250 * File Transfers: Kermit; FTP; XYModem IXF (with Tandem 6530 Client Option installed); ZModem; IND$FILE (with TN3270 Client Option installed) * Connectors: Direct Serial; Telnet; Meridian LAT32; Trace Player; Modem (TAPI) SNA Server (with TN3270 Client Option installed); SSH To view the latest information on any of the above, visit our web site: www.futuresoft.com ================================================================================ 2.0 New In DynaComm Connectivity Series 9 * Transport Layer Security (TLS) protocol for TN3270 * New script functions for the TN3270/TN5250 emulation supporting TLS * New option for SEND command for TN3270/5250 emulation supporting TLS * New strings/keywords for the EMULCONFIG and CONNCONFIG scripting commands supporting TLS ================================================================================ 3.0 System Requirements 3.1 DynaComm Connectivity Series, requires one of the following: - Windows 2000 Professional - Windows 2000 Server - Windows XP Professional - Windows 2003 Server - Windows Vista - Windows 2008 Server 3.2 Client Options All add-on Client Options require installation of the DCS 9 base product. ================================================================================ 4.0 Notes on DynaComm Connectivity Series 9 and all add-on Client Options 4.1 General 4.1 Starting DCS 9 from a command line. When starting DCS 9 from a command line, a file may be specified by using local pathing or URL addressing (session [.SES] files only). Verify the proper extension is included in the file name as follows: .SES (session), .DCM (memo), .DCP (script), or .DCT (compiled script). 4.2 Session file compatibility. All session files created in DCS 7.1.0.2 and up are compatible with DCS 9. However, session files created in DCS 9 cannot be used in DCS 7.1.0.4 and earlier. 4.3 Documentation * DCS 9 technical library includes the following: - DCS 9 Online References Master (contents.hlp and contents.cnt) - DCS 9 Administrator Online Reference (admnref.hlp and admnref.cnt) - DCS 9 Web Programmer Online Reference (dcsdtc.hlp and dcsdtc.cnt) - DCS 9 Web SDK Online Reference (dcsweb.hlp and dcsweb.cnt) - DCSeries Online Reference (dcseries.hlp and dcseries.cnt) - DynaComm Multi-user Administrator (DMA) Online Reference (dma.hlp and dma.cnt) - FTP Online Reference (fsftp32.hlp and fsftp32.cnt) - HLLAPI Online Reference (hlapcnfg.hlp and hlapcnfg.cnt) - Script Language Online Reference (script.hlp and script.cnt) - Visual Basic Online Reference (vbclient.hlp and vbclient.cnt) - Getting Started for Users (gs.pdf) - Getting Started for Administrators (gsadmin.pdf) - Script Language Reference (scriptref.pdf) - Getting Started: Using DCS 9 Web with VB and Microsoft FrontPage (Getting Started.doc) - DCS 9 Readme (readme.txt) - DynaComm Multi-user Administrator (DMA) (rdmedma.doc) * All items are provided on the installation CD-ROM in the /documentation folder. * The most current documentation is available for download from the FutureSoft web site at: www.futuresoft.com/documentation. * Send any documentation questions, errors or corrections to support@futuresoft.com. * Printed documentation can be obtained by contacting your FutureSoft Account Manager at 1-800-989-8908. 4.3 Installation/Setup/Uninstallation Program group name change with DCS 9 DCS 7.1.0.4 and earlier versions are installed under the program group name of "DCS" or "DynaComm Connectivity Series". The program group name has been changed to "DynaComm Connectivity Series 9". To avoid possible version incompatibilities, uninstall any DCS 7.1.0.4 or previous version of DynaComm Connectivity Series before installing DCS 9. If you install DCS 9 without removing a prior version, both program group names are shown. During an uninstall an error message may appear that states that the uninstall program cannot unregister certain files. This occurs due to a timing issue of the uninstall processes. Continue by clicking OK. The unistall will complete successfully. 4.4 Evaluation version installs An evaluation copy is good only for 15 days after the first date of installation. If you need to extend the evaluation period or you receive an error message during an evaluation version install, call your FutureSoft Account Manager at 1-800-989-8908. 4.5 Command-line options for installing DCS 9. The following command line arguments may be used when installing DCS 9: setup -r Causes SETUP.EXE to automatically generate a silent installation file (.ISS file), which is a record of the installation input, in the Windows folder. 4.6 Older versions of shared files. DCS 9 may require newer versions of some files to run correctly. If DCS 9 encounters older shared files during installation, a Question dialog box appears asking if you would like to replace the existing file with the newer copy. Click Yes. The installation program places a copy of the old file in the Shared directory with the same name as the original file. In the event that the newer version of the shared file interferes with your existing software, the older version of the file is still available for your use in the Shared folder. 4.7 Session display appearance. A session displays a terminal screen only after a connection is attempted. Therefore, a session window will appear empty if: 1) A saved session is opened, but the session was saved with the Auto Connect option disabled. In this case, the terminal screen appears only after a connection is attempted, or 2) A new session is configured with the Auto Connect option disabled. In this case, the terminal screen appears only after a connection is attempted. The terminal screen remains on display after a session is disconnected. This situation is documented in the script.hlp file in the Display topic. 4.8 File Send and File Receive buttons and menu items. Although these buttons and menu items are activated when a session is connected, DCS 9 will only display the file selection and setup dialogs when the host has been prepared to send or receive files. 4.9 Print Screen/SysRq key cannot be mapped for TN3270 and TN5250 emulations. The Print Screen/Sys Rq key cannot be mapped to a function with the Keyboard Mapper. The system will allow you to use the mapping procedures with this key. However, the key will not perform the mapped functions when accessed. 4.10 Creating a DCS 9 session with a DCS 9 script. All properties must be explicitly set for the session with the appropriate script command. These commands include the following: APPCONFIG, DISPLAYCONFIG, GENERALCONFIG, CONNCONFIG, EMULCONFIG, XFERCONFIG. 4.11 Using Kermit commands with FSIEvent. If Kermit commands are used with FSIEvent, the Kermit FINISH command must be used to end the script. If the Kermit FINISH command is not used, two conditions exist: 1) Kermit commands in the script will appear to not have been executed. 2) Session control is not returned. The commands are actually being executed as written. However, it is true that session control is not returned. Therefore, the FINISH command must be used for correct script execution to occur. 4.12 Using extensions for file names coded in scripts. When coding the name of a file as part of a script command or function, be aware that your Windows settings may interfere with the script's ability to locate the file. If your Windows file settings are set to hide extensions, then the file name in the script should not include an extension. This problem occurs primarily with functions such as WindowHnd () which attempt to retrieve information (such as a window handle) based on the name shown in the window title bar. A good coding practice is to use an error-checking routine to verify that the value returned by such a function is not zero, and if it is, to execute a second function with a different window title name. In this case, check once for the filename without an extension, and the second time check with the extension added. See the first two lines of Example 2 in the information on When and Wait below. 4.13 Changing menu structures when multiple windows are open. If you change the menu structure via script when multiple windows are open, the list of open windows which appears under the Windows menu will not list any windows until a new window is opened or the active window changes. 4.14 Commands * ConnConfig This command cannot be used to configure the Modem connector. To configure a modem via script, you must use the Direct Serial connector. * Connect() This function will always return a value of TRUE for the Direct Serial and Modem connectors, even when the session is not connected to a host. Both of these connectors interact with local hardware (a COM port), and will return a value of TRUE as long as they have established a connection to the COM port. To determine if you have established a connection to a host when using these connectors, create a routine using the Send command (to send data to the host) followed by one of the When commands (to determine whether the host responded). * Display The Display command does not send strings to the host; it only displays text in the session window. However, unlike previous versions of DCS 9, the Display command now works only with connected sessions. Use the Send command to send a string to a host. * File Decrypt This command is not backward compatible with versions of DynaComm Connectivity Series prior to DCS 7.0.0.0. * File Delete File names cannot contain wildcard characters. * File Encrypt This command is not backward compatible with versions of DynaComm Connectivity Series prior to DCS 7.0.0.0. * GetConnConfig() This function cannot be used to obtain the settings of the Modem connector. To obtain settings for a modem connection via script, the session must use the Direct Serial connector. * Send When using metakeys (text enclosed in braces {}) the only valid strings are those listed in the terminal keys area on the Terminal tab in the Keyboard Mapper. These strings apply only to the specific emulation. Additional keys may be added in the future. The optional coordinates for the Send command only work with emulations that support block or page modes, such as TN3270 and TN5250. Cursor positioning coordinates are ignored by other emulations. * When and Wait The DCS 9 architecture uses parallel processing for scripting operations and input/output operations. Therefore, it is possible that a script may send data to and receive data from a host before the script has executed a subsequent Wait or When command (causing the script to hang). For best results, place When commands and routines earlier in the script sequence of execution. Example 1 %hwnd = active() when string "elvis" window %hwnd resume *loop send "" window %hwnd wait resume beep 1 goto loop cancel In Example 1, the When String command has been established before the request for data. This ensures that the data cannot arrive before the script is in a state to check for the data. Example 2 %hWnd = WindowHnd ("Bbs.SES") if %hWnd = 0 %hWnd = WindowHnd ("Bbs") ; note: if the Window Handle is still zero at this point, the script will not work when string 1 "new" window %hWnd resume when string 2 "password" window %hWnd resume when string 3 "(C)ontinue" window %hWnd resume connect %hWnd wait resume send "user name" window %hWnd wait resume send "password" window %hWnd wait resume send "" window %hWnd when cancel string cancel In Example 2, all When String commands have been established before sending data and waiting for the host to respond. Again, this ensures that the data cannot arrive before the script is in a state to check for the data. ================================================================================ 5.0 Updated, Implemented or Fixed in This Release * Implemented - Transport Layer Security (TLS) protocol for TN3270 emulation * Implemented - New script functions for TN3270/TN5250 emulation * Implemented - New option for SEND command (TN3270/TN5250 emulation only) * Implemented - New strings/keywords for EMULCONFIG and CONNCONFIG script commands ================================================================================ 6.0 Technical Support For prompt and effective service, please be sure to include your company name, address, any applicable phone (or fax) numbers, name and version number of the product for which you need support. The following technical support options are available: 6.1 FutureSoft * Web: www.futuresoft.com * E-mail: support@futuresoft.com * Telephone: Monday through Friday between 08:00 and 17:00 Central Standard Time (CST) 1.281.588.6868 * FAX: 1.281.496.1090 * Ground Mail: Technical Support Services 12012 Wickchester Lane, Suite 600 Houston, Texas 77079-1222 6.2 Send files via FTP to ftp.futuresoft.com. ================================== END ========================================= Copyright 2010 FutureSoft, Inc. readme.txt DCS 9.3.0 March 31, 2010