Products Purchase Support Download    News About

Support - DynaComm® UTS

DynaComm® UTS


Technical Profile


Contents


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

I. Overview

A. Release History


II. Functionality

A. Platforms Supported

B. Basic Functionaliy

1. Emulations

2. Connectors

3. File Transfer Protocols

4. Macros

5. Scripting

6. Tools/User Interface

a. Save Screen As

b. Capture

c. Color Properties

d. Control Page Bar

e. Shortcut Key Mapper

7. Documentation/Help

C. Enhancements

1. API Options

2. Development Tools & Utilities

a. Script Bar

b. Auto Script

c. Screen Maker

d. Log Viewer

e. Trace

 

III. Technical Specifications

A. Minimum Recommended System Requirements

B. Installation

1. General

2. Installation Procedure

C. Icons

D. Configuration/Initialization Files

 

I. Overview

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

DynaComm UTS (DCUTS)

DynaComm UTS (DCUTS) is a full featured application that provides UTS terminal support for Series 1100/2200 and System 80 mainframe. DCUTS is designed to provide users with the flexibility to integrate a Unisys host mainframe with a PC–based Windows environment. The macro and scripting language allows users to automate various tasks to make host applications easier to use.

 

A. Release History

 

 
Version Release Date Release Status
DCUTS 5.1.00 August 23, 2004 Supported
DCUTS 4.1.40 August 23, 2002 Supported
DCUTS 4.1.39 April 29, 2002 Supported
DCUTS 4.1.38 January 7, 2002 Supported
DCUTS 4.1.36 April 20, 2001 Supported
DCUTS 4.1.34 August 15, 2000 Supported
DCUTS 4.1.32 March 8, 2000 Supported
DCUTS 4.0.34 August 15, 2000 Supported
DCUTS 4.0.32 January 7, 2000 Supported
DCUTS 4.0.29a August 19, 2000 Supported
DCUTS 4.0.29 September 21, 1999 Supported
DCUTS 4.0.27 June 14, 1999 Supported
DCUTS 4.0.24b April 27, 1999 Supported
DCUTS 4.0.24a April 23, 1999 Supported
DCUTS 4.0.24 April 14, 1999 Supported
DCUTS 4.0.21 March 4, 1999 Supported
DCUTS 4.0.18a February 10, 1999 Supported
DCUTS 4.0.18 November 12, 1998 Supported
DCUTS 4.0.17 October 6, 1998 Supported
DCUTS 4.0.14 September 23, 1998 Supported
DCUTS 4.0.12 June 25, 1998 Supported
DCUTS 4.0.10 May 29, 1998 Supported
DCUTS 4.0.6 March 15, 1998 Supported
DCUTS 4.0.5 January 1, 1998 Supported
DCUTS 4.0.3 November 15, 1997 Supported
DCUTS 4.1 September 6, 1997 Supported
DCUTS 4.0 July 30, 1997 Supported
 

Return to top

 

II. Functionality

 

A. Platforms Supported

  • Windows 95
  • Windows NT 3.51
  • Windows NT 4.0
  • Windows 2000
  • Windows XP

Return to top

 

B. Basic Functionality


1. Emulations -- The following terminal types are emulated by DCUTS

  • UTS20
  • UTS30
  • UTS40
  • UTS60
  • U200P/U400P
  • U300
  • SVT 1120

2. Connectors -- DCUTS connects to aUnisys 2200 host via DCP or HLC over Winsock

  • Winsock

3. File Transfer Protocols -- standard with the base DCUTS

  • FTU
  • Masterlink
  • MAPPERFTS
  • Text

4. Macros

 

A DCUTS macro control is a sequence of commands utilizing the functionality of the scripting language. The major difference between a macro and a script is that a macro is limited to 256 characters, however, a macro can execute one or more scripts which makes it flexible and easily expandable. The two methods of executing a script from a macro is through the CALL and CHAIN commands. The difference between these two commands is that if the user CALLs a script, execution will be returned to the macro key control, whereas if CHAIN is used to a script control, execution will not return to the macro.

 

