Products Purchase Support Download    News About

Support - DynaComm® SE

DynaComm® SE


Technical Profile


Contents


Related Support Documents
· DynaComm SE FAQ
· DCS Script Examples
· Telnet Troubleshooting Guide
· White Papers

I. Overview

A. Release History


II. Functionality

A. Platforms Supported

B. Basic Functionaliy

1. Emulations

2. Connectors

3. Tools/User Interface

a. Command Line Parameters

b. Color Mapping

c. Key Mapping

d. External Program

e. Quick Keys

f. Toolbar Editor

g. Entry Assist

h. Login/Connection Options

i. Mouse Options

j. Hotspots

k. Flashpads and the Flashpad Editor

4. Printing

5. File Transfers

6. HLLAPI Support

7. Macros

8. Documentation/Help


III. Technical Specifications

A. System Requirements

B. Installation

C. Configuration File and Registry Modifications

D. Directory Structure

E. Icons

F. Configuration/Initialization Files

 

I. Overview

This Product Profile is intended to provide general technical information about DynaComm Special Edition 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 Special Edition may differ in functionality and/or configuration from the current released version.

A. Release History


 

Version

Release Date

Release Status

DCSE 3200

February 3, 1997

Latest Release

DEC 31100

September 11, 1996

Supported

 

Return to top

 

II. Functionality

A. Platforms Supported

  • Windows 95, Windows NT 3.51, Windows NT 4.0
  • Windows 3.1, Windows for Workgroups (16 bit version only)

Return to top

 

B. Basic Functionality

1. Emulations

  • DEC VT 52
  • DEC VT 100
  • DEC VT 101
  • DEC VT 102
  • DEC VT 220
  • DEC VT 320
  • DEC VT 420
  • IBM 3278
  • IBM 3279
  • IBM 5250 Model 2
  • IBM 5250 Model 5

2. Connectors -- standard with the base DCE installation

  • TELNET
  • TN3270
  • TN3270E
  • TN5250

Return to top

3. Tools/User Interface

DCSE provides users with several tools to customize their workplace and simplify or automate common tasks.

a. Command Line Parameters

 

 
Purpose: Allow different startup parameters for DCSE, such as selection of a specific session profile, .INI file, IP address to connect on startup, or enable debug mode. These parameters are documented fully in the online help, under the heading Command Line Options.
Accessed via: Windows command line (e.g, under the Shortcut tab of a Shortcut’s properties).
Configuration: Not applicable.
Settings stored: Command line parameters can be assigned to a permanent Windows shortcut.
Defaults: None.
Scope: Application Global.

 

Return to top

b. Color Mapping

 

 
Purpose: Create and save custom color schemes remapping default colors associated with host field or character attributes.
Accessed via: Settings: Session Profile: Colors

Settings: Session Profile: Color Palette

Configuration: UI provides a color set which can be mapped to standard terminal character attributes (such as Reverse, Blink, etc.) Color Palette allows users to modify the standard color set to their own preference.
Settings stored: DCSE3270.INI contains the color map under the associated session profile heading. Color Palette modifications are saved in DCSE3270.INI under the [System.Colors] heading.
Defaults: Default settings are hard-coded. Settings are saved to DCSE3270.INI only if modifications are made. UI provides a Reset All to restore default colors.
Scope: Color-to-attribute maps are session-specific, Color Palette modifications are application global.

 

Return to top

c. Key Mapping

 

 
Purpose: Allows user to map macros, system commands, host keys, or special characters to PC keys.
Accessed via: For the keyboard editor, Settings: Keyboard Mapping

To load a keyboard map, Settings: Session Profile: Keyboard

Configuration: A graphic representation of the PC keyboard is given. Host keys, macros, system commands or special characters can be assigned to a key or a key’s meta states, using a drag-and-drop interface. ‘List Assigned Functions’ provides a handy list of the current mapping of keys.
Settings stored: DCSE3270.INI, under a profile named [Keymapname.Key].
Defaults: Defaults are hard-coded and will be used if no keymap is specified.
Scope: Available globally once created and saved, session specific once attached to a session.

 

Return to top

d. External Program

 

 
Purpose: Allows the user to define the path to an external FTP program, such as FutureSoft’s FTPEXE or WS_FTP95. Also allows the user to define a web browser to use when a hotspot URL is clicked in the terminal session.
Accessed via:

Settings: Session Profile: Ext Progs.

Configuration: The user designates the path to the desired executable in the listboxes. To use the browser feature, hotspots must be enabled.
Settings stored: DCSE3270.INI, under the appropriate session profile heading.
Defaults: FTP: \DCSE\Programs\FSFTP.EXE

Browser: NETSCAPE.EXE

Scope: These settings are session specific.

 

Return to top

