 |
|
I. Overview
A. Release History
II. Functionality
A. Platforms Supported
B. Basic Functionaliy
1. Emulations
2. Connectors
3. File Transfer Protocols
4. Scripting
5. Tools/User Interface
a. Toolbar Editor
b. Menu Editor
c. Attribute Mapper
d. Character Map Editor
e. Keyboard Mapper
f. Mouse Properties
6. Documentation/Help
C. Enhancements and Related Products
1. Client Options
2. Development Tools and Utilities
a. Dialog Editor
b. Trace
c. Debug
d. Hotspots
e. Visaul Basic Interface
f. DCS 9 as an OLE Automation Server
III. Technical Specifications
A. Minimum Recommended System Requirements
B. Installation
1. General
2. Installation Procedure
3. Deployment Considerations
C. Registry Modifications
D. Directory Structure
E. Icons
F. Configuration/Initialization Files
This Technical Profile provides technical information about DynaComm Connectivity Series 9 (DCS 9) features,
specifications and configuration. Information in this document pertains to the most current release of the product
(see the Product Release History below). Earlier versions of DynaComm Connectivity Series 9 may differ in functionality
and/or configuration from the current released version.
DynaComm Connectivity Series 9 is designed to provide users with the flexibility to integrate host mainframe
and minicomputer systems with a PC-based Windows environment. The Script Language provides the power to automate
processes, pass data between productivity applications and quickly design and implement custom communication
applications. For customers who connect to multiple host systems, DCS 9’s multiple session capability
within a single application instance offers an enterprise solution. Optional client emulation components such
as Tandem 6530 and TN3270 are fully integrated into the product when installed. DCS 9 is fully OLE compliant
and has ActiveX document support. This extends the program’s functionality to include support for OLE automation
and web browser integration.
| |
| Version |
Release Date |
Release Status |
| DCS 9.3.0.0 |
March 31, 2010 |
Latest Release |
|
|
Return to top
- Windows 7
- Windows Vista
- Windows 2008 Server Edition
- Windows 2003 Server
- Windows XP
- Windows 2000
Return to top
- ADDS VP/60
- ANSI BBS (ANSI, TTY and SCO ANSI extensions)
- Digital VT-52, 100, 101, 102, 220, 320 and 420
- AT&T 605/705
- TeleVideo 925/950
- Wyse 50/60
*Product
DynaComm Connectivity Series uses an embedded FIPS 140-2-validated
cryptographic module (Certificate #1051) running on a Windows platform per
FIPS 140-2 Implementation Guidance section G.5 guidelines.
Source scripts written in earlier versions of the product can be recompiled to work in DCS 9. When performing
script conversion, modifications to legacy scripts may be required.
Return to top
DCS 9 provides users with several tools to customize their workspace and automate common tasks.
| |
| Purpose: |
Allows the user to customize the application floating toolbars. |
| Accessed via: |
Tools: Customize: Toolbar or View: Toolbar. |
| Configuration: |
Allows the user to add default or custom buttons to toolbars which can be assigned to run a
script, launch a program, send a string to the host or execute a menu command. Icons can be
chosen from standard toolbars or from the custom icon library. Tooltips for buttons can be
entered by the user. |
| Settings stored: |
Settings are stored in the Registry at:
HKEY_CURRENT_USER\Software\FutureSoft\DCSeries. |
| Defaults: |
Only the Standard toolbar is selected by default. Other preconfigured toolbars include File, Edit,
Session, Transfer, Trace, OLE and Script toolbars. |
| Scope: |
Toolbar settings are global (application-wide). |
|
Return to top
| |
| Purpose: |
Allows menus and menu items to be deleted or added to the main, memo, script and session windows. |
| Accessed via: |
Tools: Customize: Mneus |
| Configuration: |
Menus, submenus and menu items can be added. Menu items can be assigned to launch a script,
send a string to the host or execute a menu command. |
| Settings stored: |
Settings are stored in the Registry at:
HKEY_CURRENT_USER\Software\FutureSoft\DCSeries. |
| Defaults: |
If Registry entries are not present when launched, DCS 9 will use the hard-coded default menu structure. |
| Scope: |
Menu settings are global (application-wide). |
|
Return to top
| |
| Purpose: |
Allows users to create and save custom color maps which associate host character attributes to
local terminal colors. |
| Accessed via: |
Session: Properties: Emulations: Attributes |
| Configuration: |
Host character attributes are displayed with their current video characteristics. Users can modify
the foreground and background color and assign display attributes such as Blink and Reverse locally.
Custom colors can also be created by the user and assigned to the color palette.
NOTE: 16-bit color is recommended for using custom colors. |
| Settings stored: |
Color maps are saved in the DCSeries\MAPS subdirectory with the extension .ACM.
The name of the color map assigned to the current session is stored in the corresponding session file under
the [EMULATION] heading. |
| Defaults: |
Each emulation shipped with the Core Product or with Client Options has a default color map associated
with it. If the user wishes to use a different color map than the default, existing .ACM files can be
loaded from the Map File drop-down list box. |
| Scope: |
Color map settings apply only to the session for which they are selected. |
|
Return to top
| |
| Purpose: |
Allows user to edit or create character translation between the host and the emulator and/or vice versa. |
| Accessed via: |
Session: Properties: Emulations: Translation |
| Configuration: |
User selects and edits the default or previously saved translation file that is associated with the
chosen emulation. The user may select which direction the character should be converted based on the
tabs available in the editor. Host to Display will affect how the character is displayed to the user
when coming from the host. Display to Windows will affect what character is sent to the clipboard when
text is copied from the display. The resulting translation file (.TRF) saves the mapping between the
host and the display and between the keyboard and the host. |
| Settings stored: |
Translation files (.TRF) are stored in the Maps directory. The name of the translation file selected
for the current session is stored in the corresponding session file under the heading [EMULATION] and
the section CHARTRANSFILE. |
| Defaults: |
Emulation defaults are stored in the respective emulation’s .FLX file. Each emulation shipped
with the Core Product or with emulation Client Options has a default translation file associated with
it. Only translation files that are associated with a specific emulation may be used for that emulation. |
| Scope: |
Translation files (.TRF) apply only to the session for which they are selected. |
|
Return to top
| |
| Purpose: |
Allows user to edit or create host-to-PC keymaps or to assign scripts, strings or menu selections to PC keys. |
| Accessed via: |
Session: Properties: Emulations: Keyboard |
| Configuration: |
User selects and edits the default or previously saved keymap that is associated with the chosen
emulation. The user may also choose the nationality of the local PC keyboard they are using. Host
keys may be assigned to local PC keys by selecting the desired functionality in the Mapping Options
box and clicking the Map Key button. The resulting keymap file (.KBM) saves the mapping between host
and local PC keys. |
| Settings stored: |
Keymap (.KBM) files are stored in the Maps directory. The name of the keymap selected for the current
session is stored in the corresponding session file under the heading [EMULATION]. The local PC keyboard
setting is stored at HKEY_CURRENT_USER\Software\FutureSoft\DCSeries. |
| Defaults: |
Host defaults are stored in the respective emulation’s .FLX file and local PC default templates
are stored in the Keymapr.dll file. Each emulation shipped with the Core Product or with emulation
Client Options has a default keymap associated with it. Only keymaps that are associated with a specific
host may be used for that host. |
| Scope: |
Keymap (.KBM) files apply only to the session for which they are selected.
Local PC nationality settings are application global. |
|
Return to top
| |
| Purpose: |
Allows the user to configure custom mouse click functionality which can be saved to a session file. |
| Accessed via: |
Session: Properties: Mouse |
| Configuration: |
Left, middle and right mouse buttons can be set to perform tasks such as make a box selection, move
the cursor, execute a script or display pop-up menu. These tasks can be set to either a single or
double click of the mouse button and with or without a modifier key depressed. |
| Settings stored: |
All Mouse Properties settings are saved under the [Left Mouse Button], [Middle Mouse Button] and
[Right Mouse Button] headings respectively in the corresponding session (.SES) file.
The default directory for session files is:
Program Files\FutureSoft\DCSeries\Session |
| Defaults: |
The defaults are hard-coded in the tdisplay.flx file under Program Files\FutureSoft\DCSeries\Display. |
| Scope: |
Mouse Properties settings apply only to the session for which they are selected. |
|
Return to top
All DCS 9 documentation is available online and includes readme, help and PDF files. The following table lists
the documents and the associated help files, which are stored in the DCS 9 home directory. With this release,
all help files are HTML based and require Windows Internet Explorer.
| |
| TITLE |
Format |
File Name |
| Getting Started for Users |
PDF |
GS_User.pdf |
| Getting Started for Administrators |
PDF |
GS_Admin.pdf |
| Getting Started for Administrators |
Help |
AdmOlref.chm |
| Script Reference |
HTML Help |
Script.chm |
| Script Reference |
PDF |
Script.pdf |
| Futuresoft FTP Help |
Help |
FSFTP32.chm |
| HLLAPI Auto Launch Configuration Reference |
Help |
HLAPCnfg.chm |
| VB Client Help |
Help |
VBClient.hlp |
|
Return to top
DCS 9 has a number of Client Options, sold separately, which provide additional emulation, file transfer and
host connectivity capabilities when installed with the DCS 9 Core Product. Currently available Client Options
are outlined below. Installation of a Client Option adds emulator, connector and/or file transfer .DLLs to the
appropriate DCS 9 subdirectories, help files to the DCS 9 home directory and any necessary color and keyboard
maps to the MAPS subdirectory. After installation, the new emulator/connector/file transfer are integrated into
the product, available from the appropriate tab of the Session Properties dialog.
| |
| Tandem 6530 Client Option |
Provides Tandem 6530 emulation and IXF file transfer. Online documentation is also included
with the file TANDEM.HLP. |
| TN3270 Client Option |
Provides IBM 3270 emulation, LU1 and LU3 print emulation, Microsoft SNA Server and TN3270
connectors and IND$FILE file transfer capability. Online documentation included with the
file IBM.HLP. |
| TN5250 Client Option |
Provides IBM 5250 emulation via TN5250. Basic 5250E is also available including device naming,
auto-logon and print support. Online documentation is included with the file IBM.HLP. |
| AT&T 4425 Client Option |
Provides AT&T 4425 emulation. Online documentation is included with the file ATT4425.HLP. |
| HP 700/94 Client Option |
Provides HP 700/92-94 emulation. Online documentation is included with the file HP70094.HLP. |
|
Return to top
Note: As of release DCS 7.1.0.4, the Dialog Editor is no longer supported or
shipped as part of the DynaComm Connectivity Series. It is available as a free download.
The Dialog Editor is a standalone executable program which generates DynaComm Script Language code to create
dialog boxes. The Dialog Editor features a graphical interface to make designing dialog boxes easier. The code
generated by the Dialog Editor can then be compiled, edited or ported to another script.
DCS 9 has an integrated trace facility to aid with problem diagnosis and troubleshooting. The trace facility
is available under the Session menu > Properties > Trace and gives the user the option to easily capture and replay
traces with no special files or utilities required. It can be configured to trace outbound and/or inbound data,
producing either a binary trace file or a report of data transactions.
The DEBUG script command can be used to diagnose script problems. Debug writes commands and functions to a file
as they execute. SHOW and NOSHOW can be used to turn the file writes on and off at different points in the script.
DEBUG takes a filename as an argument, but can also take a question mark as an argument. When the question mark is
used, followed by SHOW, the DEBUG window appears and allows you to step through script execution a command at a
time using the RESUME button.
Hotspots are available across all emulations and can be found under the Session menu > Properties > Emulations tab >
Hotspots tab. In order to enable Hotspots, go to the Session menu > Properties > Displays tab and check
“Enable Hotspots”.
The Visual Basic interface is available using the ActiveX control “FSIEvent.ocx”. FSIEvent.ocx is
located in the VBClient directory within the DCSeries default installation directory. This interface allows
VB-trained programmers to access DCS 9 events and methods within their VB 5.0 and above applications.
Documentation is available that includes VB commands and functions in an online Help file (VBClient.hlp).
To access the Help file, navigate in Windows Explorer to \FutureSoft\DCSerires\vbclient and double-click vbclient.chm.
DCS 9 supports OLE Automation as a server that enables any client application to drive DCS 9. Initialization of
the DCS object is as follows:
Dim wnh As Long
Set DCS = CreateObject("dcseries.script")
Call DCS.MakeAppVisible(ShowWindow)
wnh = DCS.windowopen(1, "Session1.ses", 0, 0, 0, 300, 300)
Return to top
- IBM compatible PC with a 486 or higher microprocessor, with at least 16 megabytes of RAM
- Floppy disk drive
- Hard disk with at least 20 MB of free disk space
-
Microsoft Windows 95, Windows 98, Windows NT (Workstation or Server), Windows NT Server, Terminal Server
Edition, Windows 2000, Windows 2003 Server, Windows XP and Windows Vista
- Free serial port or network connection
- Hayes compatible modem (if communication link is made over a phone line)
Return to top
-
DCS 9 is downloaded and activated with a license key; if needed, a hard copy of the installation
software can be requested
- Full Installation Footprint: 12 MB*
*Plus shared files. This may add up to an additional 1.83 MB.
The installation of DCS 9 performs the following main functions, in this order:
-
Checks the Registry to see if a previous version of DCS is installed. If a previous version is found,
it launches the component install/uninstall SETUP program.
- Asks to verify removal of installation files.
- Extracts files.
- Displays Software LIcense Agreement and requests acceptance.
- Requests customer information.
- Requests setup type: Complet or custom.
- Installs files.
When installation is complete, the base DCS 9 product and Client Options (purchased separately) are licensed
with Licenser. Licenser is accessed through the DynaComm Connectivity Series 9 program group with the Licenser
selection.
-
Compatibility Digit in DCS Version Number: The version number of DCS 9.0 will be a four digit number, 9.x.y.z.
The x digit indicates compatibility between Core Product and Client Options. For example, if you upgrade the Core
Product from DCS 8.0.0.5 to DCS 9.0.0.0, you will need to upgrade the Client Options as well. The versions of all
installed modules can be accessed from the Help > About dialog.
-
Registry File Locations: In the Tools > Options > File Locations menu item, the user can specify the location of
their sessions, scripts, memos, mapped files and up/downloaded files. DCS 9 stores any changes from the defaults
in the Registry, so deploying changes to many users involves deployment methods discussed in the white paper
mentioned above.
Return to top
DCS 9 modifies the Windows Registry as noted below. This information is provided for Application Administration
personnel, not the casual user. Since InstallShield is used for installation and removal, users have no need for
this detailed information.
-
These areas of the registry contain the program group and path used by DCS 9. Settings stored here include:
Telnet host name and port settings, print setup options, recent file list settings, user information, toolbar
settings, menu settings and keyboard mapper settings.
[HKEY_CURRENT_USER\Software\FutureSoft\DCSeries]
[HKEY_USERS\Default\Software\FutureSoft\DCSeries]
-
This registry entry is used to store release version information for DCS 9 and its Client Options.
[HKEY_LOCAL_MACHINE\SOFTWARE\FutureSoft\DCSeries]
-
Session (.SES), script (.DCP and .DCT) and memo (.DCM) document types are registered with Windows under
these keys to create a shell association with DCSERIES.EXE.
[HKEY_CLASSES_ROOT]
[HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES]
- This entry stores the pointer to the DCS 9 Uninstall string.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
\DCSeriesDeinstKey]
Return to top
You can select the default directories and the default components with the Tools > Options > File Locations
menu option.
Return to top
| |
 |
