Environment
Situation
This technical note describes introductory information about Attachmate EXTRA! X-treme that will be helpful to users who are migrating from NetManage RUMBA.
Note: EXTRA! X-treme includes a Migration Wizard that you can use to migrate session configuration, macros, and customized keyboard maps from other vendors' formats to EXTRA!. See KB 7021883 for detailed information.
Resolution
RUMBA Keyboard, Color, Toolbar, and Menu Schemes
Use the Options > Settings dialog box in EXTRA! X-treme to configure settings. On each of the settings pages for Toolbars, Menus, Keyboards, and Colors, you will find configuration schemes that provide a look and feel similar to NetManage RUMBA. By default, configuration files that you migrate from RUMBA to EXTRA! X-treme will use settings similar to those used in RUMBA.
RUMBA Macro Conversion Notes
Characters In Macro Labels
When RUMBA macro labels (used as the targets of GoTo commands) are converted to EXTRA! Basic macros, the characters dot ( . ), backslash ( \ ), forward slash ( / ), single quote ( ' ), tilde (~), exclamation point ( ! ), at sign ( @ ), and number sign (#) are omitted from the new labels. These characters are not permitted in EXTRA! Basic labels.
UNIX Kermit File Transfer
Conversion of RUMBA UNIX macros that use Kermit file transfer is not supported.
Receive Command
Like its RUMBA equivalent, the EXTRA! Basic command Receive uses the Find At and Find Anywhere features. Find string Starting At is not supported in EXTRA! Basic.
RunApplication
The RUMBA RunApplication macro command, which calls a macro from within another macro, is not supported in EXTRA! Basic.
Unsupported RUMBA Keystrokes
The following RUMBA keystrokes do not have equivalents in EXTRA! X-treme:
| 5250 Keystrokes |
3270 Keystrokes |
VT Keystrokes |
| WP Require Backspace |
Test |
Answer Back |
| WP Required Tab |
ScrR->L |
User 6 |
| WP Required Tab |
Screen Forward |
User 7 |
| WP Required Space |
Screen Backward |
User 8 |
| WP Insert Symbols |
Local Help Cursor |
User 9 |
| WP Begin Bold |
Help |
User 10 |
| WP Center |
ChangeRev |
User 11 |
| WP Next Column |
Field Forward |
User 12 |
| WP Half Index Down |
Field Backward |
User 11 |
| WP End Bold/Underline |
Close |
User 12 |
| WP Next Stop Code |
USM |
User 13 |
| WP Page End |
Change Screen |
User 14 |
| WP Required Page End |
DOC On/Of |
User 15 |
| WP Stop Code |
Change Format |
User 16 |
| WP Begin Underline |
PA4 |
User 17 |
| WP Word Underline |
PA5 |
User 18 |
| WP Half Index Up |
PA6 |
User 19 |
| WP Bottom of Page |
PA7 |
User 20 |
| WP Beginning of Line |
PA8 |
|
| WP End of Line |
PA9 |
|
| WP Top of Page |
PA10 |
|
| WP Carrier Return |
|
|
Running RUMBA API Applications with EXTRA! X-treme
Connecting with a Session
By using an application program interface (API), an application program can connect with an EXTRA! X-treme emulator session regardless of whether the session has been started already. If the target session has not been started when the connection request is made, the API first starts the session (hidden, with no visible user interface), then sets up the connection and returns control to the application.
By comparison, a NetManage RUMBA emulator session must be started before an application program can connect with it. If the target session has not been manually started previously, the application will call the API function WD_RunProfile to start the session before requesting logical connection.
To convert an existing RUMBA application to work with EXTRA! X-treme through the WD_API wrapper, calls to WD_RunProfile must be located and the parameter string modified to specify an EXTRA! X-treme session file (.EDP file) instead of a RUMBA profile. No other change should be needed.
Disconnecting from a Session
With both Attachmate EXTRA! X-treme and NetManage RUMBA, an application program can connect with no more than one session at a time. To connect to another session, the application can either explicitly disconnect from the current session, or it can implicitly disconnect from the current session by requesting connection with a different session.
When an application logically disconnects from an EXTRA! X-treme session, the EXTRA! X-treme emulator does not terminate; it remains in memory awaiting another connection request. An application is expected to call function 21 (Reset System) when it has no further use for the sessions to which it was connected. When function 21 is called, the API removes from memory the emulator for any session the application has started. Manually-started sessions and sessions in use by other applications remain unaffected by this process. Typically, an application will make a function 21 call as part of its exit sequence.
By comparison, with the NetManage RUMBA product, an application can call WD_DeletePS to disconnect from and close a session. Any emulator session started by an application is automatically removed from memory when that application exits.
To convert an existing RUMBA application to work with EXTRA! through the WD_ API wrapper, the code should be reviewed to identify any exit sequences, whether normal or abnormal end. In all cases, WD_ResetSystem should be called to ensure that sessions programmatically started by the application are released and closed when the application exits. No other change should be needed.
Other API Functions
Except as noted above, Attachmate EXTRA! and NetManage RUMBA are functionally equivalent in operation with respect to this proprietary RUMBA API. While the Attachmate WD_ API wrapper does not implement every entry point defined in the RUMBA API, testing with real-world applications has demonstrated that functions omitted in the wrapper are rarely used. If your organization’s applications depend on one or more of these functions, please contact your Attachmate representative to discuss requirements.