e. Quick Keys

 

 
Purpose: Allows the user to create short macros which can send text, execute menu commands, and simulate keystrokes. Once created, Quick Keys can be assigned to flashpads, the keyboard mapper, hotspots, or the toolbar.
Accessed via:

Settings: Quick Key Editor.

Configuration: Strings and host functions (e.g., <LOGINID> ENTER) can be appended together and assigned to a Quick Key Name. Set, Clear, Run and Save are provided to build and test Quick Keys.
Settings stored: DCSE3270.INI, under the [Default.Mac] heading.
Defaults:

No Quick Keys are present by default, they must be created by the user.

Scope: Quick Keys are created and become available globally to other UI tools in DCSE. The actual Quick Key assignments are specific to whatever tool is being used to make them.

 

Return to top

f. Toolbar Editor

 

 
Purpose: Allows the user to define buttons with the full range of functionality: they can execute system commands, edit commands, or Quick Key macros, or send characters or host keystrokes to the host.
Accessed via:

Settings: Session Profile: Toolbar

Configuration: A graphic interface allows the user to select an existing toolbar button or an empty space, and assign it an icon and a function. Load, save, and reset to default are supported. Up to 40 toolbar buttons may be defined.
Settings stored: In DCSE3270.INI under the appropriate profile heading, separated by commas, with the tag Toolbar Commands=. The bitmap icons assigned to the buttons are also stored under the profile heading, separated by commas, under the tag Toolbar Bitmap IDS=.
Defaults:

Eleven buttons are defined by default: Open session, Close session, Save profile, Print Screen, Cut, Copy, Paste, Upload, Download, Help, and What’s This. If no toolbar entries are made in a session profile, the defaults will be used.

Scope: Button command definitions are session specific.

 

Return to top

g. Entry Assist

 

 
Purpose: Allows the user to employ certain text editing formatting features such as margins and tab stops when using host based text editors. Traditionally, host support was required for standard Entry Assist features, but DCSE’s Entry Assist emulates these features on the client end, making host support unneccessary. It also supports additional features such as a margin bell and word wrap.
Accessed via: Settings: Session Profile: Entry Assist.
Configuration: The interface allows the user to set, clear, and clear all tab stops, and to load and save Entry Assist settings.
Settings stored: In DCSE3270.INI, under the associated session profile.
Defaults: Entry Assist is disabled by default.
Scope: Entry Assist settings are session specific.

 

Return to top

h. Login/Connection Options

 

 
Purpose: Allows a session to be configured to connect using several different Telnet and security / identification options.
Accessed via: Settings: Session Profile: Host
Configuration:

DCSE supports Telnet Name Override, which allows the user to force the session’s Telnet name to be any terminal name allowable by the host, while overriding the name defined under the terminal model selection dialog. DCSE can specify an eight character Session Long Name, which will be displayed in the terminal window in the Operator Information Area for reference.

For IBM 3270, an option exists to specify an LU name as part of the Telnet Name, if the Telnet server gateway supports RFC 1646. This can be either a specific LU or an LU pool name. Users can also define a password for the session. This password is then made available to the Password System Command and can thus be mapped to a key, hotspot, flashpad, etc. This password is encrypted when stored in the DCSE3270.INI file. TCP Port and Connect Timeout parameters can also be set here. These settings can all be loaded and saved from the Hosts dialog.

Settings stored: DCSE3270.INI, under the appropriate session profile heading.
Defaults:

IP/Host Gateway: Default is the host for the selected session.

Session Long Name: Sess - (x), where (x) is the number of the current session.

TCP Port: 23

Connect Timeout: 30

All other values are empty by default.

Scope: These settings are session specific.

 

Return to top

i. Mouse Options

 

 
Purpose: DCSE provides mouse button customization features which give users quick access to commonly performed functions.
Accessed via: Settings: Session Profile: Mouse
Configuration: The right and left mouse buttons, alone or in combination with Shift, Control Key, or Shift+Control key combinations, can be assigned to execute system commands or edit commands, launch Quick Keys, send characters, or simulate host keystrokes. Single and double click functionality can be redefined. User changes can be set, reset, loaded or saved to/from a session profile.
Settings stored: In DCSE3270.INI, under the associated session profile.
Defaults: Defaults are hard-coded, and will be used if no entry is present in DCSE3270.INI under the selected session profile. Defaults may be restored by selecting Reset All in the Session Profile: Mouse dialog.
Scope: Mouse settings are session specific.

 

Return to top

