QTerm 7.0

The 7.0 version of QTerm brings a new look and easily accessible function panels which can be permanently displayed (pinned) or can be automatically hidden and only displayed when moused over. Mutiple frame windows are also supported with one or more terminal windows in each frame. This allows you to easily take advantage of multiple monitors.

If you are interested in trying out the new version please click here to download the software

Click New to close.





ActiveUTS is an ActiveX control that provides the complete functionality of a UTS type terminal connected over TCP/IP to a Unisys 2200 mainframe.  As an ActiveX control, it must be hosted inside a container, such as a Visual Basic program, which can use the over 200 properties, methods and events provided.

VTermUTS is a sample VB program that contains a single instance of the ActiveUTS control.  The menus, toolbar and status bar are provided by the VB program which calls on the various control methods to activate the commands.  All screen interaction via mouse and keyboard is performed directly by the control.

Sample ActiveUTS VB container program

Typical usage falls into one of two arenas, as a visible "terminal" screen on the container's window or .as an invisible transport provider for host connections:

Visible Terminal

Here you would design an application (eg Visual Basic or PowerBuilder) and make space available on your main window to show the control (as in the example above).  In this case the user interacts with the screen via mouse and keyboard as with the full QTerm emulator. You can add buttons and list boxes etc. to your program and use them to drive the exposed properties and methods of the control to augment the user interaction.

Invisible Transport

A typical scenario would be where you develop a GUI program tailored to your host transactions and need the control to provide the host transport, presentation protocol and data stream interpretation. What this means is that a hidden screen is used to "display" all the host messages and your messages to be sent to the host. Your program can then use the events or screen scraping methods provided in order to conduct a conversation with the host. In this case you will probably make most use of the exposed properties and methods to control the session because all user interaction would be with your program and not directly with the control's screen (it being invisible).


Please refer to the QTermSDK for a detailed description of the programming interfaces.