Can WND Terminal run Reflection VBA macros?

No. VBA and Reflection Basic macros are counted and listed for a person in the Migration readiness report. Fill from Excel and Capture all pages cover many common VBA uses.

Why won't my .rsf file import?

Reflection for IBM 12 and later saves .rsf files in binary. Save the settings as XML from Reflection and import the XML. WND Terminal explains how when you drop the file.

Can WND Terminal open encrypted Reflection session documents?

No. It recognizes them and explains why it can't read them. The readiness report lists them as needing a person.

Import Reflection .rd3x, XML and .rsf Files

Reflection file	Result
Reflection Desktop 3270 session document (`.rd3x`)	Imported. Host address, port, terminal name, code page and other settings found by name.
Reflection for IBM settings saved as XML	Imported the same way.
`.rsf` text settings, Reflection for IBM 11 and earlier	Imported.
`.rsf` from version 12 and later	Saved in binary. The app explains how to save the settings as XML from Reflection.
Encrypted session documents	Recognized and explained.
VT sessions (`.rdox`)	Recognized and explained. WND Terminal has no VT emulation.
Reflection’s demo host	Recognized and explained.

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.

Reflection Desktop session documents (.rd3x)

An .rd3x file is a zip archive. Inside, documents/settings/settings.xml holds HostAddress, Port and the rest of the session. Rocket doesn’t publish the schema, so WND Terminal finds settings by name and lists anything it can’t use.

rcDeviceName becomes the connection’s terminal name (LU). The session then uses TN3270E and asks the mainframe for that name.
HostCodePage gives the session the right character set, so national characters show correctly.

Reflection for IBM XML settings

Settings that Reflection for IBM saved as XML are read the same way, by setting name.

Reflection for IBM .rsf files

Version 11 and earlier save .rsf files as text, with lines such as .SetString rcHostName, "mvs". WND Terminal reads these directly.

Version 12 and later save .rsf in binary, which WND Terminal can’t read. When you drop one, the app explains how to save the settings as XML from Reflection. Then import the XML.

Keyboard maps

Keyboard maps imported from Reflection open in the same keymap editor as any other map (Ctrl+K > Keyboard maps). An imported map takes precedence over WND Terminal’s own copy and paste keys, so people keep the keys they know. See Keyboard maps.

Macros

WND Terminal doesn’t run VBA or Reflection Basic macros. The Migration readiness report counts them and lists each file for a person, so you know the size of the job before you start.

Many common VBA uses are built in. Fill from Excel types a spreadsheet into an entry screen, and Capture all pages turns a multi-page list into one Excel table. For logon steps, record a WND Terminal macro. See Macros.

Extra! sessions

Convert Extra! sessions to Reflection format with the vendor’s own tool, then import the result.

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 session document says. With AllowOtherHosts = false, people can only use IT’s connections.

Importing a whole share

The Migration readiness report reads every Reflection file on a share, along with PCOMM, BlueZone and ACS files. It sorts each into “imports cleanly”, “imports with small notes” or “needs a person”. Encrypted documents, binary .rsf files, VBA and Reflection Basic macros, and VT sessions land in “needs a person” with the exact file list. It changes nothing in the folder.

Import from Reflection