5. Scripting

 

The scripting language in DynaComm UTS is a powerful assistant to the interactive terminal work. A script file can be invoked for each terminal concurrently, which allows the user to have one script waiting for a particular message in one terminal window, while executing different scripts in other terminal windows. The scripts within DCUTS are uncompiled text files that can be created and modified either within the DCUTS application or in other text editors. The editor that DCUTS launches to create and open scripts is Windows Notepad. DCUTS includes powerful scripting tools for debugging purposes and in the creation of screens that look and feel like host application screens.

 

Return to top

 

6. Tools/User Interface

 

DCUTS provides users with several tools to customize their workspace and automate common tasks.

 

a. Save Screen As

 

 
Purpose: Take a snapshot of a terminal screen including all text and screen control characters (color, protection, highlighting etc.) In combination with the Screen Maker, it can be used to design terminal screens, including field edits, color, line and box drawings, which can be incorporated into user designed scripts.
Accessed via: File: Save Screen As
Configuration: Creates a graphic .SCN or .WMF file, configuration is accessible via the Windows Save As dialog.
Defaults: The default folder/directory for the graphic file is DynaCommUTS, but other folders/directories can be selected.
Scope: Applies to a single terminal screen.

 

Return to top

 

b. Capture

 

 
Purpose: Capture all data sent from the host to the active window in a text file.
Accessed via: File: Capture
Configuration: If Snap Screen Text is selected, the contents of the active window will be copied to the capture file. Selecting the Clear Captured Text item will clear all text captured in the buffer and in the currently assigned capture file.
Settings stored: In the configuration file .CFG located in the DynaCommUTS folder/directory.
Defaults: The Capture option is off by default.
Scope: Capture option applies to a single terminal window. If the user wants to capture data for multiple terminals, a capture file needs to be set up for each terminal.

 

Return to top

c. Color Properties

 

 
Purpose: Allows users to create and save custom color schemes which associate host field attributes to the terminal colors specified.
Accessed via: Settings menu: Terminals: Colors
Configuration: Host field attributes are displayed with their current color schemes. Users can modify the foreground and background color by selecting the field attribute(s) and choosing the color from the palette. The selected color scheme can be applied to the current terminal or to all configured terminals.
Settings stored: The custom color scheme is stored in the configuration file .CFG located in DCUTS home directory.
Defaults: The default configuration file DCUTS.CFG comes with hard coded color schemes for the different host field attributes. If the user creates a new settings file, the default colors will be black on white on most fields, except for unprotected fields which will have green on black.
Scope: Color schemes are specific to the configuration file. They can be applied to terminals on an individual basis or to all the terminals defined in the configuration file

 

Return to top

 

 

d. Control Page Bar

 

 
Purpose: Represents the standard terminal control page. Each screen has its own control page options and, when this toolbar is visible, the current control page values are displayed and updated if the host sends messages that changes any of these options.
Accessed via: File: Control Page Bar
Configuration: The toolbar can be expanded to show file transfer details for a control page file transfer in progress. The user can also select one of the following print modes, FORM, PRNT or XPAR, in addition to selecting a Transmit and/or Transfer mode.
Defaults: The defaults are PRNT for the Print mode, and VAR for the Transmit and Transfer modes.
Scope: The Control Page Bar is specific to the terminal in which it is accessed.

 

Return to top

 

e. Shortcut Key Mapper

 

 
Purpose: Allows user to edit shortcut keys for any menu entry.
Accessed via: Settings menu: Keys
Configuration: User selects an existing key map style (1, 2 or 3) to edit, and is then able to create, change, or delete the shortcut keys for the menu items. It is possible to have the same menu item accessed by multiple shortcut keys.
Settings stored: The user defined shortcut key settings are stored in the configuration file .CFG in DCUTS home directory.
Defaults: The shortcut keys are specific to the chosen key map style, and applies to all terminals within that particular configuration file. The DCUTS.CFG configuration file that comes with DCUTS and new configuration files use the 3 hard coded key map styles by default.
Scope: The shortcut keys applies to all terminals specified within the current configuration file.

 

