Release Notes: DynaComm Connectivity Series Release Version: 11.0.0 Release Date: 04/10/2023 ================================================================================ 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 3.0 System Requirements 4.0 Notes on DynaComm Connectivity Series 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-sessions; custom keyboard mapping; OLE compliance; custom toolbar editor; custom menu editor; 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 ADDS Viewpoint/60; TeleVideo 925/950; ANSI/SCO-ANSI; HP 700/94; AT&T 4425; Digital VT 52/100/102/220/320/420; AT&T 605/705; Wyse 50/60; Tandem 6530 IBM TN3270 and TN5250 are available as upgrades * File Transfers: Kermit; FTP; XYModem IXF (with Tandem 6530 Client Option installed); ZModem; IND$FILE (with TN3270 Client Option installed) * Connectors: Direct Serial; Telnet (TLS); Meridian LAT32; Trace Player; Modem (TAPI) SNA Server (with TN3270 Client Option installed); SSH2 Visit our web site to see the latest information on all of our products: www.futuresoft.com ================================================================================ 2.0 New In DynaComm Connectivity Series * New script options (see 5.1 Script changes) * Transport Layer Security (TLS) protocol for TN3270 * New strings/keywords for the EMULCONFIG and CONNCONFIG for TLS options * Floating toolbars can now be resized with the mouse * Transport Layer Security (TLS) is FIPS 140-2 validated * The autostrt.dct can be executed from the install directory * Leave Print options enabled even if no default printer is found * Display correct interactive file transfer dialogs under Vista/Win7 * Added support for CERT file types of CER in addition to PEM - See 5.2 * Set script RESULT() with correct status code after IND$FILE download * TLS connection logging option * Show message if no printers are defined during Print setup * Include DcsDtc.ocx and DCSWeb.dll (These are no longer supported) * LDAP Authentication with CAC/PIV/Smart Card * Allow TLS1.0 (along with TLS1.1/TLS1.2) allowing server to determine level * New TLS option to Ignore Server CERT/Chain Errors ================================================================================ 3.0 System Requirements 3.1 DynaComm Connectivity Series, requires one of the following: - Windows 8 and above - Windows 2008 Server and above ================================================================================ 4.0 Notes on DynaComm Connectivity Series and all add-on Client Options 4.1 General 4.1 Starting DCS from a command line. When starting DCS 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. However, new session files cannot be used in earlier versions. 4.3 Documentation * The most current documentation is available for download from the FutureSoft web site at: http://www.futuresoft.com/Support/DCS/dcs11.html 4.4 Evaluation version installs An evaluation copy is good only for 25 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 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.6 File Send and File Receive buttons and menu items. Although these buttons and menu items are activated when a session is connected, DCS will only display the file selection and setup dialogs when the host has been prepared to send or receive files. 4.7 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.8 Creating a DCS session with a DCS 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.9 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.10 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.11 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.12 Script Commands notes * 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, 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 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, 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. 4.13 Floating toolbars can be resized When adding customized buttons to toolbars, it will automatically resize. After the customization is complete, resize to the desired width/height by dragging the edges with the mouse. ================================================================================ 5.0 Updated, Implemented or Fixed in This Release * 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 commands * Implemented - Transport Layer Security (TLS) protocol for TN3270 emulation * Implemented - New script options for application window and DIALOG boxes * Implemented - New script commands/functions for multiple SCRIPT/TASK control * Implemented - Floating toolbars can be resized * Implemented - New script DISPLAY option to display text in the statusbar * Implemented - Transport Layer Security (TLS) is FIPS 140-2 validated * Fixed - TLS load flags for Windows 7 memory mapping issue * Implemented - SYSTEM commands/functions to read/write the registry * Implemented - Script Editor converts tab to 3 space indents * Implemented - Script Editor expands double-click selection to variable type * Implemented - New Telnet option to process Data Mark without IAC command (RedHat telnet-server) * Implemented - Process OOB IAC w/Data Mark (RedHat telnet-server) * Implemented - IBM ELF (Express Logon Feature) CAC/PIV/Smart Card support * Implemented - Disable Auto Reconnect w/Smart Card * Implemented - LDAP Authentication script options 5.1 Script changes * BUFFER (Row, Column, Length, WinHandle) TN3270/TN5250 emulation only. See script reference for details. * FLDTEXT (Field, WinHandle) TN3270/TN5250 emulation only. See script reference for details. * SEND ... NOPROTECT ... TN3270/TN5250 emulation only. See script reference for details. * Moved TLS option to CONNCONFIG CONNCONFIG "FS3270_TLS=1" See script reference for details. * Added OpenSSH option to CONNCONFIG SET CONNECTION "OPENSSH" CONNCONFIG "SSHLEVEL=2ONLY" See script reference for details. * SET APPTITLE ... WINDOW value The optional WINDOW option allows the DCS Title Bar to be hidden. To hide the Title Bar, use -1 and to show (or unhide) it use 1. Example: SET APPTITLE "Hide Title Bar" WINDOW -1 WAIT DELAY "4" SET APPTITLE "Show Title Bar" WINDOW 1 * DIALOG ... NOPARENT bool The optional NOPARENT option will create the DIALOG as its own window independent of the DCS application. Any coordinate set (x,y) gives the location on the desktop. Example: DIALOG (0, 0) "Hello" NOPARENT TRUE DIALOG END * TASKLIST() Returns a string of all running script/task IDs. Each ID is separated by a comma. If a parameter of -1 is given, the current running task ID is returned, otherwise a list of all running task IDs is returned. Example: $AllTasks = TASKLIST() If three scripts/tasks are running the string would contain something like: 0x0CF0,0x07BC,0x0D38 $MyTask = TASKLIST(-1) The string will have one ID like: 0x07BC * TASKNAME(TaskNumber) Returns the name of the running task ID number. * TASKFILE(TaskNumber) Returns the filename of the running task ID number. Example: $MyTask = TASKLIST(-1) $taskname = TASKNAME(NUM($MyTask)) $taskfile = TASKFILE(NUM($MyTask)) * TASKSTOP TaskNumber Stops the given task. (Use SPAWN to start a task) Example: TASKSTOP NUM($taskID) * DISPLAY (Row, Col) String If only one number is given, the text will be displayed in the statusbar at the bottom of the DCS window. If the statusbar is visible. Example: DISPLAY (99) "Hello from the statusbar!" * AUTOSTRT.DCT can now be placed in the EXE directory As before, autostrt.dct is still executed from the users SCRIPTS/TASKS directory, if it exists. But autostrt.dct will also be executed if found in the EXE directory. This allows a default script even if the users customized their SCRIPTS/TASKS directory locations. * SYSTEM commands/functions to read/write the registry 0x0720 - Read/Write string 0x0721 - Read/Write number (as string) Example: (the user must have permission to write to HKEY_LOCAL_MACHINE) SYSTEM 0x0720 "HKEY_LOCAL_MACHINE\\SOFTWARE\\FutureSoft\\Testing" "exampleStr" "str1" SYSTEM 0x0721 "HKEY_LOCAL_MACHINE\\SOFTWARE\\FutureSoft\\Testing" "exampleNum" "1" $s = SYSTEM(0x0720, "HKEY_LOCAL_MACHINE\\SOFTWARE\\FutureSoft\\Testing", "exampleStr") $n = SYSTEM(0x0721, "HKEY_LOCAL_MACHINE\\SOFTWARE\\FutureSoft\\Testing", "exampleNum") Example: (HKEY_CURRENT_USER is the default and may be left out) SYSTEM 0x0720 "HKEY_CURRENT_USER\\SOFTWARE\\FutureSoft\\Testing" "exampleStr" "str2" SYSTEM 0x0721 "HKEY_CURRENT_USER\\SOFTWARE\\FutureSoft\\Testing" "exampleNum" "2" $s = SYSTEM(0x0720, "SOFTWARE\\FutureSoft\\Testing", "exampleStr") $n = SYSTEM(0x0721, "SOFTWARE\\FutureSoft\\Testing", "exampleNum") * IBM ELF (Express Logon Feature) CAC/Smartcard support (The z/OS TN3270E Telnet server or DCAS must be configured for ELF) (You must have a CAC/Smartcard and reader connected to your PC) Under the Telnet connector, enable the TLS and MS (CAPI) options. Use Certificate/ELF dialog set your Certificate and ELF options. If you wish to set your APPLID while connecting, enter it and check Send w/Initial Telnet Query if requested IBMELF/IBMAPPLID. To set the APPLID from script, use the SEND option ELFAPPLID. You may set a string or the value from the APPLID field dialog. Example: (send the APPLID tsotest via TNOPT_NEWENV/IBMAPPLID) SEND ELFAPPLID "tsotest" This example sets the value entered in the APPLID field: SEND ELFAPPLID "{ELFAPPLID}" WAIT QUIET "2" SEND ")USR.ID(" SEND "{TAB}" SEND ")PSS.WD(" SEND "{ENTER}" * LDAP Authentication script options If LDAP Authentication with CAC/PIV/Smart Card is enabled, the UPN (principal name) is used to query the LDAP server. The the values for PICSID and TSOID are saved from the LDAP reply. This example shows how to get the values: $myPics = getconnconfig("LDAP_PICSID") $myTso = getconnconfig("LDAP_TSOID") 5.2 Transport Layer Security (TLS) is FIPS 140-2 validated * All TLS options are now under the Telnet connector. * If the FIPS cryptographic validation fails, the connection is aborted. * The connection icon in the status bar will display a lock icon if the connection is encrypted. A checkmark if FIPS validated. * Added support for Client/Server file types of CER in addition to PEM. If Client KEY file is not given, the CERT file is assumed to contain it. * Added support for Server CERT authentication with peer server matching or a matching CERT chain. 5.3 TLS connection logging options for debugging * Add to SES file for detailed connection information during TLS connections. All file names will have a unique ID appended. Example: [TLS] TLSLogFile=c:\temp\tls_text TLSLogCert=c:\temp\tls_cert TelnetLogFile=c:\temp\telnet_text 5.4 Updated installer to register VB Client for newer VB versions (VB2008, VB2010, etc) * Fsievent ActiveX Interop version will show 2.0.0.0 ================================================================================ 6.0 Technical Support For prompt service, please be sure to include your Serial Number Key in your E-mail to support. The SN is displayed in the About box. The following technical support options are available: 6.1 FutureSoft * Web: www.futuresoft.com * E-mail: support@futuresoft.com * Telephone: 1.800.261.6357 ================================== END =========================================