Converting EXTRA! Personal Client Files to Reflection for IBM Files

The Reflection for IBM Conversion Tool converts your EXTRA! Personal Client Files to Reflection for IBM files. You can convert 5250 and 3270 display sessions, keyboard mappings, and logon macros by using either a quick drag-and-drop method or by configuring a command line. This technical note includes tips on migrating from Attachmate EXTRA! to Reflection for IBM.

Note the following:

• 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.
• If you are migrating to Reflection for IBM 2007, you need not convert your EXTRA! files. For information about supported legacy files in Reflection for IBM 2007, see KB 7021495.

Supported EXTRA! File Types

The following table lists supported EXTRA! file types and describes the Reflection output files you will see after using the conversion tool:

EXTRA! Source Files	Reflection Output Files
Display session files (*.edp) Sample Input: Session1.edp	Reflection settings files (*.rsf) Sample Output: Session.edp.rsf
Keyboard map files(*.ekm) Sample Input: Mykeys.ekm	Reflection Key/Mouse files (*.map) Sample output: Mykeys.ekm.map
EXTRA! Basic files(*.ebm) Sample Input: Logon.ebm	Visual Basic files (*.bas) Sample output: Logon.ebm.bas
APPN Node files(*.xcp) Sample Input: Default.xcp	SNA Configuration file (*.rlf) Output: Wrqsna.rlf

Notes

• The conversion tool does not convert all EXTRA! connection types. The following transport types are supported: TN3270, TN3270e, TN5250, MPTN, Microsoft SNA Server (3270 & 5250), and 802.2 DLC (3270 & 5250).
• The conversion tool cannot convert VAX/VMS, UNIX, or asynchronous host sessions. You can use Reflection for OpenVMS to configure sessions of this type.
• If you have converted an EXTRA! 3270 MS SNA session that uses the "Connect to any resources" option, you will see the following message the first time you try to connect using Reflection: "MS SNA Server : Configuration is incomplete. Enter new LU Name." You can use the list provided to select an available LU and complete your connection.

Working with EXTRA! APPN Node (XCP) Files

In order to make 802.2 DLC connections, you must configure LU links information. EXTRA! stores information about LU resources in an "APPN Node" file. By default, this file is called Default.xcp and is located in your E!PC folder. Reflection stores equivalent information in an "SNA Engine Configuration" file called Wrqsna.rlf by default.

To convert EXTRA! session files configured to use 802.2, you must convert your session files and your XCP files together. For example, if you have an EXTRA! 802.2 display session called Session1.edp, you should select both Session1.edp and Default.xcp, and then drag them onto Ribmconvert.exe. The 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 APPN Node file (*.xcp). In the example above the conversion tool would create two files: Wrqsna.rlf and Session1.edp.rsf.

Your Reflection settings file 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 \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, 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.

Note: If you have multiple EXTRA! sessions configured that all use the same Default.xcp file, you should convert them all at the same time. This helps ensure that the Wrqsna.rlf file created by the conversion tool will correctly support all of your converted sessions.

Converting EXTRA! Keyboard Maps

You can use the conversion tool to import your EXTRA! keyboard mappings into Reflection. EXTRA! stores keyboard mapping information in Keyboard Map files (*.ekm) that are stored by default in the E!PC/Schemes folder. To use a custom mapping, you link a session to 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 EXTRA! *.ekm files. After you convert your EXTRA! keyboard map files, you can import the keyboard mapping information directly into Reflection settings files.

For example, if you have an EXTRA! display session called Session1.edp that uses a custom keyboard mapping called Mykeys.ekm, you could use the following procedure to import all of your EXTRA! 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 Session1.edp.rsf and Mykeys.ekm.map.)
2. Double-click the converted display session (in this example Session1.edp.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 (in this example Mykeys.ekm.map), and then click open.
4. On the Reflection File menu, click Save Session1.edp.rsf (or use Save As to select a new name). Your Reflection settings file now contains both connection information and your custom keyboard mapping.

Notes

• 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 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 EXTRA! Basic Macros

You can use the conversion tool to convert EXTRA! logon macros to Reflection Visual Basic for Applications (VBA) macros.

EXTRA! macros are saved in individual EXTRA! Basic macro files (*.ebm). In contrast, Reflection VBA macros are saved in a VBA project that is saved with your other Reflection settings. After converting your EXTRA! macros, you will 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 *.edp and *.ebm files by dragging them onto Ribmconvert.exe (or using a command line). The converter will create 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 will be 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, select 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.

Notes

• The converter is able to handle only a small number of EXTRA! Basic 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.
• 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.

Legacy KB ID

This document was originally published as Attachmate Technical Note 1731.