WND Terminal is the emulator enterprises switch to when they want their people to notice nothing but the bill. Today’s release adds ten capabilities that people will notice: less retyping, faster answers, cleaner migrations and evidence security teams have never had from the terminal. They all ship today, and they all run inside your network.
When Union Pacific moved 7,800 operations users to WND Terminal in eight weeks, people kept their existing keyboard layouts. When Texas HHSC rolled it out, the trial group started forwarding each other screenshots of Excel. Both are what a good emulator should do: keep the screens and keys people trust, and take the busywork off them.
This release takes that second part further, for the three groups that live with the green screen: the people who do the work, the IT team that runs it, and the security and operations teams that answer for it.
For the people who do the work
Fill from Excel
Drop a spreadsheet on a CICS transaction, an ISPF panel or an IBM i entry screen. WND Terminal matches the columns to the screen’s fields by their labels (“Acct No” finds ACCOUNT NUMBER), shows a dry run without sending anything, then types every row. It reads what the host said after each one, stops at the first error with Resume, Skip and Stop, and saves a copy of your spreadsheet with a Status and a Result column. Every row is in the audit log, without what was typed.
Capture all pages
One key (Ctrl+Shift+A) on an ISPF 3.4 list, an SDSF job list or an IBM i Work with Spooled Files list, and WND Terminal pages to the end, keeps the headings once, drops the rows that overlapping pages repeat, and gives you one table: “Captured 600 rows from 36 pages.” Save it as Excel with leading zeros intact, or as CSV.
Modern view
One key (Ctrl+Shift+M) turns the same live screen into a clean form: labeled fields, hints, numeric fields that take only numbers, a Today button on dates, function keys as buttons, messages as colored banners, lists as sortable grids and menus as options to click. It’s the same connection, so nothing changes on the host and there is no project to set up. Anyone can improve a screen with Customize; IT can give everyone the same screen layouts from a share.
Guided training on live screens
A trainer does a task once; WND Terminal writes each step’s hint in plain English. New hires then follow it on the real screen: the field to type into is outlined with a callout (“Type the policy number here, then press PF5”), the key pulses, and the guide moves on as each screen appears, whatever data is on it. It notices when someone goes off track, and managers see progress in one view, never what was typed.
For the people who need answers
Ask WND
Type “Why did PAYRL01 fail last night?” and WND works your session the way you would: it opens SDSF, filters to the job, opens last night’s run, reads the job log and the program’s messages, finds the S0C7, and explains what happened and what to check next, citing the screens it read. On IBM i, it reads the job log through WRKJOB and explains messages such as MCH1202. Every step shows as it happens, and Stop ends it at once.
It’s read-only by default: before any key reaches the host, WND checks whether it could change data and refuses if so. IT can switch it to ask the person first, or turn it off. Everything sent to the model is masked first, and the model is the one IT points it to, on the PC or inside your network.
Send to help desk
When a screen goes wrong, one click (Ctrl+Shift+H) creates a ServiceNow incident, a Jira issue or an e-mail with a masked screenshot drawn from the screen itself, the AI explanation, the last few screens, a masked recording of the last five minutes of the data stream, and the PC and connection details. No more “send us a screenshot” or “which system?”
For the IT team
Migration readiness report
Point WND Terminal at the share that holds your PCOMM, Reflection, BlueZone and IBM i Access Client Solutions files. It reads every one, sorts each into “imports cleanly,” “imports with small notes” or “needs a person” (with the reason), removes duplicates, converts PCOMM macros where it can, and writes a one-page report for leadership, a detail workbook, and the distinct connections as policy.json, a Windows .reg file and a Mac configuration profile. It runs from the app or a script, and it changes nothing in the folder.
WND Terminal in a browser
The same app in Chrome, Edge, Firefox or Safari, through one small gateway your IT team runs on its own server. People sign in with Microsoft Entra ID, Okta, Google or any OpenID Connect provider and get the same screens, keys and features, under the same policy, license and audit log. A person is one seat whether they use the browser, the desktop app or both. It’s built for contractors, personal devices and anyone without a managed PC or Citrix.
See WND Terminal in a browser →
Full IBM i support, and IT presets
WND Terminal is a complete 5250 emulator on Windows, Mac and the browser: IBM i printers, automatic sign-on that sends a one-time password substitute instead of the password, IBM’s graphical windows and controls, and Japanese, Chinese and Korean. IT can preset everything (connections that open at start, the host type locked, every setting pre-filled) so people just open the app.
For security and operations
Session recording for privileged users
For SOX, PCI DSS and DORA evidence, WND Terminal records what system programmers and other privileged users do on production: every screen and every key, with passwords never recorded and card numbers and your patterns masked before anything is written. Each recording is hash-chained and signed, stored in your own storage, searchable (“DELETE”, “RACF”, “ALTER”) and replayable, with an exportable report for auditors. No separate privileged-access product or jump server is needed.
Mainframe response-time monitoring
WND Terminal already sees every key go to the host and every answer come back. Now, when IT turns it on, it times each transaction for every user, sums it up each minute with no screen contents or typing, and sends the summaries to a shared folder and Splunk. The Operations view finds slowdowns by itself and says them in one sentence, such as: “CICS PROD went from 0.4 s to 3.1 s at 10:42 for 1,200 users.” (An example from the app’s built-in sample data.)
How response-time monitoring works →
Same rules as always
None of this changes how WND Terminal treats your data. Sessions go straight from the PC, or your own gateway, to your hosts. The license is checked on the computer. Usage logs, audit logs, recordings, response times and training progress go to folders and collectors you name. The AI uses a model you choose, on the PC or inside your network. Nothing is sent to WND Software. Read the security overview →
See it
We’re at IBM TechXchange in Atlanta, October 26–29, showing Capture all pages, Fill from Excel, Modern view and Ask WND in five minutes, on a laptop with Wi-Fi off.
Or see it on your own systems: a proof of value is free for two to four weeks, and it starts with a Migration readiness report on your emulator files.
Current customers: everything above comes in the October release of WND Terminal, on the customer portal. Fill from Excel, Modern view, the AI and guide recording can each be turned off in the policy; session recording and response times stay off until IT turns them on. WND Terminal in a browser, session recording and response-time monitoring are in the Enterprise plan; everything else is in every plan.