j. Hotspots

 

 
Purpose: Allows the user to define text strings to be highlighted when they appear in the terminal window. When the user double clicks the hotspot, it can execute a system command, launch a Quick Key macro, send a character, or send a host keystroke. When hotspots are enabled, URLs will also be identified as hotspots and will launch the browser configured under Ext Progs when clicked (see External Programs above for more information)
Accessed via: Settings: Hotspots
Configuration: Hotspot values support optional case sensitivity, and also provide several predefined default hotspot sets for function and PF keys. These values are also saved and applied globally to all sessions. However, the property to enable/disable hotspots is session specific, set under Settings: Session Profile: Display: Show Hotspots. Also note that hotspots, when enabled, will appear anywhere that the specified text appears in the terminal window, regardless of the screen’s context.
Settings stored: DCSE3270.INI file, under the heading [Default.Hotspots]. The setting to enable/disable hotspots is session specific, and stored under the tag Show Hotspots= in the appropriate session profile.
Defaults: Hotspots are disabled (in the session) by default. Three default hotspot sets are available globally, and are all turned on by default.
Scope: Hotspots are enabled/disabled for individual sessions. However, the hotspots available to a given session are defined globally. See above for more details.

 

Return to top

k. Flashpads and the Flashpad Editor

 

 
Purpose: DCSE comes with a default flashpad with commonly used functions. The flashpad’s dimensions can be dynamically resized by the user. DCSE also gives the user the ability to edit custom flashpads.
Accessed via: Settings: Flash Pad Editor (to create or edit a flashpad)
Settings: Load Flash Pad (to load a default or custom flashpad)
Configuration: Flashpads can be programmed to execute system commands, launch a Quick Key macro, send a character, or send a host keystroke. 16 buttons are defined in the default flashpad, but the user may add more (DCSE supports more flashpad buttons than can actually be displayed on the screen!). Up to five flashpads are supported simultaneously.
Settings stored: The flashpad definition is saved under the [Flashpadname.Poppad] section of the DCSE3270.INI file. If a flashpad is active when the last open session is closed, that status is written to the [System.Settings] section of DCSE3270.INI under the Active Poppads= label.
Defaults: No flashpads are loaded by default when DCSE starts.
Scope: The flashpads are available to all sessions, and once launched, apply to whatever session is in focus.

 

Return to top

 

4. Printing

Version 3.2 of DCSE supports 3270 printer emulation via a stand - alone executable, DCPRT32.EXE (DCPRT16.EXE for 16 bit installations). Both LU1 (SCS) and LU3 (DSC) printer types are supported. DCSE also provides Print Screen functionality for all supported emulations.

 

Return to top

 

5. File Transfers

DCSE supports IND$FILE transfers under CICS, TSO and CMS. It can designate either a file or the clipboard as the target/source for the transfer. DCSE also supports FTP, via a menu pick which launches any FTP program designated by the user. The default FTP program is FutureSoft’s FTP. The path is designated under Settings: Session Profile: Ext Progs: FTP program, and the default path is: DCSE\Programs\FTPEXE.EXE. Please note that any other FTP program, such as WS_FTP, can be designated here. See section II B3.4 External Programs for more information about this feature.

 

Return to top

 

6. HLLAPI Support

DCSE supports the following standards: EHLLAPI, HLLAPI, WOSA WinHLLAPI, and DOS HLLAPI VxD. DCSE contains 3 sample HLLAPI applications which demonstrate support for HLLAPI function calls in DCSE. These three executables are EHLLTEST.EXE (to demonstrate support of the 16 bit EHLLAPI standard) and WHLLTEST.EXE and WHLTST32.EXE, to demonstrate 16 and 32 bit WinHLLAPI support, respectively. These demonstrations reside in the DCSE\DEVKIT subdirectory.

 

Return to top

 

7. Macros

Macro capability in DCSE is implemented using WinWrap Basic, a high-level macro language with syntax similar to Visual Basic. The product includes a macro editor and a macro recorder utility to aid in application development. DCSE v. 3.2 does not contain support for the DynaComm Scripting language.

 

Return to top

 

8. Documentation/Help

 

DCSE’s documentation is all available online as Windows Help files. No printed manuals are currently available for DCSE.

 
TITLE DOCUMENT # EDITION Help File
DynaComm Special Edition Help
(32-bit)
Not availale. Not availale. DCSE32EN.HLP
DynaComm Special Edition Help
(16-bit)
Not available Not available DCSE16EN.HLP
PrintSession Help
(32-bit)
Not available Not available DCPRT32.HLP
PrintSession Help
(16-bit)
Not available Not available DCPRT16.HLP
FutureSoft FTP Help Not available Not available FSFTP.HLP
WinWrap Basic Help Not available Not available WINWRAP.HLP
WinHLLAPI Programmer’s guide Not available Not available WHLLAPI.HLP

Return to top

 

III. Technical Specifications

 

A. System Requirements


Minimum

  • IBM compatible PC with a 386 or higher microprocessor, with at least 8 MB RAM
  • Floppy disk drive
  • Hard disk with at least 10 megabytes of free disk space
  • Microsoft Windows 3.x (this requires the 16 bit version of DCSE)
  • Winsock compatible TCP/IP stack

