Docs

Import from Extra!, PowerTerm, Rumba and other emulators

Drop session and keyboard files from older emulators on the WND Terminal window. It reads the ones it can and explains the rest.

In short

WND Terminal imports session files from Extra!, PASSPORT, PowerTerm, HostExplorer, TN3270 Plus, QWS3270, Vista tn3270 and PuTTY, with keyboard maps that are stored as text. Rumba+ profiles come across through Reflection Desktop, which saves them as .rd3x and .rd5x files WND Terminal reads. Extra! Basic, HostExplorer Basic and PowerTerm PSL macros run as they are.

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

ProductSession filesWhat comes acrossKeyboard mapsMacros and scripts
Extra!.edpHost, port, encryption, terminal type, code page and backup hosts.ekm, when the file is text.ebm, .ebs run as they are
PASSPORT.zwsHost, port, SSL, screen size, LU name, code page, IBM i device type and hot backup hostsNoneNone
PowerTerm.pts, .ptcHost, port, LU or device name, SSL and terminal type.ptk, when the file is text.psl run as they are
HostExplorer.hepHost, port, LU or device name, model and TLS, found by name when the file is text.kbd, when the file is text.ebs run as they are
TN3270 Plus.tspHost, port, LU or device name, model and TLS, found by name when the file is text.tkm, when the file is text.mac listed for a person
QWS3270.jgs, .jgpHost, port, LU or device name, model and TLS, found by name when the file is textqws3270s.key, when the file is textNone
Vista tn3270.sesHost, port, LU or device name, model and TLS, found by name when the file is textNone.mac listed for a person
Rumba, Rumba+.rsdm, .rsda, .wdm, .wdaThrough Reflection Desktop, which saves them as .rd3x or .rd5x. The profiles themselves are binary, so each one is recognized and explained..map, when the file is text.rmc and .csf converted, when the file is text
PuTTYA .reg export of its saved sessionsSSH and Telnet sessions with host, port, user name, terminal type, key file and window sizeNoneNone

How to import

Drop the files anywhere on the WND Terminal window. You can also use Import… on the connect page, or press Ctrl+K and choose Import. WND Terminal shows what it found before it saves anything. Each session says whether it’s a mainframe (3270), IBM i (5250) or UNIX and Linux session.

A file WND Terminal can’t read is never guessed at. The import says what the file is and what to do instead. For a session, that usually means noting the host, port and terminal (LU) or device name in the old emulator and adding the connection in WND Terminal or in IT’s policy.

Extra!

Extra! session files (.edp) are text. WND Terminal reads the host list Rocket documents for them. The first host is the connection, and the rest become backup hosts, tried in order when the main one doesn’t answer.

  • Security types 1, 11 and 12 import as encrypted connections.
  • Security type 10 uses Attachmate’s own security components, which keep their settings outside the file. The session imports without encryption, and a note says so.
  • An .edp file that isn’t text is explained. Reflection Desktop can open it and save it as .rd3x or .rd5x, which WND Terminal also reads.
  • Printer sessions (.epp), layouts (.elf), QuickPads (.eqp) and toolbars (.etb) are recognized. A layout lists the sessions it opens.

PASSPORT

PASSPORT profiles (.zws) are text, and WND Terminal reads the settings PASSPORT documents. A Specific connection keeps its LU name. A Generic connection uses the pool. An IBM i device type makes the session a 5250 session. A Dynamic screen size becomes 24×80, with a note, so you can pick another size.

PowerTerm

PowerTerm terminal setup files (.pts) and communication setup files (.ptc) are text. Ericom doesn’t publish the setting names, so WND Terminal finds them by name, such as Host-Name, Telnet-Port, LU-Name, Device-Name and SSL-Type. The default setup file is ptdef.pts.

PowerTerm keeps the terminal type in the .pts file. A file that doesn’t name one imports as a mainframe session, with a note. Import the matching .pts if it’s an IBM i session. VT sessions import as UNIX and Linux connections. Power Pads (.ptp) are recognized.

HostExplorer, TN3270 Plus, QWS3270 and Vista tn3270

These vendors don’t publish what’s inside their session files. When a file is text, WND Terminal reads the settings by name. HostExplorer’s programming interface calls them HostName, Port, LUName, DeviceName and TerminalModel, and TN3270 Plus shows Host Name, Telnet Port and Resource Name in its dialogs. A file that isn’t text is recognized and explained.

Rumba and Rumba+

Rocket documents that Rumba+ stores session profiles in a binary format, and it doesn’t publish the format. WND Terminal doesn’t guess at a file it can’t check, so it doesn’t read Rumba profiles directly. It recognizes each one and gives a documented way across, through Reflection Desktop, which opens Rumba display profiles and converts them (Rocket KB 7021468).

  1. Open the Rumba profile (.rsdm for a mainframe, .rsda for AS/400, or the older .wdm and .wda) in Reflection Desktop. Rumba keeps them in %LOCALAPPDATA%\Micro Focus\Rumba\Mframe and ...\AS400.
  2. Save it as a Reflection session document, .rd3x for a mainframe session or .rd5x for AS/400.
  3. Drop the file on WND Terminal, or put it in the folder the readiness report reads.

By Rocket’s list of converted settings, the host name, port, device (LU) name and host code page come across, and for AS/400 the screen size. Add backup hosts to the connection by hand. Rumba encrypts its security settings, so turn on encryption for the connection in WND Terminal or in your policy if the host needs it. The Migration readiness report explains these steps for every Rumba profile it finds.

