# NonStop 6530 Terminal Emulator

Source: https://wndsoftware.com/nonstop-terminal-emulator

### NonStop 6530 Terminal Emulator in WND Terminal

Use 6530 emulation with HPE NonStop and Tandem applications. Work in conversational mode, then use protected fields and host function keys in block mode.


### Supported terminals and connections

On a small screen, swipe the table to read all columns.


| System | Terminal | Connection | Where it runs | Current scope | Release |
| --- | --- | --- | --- | --- | --- |
| [HPE NonStop 6530](https://wndsoftware.com/nonstop-terminal-emulator) | 6530 | Telnet | Windows, Mac, Linux | Conversational and block-mode 6530 sessions with function keys, common page behavior and status responses. | v1.0.319 |

The 6530 profile answers terminal-status requests and keeps independent selected and displayed pages. Applications needing block LRC/ACK retries or gateway-specific behavior need a compatibility check.


### What the sample does

The simulated NonStop host starts at a TELSERV choice prompt. Select TACL and run an inquiry for JONES, amount 250, with F1.

[Download the compatibility lab](https://wndsoftware.com/downloads/wnd-compatibility-lab.zip) (Python 3 and WND Terminal required)


### Connect to your host

Choose Tandem 6530 on the WND Terminal connect page and enter the host address. The current profile uses Telnet, with port 23 as its default.

[Read the connection guide](https://wndsoftware.com/docs/other-terminals)

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](https://wndsoftware.com/docs/import-other-emulators) for supported source formats; the connection type alone does not prove that an old profile or macro can be imported.


### Check HPE NonStop 6530 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 |
| --- | --- |
| Start with TELSERV and TACL | Confirm the expected service selection and a read-only TACL inquiry before proceeding to the business application. |
| Exercise block mode | Navigate protected and editable fields and send the host function key expected by the application. Compare the resulting host action with the working client. |
| Check page selection | The profile keeps selected and displayed pages independently. Use a workflow that changes pages and verify the application returns to the expected display. |
| Keep error handling in the test | Try a validation error and cancellation path. Ordinary inquiry success can miss cursor, protection and keyboard-state problems. |
| Identify gateway dependencies | Block LRC/ACK retry handling and gateway-specific behavior need a customer-host compatibility check; do not infer them from a basic Telnet connection. |

Bring the host address, selected terminal type, keyboard map and the steps that reproduce a problem to a [proof of value](https://wndsoftware.com/proof-of-value). Distinguish a simulated sample from a customer-host result in the test record. See [supported systems and profile limits](https://wndsoftware.com/supported-systems) for the current release scope.


### Keyboard and host workflow

Record how the current connection selects a service through TELSERV and reaches TACL or the business application. Test conversational input before switching to the application's block-mode screens. In the block workflow, include protected labels, editable fields and the function key the host expects to submit the record. Check both the selected page and the displayed page when the application changes them; treating those as the same state can hide a navigation problem.


### When a screen or key behaves differently

A NonStop application error is not automatically a terminal-emulation failure. Preserve the host message, selected service, last key and screen state. Repeat a read-only inquiry and then a validation-error path using fictional data. If a failure appears only through a particular gateway, compare that path separately. Block LRC/ACK retries and gateway-specific behavior require a customer-host compatibility check rather than an inference from a successful Telnet connection.


### Replacing an existing terminal client

For an existing Tandem or 6530 workstation estate, retain the service selection and keyboard configuration alongside the connection address. The sample TELSERV and TACL inquiry demonstrates a defined software-host workflow. It does not prove every NonStop application or retry convention. Keep evidence of conversational entry, block submission, page changes and cancellation before deciding that the replacement is ready for a group rollout.

[Keyboard-map documentation](https://wndsoftware.com/docs/keyboard-maps) · [Specialty terminal configuration and limits](https://wndsoftware.com/docs/other-terminals)


### Related terminal models

[Unisys T27 and UTS Terminal Emulator](https://wndsoftware.com/unisys-terminal-emulator) · [HP 3000 Terminal Emulator: HP 700/92 and 2392A](https://wndsoftware.com/hp3000-terminal-emulator) · [VT Terminal Emulator for UNIX and Linux](https://wndsoftware.com/vt-terminal-emulator)

Use the [supported-systems index](https://wndsoftware.com/supported-systems) to compare released profiles and limits. The [emulator evaluation checklist](https://wndsoftware.com/emulator) covers the broader deployment decision.