Recommended

  • IBM Compatible PC with a 486 or higher microprocessor, with at least 16 MB RAM
  • Floppy disk drive
  • Hard disk with at least 10 megabytes of free disk space
  • Microsoft Windows 95, or Windows NT v.3.51 or higher
  • Microsoft’s 32 bit TCP/IP stack

Return to top

 

B. Installation

 

DCSE ships with five 3.5 inch floppy diskettes. Note: DCSE includes all files required for 32 bit or 16 bit operating systems in the 5 disk package. Setup will detect the operating system in use and install the appropriate version of DCSE.


 
Disk Usage Table 32-bit install 16-bit install
Program Files 2,754 Kbytes 3,726 Kbytes
HLLAPI Development Files 833 Kbytes 532 Kbytes
True Type Fonts 170 Kbytes 170 Kbytes
WinWrap Basic Sample Programs 30 Kbytes 30 Kbytes
Full Installation Footprint 3,657 Kbytes 4,458 Kbytes

 

Return to top

 

C. Configuration File and Registry Modifications


DCSE does not make Windows Registry additions or modifications. Likewise, SYSTEM.INI and WIN.INI are not modified. The only file which resides outside of the DCSE directory structure is DCSE3270.INI, which is placed in the Windows directory by default.

 

Return to top

 

D. Directory Structure

 

 

Return to top

 

E. Icons


 
DCSE32EN.HLP (DCSE16EN.HLP for 16 bit systems) is the main Windows help file/online manual for DCSE. This file is located in the DCSE\Programs subdirectory.
This is the shortcut to DCSE32.EXE (or DCSE16.EXE for 16 bit systems), the main executable for Special Edition. This executable brings up the Open New Session dialog when launched, and allows the user to select VT, 3270, or 5250 emulation.
This icon launches an EHLLAPI sample application which demonstrates 16 bit EHLLAPI function calls supported in DCSE. The file, EHLLTEST.EXE, resides in the DCSE\Devkit subdirectory.
This is the shortcut to DCPRT32.EXE (or DCPRT16.EXE for 16 bit systems), the stand-alone print emulator included with DCSE 3.2. This will launch PrintSession in its own frame, and allow emulation of LU1 (SCS) or LU3 (DSC) printers via TN3270.
README.WRI contains the release notes for DCSE. See also FIXES.WRI for information on bug fixes/enhancements added to the associated release.
Shortcut to TELNET.EXE. This executable acts as a shim to allow multiple session support under Windows 3.1x. It will bring up the Open New Session dialog preconfigured to select a DEC VT terminal emulation.
Shortcut to TN3270.EXE . This executable acts as a shim to allow multiple session support under Windows 3.1x. It will bring up the Open New Session dialog preconfigured to select an IBM 3270 terminal emulation.
Shortcut to TN5250.EXE. This executable acts as a shim to allow multiple session support under Windows 3.1x. It will bring up the Open New Session dialog preconfigured to select an IBM 5250 terminal emulation.
This icon launches \WIN95\UNINST16.EXE and passes the parameter -fC:\DCSE\DeIsL1.isu to uninstall DCSE. under Windows 3.1x and Windows NT 3.51. The icon is not neccessary under NT 4.0 and Windows 95, which use Add/Remove Programs.
This icon launches a WinHLLAPI sample application which demonstrates 16 bit WinHLLAPI function calls supported in DCSE. The file, WHLLTEST.EXE, resides in the DCSE\Devkit subdirectory.
This icon launches a WinHLLAPI sample application which demonstrates 32 bit WinHLLAPI function calls supported in DCSE. The file, WHLTST32.EXE, resides in the DCSE\Devkit subdirectory.
WHLLAPI.HLP is the online WinHLLAPI Programmer’s Guide, in Windows Help format. It is located in the subdirectory DCSE\DEVKIT.

 

Return to top

 

F. Configuration/Initialization Files

 

 
NAME TYPE DEFAULT LOCATION DESCRIPTION
SETUP.INI TEXT Installation Disk 1 Holds setup data, can configure DCSE to install additional files, customize default path for installed files.
DCSE3270.INI TEXT Windows home directory Contains all global DCSE system settings, session profiles, and session preferences. All session preferences are stored in this file.

 

Return to top


Purchase Contact Privacy Policy Terms of Use Sitemap Blog
© 2010 FutureSoft, Inc. All Rights Reserved

 
DynaComm i:filter | Internet Filtering | Employee Internet Monitoring | Managing Internet Access | Web Filtering | Internet Monitoring | DCS
Terminal Emulation | TN 3270 | ProComm Plus Replacement | Windows Terminal Emulation | TN 5250 | DynaComm Connectivity Series | MultiView