Without Reflection Desktop, note each session’s host name, port and LU or device name in Rumba and add the connection in WND Terminal or in IT’s policy. In a proof of value, WND Terminal does this with you. Printer profiles (.rspm, .rspa), UNIX and HP profiles (.rsdu, .rsdh) and desktop profiles (.rdps) are recognized too. Set the UNIX hosts up as UNIX and Linux connections. See WND Terminal vs. Rumba.

Keyboard maps

None of these keyboard map formats is published. When a map is text with key names and functions in it, such as RightCtrl=Enter or Ctrl+F1=PA1, WND Terminal reads it. Functions it doesn’t have are listed. Otherwise the file is explained, and you make the map again in the keymap editor. See Keyboard maps.

Macros and scripts

Extra! Basic (.ebm, .ebs), HostExplorer Basic (.ebs) and PowerTerm PSL (.psl) macros run in WND Terminal as they are. Import them in the Macros panel with Import a macro, and any line WND Terminal can’t run is listed with its line number. See Run your existing macros.

Rumba text macros (.rmc) and Script Editor scripts (.csf) convert to WND Terminal macros line by line, and lines with jumps, decisions, other programs, file transfer or printing are listed for a person. A .rmc in Rumba’s own binary format is recorded again. See Run your existing macros. Rumba’s .js and .vb scripts, and TN3270 Plus and Vista macros, aren’t converted, because their formats aren’t published. The import and the readiness report list each one. Record the same steps as a WND Terminal macro, which can make decisions and repeat steps. The macros docs show how common Basic statements map across.

PuTTY and VT sessions

Export PuTTY’s saved sessions from the registry with reg export HKCU\Software\SimonTatham\PuTTY\Sessions putty.reg and drop the .reg file on the window. The VT sessions of Reflection (.rdox), BlueZone (.zvt), HostExplorer, PowerTerm, Extra!, PASSPORT and IBM i Access Client Solutions import the same way, as UNIX / Linux (SSH) or VT (Telnet) connections. See UNIX and Linux sessions.

Where the files are

Copy the files for the import, or point the Migration readiness report at these folders on Windows.

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

ProductFilesUsual folder
Rumba+.rsdm, .rsda, .map, .rmc%LOCALAPPDATA%\Micro Focus\Rumba\, in the Mframe and AS400 subfolders
HostExplorer.hep, .kbd, .ebsThe User Files folder, such as %APPDATA%\Hummingbird\Connectivity\14.00\. Keyboard maps are in HostExplorer\Keymap.
Extra!.edp, .ekm, .ebm, .eqpThe Extra! Sessions folder, such as C:\Program Files\E!PC\Sessions. Keyboard maps are in its Schemes subfolder.
PASSPORT.zwsThe PASSPORT folder, such as C:\Program Files\PASSPORT\
PowerTerm.pts, .ptc, .ptk, .pslThe PowerTerm folder
TN3270 Plus.tsp, .tkm, .mac%APPDATA%\SDI\TN3270 Plus\, or the install folder in older versions
QWS3270 Secure.jgs, .jgl, qws3270s.key%APPDATA%\Jolly Giant Software\QWS3270 Secure\
Vista tn3270.ses, .macC:\Program Files (x86)\TomBrennanSoftware\VistaTN3270\

Importing a whole share

The Migration readiness report reads these products’ files along with PCOMM, Reflection, BlueZone and ACS files. Its table has a row for each product, with how many files import cleanly, import with small notes or need a person. Macros that run as they are land in “imports with small notes”. Rumba profiles not yet converted, files in a format the vendor doesn’t publish, QuickPads, toolbars and macros WND Terminal can’t run land in “needs a person”.

Several products use the same extensions as other programs, such as .map, .key, .kbd and .mac. The report uses the folder names above to tell them apart, so scan the folders themselves or a copy that keeps their names.

Policy still applies

IT’s policy holds for imported sessions as for any other. With RequireEncryption set, every connection is encrypted whatever the old file said. With AllowOtherHosts = false, people can only use IT’s connections.

Extra!, Rumba and HostExplorer are trademarks of Rocket Software. PowerTerm is a trademark of Ericom Software. PASSPORT, TN3270 Plus, QWS3270 and Vista tn3270 are trademarks of their owners. WND Software is not affiliated with or endorsed by these companies.

Questions

Can WND Terminal import Rumba session profiles?

Through Reflection Desktop. Rumba+ stores profiles in a binary format that isn’t published, so open each profile in Reflection Desktop and save it as .rd3x or .rd5x, and WND Terminal imports that. The readiness report explains the steps, and WND Terminal does it with you in the proof of value.

Do we still need Reflection Desktop to move Extra! sessions?

No. WND Terminal reads Extra! .edp session files directly, with their backup hosts. Only an .edp file that isn't text needs Reflection Desktop to save it as .rd3x or .rd5x first.

Do Extra! Basic macros and PowerTerm scripts still work?

Yes. WND Terminal runs Extra! Basic, HostExplorer Basic and PowerTerm PSL macros as they are, and lists any line it can’t run with its line number. Rumba text macros and scripts convert to WND Terminal macros. TN3270 Plus and Vista macros still need a person.

What happens to a HostExplorer profile that isn't text?

It's recognized and explained, never guessed at. Note the host, port and LU or device name in HostExplorer and add the connection in WND Terminal or in IT's policy.

See it on your own mainframe.

Install WND Terminal on a handful of PCs or Macs, import your sessions and keymaps, and let a real team use it next to what you run today. Free, two to four weeks.