| PCOMM file | What WND Terminal brings across |
|---|---|
.ws workstation profile | Host, port, encryption, screen size, backup hosts, terminal name (LU) and host code page. |
.kmp keyboard file | Every key assignment, with Shift, Ctrl and Alt. The [print] key becomes Print. |
.mac macro | The common lines become macro steps. The rest are listed. |
How to import
- Drop the files anywhere on the WND Terminal window.
- Or use Import… on the connect page.
- Or press Ctrl+K and choose Import.
WND Terminal shows what it found before it saves anything. Drop a .ws profile together with the .kmp file it names, and the two are linked, so the session opens with its own keyboard map.
Workstation profiles (.ws)
A profile brings its host, port, encryption setting and screen size. Three more things come across when the profile has them.
- Backup hosts. IBM doesn’t publish the profile format, so WND Terminal reads the spellings seen in real profiles, such as
HostName1=andHostPortNumber1=. When the main address doesn’t answer, WND Terminal tries each backup in order and shows a Backup tag in the status line. - Terminal name.
LUName=becomes the connection’s terminal name. The session then uses TN3270E and asks the mainframe for that name. - Code page.
HostCodePage=1141-Ugives the session the right character set, so accented letters, £ and € show correctly.
Keyboard files (.kmp)
Every key assignment in a .kmp file becomes part of a WND Terminal keyboard map, with Shift, Ctrl and Alt. You can edit it in Ctrl+K > Keyboard maps like any other map. An imported map takes precedence over WND Terminal’s own copy and paste keys, so people keep the keys they know.
Keys WND Terminal can’t map are listed in the import results. See Keyboard maps for the editor.
Macros (.mac)
Open Ctrl+K > Macros and import the .mac file. Common lines become steps in a WND Terminal macro, and the rest are listed so you can see what didn’t convert. Simple macros convert fully, or with message boxes left out. Macros with program logic or screen reading need a person to rebuild them. Run an imported macro from the Macros panel, the Ctrl+K palette or a key. See Macros for the script commands.
Importing a whole share
For hundreds or thousands of profiles, use the Migration readiness report. Press Ctrl+K, choose Migration readiness report and point it at the share. It reads every file without changing any and sorts each into “imports cleanly”, “imports with small notes” or “needs a person”. It also removes duplicates and writes the distinct connections as a policy. It can also run from a script.
wnd-terminal --readiness-report "\\fileserver\emulators$" --out "D:\Reports"Union Pacific imported 1,900 session profiles and 340 keyboard maps, then moved 7,800 users in eight weeks against a nine-month estimate. Read the Union Pacific story.
Policy still applies
IT’s policy holds for imported sessions in the same way as for any other. With RequireEncryption set, every connection is encrypted whatever the profile says. With AllowOtherHosts = false, people can only use IT’s connections. See the policy settings reference.