The Reflection for IBM Conversion Tool converts your ViewNow settings to Reflection for IBM files. You can convert 5250 and 3270 display sessions, keyboard mappings, and logon scripts. This technical note includes tips on migrating from ViewNow 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.
Supported ViewNow Conversions
The Reflection for IBM conversion tool can be used to convert your ViewNow sessions and custom attachments. The following table lists the supported conversions and describes the Reflection output files you will see after using the conversion tool:
||Reflection Output Files
|Supported display and router sessions (information stored in the Windows registry)
||Reflection settings files (*.rsf)
Sample Output: 3270 display.rsf
|Keyboard map files (*.3km, *.5km)
Sample Input: Mykeys.3km
|Reflection Key/Mouse files (*.map)
Sample output: Mykeys.3km.map
|ViewNow macro files(*.csf)
Sample Input: Logon.ebm
|Visual Basic files (*.bas)
Sample output: Logon.csf.bas
- Printer sessions are not converted.
- The conversion tool does not convert all ViewNow IBM connection types. The following transport types are supported: TN3270, TN3270e, TN5250, TN5250E, MPTN (AnyNet), Microsoft SNA Server (3270 & 5250), and 802.2 DLC (3270 & 5250).
- The conversion tool cannot convert UNIX host sessions. You can use Reflection for OpenVMS to configure sessions of this type.
- The conversion tool cannot convert X Windows sessions. You can use Reflection X to configure sessions of this type.
Converting ViewNow Sessions
Because ViewNow connection settings are stored in the Windows registry, you can't use the drag-and-drop method for converting this information. Convert your ViewNow settings using the command line. When you use the /VIEWNOW option, all of your ViewNow sessions are converted.
To convert your ViewNow Sessions:
- Install the Reflection for IBM Conversion Tool on the computer whose settings you want to convert.
- On the Windows Start menu, select Run.
- Enter a command line like the one shown here and click OK. (Edit the path information as needed to match the location of Ribmconvert.exe on your system, and replace "c:\mypath" with your desired output folder.)
"C:\Program Files\Wrq\RToolkit\ribmconvert" /viewnow /output c:\mypath
The converter creates subfolder names that correspond to the workspace names you have defined in the ViewNow Host Access Manager. These folders contain converted Reflection for IBM settings files (*.rsf) with settings that match those in your ViewNow display sessions.
Use either of these methods to open your converted session files:
- From Windows Explorer, double-click the converted *.rsf file.
- Launch Reflection. On the File menu, click Open and browse to locate your converted file.
Converting 802.2 and AnyNet Sessions
When you convert 802.2 and AnyNet sessions, Reflection requires an SNA Configuration file (Wrqsna.rlf) in addition to Reflection settings file(s) (*.rsf). The converter creates the SNA Configuration file automatically when you convert sessions that require it.
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, it's stored by default in C:\Documents and Settings\All users\Application Data. After you have 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 open the new Reflection settings file. On the Reflection Setup menu click View Settings, then search for "SNA Engine Configuration File." Under Setting details, enter the full path and file name of the newly converted Reflection Wrqsna.rlf file. Save the settings file to keep this change. After you've done this, the converted SNA configuration information will be available whenever you open the modified settings file. Note that this change affects only the edited settings file.
Converting ViewNow Keyboard Maps
You can use the conversion tool to import your ViewNow keyboard mappings into Reflection.
ViewNow stores keyboard mapping information in keyboard map files (*.3km or *.5km) that are stored by default in the C:\Program Files\NetManage\Data\ folder. To use a custom mapping, you attach a session to a keyboard map file.
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 ViewNow map files. After you convert your ViewNow keyboard map files, you can import the keyboard mapping information directly into Reflection settings files.
For example, you could use the following procedure to convert all of your ViewNow sessions and keyboard information and import the keyboard mapping information into your newly created Reflection settings files.
- Use a command line like the one shown here to convert your ViewNow display sessions and keyboard map files. (You will need to edit the paths to match your actual ViewNow installation folder and desired output folder.)
ribmconvert /viewnow "C:\NetManage\Data\*.*km" /output c:\mypath
In this example, you will find converted keymaps in C:\Mypath. The converted display sessions will be in subfolders in the output folder with names that correspond to the workspace names you have defined in the ViewNow Host Access Manager.
- On the Reflection File menu, click Open. Select a converted session file and click Open.
- On the Reflection File menu, click Open again. This time set Files of type to Key/Mouse (*.map), select the converted keyboard map file you want to import, and then click Open.
- On the Reflection File menu, click Save <session name> (or use Save As to select a new name).
Your Reflection settings file now contains both connection information and your custom keyboard mapping.
- To view and/or edit the keyboard mappings in Reflection open the Setup menu and click Keyboard. In the Keyboard Setup dialog box, mapped keys are shown using a blue-green color. Click any mapped key on the PC keyboard (above) to see its mapping on the terminal keyboard (below).
- The conversion tool supports ViewNow key mappings made using the default keyboard (Enhanced 101). Other keyboards are not supported.
- 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.
Converting ViewNow Scripts
You can use the conversion tool to convert simple ViewNow logon scripts to Reflection Visual Basic for Applications (VBA) macros.
ViewNow scripts are saved in individual script files (*.csf). In contrast, Reflection VBA macros are saved in a VBA project that is saved with your other Reflection settings. After converting your ViewNow macros, you will need to import the converted code into your converted settings file.
For example, to convert a logon file that is tied to a display session:
- Use a command line like the one shown here to convert your ViewNow display sessions and script files. (You will need to edit the paths to point to your actual script file location and desired output folder.)
ribmconvert /viewnow "c:\my scripts\*.csf" /output c:\mypath
In this example, you will find converted scripts in C:\Mypath. A new Visual Basic code module (*.bas) is created for each script file. Converted display sessions are saved to subfolders in the output folder with names that correspond to the workspace names you have defined in the ViewNow Host Access Manager.
- Open the Reflection settings file that you want to use the converted script with. (This file will have the same name you used in your ViewNow workspace).
- On the Reflection Macro menu, click Visual Basic Editor.
- On the Visual Basic Editor's File menu, click Import File. Browse to locate the newly created VBA code module (*.bas) that you use for this display session and click open. A new module (Module1, Module2, and so on) is added for each file you import.
- Save your updated settings file.
To run the converted script:
- Open the Reflection Macro menu, and click Macros.
- Your converted script will be listed in the Reflection Macros dialog box identified as "Main". (Reflection macros take their name from the Sub procedure name, and all ViewNow scripts 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:
- On the Reflection Connection menu, select Session Setup.
- Enter the macro you want to run under Connect macro (use Browse to see a list of available macros), then click OK.
- The converter is able to handle only a small number of script commands -- those that are used when you connect and send text and keystrokes to the host. Use the conversion log to determine which commands were used in the converted macros. See the section, "Reading the Log File," in Technical Note 1143 for information about using the log.
- The conversion tool support conversion of Script (*.csf) files only. It does not convert Macro Object Path (*.mop) files.
- When you open a Reflection settings file, Reflection automatically creates a file that has the same base name as your settings file and a *.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 available in the same folder as your Reflection settings file.