Return to top

 

7. Documentation/Help

 

All DCUTS documentation is available online. The help file is stored in the root of the DCUTS folder as “dcuts.hlp”.

 

Return to top

 

C. Enhancements

 

1. API Option

 

The optional user program for the DCUTS application is no longer available.

 

2. Development Tools and Utilities

 

a. Sript Bar

 

The Script Bar helps the user in monitoring and debugging scripts in DCUTS. It can be accessed manually from the View Menu: Script Bar, the Tools menu: Step Into Script, or if the command ON SHOW is included in the script. The Script Bar allows single command line execution via the step option or it can execute the lines automatically without user intervention. Using the Step Mode the user is also able to ignore a command line if he/she does not want it to be executed.

 

b. Auto Script

 

The Auto Script item under the Tools menu, allows the user to record a script automatically. To start recording, go to the Tools Menu: Auto Script and enter a filename for the script. The keystroke will be recorded by the Auto Script to the specified file. When the user is finished recording, the script can be stopped by selecting the Auto Script item again.

 

c. Screen Maker

 

DCUTS has a Screen Maker that is most often used in combination with the Save Screen option. The Screen Maker supports the field control character operations for the user to create his/her own screens or it can be used to check the field types that the host sends to the terminal. With the Screen Maker, the user can create screens that look and feel like terminal screens, save them using the Save Screen option and access them from a script. The Screen Maker Bar can be accessed from the View Menu: Screen Maker Bar.

 

d. Log Viewer

 

The Log Viewer allows the user to capture information that is entered in the terminal and that is sent to the host. It provides several options for what information the user wants to capture in the log by the use of different filters. For instance, if the user wants to check for the keystrokes entered in the terminal, enabling the Keystrokes filter will log every keystroke the user makes. The log viewer can be accessed from the Tools Menu: Log Viewer.

 

e. Trace

 

DCUTS has included a specific trace option to aid with diagnostics and troubleshooting. Available under the Tools menu, Trace gives the user the option to capture information to and from the host. It also has options to select different filters depending on the type of problem that needs to be investigated, in addition to a comments section where the user can make personal notes to the nature of the trace.

 

Return to top

 

III. Technical Specifications

 

A. Miniumum Recommended System Requirements


  • IBM compatible PC with a 486 or higher microprocessor, with at least 16 megabytes of RAM
  • Floppy disk drive
  • Hard disk with at least 2 megabytes of free disk space
  • Microsoft Windows 95, or Windows NT v.3.51 or higher, or Windows 2000, or Windows XP
  • Free network connection

Return to top

 

B. Installation


1. General

  • DCUTS ships with one 3.5 inch floppy diskette
  • Full Installation Footprint: 1.82 Mbytes

 

2. Installation Procedure


The installation of DCUTS performs the following main functions, in this order:

  1. Asks the user to enter the name of the registered user and their company name.
  2. Creates a program group and copies the user files.
  3. Launches the product.

Return to top

 

E. Icons


 
DCUTS.EXE is the DynaComm UTS main executable. This executable can be set up to open a connection to a host or perform a macro or a script when it is launched.
DCUTS.HLP is the on-line help file that includes details about the functionality of DynaCommUTS in general, as well as its macro and scripting language.
UNINSTALL.EXE is stored in the root folder of DynaCommUTS. Executing Uninstall will remove the DCUTS executable and its configuration files from the hard drive.

 

Return to top

 

F. Configuration/Initialization Files

 

 
NAME TYPE DEFAULT LOCATION DESCRIPTION
*.CFG TEXT DynaCommUTS Configuration preferences (terminal names, keys, macros etc.)
DCUTS.CNT TEXT DynaCommUTS Table of contents for the help file
INSTALL.LOG TEXT DynaCommUTS Logs the paths to where DCUTS is installed. Used when uninstalling DCUTS
QHOSTS TEXT DynaCommUTS Host configuration 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