Technical Notes

Converting RUMBA Settings to Reflection for IBM
Technical Note 1733
Last Reviewed 07-May-2004
Applies To
Reflection for IBM version 11.0 through 14.x
Summary

The Reflection for IBM Conversion Tool converts your NetManage RUMBA files to Reflection for IBM settings files. You can convert AS/400 and Mainframe display sessions, keyboard mappings, and macros by using either a drag-and-drop method or a command line. This technical note includes tips on migrating from Rumba to Reflection for IBM.

Note: This note should be used in conjunction with Technical Note 1143, which includes information about obtaining, installing, and using the Reflection for IBM Conversion Tool.

This technical note includes the following topics:

Supported RUMBA File Types

The following table lists supported RUMBA file types and describes the Reflection output files you'll see after using the conversion tool. Note that Reflection uses the same settings file type (*.rsf) for both AS/400 and Mainframe sessions.

RUMBA Source Files	Reflection Output Files
AS/400 display profile files (*.wda) Sample Input: Myhost.wda	Reflection settings files (*.rsf) Sample Output: Myhost.wda.rsf
Mainframe display profile files (*.wdm) Sample Input: Myhost.wdm	Reflection settings files (*.rsf) Sample Output: Myhost.wdm.rsf
Keyboard map files (*.map) Sample Input: Mykeys.map	Reflection Key/Mouse files (*.map) Sample output: Mykeys.map.map
Macro files (*.rmc) Sample Input: Logon.rmc	Visual Basic files (*.bas) Sample output: Logon.rmc.bas
SNA (APPC) configuration file Input : Wdsna.cfg	SNA Engine Configuration file (*.rlf) Output: Wrqsna.rlf

Note the following:

• The conversion tool does not convert all RUMBA connection types. The following transport types are supported: TN5250, TN3270, TN3270E, MPTN, and 802.2 DLC.
• The conversion tool only converts sessions that are supported by Reflection for IBM. It cannot convert HP or UNIX sessions. Use Reflection for HP to configure HP sessions. Use Reflection for OpenVMS to configure UNIX sessions.
• In RUMBA TN5250 sessions, you can configure a value for "Connect Timeout." This value is stored in a file called Wdtelnl.ini. If Wdtelnl.ini is present in the same folder as your *.wda file, the converter configures the Reflection setting called "Host Communication Timeout" to match your RUMBA setting. If no Wdtelnl.ini file is present, Reflection uses the default value for this setting. To change your Reflection setting, use Setup > View Settings.
• In RUMBA AS/400 sessions, you can configure User ID and Password information using the Security tab of the Connection Configuration dialog box. These values are saved in encrypted form in a file called Config.ehn. Because the values are encrypted, the conversion tool cannot convert information stored in the Config.ehn file. After you have converted your files, you can configure your name and password in Reflection using the Advanced tab of the Session Setup dialog box. This information is saved to your Reflection settings file, where the password information is saved in encrypted form.

Converting SNA Sessions (MPTN and 802.2)

RUMBA 802.2 DLC and MPTN sessions use SNA configuration information, which is stored in your RUMBA program folder in the Wdsna.cfg file. Reflection stores equivalent information in the Reflection SNA Configuration file (Wrqsna.rlf).

To convert RUMBA session files configured to use 802.2 or MPTN, you must convert your session files and your Wdsna.cfg files together. For example, if you have a RUMBA AS/400 display session configured to use the RUMBA Router and 802.2 DLC, you should select both the session file (*.wda or *.wdm) and Wdsna.cfg and drag them together onto Ribmconvert.exe. A sample command line equivalent (with paths omitted) is:

The converter creates a Reflection settings file (*.rsf) for each session you convert. It also creates an SNA Configuration file (Wrqsna.rlf) based on your Wdsna.cfg file. In the example above the conversion tool would create two files: Wrqsna.rlf and MySession.wda.rsf.

Your Reflection settings file(s) must be able to find the information in the newly created Wrqsna.rlf file. You can accomplish this in either of the following ways:

• Copy Wrqsna.rlf to the default location used by Reflection. (On Windows 98 and NT systems, Wrqsna.rlf is stored by default in the directory where your operating system is located. On Windows XP and 2000 systems, the default location is \Documents and Settings\All users\Application Data. After you've done this, the converted SNA configuration information will be available to all Reflection sessions.
• Edit the converted settings file to look for the SNA configuration information in a non-default location. To do this:

1. Open the new Reflection settings file.
2. On the Reflection Setup menu click View Settings, then search for "SNA Engine Configuration File."
3. Under Setting details, enter the full path and file name of the newly converted Reflection Wrqsna.rlf file.
4. Save the settings file to keep this change.

Converting RUMBA Keyboard Maps

You can use the conversion tool to import your RUMBA keyboard mappings into Reflection. RUMBA stores keyboard mapping information in keyboard map files (*.map). To use custom keyboard maps, you create custom map files and associate your display sessions with one of these files.

Reflection supports two ways of saving keyboard mapping information. Keyboard mappings can be saved directly in a Reflection settings file (*.rsf) or they can be saved in a separate Key/Mouse partial settings file (*.map). The conversion tool creates Reflection *.map files using the mapping information in your RUMBA *.map files. After you convert your RUMBA keyboard map files, you can import the keyboard mapping information directly into Reflection settings files. (Note that both RUMBA and Reflection use *.map as the extension for keyboard map files. The converter adds a second map extension to your existing map file. So, a file called MyKeys.map will be called MyKeys.map.map after conversion.)

For example, if you have a RUMBA Mainframe display session called MyMainHost.wdm that uses a custom keyboard mapping called Mykeys.map, you could use the following procedure to import all of your RUMBA session and keyboard mapping information into a single Reflection settings file:

1. Drag your session and keyboard files to Ribmconvert.exe. These files can be converted separately or together. The converter will create new session and keyboard map files. (In this example, MyMainHost.wdm.rsf and Mykeys.map.map.)
2. Double-click the converted display session (MyMainHost.wdm.rsf) to open the new display session in Reflection.
3. On the Reflection File menu, click Open. Set Files of type to Key/Mouse (*.map), select your converted keyboard map file (Mykeys.map.map), and then click Open.
4. On the Reflection File menu, click Save MyMainHost.wdm.rsf (or use Save As to select a new name). Your Reflection settings file now contains both connection information and your custom keyboard mapping.

Note the following:

• To view and/or edit the keyboard mappings in Reflection, click Setup > Keyboard. In the Keyboard Setup dialog box, mapped keys are shown in blue-green. Click any mapped key on the PC keyboard (above) to see its mapping on the terminal keyboard (below).
• The conversion log file contains information about key mappings that could not be converted. See the section, "Reading the Log File," in Technical Note 1143 for information about using the log.
• Keys mapped to macros are not converted. To map Reflection keystrokes to your macros, first convert your RUMBA macros and import them into Reflection. (See the following section for detailed information.) Once this is done you can map a Reflection keystroke to any imported macro:

1. To select a keystroke, click Setup > Keyboard.
2. Under PC Keyboard, click the keystroke combination you want to map.
3. To map this to a macro, click Commands, then click Macros, and select the macro you want to map.
4. Click OK to close the open dialog boxes.

Converting RUMBA Macros

You can use the conversion tool to convert RUMBA macros to Reflection Visual Basic for Applications (VBA) macros. All RUMBA commands are supported by the converter, but there are a small number of options you can configure in RUMBA macros that are not supported in Reflection macros. (See the Note section below for details.) If your RUMBA macro includes an unsupported feature, a message box displays this information when you run the converted macro in Reflection.

RUMBA macros are saved in individual macro files (*.rmc). In contrast, Reflection VBA macros are saved in a VBA project file with your other Reflection settings. After converting your RUMBA macros, you'll need to import the converted code into your settings file. For example, to convert a logon file that is tied to a display session:

1. Convert the display session file (*.wda or *.wdm) and the macro file (*.rmc) by dragging them onto Ribmconvert.exe (or using a command line). The converter creates a new Reflection settings file (*.rsf) based on the display session file, and a new Visual Basic code module (*.bas) based on the macro file.
2. Double-click the Reflection settings file to open your converted display session.
3. On the Reflection Macro menu, click Visual Basic Editor.
4. On the Visual Basic Editor's File menu, click Import File. Browse to locate the newly created VBA code module (*.bas) and click open. A new module (Module1, Module2, and so on) is added for each file you import.
5. Save your updated settings file.

To run the converted macro:

1. Open the Reflection Macro menu, and click Macros.
2. Your converted macros are listed in the Reflection Macros dialog box identified as "Main." (Reflection macros take their name from the Sub procedure name, and all EXTRA! Basic macros use a Main Sub procedure.) If you want a more descriptive name, edit the Sub procedure line of the macro. For example, change "Sub Main" to "Sub Logon."

To set Reflection to run a logon macro automatically as soon as a connection is made:

1. On the Reflection Connection menu, click Session Setup.
2. Enter the macro you want to run under Connect macro (use Browse to see a list of available macros), then click OK.

Note the following:

• The RUMBA Paste To command allows you to paste text to an external application. This feature is not supported in Reflection.
• The RUMBA Receive command supports an Ignore case option. This feature is not supported in Reflection.
• When you open a Reflection settings file, Reflection automatically creates a file that has the same base name as your settings file and an *.rsf extension (called *.rvx in versions earlier than 12.0). This file contains VBA project information. If you are using Reflection macros, this file must be in the same folder as your Reflection settings file.

Related Technical Notes

1143	Tips and Tools for Migrating to Reflection for IBM