Unisys T27 and UTS Terminal Emulator in WND Terminal
Open ClearPath MCP applications with T27 emulation and OS 2200 applications with UTS 60 emulation. Use the host's forms and actions in the same app as your IBM sessions.
Supported terminals and connections
On a small screen, swipe the table to read all columns.
| System | Terminal | Connection | Where it runs | Current scope | Release |
|---|---|---|---|---|---|
| Unisys ClearPath MCP T27 | T27, TD830 family | Telnet | Windows, Mac, Linux | Forms, XMIT/SPCFY, configurable F/SF keys and page memory in T27 Telnet sessions. | v1.0.319 |
| Unisys ClearPath OS 2200 UTS 60 | UTS 60 | Telnet | Windows, Mac, Linux | Formatted fields, XMIT, function keys, message waiting and conventional tab navigation over Telnet. | v1.0.319 |
T27 supports configured F/SF key bytes and page memory; automatic host-programmed key definitions still need a customer-host check. UTS 60 uses Telnet. Its RFC 1006 transport probe does not implement the OS 2200 application envelope.
What the sample does
The simulated T27 host shows an ACME customer balance after an XMIT form submission. The UTS host accepts a BOLT order for 12 using a hidden PIN field, then displays a message-wait notice.
Download the compatibility lab (Python 3 and WND Terminal required)
Connect to your host
Choose Unisys, HP, Tandem and airline hosts on the WND Terminal connect page. Select T27 or UTS 60 and enter the host address. Both current profiles use Telnet; the default port is 23.
The software-host examples let you try these workflows now. WND Software checks your application workflows during a proof of value and addresses compatibility differences found.
Move an existing session
Bring the host address, port, terminal type, key assignments and macros used by your team. Create a WND Terminal connection with the settings above, then run the actual screens and keys your application uses. Check the session import guide for supported source formats; the connection type alone does not prove that an old profile or macro can be imported.
Test your exact terminal model.
Bring the connection settings and screens your team uses. We will agree on the workflow to prove during a free two-to-four-week proof of value.
Check T27 and UTS 60 against your application
Keep a working session profile and a repeatable test case. Compare what the application receives as well as what the terminal draws. Use the software-host examples as a starting point, then record the results on the actual host before a rollout.
On a small screen, swipe the table to read all columns.
| Application check | What to verify |
|---|---|
| Match the host family | Use T27 for MCP and UTS 60 for OS 2200. A successful TCP connection does not establish that the application data stream matches the selected family. |
| Test a form submission | For T27, compare the configured XMIT and function-key bytes with the working terminal. Include a form that spans more than one page. |
| Check the UTS workflow | Exercise input fields, the hidden PIN field and message-wait behavior with fictional data before testing a customer application. |
| Confirm transport | The current profiles use Telnet. Do not assume the RFC 1006 probe implements the OS 2200 application envelope. |
| Review host-programmed keys | T27 automatic host-programmed key definitions require a customer-host check. Preserve the current key map and identify every action that depends on it. |
Bring the host address, selected terminal type, keyboard map and the steps that reproduce a problem to a proof of value. Distinguish a simulated sample from a customer-host result in the test record. See supported systems and profile limits for the current release scope.
Keyboard and host workflow
Start with the terminal family, not the ClearPath brand alone. A T27 application on MCP and a UTS 60 application on OS 2200 use different screen and submission rules. For T27, record the F and SF keys, the bytes configured for each key, and the page displayed before transmission. Compare an XMIT submission with the working client. For UTS, include a form with a protected label and a hidden input so the test checks what is transmitted as well as what is visible.
When a screen or key behaves differently
Keep the MCP or OS 2200 application response together with the current terminal profile. A form that paints correctly can still submit the wrong fields or key sequence. Separate host validation messages from a connection failure, then repeat the smallest failing inquiry with fictional data. T27 automatic host-programmed key definitions and the OS 2200 application envelope over RFC 1006 need explicit verification; the released Telnet sample does not establish those behaviors.
Replacing an existing terminal client
When replacing an InfoConnect or another Unisys workstation setup, inventory the session transport, function-key definitions and any peripheral services separately. The T27 and UTS software hosts supplied with WND Terminal are useful for checking a repeatable baseline. They are not a substitute for proving the real customer application's pages and transmission rules. Preserve the working client until those workflows have passed.
Keyboard-map documentation · Specialty terminal configuration and limits
Related terminal models
HP 3000 Terminal Emulator: HP 700/92 and 2392A · NonStop 6530 Terminal Emulator · Airline ALC Terminal Emulator
Use the supported-systems index to compare released profiles and limits. The emulator evaluation checklist covers the broader deployment decision.