HP 700/94 Terminal Emulator: Partial Profile in WND Terminal
Choose HP 700/94 for a first HP 3000 application check with character, block and basic form behavior.
Supported terminals and connections
On a small screen, swipe the table to read all columns.
| System | Terminal | Connection | Where it runs | Current scope | Release |
|---|---|---|---|---|---|
| HP 700/94 partial profile | HP 700/94 (partial) | Telnet | Windows, Mac, Linux | HP 700/94 selection with common character, block and basic form behavior over Telnet. | v1.0.319 |
The current common-form subset excludes 700/94-specific edited and transmit-only fields, data checks, forms cache, query replies and full VPLUS behavior.
What the sample does
The software HP host starts at a prompt and accepts a three-field order entry without HP hardware.
Download the compatibility lab (Python 3 and WND Terminal required)
Connect to your host
Choose HP 3000, select HP 700/94 (partial), enter the host and port, and confirm the terminal-type value expected by the host.
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 Partial HP 700/94 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 |
|---|---|
| Choose the partial model deliberately | Select HP 700/94 only when its documented common-form subset fits the application test. It is distinct from the HP 700/92 and 2392A profiles. |
| Test prompt and form transitions | Use a read-only command, then the supplied three-field order form. Compare cursor placement and what the host receives at submission. |
| Inspect validation behavior | Trigger an application validation error with fictional data. A successful normal form does not validate all data checks or edited-field behavior. |
| Check VPLUS dependencies | Full VPLUS behavior, forms cache, query replies, and model-specific edited or transmit-only fields are outside this subset. |
| Agree acceptance criteria | List every workflow that relies on the excluded behaviors and test it with the customer host. Do not use the software example as a claim of complete HP 700/94 hardware equivalence. |
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
HP 700/94 is a partial profile separate from the HP 700/92 and 2392A choices. Select it only when its documented common-form behavior matches the application being evaluated. Start with a read-only command and then the sample three-field order form. Compare field entry, cursor position and the data submitted by the normal application key. Keep the existing terminal model and key definitions with the test record.
When a screen or key behaves differently
A form that accepts one record does not establish full VPLUS behavior. Trigger an application validation error with fictional data and compare the redraw and editable fields. Preserve the exact screen and operation when behavior differs. Full VPLUS, forms cache, query replies and model-specific edited or transmit-only fields are outside the subset; identify these requirements before interpreting a failed workflow as a general connection problem.
Replacing an existing terminal client
An existing HP workstation can depend on behavior absent from the sample form. Inventory those dependencies before replacing it and consider the separate HP 3000 profiles only when they match the host configuration. WND Terminal's software example establishes a repeatable starting point for comparison. A customer-host proof of value must establish the actual workflows, and any excluded functions should remain on the known working client until a suitable path is proved.
Keyboard-map documentation · Specialty terminal configuration and limits
Related terminal models
HP 3000 Terminal Emulator: HP 700/92 and 2392A · Unisys T27 and UTS Terminal Emulator · NonStop 6530 Terminal Emulator
Use the supported-systems index to compare released profiles and limits. The emulator evaluation checklist covers the broader deployment decision.