DCSERIES.EXE is the DCS 9 main executable. This executable can take existing scripts or
session files as command line parameters, launching the session or script at startup. It
is located in the DCS 9 home directory. |
 |
README.DOC contains information pertinent to the latest release of DCS 9 and may include
current information not available in manuals. It is located in the DCS 9 home directory. |
 |
FUTRSOFT — Shortcut URL to the FutureSoft web site. |
 |
ONLNEREG — Shortcut URL to the FutureSoft online registration form located on our
web site at www.futuresoft.com. |
 |
FTSFTP32.EXE is a standalone executable which provides an easy-to-use graphic interface
to manipulate file transfer to and from a remote host. It is located in the “ft” directory
within the DCS 9 home directory. |
|
Return to top
| |
| NAME |
TYPE |
DEFAULT LOCATION |
DESCRIPTION |
| Registry Entries |
Registry |
HKEY_CURRENT_USER\
Software\
FutureSoft\
DCSeries |
See Registry Modification above. |
| *.ACM |
BINARY |
DCSeries\MAPS |
The default attribute/color map for a specified emulation |
| *.DCM |
TEXT |
DCSeries\MEMOS |
DCS 9 Memo file |
| *.DCP |
TEXT |
DCSeries\SCRIPTS |
DCS 9 Script source file |
| *.DCT |
BINARY |
DCSeries\SCRIPTS |
Compiled DCS 9 script |
| *.KBM |
BINARY |
DCSeries\MAPS |
The default keybaord map for an emulation |
| *.SES |
TEXT |
DCSeries |
Session preferences (connector, emulation, startup script, mouse properties, display properties,
file transfer, trace properties) |
| *.TRF |
TEXT |
DCSeries\MAPS |
Character translation file for an emulation |
| *.ISU |
BINARY |
DCSeries |
Uninstall files, used by Add/Remove Programs to properly remove Core Product or Client Options. |
| AUTOSTRT.DCT |
BINARY |
DCSeries\SCRIPTS |
Script executed automatically when DCS 9 is launched. |
|
Return to top
|
|
