rumba 8.3: system administrator guide - micro focus this guide the rumba system administrator guide...

Rumba 8.3

SystemAdministrator

Guide

Micro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUKhttp://www.microfocus.com

Copyright © 1984-2012 Micro Focus. All rights reserved.

MICRO FOCUS, the Micro Focus logo and Rumba are trademarks or registered trademarks ofMicro Focus IP Development Limited or its subsidiaries or affiliated companies in the UnitedStates, United Kingdom and other countries.

All other marks are the property of their respective owners.

2012-06-11

ii

Contents

About This Guide ............................................................................................... 8Conventions used in this guide ........................................................................................... 8How this guide is organized ................................................................................................ 8Available documentation ..................................................................................................... 9

Introducing Rumba .......................................................................................... 10About Rumba .................................................................................................................... 10Rumba products ................................................................................................................10Rumba applications ...........................................................................................................11Tools ................................................................................................................................. 12

End-user productivity tools ..................................................................................... 12Rumba software installation and maintenance .......................................................14Developer tools ...................................................................................................... 15

Rumba Products and Features ....................................................................... 16Product overview ...............................................................................................................16Rumba product listing ....................................................................................................... 16

Product Overview ................................................................................................... 16Individual application features ................................................................................ 17

New features ..................................................................................................................... 18New shared features .............................................................................................. 18New AS/400 features ............................................................................................. 18New mainframe features ........................................................................................ 18

Host-specific features ........................................................................................................18Mainframe features ................................................................................................ 19New AS/400 features ............................................................................................. 20UNIX and HP features ............................................................................................20Shared feature descriptions ................................................................................... 22

Core features .................................................................................................................... 22Features summary ................................................................................................. 22

Installing Rumba .............................................................................................. 26Planning installation and deployment ................................................................................26

Windows terminology ............................................................................................. 26Windows Installer service .......................................................................................27Changes to Rumba components ............................................................................29

Using License Manager .................................................................................................... 29Using a central license server ................................................................................ 29Uninstalling a product that uses Sentinel RMS ...................................................... 29Managing licenses ..................................................................................................30Licensing tasks .......................................................................................................30

The installation process .................................................................................................... 33Default path of user profile ..................................................................................... 34Using the Setup wizard .......................................................................................... 34Using transforms .................................................................................................... 35Rolling back an installation .....................................................................................36Modifying Rumba ................................................................................................... 36Repairing Rumba ................................................................................................... 36Removing Rumba ...................................................................................................37

Customizing Setup ............................................................................................................ 37Transforms ............................................................................................................. 37Windows Installer command line arguments ..........................................................38

Distributing Rumba with SCCM .........................................................................................39

Contents | 3

Uninstalling previous versions of Rumba ............................................................... 40Preparing client computers for Windows Installer .................................................. 40Creating a Rumba deployment package ................................................................ 40Advanced deployment issues .................................................................................40

Rumba file locations for Windows XP ............................................................................... 41Rumba file locations for Vista and Windows 7 .................................................................. 43

Using Rumba .................................................................................................... 46Rumba folders ...................................................................................................................46Using Rumba menus, toolbars, and the status bar ........................................................... 46

Customizing menus and toolbars ........................................................................... 46Mainframe status bar ..............................................................................................46AS/400 status bar ...................................................................................................47HP status bar ..........................................................................................................47UNIX status bar ...................................................................................................... 48

Rumba Session Profiles ....................................................................................................48About Session Profiles ........................................................................................... 48Supplemental and interface configuration files .......................................................49Migrating Session Profiles from Rumba 6.x or 7.x ................................................. 49

Rumba Desktop Profiles ................................................................................................... 50About Desktop Profiles ...........................................................................................50Session Profile locations ........................................................................................ 50

HP keyboard key codes .................................................................................................... 50Keys mapped to active default settings ..................................................................50Keys used to send 7-bit control characters ............................................................ 51Codes sent by editing keys .................................................................................... 52Codes sent by arrow keys ...................................................................................... 52Codes sent by numeric keypad keys ......................................................................53

VT keyboard key codes .....................................................................................................53VT codes sent by top-row function keys .................................................................53VT keys used to send 7-bit control characters ....................................................... 54VT codes sent by editing keys ................................................................................55VT codes sent by arrow keys ................................................................................. 55VT codes sent by numeric keypad keys .................................................................55

AS/400 Getting Connected .............................................................................. 57Connecting to the host ...................................................................................................... 57

Starting the connection process ............................................................................. 57Selecting an interface .............................................................................................58Configuring the interface ........................................................................................ 59Successful connection indicator ............................................................................. 59Other helpful features .............................................................................................60

Using the Rumba Router to configure an APPC link .........................................................60Overview of Rumba Router .................................................................................... 60Connection Configuration dialog box ..................................................................... 60Setting up the connection .......................................................................................61Rumba Router link types ........................................................................................ 63

Native TCP support ...........................................................................................................66Rumba TCP architecture ........................................................................................66Supported Rumba components ..............................................................................67Configuring a TCP connection ............................................................................... 67Trace support for TCP applications ........................................................................67

Configuring an MPTN connection ..................................................................................... 67About MTPN ...........................................................................................................67AS/400 considerations ........................................................................................... 68MPTN parameters .................................................................................................. 68

Configuring a Microsoft SNA Server connection ...............................................................69Diagnostics ........................................................................................................................69

4 | Contents

Configuring the AS/400 Communications tool .................................................................. 69Connecting to the host ........................................................................................... 70Interface page ........................................................................................................ 70Security page ......................................................................................................... 71Character page .......................................................................................................72Diagnostics page ....................................................................................................72

AS/400 File Transfer .........................................................................................73AS/400 File Transfer features ........................................................................................... 73Installation ......................................................................................................................... 73Using profiles .................................................................................................................... 73User files ........................................................................................................................... 74Changing the library list on the AS/400 host ..................................................................... 74

Copying the QDFTJOBD file .................................................................................. 75Changing the library list in the QDFTJOBD file ...................................................... 75Updating the user profile ........................................................................................ 75

Creating a PC description file ............................................................................................75Structure of the PC description file .........................................................................76Sample PC description file ..................................................................................... 79

Using SQL: Examples ....................................................................................................... 79Example 1: Using SELECT, WHERE, and ORDER BY ......................................... 80Example 2: Querying multiple files with JOIN BY ...................................................81Example 3: Summarizing records with GROUP BY ............................................... 82

AS/400 Client Application ................................................................................84AS/400 Client installation and availability ..........................................................................84Before starting ...................................................................................................................84Interfaces supported ......................................................................................................... 84Rumba Submit Remote Command ................................................................................... 84

Mainframe File Transfer ...................................................................................86Mainframe file transfer features ........................................................................................ 86Sending and receiving files ............................................................................................... 86

Configuring your PC ............................................................................................... 86Sending a file to the host ........................................................................................87Receiving a file from the host: ................................................................................ 87

Using file transfer templates ..............................................................................................87Creating a TSO template ........................................................................................88Creating a CMS template ....................................................................................... 88Creating a CICS template ...................................................................................... 89

Batch file transfers ............................................................................................................ 89Creating a batch file ............................................................................................... 90Running a batch file transfer .................................................................................. 91

File transfer registry settings ............................................................................................. 91Using macros to transfer files ............................................................................................92

Creating a file transfer macro ................................................................................. 92IND$FILE TRANSxx codes .................................................................................... 93

HP and UNIX File Transfer ...............................................................................96How to Transfer Files Using Rumba HP and UNIX ...........................................................96

Understanding the file transfer process ..................................................................96MPE file transfers ................................................................................................... 97

Using compatible file transfer protocol versions ................................................................978-bit binary transparent communications ............................................................... 97

Using Rumba Macros to Transfer Files .............................................................................98AS/400 and Mainframe Printers ...................................................................... 99

AS/400 and Mainframe printer features ............................................................................ 99Printing AS/400 and mainframe documents on a PC printer ............................................ 99Viewing documents before printing ................................................................................... 99

Contents | 5

Monitoring and controlling printers and print jobs ............................................................. 99AS/400 Printer Queues ........................................................................................ 100Direct printing ....................................................................................................... 100Printer sharing and End print job ..........................................................................100PC Printer Queues ............................................................................................... 100

Viewing print job history .................................................................................................. 100Formatting printed documents ........................................................................................ 101

Host Print Transform ............................................................................................ 101Font mapping ....................................................................................................... 101Character translation ............................................................................................ 101

Rumba Telnet Edition .................................................................................... 103Rumba applications for TCP/IP networks ....................................................................... 103For AS/400 hosts ............................................................................................................ 103For Mainframe hosts ....................................................................................................... 103For UNIX hosts ................................................................................................................104For HP hosts ................................................................................................................... 104Getting connected ........................................................................................................... 104

Automating Rumba ........................................................................................ 106Creating macros ..............................................................................................................106Connect and disconnect macros .....................................................................................106

Specifying connect and disconnect macros ......................................................... 107Macro Editor ....................................................................................................................107

Copying data between applications ......................................................................107Using variables ....................................................................................................108

Running Macros .............................................................................................................. 110Running standard or custom macros ................................................................... 110Macros as Hotspots ..............................................................................................110Macros on your toolbars ......................................................................................111Keyboard macros ................................................................................................. 111

Macro Commands ...........................................................................................................112Mainframe macro commands ..............................................................................112AS/400 macro commands .................................................................................... 112HP and UNIX macro commands .......................................................................... 113

Connection Tools ........................................................................................... 115Rumba APPC Configuration tool .....................................................................................115

Connections ......................................................................................................... 116International character set translation .................................................................. 116AS/400 modes ......................................................................................................117Remote and local logical units ..............................................................................117CPI-C side information file ....................................................................................117Transaction programs .......................................................................................... 118Conversation security ...........................................................................................118

Administrator Override File ............................................................................................. 118Administrator override file definition .................................................................... 118Administrator override file function ...................................................................... 119Local connection configuration ............................................................................119Administrator override file creation .......................................................................120Editing existing administrator override files .......................................................... 120To set user access to administrator override file ..................................................120Assessing workstation setup ................................................................................ 121

Rumba AS/400 Communications Utility ......................................................................... 121AS/400 Communications Utility overview .............................................................122AS/400 Communications Utility link configuration ................................................ 122

Communication Monitor .................................................................................................. 123Diagnostic and Development Tools ............................................................. 124

6 | Contents

Rumba Trace tool ............................................................................................................124Application program interface options .................................................................. 124Difficult troubleshooting tasks ...............................................................................125Display software code version ..............................................................................125Playback display and printer data stream trace .................................................. 125

Rumba Tracer ................................................................................................................. 126Development Tools ......................................................................................................... 126

Contacting Micro Focus ................................................................................ 128Information Needed by Micro Focus SupportLine ...........................................................128

PDF Feedback .................................................................................................129

Contents | 7

About This GuideThe Rumba System Administrator Guide has been written to help system administrators to:

• Plan the deployment of Rumba• Install Rumba• Support end users• Troubleshoot Rumba

This guide contains a number of sections, each focussing on one of Rumba's many features.

The guide is provided in Portable Document Format (PDF) so that you either read it online or print selectedinformation for your convenience.

Conventions used in this guideThe following conventions are used in this guide:

Item Description

File names File names and extensions are listed in monoface type.

Example: .rsda is the file extension of all RumbaAS/400 profiles.

Note: Note text An item of interest.

Command Line Text that appears in the command line (either entered bythe user or generated as a response to user entry)appears in monoface type.

Blue text Cross-references to additional information are in bluetext.

For More Information Pointers to other sections in this guide, to online Help, orto Web pages available on the Internet.

How this guide is organizedThe System Administration Guide contains the following sections:

Rumba Features Summarizes the features provided with Rumba.

Installing Rumba Describes how to install Rumba on Windows XP, Windows Vista, andWindows 7 with Microsoft Installer.

Introducing Rumba Provides an introduction to Rumba.

AS/400 Getting Connected Describes how to configure and maintain Rumba AS/400 display andprinter connections.

AS/400 File Transfer Describes the AS/400 file transfer program.

AS/400 Client Application Describes the AS/400 Client Application which allows you to start andcontrol non-interactive programs on your AS/400 host system withoutopening a display session.

8 | About This Guide

Mainframe File Transfer Describes the mainframe file transfer program.

HP and UNIX File Transfer Describes the HP and UNIX file transfer programs.

AS/400 and MainframePrinters

Provides an overview of the AS/400 and mainframe printer features.

Rumba Telnet Edition Describes how you can use Rumba over TCP/IP to connect to multiplehosts, transfer files, and share host file systems with PCs.

Automating Rumba Describes how to use macros and scripts to perform automated Rumbatasks.

Connection Tools Describes the most commonly used Rumba tools: Rumba APPCConfiguration utility, Administrator Override File, Rumba AS/400Communications utility, and Rumba Communication Monitor.

Diagnostic andDevelopment Tools

Describes the Rumba Trace Console, Rumba development tools for .NET,and the Rumba Development Add-in for Visual Studio.

Available documentationIn addition to this guide, Rumba documentation consists of the Readme file and the Rumba Help.

Readmefile

The Readme file contains late-breaking information on Rumba. There are many Rumbaproducts. Some of these products might share the same Readme file. Therefore, theReadme file might contain information about other Rumba products, in addition toinformation about the product you are currently installing.

RumbaHelp

Information on how to customize and use Rumba can be found in the Rumba Help. TheHelp does not include installation information. For details on installing, see InstallingRumba.

To start the Help:

• Click Help > Rumba Help Topics (classic interface).• Click the Help icon on the Rumba toolbar (ribbon interface).

You can then browse the Table of Contents or search for specific terms.

About This Guide | 9

Introducing RumbaThis section is intended for information solution providers who are evaluating Rumba, and for systemadministrators who want a quick summary of the features that are included in Rumba.

The section introduces the entire Rumba product line, which provides access to multiple host types: IBMMainframe, IBM AS/400, UNIX, OpenVMS, and HP. Your Rumba software may be able to access one orall of these host types depending on your individual needs.

Rumba feature descriptions contains summary descriptions of the standard features in the various Rumbahost products.

About RumbaRumba is a software suite that connects your users to information residing on multiple hosts and serversacross your organization. With Rumba, you have your choice of protocols such as TCP/IP and RumbaRouter (MPTN).

All Rumba products operate on Windows 7, Windows Vista, Windows XP, Windows 2003, WTS, and CitrixPresentation Server. In addition to providing multiple access solutions, the Rumba product suite:

• Gives users tools with which they can view, print, and transfer data located anywhere in theorganization. These tools help users attain a higher level of efficiency.

• Gives system administrators flexibility in deploying and maintaining Rumba software.• Offers developers the functionality needed to quickly generate custom client/server solutions using

ActiveX technology.

Rumba products are designed to meet our customers’ specific access needs. Micro Focus produces andpackages Rumba products to support multiple or single host access needs, with multiple connectionsolutions. We also provide Rumba versions for popular LANs, and migration products that help you movefrom one Rumba product to another, as well as from competitor products to Rumba.

Rumba productsThe following table lists multiple-host Rumba products:

Rumba product Product description Connection requirement

Rumba OFFICE • Supports IBM Mainframe, IBM AS/400, Digital OpenVMS, and UNIXsystems, and HP 3000 and 9000systems

• Supports multiple servers andnetwork protocols

• Supports display, printing, and filetransfer capabilities for all hosts

• Provides browser-to-hostconnections and an integrated setof Internet applications

Multiple network protocols

Rumba Telnet Edition • Supports IBM Mainframe, IBM AS/400, Digital OpenVMS, and UNIX

Telnet, TCP/IP

10 | Introducing Rumba


systems, and HP 3000 and 9000systems

• Designed specifically for theTelnet network protocol



Rumba applicationsThe following table describes the applications that make up the Rumba suite:

Rumba application Feature description

Rumba Mainframe Edition • Supports BM Mainframe• Supports multiple servers and network protocols• Supports display, printing, and file transfer capabilities

for the mainframe host• Provides browser-to-host connections and an

integrated set of Internet applications

Rumba AS/400 Edition • Supports IBM AS/400• Supports multiple servers and network protocols,

including native TCP/IP• Supports display, printing, and file transfer capabilities

for the AS/400 host• Designed to maximize the file, print, and database

serving capabilities of the AS/400 with such featuresas Shared Folders, Submit Remote Command, VirtualPrint, Data Queues, and Rumba AS/400 OptimizedServer Driver

• Provides browser-to-host connections and anintegrated set of Internet applications

Rumba UNIX-HP Edition • Supports Digital OpenVMS and UNIX systems• Supports multiple servers and network protocols• Supports display, printing, and file transfer capabilities

for the UNIX and VMS host• Provides browser-to-host connections and an


• Supports HP 3000 and 9000 systems, and UNIXsystems supporting HP terminal types

• Supports multiple servers and network protocols• Supports display, printing, and file transfer

capabilities, including MPE native file transfer, for theHP host

• Provides browser -to-host connections and anintegrated set of Internet applications

Introducing Rumba | 11

ToolsAll Rumba products contain the following tools:

• End-user productivity tools• Rumba software installation and maintenance tools• Developer tools

More complex and powerful task automation can also be provided by the Script Editor and Script Playerapplications, provided separately.

End-user productivity toolsRumba software applications contain tools that help end users attain a higher level of efficiency byeliminating time-consuming file and application manipulation. For example, with these tools, your users cancopy from a host database and paste it into another application, like a spreadsheet or word processor. ThePaste Link facility automatically updates the data in a Windows application whenever both it and a Rumbasession to the host are open.

Other useful features include:

• Rumba Office Integration. From within the Rumba desktop, users can instantly send the current screentext or image, fully or selectively into any Office item.

• Rumba Session Screens History Tracking. Rumba introduces an embedded, fully visual way of trackingscreens visited throughout a session. Users can go back to previously visited host screens and work onthem. This ability is enhanced with search capabilities, database navigation, export and import supportfor session sharing, information sorting and automatic or manual capturing options.

• Rumba Toolbars Enhancements. Support for user-defined, customized toolbars that can be undockedand ‘floated’,rather than just fixed and docked to the top of the application. Ability to define more typesof buttons and the ability to export and import toolbars to and from files.

• Enhanced Rumba Desk Management. The new Rumba desktop is designed to support the tiling andrepositioning of all session types within the Rumba desktop in an easy, dynamic and intuitive way. TheRumba desktop can then be saved in the desktop profile to be reused when Rumba is restarted.

As a system administrator, you can help your users by:

• Automating log-on procedures by creating macros for them• Setting up batch files that they can use to print multiple host screens to a PC printer (Print Area Setup)

Many of these features can help personalize the workplace. For example, you and your users can changethe look of a Rumba display by using watermarks or customizing the display.

The following table references the more important end-user tools for the Rumba suite. The table lists thetools, then provides corresponding Rumba menus and commands, and brief descriptions.

Tool Menu/ Command Description

Rumba Desktop A tabbed interface to Rumba thatmakes it easy to manage severaldifferent sessions at once, even todifferent hosts.

Profiles File/ New, Open, Save, Save As,Properties Options/ Profile

Saves Rumba customized display/printer and interface configurationinformation. Using profiles, a user cantailor a Rumba session for a specifichost or application and save it for re-use. Session Profiles save



information relating to a single hostsession, whereas Desktop Profilessave a set of Session Profiles.

Print screen File/ Print, Print Preview Specifies how to print a screen withinthe Rumba window. Users can printto the Clipboard, current Windowsprinter, or to a file. Users can alsodesignate printers and fonts, andview how the screen will look whenprinted.

Send screen File/ Send Screen Activates the user’s installed mail ormessaging system. Users can send ascreen without exiting the Rumbawindow.

Print Area Setup File/ Print Area Setup Sets up batch files to print multiplehost screens to a PC printer.

Edit Clipboard Edit/ Undo, Cut, Copy, Paste Options/Edit

Supports data cutting, copying, andpasting activities.

Paste Area Setup Edit/ Paste Area Setup Sets up host screens to receive datapasted from the Windows Clipboard.Using this feature, users can pastedata from a third-party application intomultiple screens of a host application.

Title Bar View/ Title Bar Customizes the title bar text for theRumba window.

Configurable toolbars View/ Toolbars Customizes the Rumba toolbar. Youcan create and modify toolbars to suituser needs and preferences.

Note: This is currentlyavailable only in the Classicinterface.

Watermark View/ Watermark Displays an image in the backgroundof the current Rumba window.

Status bar View/ Status Bar Toggles the 3D status bar on and off.

Customized display Options/ Display Customizes the look of the Rumbawindow: fonts, colors, cursor settings,and more.

Keyboard mapping Options/ Keyboard Maps special terminal keys to the PCkeyboard. Users can also selectdifferent keyboards and internationalkeyboard options.

Capture Screen Options/ Capture Screen Setup,Capture Screen

Captures the current Rumba screenin a specified .txt file (or capture.txt ifno file is specified).

Macros Tools/ Run Macro, Record Macro,Edit Macro, Macro Properties

Records a series of actions, such askeystrokes and commands. Onceusers record a macro, they can play itback to automate routine tasks.

Users can assign macros to aHotspot (see below), a Rumba



toolbar button, or a key combinationon the keyboard.

Hotspots Tools/ Hotspots Makes any non-protected text on ahost screen into a Hotspot andassociates that text with a macro.When the user clicks on the Hotspot,the macro runs.

Customized menus View/ Toolbars Customizes Rumba menus. Forexample, users can create new menuitems that start non-Rumbaapplications.

Note: This is currentlyavailable only in the Classicinterface.

Online help Help Provides detailed instructions on howto use Rumba. Users can browse theContents for information, or searchfor a specific term.

Rumba software installation and maintenanceThe most common way to connect Rumba software to a host is by selecting and configuring an interfacefrom the Rumba display or printer. However, if you are connecting to an IBM Mainframe or AS/400, thereare additional tools available to you. The following table provides descriptions for the other availableconnection tools.

Table 1: Other connection tools

Application Description

APPC Configuration Utility Provides advanced configuration options for mostMainframe and AS/400 interfaces. Allows for theconfiguration of the following APPC items: Remote andlocal logical units (LUs), Modes, transaction programs(TPs), CPI-C side information, and conversation securityfor TPs.

AS/400 Communications utility Used primarily to configure connections for SharedFolders, Data Queues, Submit Remote Command, andAS/400 file transfers.

Use the following diagnostic tools (available with all products) to monitor and troubleshoot Rumbaconnections on your network.

Table 2: Diagnostic/Troubleshooting tools

Feature Description

Trace Console Traces and records communication sessions.Specifically:

• Data streams from the Mainframe Display and Printer,AS/400 Display and Printer, UNIX Display and HPDisplay

• SNA communications


Feature Description

• Rumba Display APIs, such as DDE, EHLLAPI, andWinHLLAPI; EHNAPPC

• Host System APIs, such as Data Queues, SharedFolders, AS/400 file transfers, and Submit RemoteCommand

Rumba Communication Monitor Displays an in-depth look at the connections of aworkstation.

Note: Not available for Rumba UNIX-HP Edition.

Developer toolsThe AS/400 client applications, such as File Transfers, have APIs associated with them. Additionally, theSubmit Remote Command is available as ActiveX controls.

Rumba PC-to-Host consists of a family of ActiveX controls and Rumba Web-to-Host consists of bothActiveX controls and JavaBeans. You may use these ActiveX controls and JavaBeans to create newapplications using languages such as Visual Basic, C++, and Java. Information and samples for usingthese components can be found on the Micro Focus web site.


Rumba Products and FeaturesThis section is intended for information solution providers who are evaluating Rumba, and for systemadministrators who want a quick summary of the features that are included in Rumba.

The section introduces the entire Rumba product line, which provides access to multiple host types: IBMMainframe, IBM AS/400, UNIX, OpenVMS, and HP. Your Rumba software may be able to access one orall of these host types depending on your individual needs.

Rumba feature descriptions contains summary descriptions of the standard features in the various Rumbahost products.

Product overviewRumba is a software suite that connects your users to information residing on multiple hosts and serversacross your organization. With Rumba, you have your choice of protocols such as TCP/IP and RumbaRouter (MPTN).

All Rumba products operate on Windows 7, Windows Vista, Windows XP, Windows 2003, WTS, and CitrixPresentation Server. In addition to providing multiple access solutions, the Rumba product suite:

• Gives users tools with which they can view, print, and transfer data located anywhere in theorganization. These tools help users attain a higher level of efficiency.

• Gives system administrators flexibility in deploying and maintaining Rumba software.• Offers developers the functionality needed to quickly generate custom client/server solutions using

ActiveX technology.

Rumba product listingRumba products are designed to meet our customers’ specific access needs. Micro Focus produces andpackages Rumba products to support multiple or single host access needs, with multiple connectionsolutions. We also provide Rumba software versions for popular LANs, and migration products that helpyou move from one Rumba product to another as well as from competitor products to Rumba.

The remainder of this section consists of three tables that list the variety of Rumba products available. Thefirst two tables list the Rumba product (as a general overview, and then as the individual applications thatmay be included), with a brief description. Each table first lists multiple protocol products and then productsthat include network-specific protocols. The third table lists migration products with a short explanation ofwhat they do.

Product OverviewThe following table lists multiple-host Rumba products. The multiple network protocol product is listed first,followed by network-specific protocol products.


Rumba OFFICE • Supports IBM Mainframe, IBM AS/400, Digital OpenVMS and UNIXsystems, and HP 3000 and 9000systems

• Supports multiple servers andnetwork protocols

Multiple network protocols

16 | Rumba Products and Features




Rumba Telnet Edition • Supports IBM Mainframe, IBM AS/400, Digital OpenVMS and UNIXsystems, and HP 3000 and 9000systems

• Designed specifically for theTelnet network protocol



Telnet, TCP/IP

Individual application featuresThe following table provides information on the applications that make up the Rumba suite.


Rumba Mainframe Edition • Supports the IBM Mainframe• Supports multiple servers and network protocols• Supports display, printing, and file transfer capabilities

for the mainframe host• Provides browser-to-host connections and an


Rumba AS/400 Edition • Supports the IBM AS/400• Supports multiple servers and network protocols,

including native TCP/IP• Supports display, printing, and file transfer capabilities

for the AS/400 host• Designed to maximize the file, print, and database

serving capabilities of the AS/400 with such featuresas Shared Folders, Submit Remote Command, VirtualPrint, Data Queues, and Rumba AS/400 OptimizedServer Driver

• Provides browser-to-host connections and anintegrated set of Internet applications

Rumba UNIX-HP Edition • Supports Digital OpenVMS and UNIX systems• Supports multiple servers and network protocols• Supports display, printing, and file transfer capabilities

for the UNIX and VMS host• Provides browser-to-host connections and an


• Supports HP 3000 and 9000 systems and UNIXsystems supporting HP terminal types

• Supports multiple servers and network protocols

Rumba Products and Features | 17


• Supports display, printing, and file transfercapabilities, including MPE native file transfer, for theHP host

• Provides browser -to-host connections and anintegrated set of Internet applications

New featuresThis section contains a brief description of the new features in this release as well as the standard featuresin the various Rumba host applications.

• Shared features are those features that can be found in most Rumba products. Some shared featuresinclude the separate Macro Editor (which is bundled with most editions of Rumba), keyboardconfiguration, and other tools for end-users, system administrators, and developers.

• Host-specific features are features that are available only with the appropriate host application. Forexample, the Rumba Mainframe Display is considered a host-specific feature because it is availableonly in installations that include the Rumba Mainframe application.

For detailed instructions on how to use each of these new features, whether shared or host-specific, seethe product Help.

New shared featuresThe following list briefly describes the new shared features available in this release. This release of Rumbaprovides:

• Rumba supports specifying Internet Protocol version 6 (IPv6) formatted IP addresses for hosts. IPv6support provides the functionality to connect to hosts on the network as Internet technology continues togrow.

• The new Rumba Tracer feature records information about a program's execution (see Rumba Tracer).

New AS/400 featuresThe following new features are available in AS/400 applications (Display, Printer, and AS/400 FileTransfer).

• Spell checking• Automatic hyperlink detection• Automatic email address detection

New mainframe featuresRumba provides the following new mainframe features:


Host-specific featuresThis section describes the features specific to individual Rumba host applications.


These feature descriptions are organized by host in tables with a listing of features and a short descriptionof what each feature does.

Mainframe featuresMainframe Display and Printer. With the Mainframe Display, they view host applications and transfer files.With the Mainframe Printer, they can route jobs from the mainframe printer queue to a Windows printer.Both the Mainframe Display and Printer use interfaces to connect to the host.

The following provides summary descriptions for Rumba Mainframe Edition standard features andinterfaces.

Table 3: Standard features

Feature Description

Display • Presents the traditional mainframe display terminals(3278/79) in a Microsoft Windows application: theRumba Page.

• Includes GDDM support, which makes working withIBM mainframe graphics similar to using Windowsgraphics packages.

• Users can run multiple host sessions, displaying andworking with PC and host applications simultaneously.

File transfer • Supports host file transfer programs IND$FILE andSimXfer.

• Supports ASCII or binary transfers, Write StructuredField or Buffered data streams, EBCDIC-to-ASCIItranslation, and data compression.

• Provides DOS-based, batch, and drag-and-drop filetransfer features.

Switching system keyboards • Allows switching keyboard displays as in Windows(ALT+SHIFT).

Table 4: Printer

Feature Description

Rumba Mainframe Printer (3287 emulation) Allows users to route jobs from the mainframe printerqueue to a Windows printer.

PC printer queues Lists the printer queues for all network and local printersset up in Windows Print Manager.

Users can use PC Printer Queues to control Windowsprinters.

Print log Lists documents that have printed through the Rumbaprinter, including documents printed from host as well asfrom PC applications.

Table 5: Interfaces

Feature Description

Microsoft SNA Server Connects to mainframe hosts through a suite ofintegrated services. SNA Server acts as an SNA gateway


Feature Description

using two types of connections, client-to-server andserver-to-mainframe.

MPTN (SNA over TCP/IP) Connects to a mainframe host using SNA APPC tocommunicate over TCP/IP networks.

Provides transparent access to functions such asmainframe printing and file transfer.

TN3270E Uses a TCP/IP protocol stack to connect to a mainframehost via a Telnet server.

New AS/400 featuresThe following new features are available in AS/400 applications (Display, Printer, and AS/400 FileTransfer).


UNIX and HP featuresWhen using Rumba UNIX-HP Edition, users perform the majority of their tasks with the host using theUNIX or the HP Display. This includes viewing host applications, transferring files, and printing from thehost. The UNIX Display and the HP Display connect to a host over a TCP/IP interface.

The following tables provide summary descriptions for UNIX and HP standard features.

Table 6: Rumba for UNIX

Standard feature Description

Display Presents the traditional VT display terminals in aMicrosoft Windows application supporting the wholerange of VT terminals from VT 52 to VT 420 as well asVT340 ReGIS, Sixel, SCO ANSI, BBS ANSI andTektronix 4010/4014 graphics support.

Users can run multiple host sessions, displaying andworking with host applications simultaneously.

File transfer Supports Kermit, Text, and X-, Y-, Z-Modem file transferprotocols over all the supported interfaces. It supports aRumba software initiated mode where the user need onlyselect the protocol and file to be transferred, and Rumbasoftware provides the underlying commands tosuccessfully transfer the file.

Enhanced security Supports SSL 3.0 (Secure Sockets Layer), TLS 1.0(Transport Security Layer), and SSH (Secure Shell) toallow users to securely access applications and transferdata between their desktops and Mainframe, AS/400 andUNIX systems, encrypting the session data stream to ahost capable of supporting these protocols.

Switching system keyboards Allows switching keyboard displays as in Windows (ALT+SHIFT).

Keyboard shortcut to open Split Display or Historywindow.

Provides a keyboard shortcut (CTRL+SHIFT+Z) to openthe Split display and History window on a UNIX Display.



Double-click auto select When connecting to UNIX and double-clicking data, thedata is automatically selected and copied to theclipboard. Then when you right-click at the new locationthe data is pasted without displaying the right-click, pop-up menu.

Table 7: Printer


Terminal-routed printing Prints the display screen, selected text, and full colorgraphics, or routes print jobs from the host printer throughyour Windows print driver.

Table 8: Interfaces


Async Connects to a remote UNIX host through a phone lineand a standard asynchronous modem or directly to thehost or terminal controller using an RS-232 directconnection.

Telnet Connects to the UNIX host using the TCP/IP protocol.

Table 9: Rumba for HP


Display Presents the traditional HP terminal types in a MicrosoftWindows application.


File transfer Supports Kermit, Text, and Xmodem, Ymodem, Zmodemfile transfer protocols over all the supported interfaces,and a proprietary protocol to HP3000 servers running theMPE operating system. It supports a Rumba softwareinitiated mode where all the user needs to do is select theprotocol and the file to be transferred and Rumbasoftware will provide the underlying commands tosuccessfully transfer the file.

Table 10: Printer


Terminal-routed printing Prints the display screen or selected text, or routes printjobs from the host printer through your Windows printdriver.

Table 11: Interfaces


Async Connects to a remote HP host through a phone line and astandard asynchronous modem, or directly to the host orterminal controller using an RS-232 direct connection.



HP NSVT Connects to an HP host using the proprietary HP protocolfor Network Services Virtual Terminals (NSVT).

Telnet Connects to the HP host using the TCP/IP protocol.

Shared feature descriptionsThis section describes the features shared between the Rumba products. Features, or components, areshared because the Rumba architecture is based upon Microsoft’s ActiveX component technology. Theuse of common components results in a common user interface and predictability in the way a Rumbaproduct works. Because the user sees the common user interface and experiences the same basicfunctionality across Rumba products, Rumba common components reduce end-user training, saving timeand resources. The following table lists some of the newest standard features shared by the host-specificproducts.

Table 12: All Rumba products

New Feature Description

Enhanced Security through SSL/SSH Supports SSL 3.0 (Secure Sockets Layer), TLS 1.0(Transport Security Layer), and SSH (Secure Shell) toallow users to securely access applications and transferdata between their desktops and Mainframe, AS/400 andUNIX systems, encrypting the session data stream to ahost capable of supporting these protocols.

Multiple HLLAPI sessions originating from the sameprofile.

Permits running multiple HLLAPI sessions originatingfrom the same profile. This is an additional enhancementto the API options currently available in Rumba.

Core featuresRumba gives you easy, complete, and transparent access to host applications. PC users working withMicrosoft Windows can use Rumba to communicate with a number of hosts and host applications.

Note: Which hosts you can connect to depends on which edition of Rumba you have installed. Forexample, Rumba AS/400 Edition enables you to connect to AS/400 hosts.

This section provides an overview of the core features of Rumba. You can find more specific information inother sections of this guide.

Features summaryRumba software takes full advantage of the Windows graphical user interface and tabbed browsingcapabilities. Together, these features help improve user efficiency and simplify the sharing andmanipulation of data among multiple PC and host platforms.

Using Rumba software, you can:

• Access multiple host sessions simultaneously from the same window• Switch system keyboards as you do in Windows (ALT+SHIFT)• Copy and paste data between tabs or windows• Capture screen data to a file• Copy information to the Windows Clipboard (including, in Rumba Mainframe Edition, the ability to copy

only unprotected fields)


• Rumba AS/400 Edition: Use long passwords to provide an additional authentication mechanism withstricter encryption and tighter security

• Rumba UNIX Edition: Use the History feature to maintain a larger list of recently performed operationsand scroll back to them easily

Enhanced security through SSL/SSH

With the inclusion of SSL 3.0 (Secure Sockets Layer), TLS 1.0 (Transport Security Layer), and SSH(Secure Shell) support, users can securely access applications and transfer data between their desktopsand host systems, encrypting the session data stream to a host capable of supporting these protocols.

Host sessions

Rumba software runs on a single-user PC connected to a host, or on a local area network (LAN) with agateway connection to a host. Rumba Mainframe Edition software can also connect to a host usingmultiple Physical Unit IDs (PUIDs) with a Token Ring or Ethernet® connection.From a single window, youcan run multiple host sessions using different connection types.

You can also retrieve data from one or more hosts and transfer it to PC applications or print the data.

Rumba printerRumba AS/400 and Mainframe Editions support a wide range of printer features, including the ability to:

• Save and print host screens• Print to a disk• Route screen output to a LAN print server for shared printing• Use international character sets

Copy and pasteRumba provides full interoperability between your host applications and other Windows applications. Aswell as normal copy and paste operations, you can use the Paste Link facility to automatically update thedata in a Windows application whenever both it and a Rumba session to the host are open.

File transfersThe file transfer feature copies files between your PC and the host. Rumba software allows you to navigatethrough the host file system, listing host and PC directories to simplify file selection and transfer. When youselect the Rumba Initiated File Transfer feature, Rumba software automatically starts the file transferprogram on the host and sends or receives the file.

AS/400 file transfer

There are two ways to run file transfers from an AS/400 Display session:

• AS/400 File Transfer.

This method sends data between the host and your PC. If the AS/400 host is not in passthrough mode,the Send and Receive commands on the Transfer menu will open the AS/400 File Transfer window.

• Mainframe Passthrough.

This method uses the AS/400 as an emulator to transfer files to and from a mainframe host. You mustfirst connect Rumba to the AS/400, then run the emulator program on the AS/400 to connect to themainframe. Rumba software detects the passthrough state of the AS/400, so you can use the Send andReceive commands on the Transfer menu to transfer files between the mainframe host and your PC.

Mainframe file transfer

The file transfer feature copies files between your PC and the mainframe. The Send and Receivecommands on the Home menu (the Transfer menu if using Rumba’s Classic interface) open a setup


window where you specify the file type, transfer protocol, and host environment for the file transfer. Youcan also choose to have Rumba software initiate the file transfer protocol. The mainframe file transferfeature works transparently with SimXfer and most IBM host operating systems, including CICS, TSO, andVM/CMS.

The mainframe file transfer also provides abundant functionality such as support for ASCII or binarytransfers, Write Structured Field or Buffered data streams, EBCDIC-to-ASCII translation, and datacompression. Rumba software also supports DOS-based, batch, and drag-and-drop file transfer features.

User interfaces

This version of Rumba provides two different versions of the user interface. You can switch between theseat any time according to your personal preferences.

• Ribbon. Originally introduced by Microsoft Office 2007, this interface organizes commands into a‘ribbon’ across the top of the application window. The commands shown change according to the tabthat has been selected. This makes application features easier to find and quicker to use.

• Classic. An interface similar to that used in previous versions of Rumba, for users experienced witholder versions of Rumba.

Screen displaysRumba software takes full advantage of the GUI capabilities of Windows to offer these features:

• Support of alternate screen sizes, adjusting the host application to fit within the window• Simultaneous display of applications in a variety of screen sizes without reconfiguring your PC software

or modifying the host application• Customization of screen color schemes for existing host applications

Note: Rumba Mainframe Edition supports alternate screen sizes for IBM models 2, 3, 4, and 5

International keyboardsRumba software supports international PC and host keyboards, such as French, German, Norwegian,Swedish, Danish, Spanish, and Italian.

Rumba software supports most types of PC keyboards (for example, the PC, AT, and Enhanced 101- and102-Key). If you do not find your keyboard on the supported list, contact Micro Focus technical support.

You must install the appropriate keyboard driver (usually supplied with the keyboard or an internationalversion of Windows) using the Windows Setup option.

Supported VT featuresRumba software supports configuration of VT features and options through the keyboard, tool bar, andmenus. Features available to you when using a VT terminal and keyboard are available from your PCusing Rumba software. See Appendix B: VT Keyboard Key Codes for a complete listing.

Rumba software emulates the following VT terminal types:

• VT52• VT100• VT101• VT125• VT220• VT240• VT241• VT320• VT330


• VT340• VT420 (paging available; default if VT340 not installed)• 401x (Tektronix graphics, includes 4010/44014; automatic font adjustments occur when entering this

mode)• BBS ANSI• SCO ANSI• WYSE 50/60

You can select and configure the terminal you want to emulate.

Supported HP featuresRumba software supports configuration of HP features and options through the keyboard, tool bar, andmenus. Features available to you when using an HP terminal and keyboard are available from your PCusing Rumba software.

Rumba software emulates the following HP terminal types:

• HP70092• HP70094• HP70096• HP70098• HP2392A• HP2394A

You can select and configure the terminal you want to emulate.

Automating your workRumba provides several powerful tools for automating host communications tasks.

• Macros

Rumba macros are used to automate simple tasks such as logging on, copying and pasting textbetween Rumba Display windows and applications such as Microsoft Excel, or sending a sequence ofcommands to the host. You can configure and use Rumba macros in a variety of ways, including:

• Auto macros

You can save a macro as a connect or disconnect macro: a macro that automatically performs a tasksuch as logging on or off each time you open or close the session profile in which it was created.

• Scripts

The separate Rumba Script Editor application provides more complex and powerful automation optionsthan the Macro Editor. You can use scripts to automatically reconfigure the user interface, performrandom access file operations, automate tasks, modify functionality, and handle incoming events.

Where provided, the Rumba Script Editor can be installed by double-clicking ScriptEngine.msi.

Configuration filesUser configuration files (profiles) are stored in the My Documents folder (or the Personal folder inWindows 7 or Vista), while configuration interfaces are stored in the Application Data folder.


Installing RumbaThis section is written for IT professionals and system administrators who want to customize, install anddeploy Rumba software.

The section contains instructions for installing Rumba on Windows XP, Windows Vista and Windows 7 withMicrosoft Installer technology. Additionally, it contains information about:

• Installing, modifying, repairing, and uninstalling Rumba software• Customizing setup• Microsoft installer command line arguments• Transforms

Planning installation and deploymentThis version of Rumba requires the latest Windows Installer service to install any Rumba feature on aWindows operating systems. Using the Installer service requires less of your management time and allowsyou to design seamless deployment packages for Rumba.

Windows terminologyBefore discussing Rumba setup, it is a good idea to understand some basic terminology and features ofthe Windows policy-based management environment.

Roaming From Windows XP on, Windows allows you to move from computer to computer, yetmaintain your specific desktop profile. Your login information enables this particularfeature because your profile information is located on a server.

WindowsInstaller filetypes

The Windows Installer (.msi) replaces previous installation methods, and enablescleaner installs and uninstalls, as well as repairs.

The patch install package file (.msp) allows you to apply hot fixes to your Rumbaproduct.

The transform file (.mst) allows you to customize your Rumba installations. Beforeusing the transform file, ensure you have the latest version of Windows Installerinstalled. For more information, see Windows Installer service and How to customizeSetup.

Publishing andassigning withIntellimirror

Administrators can publish Rumba to users or assign Rumba to users or computers.

Administrators assign an application through Group Policy Objects. Assignedapplications have installation persistence. When a user selects the program for the firsttime, it is installed. If a user uninstalls an assigned application, it will re-advertiseimmediately.

Administrators publish an application by making it available to users who might wantthe application. With published applications, each user decides whether or not to installthe application from the Control Panel’s Add/Remove Programs utility.

Note: You can only publish to users, not computers.

26 | Installing Rumba

ActiveDirectory

Administrators deploy applications in Group Policy Objects (GPOs) that are associatedwith Active Directory containers such as sites, domains, and organizational units (OUs).Intellimirror (Windows XP) deployment requires Active Directory.

Windows Installer serviceThe Windows Installer service manages applications at the component level. It maintains reference countsin the form of a client list of product codes (rather than integers), so it can identify clients of the installedresource to synchronize counts. This allows clean and complete installs and uninstalls of Rumba, whethersimple or sophisticated.

Note: A Rumba installation detects a previous Rumba 7.x installation and uninstalls it before installingthe current version.

Supported operating systemsRumba operates on PCs with the following operating systems, applications, and environments:

• Windows 7• Windows Vista Business, Ultimate and Enterprise 32-bit versions• Windows XP• Windows Terminal Server (WTS)• Citrix XenApp (formerly Presentation Server)• Microsoft Application Virtualization (App-V)

Software requirementsThe following software is required to install Rumba:

• Micro Focus License Manager• Windows Installer 3.1 or later• Microsoft .NET Framework 3.5 Service Pack 1

You can install Micro Focus License Manager from the Prerequisites folder. You can install WindowsInstaller and .NET Framework either from the Prerequisites folder or download them from theMicrosoft web site.

In addition, the Microsoft Office .NET Interoperability Assemblies (PIA) is required. The PIA enables .NETmanaged code to interact with a Microsoft Office application's COM-based object model. In most cases,the PIA is installed during Office installation. However, sometime it is not. If you need to add the PIA:

1. In Control Panel, select Add/Remove Programs (Windows XP) or Uninstall a Program (Vista orWIndows 7).

2. In the opened window, select the Microsoft Office installation and click Change.3. Select Add or Remove Features.4. Click Continue.5. On the Installation Options page, click the plus sign (+) to expand the application for which you want

to install the PIA.6. Click the drop-down arrow next to .NET Programmability Support, then select Run from My

Computer.

Hardware requirementsThe following hardware is required to install Rumba:

• 400 MHz Pentium processor or equivalent (minimum). 1 GHz Pentium processor or equivalent(recommended).

• 96 MB RAM (minimum). 256 MB RAM (recommended).

Installing Rumba | 27

Disk space requirements can vary. Individual Rumba components share some common resources.Therefore, the disk space needed for an installation that includes all components is significantly less thatrequired for separate installations. Single host installations generally use 40–60 MB and complete Rumbasoftware installations generally use about 100 MB, though actual usage may vary.

Things to consider before installationWhen you install Rumba, Setup prompts you for standard information. Plan your installation based on thefollowing questions (not necessarily in this order):

• Is this a first-time installation, or is a previous version of Rumba installed?• Will you need to uninstall a Rumba version?• What type of installation will you select: Complete or Custom?• To which hosts will you connect: AS/400, Mainframe, HP, or UNIX?• Will you be using Intellimirror for your distributed installs?• Will you be using SMS for your distributed installs?• Will you be using SMS combined with Intellimirror?• Will you customize the installation with your own transforms?• Will you be installing on Windows Terminal Server (Citrix)? If you are installing on Windows Terminal

Server, then have at hand your Rumba license authorization code to be entered to Micro Focus LicenseManager for Terminal Server. For more information, see Using License Manager. After installing Rumbaon Windows Terminal Server, follow its vendor instructions on how to publish Rumba applications toyour users.

Deployment strategies

As an administrator, how you deploy Rumba depends largely on the change and configurationmanagement functions of your networks, whether simple or complex. Installing, Modifying, Repairing, andUninstalling Rumba Software contains detailed deployment and customization information for yourenterprise-wide Rumba installations.

Licensing Rumba is licensed using Micro Focus License Manager, which allows you to authorize,view, and revoke licenses. To use License Manager:

1. Navigate to the License Manager installation file in the Prerequisites folder.2. Install License Manager on a dedicated license server. For more information, see

Using License Manager.

During Rumba installation, you are asked to choose one of the following options:

• Evaluation: Installs a 30-calendar day evaluation version.• Use a License Server Name or Address: The name of the remote machine running

Micro Focus License Manager and where the Rumba license is installed.

Complete orCustominstallation

These installation options allow you to control which Rumba features are installed. Thefeatures available depend on your Rumba edition.

• Complete: Installs all Rumba features, without the opportunity to add or removeindividual features.

• Custom: Gives you the opportunity to add or remove individual features.

Migration issues and directory locationsUser-defined files and configuration files

User-defined files and configuration files reside in different locations in Rumba versionsbefore 7.0. To support Windows roaming, we classify each of these files according to theirscope and function. For example:

• Per user: Each user has their own version of a file and this file can roam with the user.


• Machine-specific: This file only relates to the machine that the product is currentlyinstalled on and cannot roam with the user.

These locations are configurable.

For detailed information on Rumba file locations on supported platforms, see Rumba filelocations for Windows XP and Rumba file locations for Vista and Windows 7.

Rumba installations before Rumba 7.0Rumba detects the existence of previous 32-bit Rumba and OnWeb Web-to-Host products.Installation does not continue until these are removed. For large SMS deployments, it isstrongly advised that you create separate SMS packages for removing previous versionsof the product and installing the new version.

Microsoft Host Integration Server (HIS) 2000 Server and Client

To configure a workstation to communicate with a Microsoft HIS 2000 server (formerly called MicrosoftSNA server), you need to have two pieces of software on the workstation: the Microsoft HIS2000/SNAclient, and the Rumba interface for the Microsoft SNA/HIS 2000 server. If you do not have the software forthe Microsoft SNA client, you can download the client from Microsoft.

Changes to Rumba componentsThe Rumba Optimized Server ODBC driver has been moved into the AS/400 File Transfer subsystem.

The TP Director was included in previous versions of Rumba to map Local LU 6.2 information for APPCand/or CPIC Transaction Programs to a specific User ID. The TP Director is no longer installed as part ofRumba, but can be installed separately using the TPDirector.msi file if required.

Similarly, the Script Editor is no longer installed as part of Rumba but can be installed separately.

Using License ManagerYou manage your product licensing by using the Micro Focus Licensing System Administration tool.

When you install your Micro Focus product, the Sentinel RMS license server is also installed to manageyour license. Depending on how your site administers licenses, you can also request licenses from acentral license server.

Using a central license serverIf your site has multiple licenses and you want to use a central license server to manage them, install theMicro Focus License Manager that is supplied with your product. Individual workstations can then beconfigured to obtain a license from the license server.

A license can be one of the following:

Network (floating)license

This is checked out from the server each time your product application starts and ischecked back in when the application closes.

Perpetual license This is downloaded once from the server, stored on the local machine, and ischecked out locally each time the product application starts.

Uninstalling a product that uses Sentinel RMSUninstalling a Micro Focus product that uses Sentinel RMS does not revoke any license that is activatedfor that product, nor does it uninstall the license server. We recommend that before you uninstall the MicroFocus product, you revoke the licenses that have been activated for it.


Caution: If you are using a timed license (for example, a 30 day trial license), do not change themachine’s date and time. If you do, the license is invalidated and you must contact Micro FocusSupportLine.

If you need to change the machine’s date and time, ensure that you have installed a full license that isnot time limited.

Managing licensesTo manage product licenses, you use the Micro Focus Licensing System Administration tool. The toolallows you to authorize, view, and revoke licenses. During product installation, you can either select a triallicense or request a license from a license server.

The trial license is installed on your machine by the product installation program. Otherwise, to request alicense from a license server, you must specify the license server’s IP address when you install theproduct.

The trial license is limited to 30 days. During this period, if you have not already authorized your productwith your authorization code, a dialog box appears when the product starts. The dialog box shows thenumber of days left on the trial license. You cannot use your product if, at the end of the trial license period,you have not provided an authorization code. See Licensing a product using a central license server.

Licensing tasksThis section describes typical licensing tasks with which you should be familiar.

Some tasks require an internet connection. For example, when you authorize a product, a connection ismade to a license server which verifies the authorization code and returns a license code string. Similarly,the revoke license process uses a license server to revoke the existing license, then provide a newauthorization code. Where a task requires an internet connection, a note is provided.

Authorizing a product using a local license serverThe following procedure describes how to authorize a product using a license server that is set up on alocal machine. The license server is set up automatically when you first install a product.

Note: An internet connection is required.

1. Start the Licensing System Administration tool. To do this, select:

Start > All Programs > Micro Focus License Manager > > License Management System

The Micro Focus Licensing System Administration window appears.

2. Select Options > Advanced Configuration.

The Advanced Configuration window appears.

3. Click Change next to Authorization server URL.

The Set Authorization Server URL dialog box appears.

4. In the New Value field, type the valid URL obtained from Micro Focus SupportLine.

5. Click Save.

6. Close the Advanced Configuration window.

7. Click the Authorize tab.

8. Type the authorization code in the Authorization Code field.

9. Click Authorize.

Note: If authorization fails, you can authorize the product manually.


Authorizing a product manuallyManual authorization is required if your machine does not have an internet connection or if normal(automatic) authorization failed. Where normal authorization fails, the appropriate page is displayedautomatically. Alternatively:




2. Select Options > Manual Authorization.

The Authorize page is displayed.

3. Do one of the following:

• If the machine has an internet connection, click the HTTP link on the Authorize page.• If the machine does not have an internet connection, paste the HTTP link into a Web browser on a

machine that has an internet connection.

The Micro Focus SupportLine Manual product authorization Web page is displayed.


The authorization code is a 16-character alphanumeric string. Depending on how you obtained yourproduct the code is one of the following:

• Printed on a colored card marked Authorization Code that is provided with the product packaging.• Provided in an accompanying e-mail if the product was obtained by electronic download.

5. Type the machine ID in the Machine ID field.

The machine ID string is displayed on the Authorize page.

6. Click Generate.

7. Copy the generated license string and paste it into the License string(s) field on the Authorize page.

8. Click Install Licenses.

Setting up a central license server and loading licensesA license server is installed automatically when you install a Micro Focus product. You can use any licenseserver installation as your central license server without any additional configuration, provided theauthorization server URL you specified is valid. See Authorizing a product using a local license server.


After you have installed the product:






3. Click Change next to Authorization server URL.

The Set Authorization Server URL dialog box appears.

4. In the New Value field, type the valid URL obtained from Micro Focus SupportLine.

5. Click Save.



7. Click the Authorize tab.


The authorization code is a 16-character alphanumeric string. Depending on how you obtained yourproduct the code is one of the following:

• Printed on a colored card marked Authorization Code that is provided with the product packaging.• Provided in an accompanying e-mail if the product was obtained by electronic download.

9. Click Authorize.

Caution: If you change the name of the dedicated machine running your license server after it hasgranted licenses, it stops working.

Licensing a product using a central license serverThis section describes how to license a workstation product if you want to obtain a license from a centrallicense server.

You need the IP address or server name for the central license server you want to access.






3. Click Change next to License server.

The Set License Server dialog box appears.

4. In the New value field, type the IP address or server name for the license server.

5. Click Save.


7. Click File > Exit.

We recommend that other options in the Advanced Configuration window are modified only underguidance from Micro Focus SupportLine.

Using the command line

You can also run the following command to license a product:

%commonprogramfiles%\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\CesCmdAdminTool –server <License_Server_Name_or_Address>

Viewing installed licenses




2. Click the Licenses tab.

The installed licenses are shown on the Licenses page.

Revoking licenses on a central license serverThere are only two scenarios when you would want to revoke a license:

• The license server is going to be replaced.


• A license has not been taken to a client machine from the central license server.





2. Click the Revoke tab.

3. Select the product license you want to revoke.

4. Click Revoke.

After a check is made to ensure no licensed products are running, the Revoke Product Licensesdialog box is displayed.

5. Specify the number of licenses you want to revoke.

6. Click Revoke.

A new authorization code for each revoked license is generated and saved to a file on your computer.The file location and the new codes are displayed on the screen.

Ensure that you keep the new authorization codes in a safe place. You need them to re-authorize products.

Note: If there is a problem accessing the Micro Focus License Authorization Server and the revokefails, the Revoke Product Licenses dialog box enables options to allow manual revocation. At thispoint, your licenses are revoked and cannot be used. To obtain an authorization code, you must sendthe License Revocation Tickets (LRTs) to Micro Focus, either by pasting them into the revoke Webpage or by sending the indicated file to your SupportLine representative.

Revoking licenses manuallyThe manual revocation process should be followed when automatic revocation fails. If automatic revocationfails, the Revoke Product Licenses dialog box displays options for manual revocation.

1. Copy the whole character string displayed in the text box at the bottom of the Revoke ProductLicenses dialog box.

This string contains the Sentinel RMS License Revoke Tickets that are required to issue a newauthorization code.

2. Click the HTTP link.

The link opens the Micro Focus SafeNet License Revocation Web page.

3. Paste the copied string in the text box, then click Generate.

The new authorization code is displayed.

Ensure you keep the new authorization codes in a safe place. You need them to re-authorize products.

Using e-mail:

1. Copy the whole character string displayed in the text box at the bottom of the Revoke Product Licensesdialog box.

2. Paste the string into an e-mail and send it to your SupportLine representative.

The installation processInstallation can be as simple as following the installation wizard on a single desktop, or as flexible as"push" and "pull" delivery options with transforms.


To modify the basic installer process, you must have a competent grasp of how to create transforms, andan authoring tool to do so, and/or are familiar with command line options.

You should already know what kind of installation you need and should already have gathered theinformation required. If not, see Things to consider before installation.

Default path of user profileRegardless of the installation type, the default path for the user profile and configuration folders is:

• Windows XP:

C:\Documents and Settings\<UserLogon Name>\Application Data\Micro Focus\Rumba

• Vista and Windows 7:

C:\Users\<UserLogon Name>\AppData\Local\Micro Focus\Rumba

If OnWeb Web-to-Host is installed on the same computer, you cannot change the destination or userprofile folder location as many files are shared by both products.

Using the Setup wizardThe first, and simplest, installation method is to use the Rumba Setup wizard. During this installation, youare asked to select a Complete or Custom installation. Complete is the default.

The Setup wizard:

• Transparently installs the Windows Installer if it is not present on your system• Transparently installs the RSS Client (for increased security) if it is not present on your system• Checks that there is sufficient disk space on your destination drive• Allows you to choose the product language (English, German, or French)• Advises you of any Rumba prerequisites that are not currently installed on your computer (Micro Focus

License Manager and/or .NET 3.5 SP1)

Standalone installationTo install on a standalone workstation using the Rumba .msi file:

1. Double-click the Rumba .msi file.2. Follow the instructions in the Setup wizard.3. Enter the license information.

When you run a silent installation for the English version, use the following command lines:

• Evaluation:

msiexec /i Rumba_english.msi /qn

• Use a License Server Name or Address:

msiexec /i Rumba_english.msiLICENSE_SERVER=<License_Server_Name_or_Address> /qn

where <License_Server_Name_or_Address> is the name or IP address of the remote machinerunning Micro Focus License Manager and where the Rumba license is installed.

Use the corresponding Rumba_french.msi and Rumba_german.msi files for the French andGerman versions.

4. Review the Rumba license agreement, then select I accept the terms in the license agreement toproceed.

5. Choose a directory for Rumba to be installed to. Micro Focus recommend that you use the default of C:\Program Files\Micro Focus\Rumba. You can also choose the location for application data files:


a. Windows Default Folders: The default location where Windows saves application data.b. Specify Private Folders: This allows you to set custom locations in which user profiles and

interface configurations are stored.6. Select the installation type: Complete or Custom.

• Complete: Installs all Rumba components. This option requires the most disk space.• Custom: This option has the same default items selected as the Complete option, but allows you to

add or remove individual components. The Feature Description panel to the right of the componentselection box shows the amount of disk space required for each feature.

Setup creates a Micro Focus Rumba directory in your Windows Start menu from which you can access allthe Rumba products and related tools that you have installed.

Note: The items that Rumba adds to the Start menu have changed since previous releases. Inparticular, the display and printer items for different hosts are now all accessed from the single MicroFocus Rumba Desktop 8.3 option.

To install on a standalone workstation using the Rumba .exe file:

1. Double-click the RUMBA.exe file.2. Follow the instructions in the Setup wizard.3. Enter the license information.

Use the following command lines:

• Evaluation:

RUMBA.exe /s /v" /qn"

• Use a License Server Name or Address:

RUMBA.exe /s /v" /qn LICENSE_SERVER=<License_Server_Name_or_Address>"

where <License_Server_Name_or_Address> is the name or IP address of the remote machinerunning Micro Focus License Manager and where the Rumba license is installed.

4. Continue with Step 4 above.

To uninstall Rumba using the Rumba .exe file, use the following command line:

RUMBA.exe /x /s /v" /qn"

Administrative installationTo install Rumba as an administrative installation, use the following command:

msiexec /a drive:\Rumba_English.msi [TARGETDIR=<Path> [/q[b]]]

Using transformsYou can perform a run-from-source (RFS) installation using transforms. This means that only a very smallsubset of files is installed on the user workstation. The bulk of the product is run directly from a centrallocation, such as a shared network drive. This approach minimizes local computer disk requirements butincreases network load.

This type of installation is done in two stages:

• Stage 1 – Server installation that prepares files for use in the workstation installation.• Stage 2 – Workstation installation.

The following procedure describes how to install the English version of Rumba. For other languages, usethe appropriate language version of the files.

Stage 1 – Server installation


1. Select the location for the installation (RFS directory). This is usually a shared directory on a networkdrive.

2. To protect the installation files, either specify read-only access to the directory for all users, orindividually change the file attributes of all the installed files to read-only.

3. To create an administrative installation, use the following command:

msiexec /a Rumba_English.msi

and specify the RFS directory as destination directory.4. Create a transform file (.mst) using your preferred tool and copy it to the RFS directory.

Stage 2 – Workstation installation

1. Run the following command from the RFS directory:

msiexec /i Rumba_English.msi TRANSFORMS=<transform>.mst

Note: Install on Demand is not supported when performing an RFS installation.

Rolling back an installationWhen you are installing Rumba in any configuration using the Setup wizard, the installation process cancompletely roll back. That is, it undoes every operation that it performs during an installation, modification,repair, or removal. This is particularly helpful if you encounter a fatal error during an installer session. Thecomputer can return to the precise state it was in before the installer session. This includes restoration ofdeleted or overwritten files, registry keys, and other resources.

Note: You cannot roll back a completed Rumba installation. You must uninstall the program toremove it.

Roll-back disk space requirements

The disk space for installing a specific feature can be twice the size of the net disk space consumption.Files that are deleted or overwritten during the course of an installation or removal are temporarily saved toa backup location so that they can be restored if necessary. After a successful installation, or installeroperation, all temporary backup files are deleted.

Modifying RumbaTo modify a Rumba installation:

1. Select Control Panel > Add/Remove Programs > Change.

The Rumba Setup wizard starts.

2. Click Next.

The Program Maintenance window appears.

3. Click Modify.

The Custom Setup window appears.

4. Make the changes you want.

Repairing RumbaTo repair a Rumba installation:

1. Select Control Panel > Add/Remove Programs > Change.

2. Click Next.

The Program Maintenance window appears.


3. Click Repair.

4. Follow the instructions in the wizard.

The Repair option can:

• Determine whether the requested components and feature are installed. If a component or feature arenot installed, the installer checks for missing files and installs them.

• Check that all components in the requested feature are properly installed. The installer verifies thekeypath of a given component to determine if that component is broken. If the keypath resource ismissing, the installer performs an on-demand repair.

Removing RumbaTo remove a Rumba installation, select Control Panel > Add/Remove Programs > Change.

Ensure that the Rumba installation folder (normally C:\Program Files\Micro Focus\Rumba) wasdeleted during removal. If not, it is safe to delete it manually.

Notes:

• OnWeb Web-to-Host uses some of the same files as Rumba. If you also have OnWeb Web-to-Host installed on your computer, the Rumba directory is not removed and should not be deletedmanually.

• If you have other Micro Focus products installed on your computer, RSS Client files are notremoved during the uninstall process. Removing them could cause another Micro Focus product tostop functioning.

Customizing SetupThis section contains information to help you customize your Rumba installation for individual, group, andenterprise-wide distributions:

The Custom option of the Rumba Setup wizard allows you to select the features you want to install. Thewizard is self-explanatory and easy to understand.

You can either create transforms (.mst files) to modify the Rumba installation or use Windows Installercommand line arguments.

For information about deploying Rumba information with SCCM, see Distributing Rumba with SCCM.

There are several ways to specify custom changes to the standard operations and behavior of the Setupprogram. Each of these methods affects a different aspect of the installation process. By combining them,you can effectively distribute Rumba to make full use of Intellimirror features as well as SCCMmanagement capabilities.

TransformsA transform modifies the base installation package file at installation time. The transform remains cachedon the computer and is applied to the base installation package whenever the Windows Installer serviceperforms a configuration change (including repair) on Rumba.

Transforms increase the flexibility of Rumba installations by applying changes to the installation databasewithout altering the original database. For example, in organizations where different departments requiredifferent installations of Rumba, Rumba's base package can be made available to everyone at oneadministrative installation point, with the appropriate customizing transforms separately distributed to eachgroup of users.

Transforms cannot be applied to an already installed application, only at initial installation.


You should be proficient at using a transform authoring tool to make full use of a Rumba distribution onWindows 2000/XP and above.

For more information, refer to http://www.microfocus.com/docs/links.asp?nx=win_inst_trans.

Caution: We recommend that you use transforms carefully because they expose a great deal offunctionality and detail. Because each installation customized by a transform is unique, Micro Focusmight not be able to support customers using such installations.

Windows Installer command line argumentsThe following information is available in more detail from the Windows Installer SDK. The most commonoptions and parameters are presented here to enable you to easily organize and customize yourdeployment options.

Option Parameters Definition

/i {package|ProductCode} Installs or configures a product. For example:

msiexec /i A:\rumba.msi

/a package Administrative installation option.

/f [p][o][e][d][c][a][u][m][s][v]{package|ProductCode} Repairs a product. This option ignores any propertyvalues entered on the command line.

p Reinstall only if file is missing.

o Reinstall if file is missing or if an olderversion is installed.

e Reinstall if file is missing or an equal or olderversion is installed.

d Reinstall if file is missing or a differentversion is installed.

c Reinstall if file is missing or the storedchecksum does not match the calculatedvalue.

a Force all files to be reinstalled.

u Rewrite all required user-specific registryentries.

m Rewrite all required computer-specificregistry entries.

s Overwrite all existing shortcuts.

v Run from source and recache the localpackage.

For example, repair an installation with thefollowing command:

msiexec /fpecms rumba.msi

/x {package|ProductCode} x Uninstalls a product.

For example:

msiexec /x rumba.msi

/L [i][w][e][a][r][u][c][m][p][v][+][!]logfile Specifies the path to the log file. The following flagsare:

i Status messages


http://www.microfocus.com/docs/links.asp?nx=win_inst_trans

Option Parameters Definition

w Non-fatal warnings

e All error messages

a Startup of actions

r Action-specific records

u User requests

c Initial user interface parameters

m Out-of-memory

p Terminal properties

v Verbose output

/p PatchPackage Applies a patch. To apply a patch to an installedadministrative image you must combine options asfollows:

/p PatchPackage

/a package

/q {n | b | r | f} In conjunction with /i (install) or /x (uninstall), setsthe user interface level.

qn No user interface.

qb Basic user interface.

qr Reduced user interface with modal dialogbox displayed at the end of installation.

qf Full user interface with modal dialog boxdisplayed at end of installation.

qn+ No user interface except for modal dialogbox displayed at end of installation.

qb+ Basic user interface with modal dialog boxdisplayed at end of installation.

qb- Basic user interface with no modal dialogboxes.

Note: /qb+- is not a supported userinterface level. The modal dialog box doesnot display if the user cancels theinstallation.

The following command displays the basic userinterface options during package installation:

msiexec rumba.msi /qb

Distributing Rumba with SCCMThe mechanics of Microsoft System Center Configuration Manager (SCCM) administration are beyond thescope of this document. It is assumed that you are familiar with the standard operations of the SCCMfamily.

Note: SCCM was previously known as Systems Management Server (SMS).


Uninstalling previous versions of RumbaBefore you can deploy this version of Rumba, you must uninstall any previous versions of Rumba that arecurrently installed.

The easiest way to uninstall Rumba varies according to the version of SCCM you have installed. In someversions of SCCM the easiest way to uninstall previous versions of Rumba is to include a response file(response.ini) or definition file (.pdf) in a command line as part of an uninstallation deploymentpackage. In this case, if you do not have the previous-version documentation and the .pdf or responsefile (or files) of your previous Rumba installation, you must create a new response file.

In other versions of SCCM, the easiest method is to create a task sequence to run the uninstallation. Referto the documentation for your SCCM version.

Preparing client computers for Windows InstallerAfter you have uninstalled a previous Rumba version, ensure that Windows Installer is resident on clientcomputers before installing the current version of Rumba. If Windows Installer is not installed, you mustinstall it.

Installing Windows Installer requires administrative rights on client computers. To install Windows Installer,use the installer setup program, InstMSI.exe.

Note: Command line options are case sensitive.

You can also create a program dependency in an SCCM deployment package which installs the MicrosoftInstaller service immediately prior to a Rumba installation, on an on-demand basis.

You can download the Microsoft Installer SDK from: http://www.microfocus.com/docs/links.asp?nx=platsdk

Creating a Rumba deployment packageBefore creating a Rumba deployment package, consider:

• Source and distribution points.• Will this be an on-demand installation?• How your collections should be configured.• Whether clients have the correct rights, or whether to configure package access accounts.• Will you configure the user interface to be used by the clients?

You can use the SCCM New Package wizard to create a deployment package.

Identifying a package source directoryThe directory where you install an administrative installation becomes the package source directory. Anyadditional files, such as Rumba profiles or transforms, must also be copied to this location. The results ofthe administrative installation, plus any modifications you make, are propagated to the specified distributionpoint servers. SCCM clients can then install the package from the distribution point servers.

Advanced deployment issues• System restarts

Because Rumba determines if a computer must be restarted at installation time, the safest option is toconfigure SCCM to perform the restart.

• Program removal


http://www.microfocus.com/docs/links.asp?nx=platsdk

Rumba is registered in Control Panel > Add/Remove Programs. This allows SCCM to remove theapplication automatically.

For more informarion, refer to http://www.microfocus.com/docs/links.asp?nx=sms

Rumba file locations for Windows XP

Preinstalled files

DEFAULT.MNC C:\Documents and Settings\All Users\Application Data\Micro Focus\Rumba

SmpleAS4.rmc Program Files\Micro Focus\Rumba\AS400\Macro

smplehp.rmc Program Files\Micro Focus\Rumba\Hp\Macro

smpletso.rmc Program Files\Micro Focus\Rumba\MFrame\Macro

smpleVM.rmc Program Files\Micro Focus\Rumba\MFrame\Macro

smplevt.rmc Program Files\Micro Focus\Rumba\Vt\Macro

Run-created files

Default.mnc C:\Documents and Settings\<USER>\Application Data\MicroFocus\Rumba

CONFIG.EHN C:\Documents and Settings\<USER>\Application Data\MicroFocus\Rumba

WDEvtLog.log C:\Documents and Settings\All Users\Application Data\Micro Focus\Rumba

WDSNA.CFG C:\Documents and Settings\All Users\Application Data\Micro Focus\Rumba

wdteldn.cfg C:\Documents and Settings\<USER>\Application Data\MicroFocus\Rumba

wdtelnl.cfg C:\Documents and Settings\<USER>\Application Data\MicroFocus\Rumba

Macros

.rmc C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\as400\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\HP\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\VT\Macro

User toolbars

The user toolbars that were used in previous releases are now saved within individual Session Profiles andcannot be shared.


http://www.microfocus.com/docs/links.asp?nx=sms

Default session profiles

.prf C:\Documents and Settings\<USER>\Application Data\MicroFocus\Rumba\Defaults

User session profiles

.rpdm C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame

.rsda C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\as400

.rspa C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\as400

.rsdh C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\HP

.rsdm C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame

.rspm C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame

.rsdu C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\VT

Desktop profiles

.rdps C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba

Print preview

.rpf C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba

Keyboard map

.map C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\AS400

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\HP

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\VT

Transferred files

? C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\AS400


C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\HP

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\MFrame

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\VT

Hotspots library

.hsp C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\as400\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\HP\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\\MFrame\Macro

C:\Documents and Settings\<USER>\Local Settings\Application Data\Micro Focus\Rumba\VT\Macro

Help files

.chm English C:\Program Files\Micro Focus\Rumba\Help\MRI2924

and

C:\Program Files\Micro Focus\Rumba\HelpRibbon\MRI2924

French C:\Program Files\Micro Focus\Rumba\Help\MRI2928

and


German C:\Program Files\Micro Focus\Rumba\Help\MRI2929

and


Font mapping file

.lcs C:\Documents and Settings\All Users\Application Data\Micro Focus\Rumba

Rumba file locations for Vista and Windows 7

Preinstalled files

default.mnc C:\ProgramData\Micro Focus\Rumba

SmpleAs4.rmc C:\Program Files\Micro Focus\Rumba\As400\Macro


SmpleHP.rmc C:\Program Files\Micro Focus\Rumba\Hp\Macro

SmpleTSO.rmc C:\Program Files\Micro Focus\Rumba\Mframe\Macro

SmpleVM.rmc C:\Program Files\Micro Focus\Rumba\Mframe\Macro

SmpleVT.rmc C:\Program Files\Micro Focus\Rumba\Vt\Macro

Run-created files

default.mnc C:\Users\<USER>\AppData\Roaming\Micro Focus\Rumba

config.ehn C:\Users\<USER>\AppData\Roaming\Micro Focus\Rumba

RumbaTRC.CFG C:\Users\<USER>\AppData\Roaming\Micro Focus\Rumba

Macros

.rmc C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\AS400\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\HP\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\MFrame\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\VT\Macro

User toolbars

The user toolbars that were used in previous releases are now saved within individual Session Profiles andcannot be shared.

Default session profiles

.prf C:\Users\<USER>\AppData\Roaming\\Micro Focus\Rumba\Defaults

User session profiles

.rpdm C:\Users\<USER>\AppData \Local Settings \Application Data\Micro Focus\Rumba\MFrame

.rsda C:\Users\<USER>\AppData \Local\Micro Focus\Rumba\as400

.rsdh C:\Users\<USER>\AppData \Local\Micro Focus\Rumba \H

.rsdm C:\Users\<USER>\AppData \Local\Micro Focus\Rumba\MFrame

.rspa C:\Users\<USER>\AppData \Local\Micro Focus\Rumba\as400

.rspm C:\Users\<USER>\AppData \Local\Micro Focus\Rumba\MFrame

.rsdu C:\Users\<USER>\AppData \Local\Micro Focus\Rumba\VT

Desktop profiles

.rdps C:\Users\<USER>\AppData \Local\Micro Focus\Rumba


Print preview

.rpf C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\AS400

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\HP

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\MFrame

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\VT

Keyboard map

.map C:\Users\<USER>\AppData\Local\Micro Focus\Rumba

Transferred files

? C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\AS400

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\HP

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\MFrame

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\VT

Hotspots library

.hsp C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\AS400\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\HP\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\MFrame\Macro

C:\Users\<USER>\AppData\Local\Micro Focus\Rumba\VT\Macro

Help files

.chm English C:\Program Files\Micro Focus\Rumba\Help\MRI2924

and


French C:\Program Files\Micro Focus\Rumba\Help\MRI2928

and


German C:\Program Files\Micro Focus\Rumba\Help\MRI2929

and


Font mapping file

.lcs C:\ProgramData\Micro Focus\Rumba


Using RumbaThis section describes how to some of the main features of Rumba.

Rumba foldersYou can access Rumba programs from Start > Programs > Micro Focus Rumba . This includes theRumba Tools folder. Exactly what programs are available depends on which components you installed.

The Rumba Tools folder contains tools for system administrators, such as:

• Micro Focus Rumba 8.3 APPC Configuration• Micro Focus Rumba 8.3 AS400 Communications• Micro Focus Rumba 8.3 Comunication Monitor• Micro Focus Rumba 8.3 Engine• Micro Focus Rumba 8.3 Submit Remote Command• Micro Focus Rumba 8.3 Trace

Using Rumba menus, toolbars, and the status barYou can use Rumba commands, from either the classic or the ribbon interface, to perform most of yourhost tasks. The status bar provides you with information about Rumba and the state of the host.

You can streamline your work environment by customizing Rumba menus and the toolbar. For example,you can add icons to launch external applications, or remove menu commands and toolbar buttons thatyou do not use. Currently, this facility is only available for the classic interface.

Customizing menus and toolbarsTo customize commands available within a profile:

1. Open the Rumba display or printer session containing the menus that you want to change.

2. Select View > Toolbars. The Customize dialog box opens.

3. On the Toolbars page, create and rearrange custom toolbars with the commands you use most often.

Use the Commands page to add commands to the standard toolbar or to change the availability ofcommands within the interface.

Note: If you make the View > Toolbars command unavailable, you cannot make further changes.

4. On the Commands page, select Rearrange Commands > Modify Selection > New Button to createnew toolbar buttons of different types.

Toolbars can be docked, undocked, and floated. They can also be imported from and exported to files.Toolbar buttons can be chosen from several types.

Mainframe status barStatus bar area Function

Status field Displays general Rumba status information.

46 | Using Rumba

Status bar area Function

Operator Indicates the operator's application session owns the screen.

SSL Indicates whether your session uses an SSL (Secure Sockets Layer) connection. Thisfield applies only to TCP/IP connections.

APL Indicates whether or not the host is in APL mode.

NUMFLD Indicates whether or not the cursor is currently in a numeric field.

LU# Shows the Logical Unit (LU) number.

OVR Indicates whether Overstrike or Insert mode is chosen.

CAP Indicates whether Caps Lock is on or off.

NUM Indicates whether the Number Lock is on or off.

W Indicates whether Word Wrap is on or off.

Cursor coordinates Lists the row and column position of the cursor.

Clock Displays the time.

AS/400 status barStatus bar area Function

Description area • Connected: The status of the host connection. If the host is not connected, thedescription area is blank.

• Toolbar button function: If the mouse cursor points to a toolbar button, thedescription area displays a description of the function performed by the toolbarbutton.

• Menu command function: If the context-sensitive help cursor points to a menucommand, the description area displays a description of the function performed bythe menu command.

SA System available. When lit, this indicates that the host is operating and available to thePC.

MW Message waiting. When lit, the host has one or more messages waiting for you.

KS Keyboard shift. When lit, the keyboard is in shift mode.

IM Insert mode. When lit, Insert is on. Characters can be inserted into a field withouttyping over the existing data.

II Input inhibited. When lit, keyboard input is not being accepted by the AS/400. Trypressing the Error Reset key. If it is still highlighted, the system is processing yourrequest.

KB Keyboard buffer. This indicator is only displayed when you are waiting for the InputInhibited indicator to go off so that keystrokes that are buffered can be processed. Toclear keystroke buffering, press the Error Rest key.

Session Name Displays the name of the server to which the Rumba session is connected.



HP status barStatus bar area Function

Communications interface Displays the communications interface you have selected, the server name (ifapplicable), and whether or not the session is connected to the host.

Using Rumba | 47

Status bar area Function

Terminal type Shows the type of terminal this session is emulating, and other kinds of statusinformation applicable to the terminal. Information appears if the terminal is in hold orwait conditions or if it is off-line.



UNIX status barStatus bar area Function

Communications interface Displays the communications interface you have selected, the server name (ifapplicable), and indicates whether the session is connected to the host.

Terminal type Shows the type of VT this session is emulating, and other types of status informationapplicable to the terminal. Information appears if the terminal is in hold or waitconditions, is off-line, or if you are composing a character sequence.

Cursor coordinates Lists the row and column position of the cursor. If you are using VT420 emulation, italso indicates the page number.

Numeric/ Application mode Toggles the state of the terminal's numeric keypad between numeric mode andapplication mode (which is not the same as the PC NUMLOCK feature).


Rumba Session ProfilesA Session Profile is a special configuration file used to store your settings for a specific session. You cancustomize the settings for a particular host connection to meet your particular needs and preferences, thensave your settings in a Session Profile. When you open the profile, the Rumba session is configured withsettings you designate.

Session Profiles also provide a method for easily deploying standardized Rumba sessions to users. Youcan create Session Profiles for customized host display and printer sessions.

All Session Profiles are stored in a subfolder of the Application Data or AppData folder. For example,an AS/400 profile would be stored at:

• Windows XP:

C:\Documents and Settings\<user>\Local Settings\Application Data\Micro Focus\Rumba\as400

• Windows Vista:

C:\Users\<user>\AppData\Local\Micro Focus\Rumba\AS400

• Windows 7:

C:\Users\<user>\AppData\Local\Micro Focus\Rumba\AS400

The subfolders are named as400, HP, Mframe, and VT (for UNIX host session profiles).

Note: Each Session Profile opens as a separate tab in the Rumba display. This gives you theflexibility of being able to open several different profiles in one window. You can save multiplesessions in one configuration file as a Desktop Profile.

About Session ProfilesSession Profiles contain specific information about the Rumba session including:

48 | Using Rumba

• Interface selection and configuration• Display settings, including color, font and status bar options• Keyboard maps and alternative character set selection• Macros and script information (if the Script Editor is installed)

When you change your Rumba environment, you can save those changes in a new or existing profile.Rumba stores Session Profile data in a binary format.

Session Profiles are host-specific. The file extension for the different hosts are as follows:

Host File extension

AS/400 .rsda

AS/400 Printer .rspa

HP .rsdh

Mainframe .rsdm

Mainframe Printer .rspm

UNIX .rsdu

Note: You can use the Profile Editor to create and edit Rumba profiles. The Profile Editor is an OLEcontrol that you can load into your Visual Basic application. To install the editor, you must run acomplete installation, or run a custom installation, then select System Options > AdministratorOptions > Profile Editor Control.

Supplemental and interface configuration filesThere are also supplemental files that work together with Session Profiles. These supplemental filescontain configuration or other important data unique to a feature. For example, the hotspot.hsp file is asupplemental file. It is also a Hotspot file, and it contains all the data required to run a series of predefinedkeystrokes.

Interface configuration files are a special class of supplemental files. They are saved in separate files withthe .cfg extension. You may have more than one of these interface files if you use multiple hostconnections.

For details on the locations of these files, see Installing Rumba.

The supplemental files and their default extensions are:

File type Extension

Interface configuration .cfg

Keyboard map .map

Macro script .rmc

Hotspot .hsp

Menu configuration .mnc

Script .csf and .vba

Toolbar .rtbr

Migrating Session Profiles from Rumba 6.x or 7.xSession Profiles that were created using Rumba versions 6.x or 7.x can be migrated to Rumba 8.3. To dothis:

1. Open the profile in Rumba in 6.x or 7.x.

Using Rumba | 49

2. Click Tools > Menu , then click the Preview tab.

3. Ensure that the Gray disabled items option is selected.

4. Save the profile.

5. Upgrade to Rumba 8.3.

Rumba Desktop ProfilesA set of multiple Session Profiles can be saved as a single Rumba Desktop Profile. This allows you toprovide a standard set of tabbed sessions to your users, minimizing the amount of configuration needed foreach individual user.

By default, Rumba Desktops are stored with the file extension .rdps in the following folder:

Windows XP:

C:\Documents and Settings\<user>\Local Settings\Application Data\Micro Focus\Rumba

Windows Vista and Windows 7:

C:\Users\<user>\AppData\Local\Micro Focus\Rumba

About Desktop ProfilesDesktop Profiles contain specific information about a Rumba instance, including:

• The set of Session Profiles used and their layout• Any customized tab names• Any vertical and horizontal tab groups

A Desktop Profile does not contain any information about which Rumba interface is used. All DesktopProfiles may be opened in either the Classic or the Ribbon interface.

Session Profile locationsA Rumba Desktop Profile contains references to the locations of all the Session Profiles that it includes.The locations of any Session Profiles that are in a different folder to the Desktop Profile are stored asabsolute paths. If a Desktop Profile is to be deployed on machines other than the one on which it wassaved, all of the relevant Session Profiles should be contained within the same folder as the DesktopProfile.

HP keyboard key codesThe HP keyboard sends a predefined escape sequence for each of its special keys. For example, editingkeys and numeric keys. Most applications written for use with HP terminals expect to use these escapesequences. If your application is looking for a different escape sequence, you can program this sequenceto a keyboard string, and map that keyboard string to a key sequence on your PC.

The tables in this section list the codes sent for each of the defined keyboard keys.

Keys mapped to active default settingsLegend Key

Line modify F1

50 | Using Rumba

Legend Key

Modify all F2

Block mode F3

Remote mode F4

Type ahead F5

Memory lock F6

Display function F7

Auto line feed F8

F1 through F8 are local function keys that do not send codes, except when configured to do so. Thesekeys are mapped to activate default softkeys. To see the key mappings:

1. Select Options > SoftKeys in the HP Display.2. In the SoftKeys Settings dialog box, select User Defined.3. Click OK.

Keys used to send 7-bit control charactersControl character mnemonic ASCII value Key pressed with Ctrl (all modes)

SOH 1 A

STX 2 B

ETX 3 C

EOT 4 D

ENQ 5 E

ACK 6 F

BEL 7 G

BS 8 H

HT 9 I

LF 10 J

VT 11 K

FF 12 L

CR 13 M

SO 14 N

SI 15 O

DLE 16 P

DC1 17 Q (see note below)

DC2 18 R

DC3 19 S (see note below)

DC4 20 T

NAK 21 U

Using Rumba | 51

Control character mnemonic ASCII value Key pressed with Ctrl (all modes)

SYN 22 V

ETB 23 W

CAN 24 X

EM 25 Y

SUB 26 Z

Note: 7-bit control codes sent only when XON/OFF support is off.

Codes sent by editing keysKey Code sent

Delete char ESC P

Insert line ESC L

Delete line ESC M

Insert char ESC Q

Prev char ESC V

Next ESC U

Clear line ESC K

Clear display ESC J

To view these codes, select Tools > Show Host Keyboard in the HP Display.

These codes are only sent when Transmit Escape Sequences to Host is enabled. To do this:.

1. Select Options > Terminal2. On the Advanced tab, check Transmit Escape Sequences to Host.3. Click OK.

Codes sent by arrow keysKey Cursor mode Application mode

Up ESC A ESCA

Down ESC B ESCB

Right ESC C ESCC

Left ESC D ESCD

These codes are only sent when Transmit Escape Sequences to Host is enabled. To do this:.

1. Select Options > Terminal2. On the Advanced tab, check Transmit Escape Sequences to Host.3. Click OK.

52 | Using Rumba

Codes sent by numeric keypad keysKey Numeric Application

0 0 ESC Q Ins

1 1 ESC F End

2 2 ESC B Down

3 3 ESC U PgDn

4 4 ESC D Left

5 5

6 6 ESC C Right

7 7 ESC h Home

8 8 ESC A Up

9 9 ESC V Pg Up

- (minus)

, (comma)

. (period) ESC P Del

Enter CR LF

Note: In Character mode, the code goes directly to host. In Format/Block mode, the code goes to thehost only when the user presses ENTER.

VT keyboard key codesThe VT keyboard sends a predefined escape sequence for each of its special keys. For example, functionkeys, editing keys, and numeric keys. Most applications written for VT terminals expect to see theseescape sequences. If your application is looking for a different escape sequence, you can program thissequence to a keyboard string and map that keyboard string to a key sequence on your PC.

The tables in this section list the codes sent for each of the defined keyboard keys.

VT codes sent by top-row function keysTable 13: VT codes set by top-row function keys

Legend Key number Code sent

Hold F1 CSI 11~

Print F2 CSI 12~

Set-Up F3 CSI 13~

Session F4 CSI 14~

Break F5 CSI 15~

F6 F6 CSI 17~

F7 F7 CSI 18~

Using Rumba | 53

Legend Key number Code sent

F8 F8 CSI 19~

F9 F9 CSI 20~

F10 F10 CSI 21~

F11 (ESC) F11 CSI 23~

F12 (BS) F12 CSI 24~

F13 (LF) F13 CSI 25~

F14 F14 CSI 26~

Help F15 CSI 28~

Do F16 CSI 29~

F17 F17 CSI 31~

F18 F18 CSI 32~

F19 F19 CSI 33~

F20 F20 CSI 34~

F1 through F5 are local function keys that do not send codes, except when configured to send codes. Tosee the assigned local keys in the UNIX Display:

1. Options > Terminal.2. Click the Key Assignments tab.

VT keys used to send 7-bit control charactersControl character mnemonic ASCII Value Key pressed with Ctrl (all modes)

SOH 1 A

STX 2 B

ETX 3 C

EOT 4 D

ENQ 5 E

ACK 6 F

BEL 7 G

BS 8 H

HT 9 I

LF 10 J

VT 11 K

FF 12 L

CR 13 M

SO 14 N

SI 15 O

DLE 16 P

54 | Using Rumba

Control character mnemonic ASCII Value Key pressed with Ctrl (all modes)

DC1 17 Q (see note below)

DC2 18 R

DC3 19 S (see note below)

DC4 20 T

NAK 21 U

SUN 22 V

ETB 23 W

CAN 24 X

EM 25 Y

SUB 26 Z

Note: 7-bit control codes sent only when XON/OFF support is off.

VT codes sent by editing keysKey Code sent

Find CSI 1~

Insert here CSI 2~

Remove CSI 3~

Select CSI 4~

Prev CSI 5~

Next CSI 6~

VT codes sent by arrow keysKey Cursor mode Application mode

Up CSI A SS3A

Down CSI B SS3B

Right CSI C SS3C

Left CSI D SS3D

VT codes sent by numeric keypad keysNumeric keypad mode setting (DECNKM), ANSI mode.

Key Numeric Application

0 0 SS3 p

1 1 SS3 q

2 2 SS3 r

Using Rumba | 55

Key Numeric Application

3 3 SS3 s

4 4 SS3 t

5 5 SS3 u

6 6 SS3 v

7 7 SS3 w

8 8 SS3 x

9 9 SS3 y

- (minus) SS3 m

, (comma) SS3 l

. (period) SS3 n

ENTER CR or CR LF (see below) SS3 M

PF1 SS3 P SS3 P

PF2 SS3 Q SS3 Q

PF3 SS3 R SS3 R

PF4 SS3 S SS3 S

In keypad numeric mode, ENTER sends the same codes as RETURN. You can use line feed/new line mode(LNM) to change the code sent by RETURN. When LNM is reset, pressing RETURN sends one controlcharacter (CR). When LNM is set, pressing RETURN sends two control characters (CR, LF).

56 | Using Rumba

AS/400 Getting ConnectedThis section is intended to help you configure and maintain Rumba AS/400 Display and Printerconnections. To do this, you use the Rumba Connection Configuration dialog box.

Notes:

• To configure connections for features such as AS/400 file transfer and shared folders, use theAS/400 Communications tool. See Using the AS/400 Communications tool.

• To build a configuration file for the Rumba SNA engine, use the APPC Configuration tool. See Rumba APPC Configuration tool.

There is more to connecting to a host than just having the physical elements in place. When you useRumba AS/400 software, you create a specific relationship between the host link and the interface optionsyou configure.

The first time you make the host connection, you define these relationships following the steps outlinedbelow. Afterwards, Rumba uses your customized parameters to configure the new session environment foryou.

Connecting to the hostThe connection procedures described here provide an overview of the tasks you must complete toconfigure an AS/400 interface for the first time.

1. Start the AS/400 Communications tool. To do this, select Start > Programs > Micro Focus Rumba >Rumba Tools > Rumba AS400 Communications.

2. In the Rumba AS/400 Communications dialog box, click the Interface tab.3. In the Installed Interface box, select an interface.4. Click Configure, then configure the interface.

Use the four pages of the Rumba AS/400 Communications dialog box to:

• Configure your connection for different types of interfaces.• Set security options.• Support an array of character sets.• Display error messages for diagnostic purposes.

Starting the connection processTo start configuring an AS/400 host connection, open the AS/4000 Connection Configuration dialogbox. To do this, in an AS/400 Display, select Connection > Configure.

The General page is the main page. The name and number of additional pages that are displayed dependon which interface you choose.

The name of the interface currently selected on the General page appears on one tab (for example,Rumba Router) and, for all but the TN5250 and Demo Host interfaces, a Security tab is displayed aswell.

Procedures for configuring each interface are described in the online Help.

AS/400 Getting Connected | 57

The Demo hostThe Demo host lets you communicate with a simulated host through a series of PC-to-host conversationspreviously recorded with the Data Stream Analyzer (DSA) Trace system.

When you use this host, Rumba sends commands to a program emulating a host. The host programresponds with the corresponding 5250 data stream segments, based on your keyboard or mouse input.

The Demo host is especially useful for training purposes. You do not have to configure the host or thesession parameters to use the Demo host.

Important: These fields are initialized with defaults based on data from your current profile, ifavailable, or from system defaults. They are the recommended settings and should not be changedexcept for special circumstances. Selecting an inappropriate starting state could result in undesirablebehavior.

Selecting an interfaceWhen establishing a host connection, you need to determine which interface to use. By matching yournetwork topology with one of the examples below, you can start choosing the most appropriate interface.

58 | AS/400 Getting Connected

LAN Direct is used when the LAN is directly connected to a host. Examples of this connection type arelisted below:

• MPTN (SNA over TCP/IP) - a Rumba Router link type• TN5250• LAN gateway

Using a LAN gateway connection, the LAN is connected first to a gateway, usually for protocol conversion.IPX and NetBIOS are two examples of protocols that require gateways, because neither are native tonormal host environments. An example of this connection type is Microsoft SNA Server.

Configuring the interfaceAfter you have determined which interface best suits the needs or constraints of your connectionrequirements and network topology, you need to tell Rumba how to find your host and how your host canfind you (the client).

To do this, you use the Connection Configuration dialog box. The best initial approach is to leave thesettings of the majority of the fields used to specify client and host data at their default values.

The connection configuration parameters required depend on the interface you select. For Rumba Routerlink types, the Rumba Router page displays additional tabs for you to specify configuration values.

Successful connection indicatorWjhen the host connection is established, the status bar description area reads Connected.

When the cursor is moved around the screen, the description area shows the last command selected.


The status bar displays SA (system available) in the first status box to indicate that the AS/400 is ready torespond.

Other helpful featuresIn addition to the connection methods already discussed, Rumba has additional features designed to saveyou time, make the connection task easier, and help you understand the entire process better.

The administrator override file

A high priority for any system administrator is standardizing system configurations. When you create anadministrator override file, you provide a set of well-defined parameters that each user can access. Thistool can significantly reduce the time spent setting up and troubleshooting workstations.

An administrator override file is a configuration file you create, then place on the network. Users canaccess this file for connection information to SNA-type machines. If the connection information changes,you can use the administrator override feature to make one central change.

Using the Rumba Router to configure an APPC linkThe Rumba Router supports Advanced Peer to Peer Networking (APPN), and the Common ProgrammingInterface for Communications (CPI-C). Workstations using the Rumba Router can connect to AS/400s overa LAN or direct physical connection.

This section provides an overview of the procedures used to specify the settings for a host connectionusing the Rumba Router.

Overview of Rumba RouterUsing the Rumba Router provides you with support for a wider range of client-based applications andconnectivity types. By processing API commands on the client workstation, the Rumba Router takesadvantage of the benefits of distributed computing to enhance both the performance and flexibility of theapplications you use to interact with your AS/400 host.

There are common elements within both the Connection Configuration and Link Configuration dialogboxes, regardless of which Rumba Router link type you use to make a connection. Because of this,specifying settings does not vary on the Rumba Router and Security pages in the ConnectionConfiguration dialog box, nor on the AS/400 AS/400 Link and Advanced pages of the LinkConfiguration dialog box.

When you select the Rumba Router, the Connection Configuration dialog box displays the RumbaRouter and Security tabs in the second and third tab positions.

When you click the Rumba Router tab and add a new connection, you see the Link Configuration dialogbox. This has three pages:

• The first is always AS/400 Link.• The second one changes to the name of the link type that you select.• The third is always Advanced.

Connection Configuration dialog boxWorkstation users normally use the Connection Configuration dialog box to configure the connectionfrom an AS/400 display or printer session. This is instead of using:

• The Rumba APPC Configuration tool, which is more suited for creating configuration files for SNAinterfaces.


• The Rumba AS/400 Communications tool, which is used to configure host connections for Rumbaclient applications.

The installed interfaces that appear in the Connection Configuration dialog box include:

• The Demo host• Rumba Router• TN5250• Microsoft SNA Server (if the SNA client is installed)

Setting up the connectionSetting up connections with the Rumba Router generally involves three steps:

1. Configure the Rumba Router interface.2. Choose a link or connection type.3. Configure the link type.

Because the settings you can specify vary so widely depending on which link type you choose, each linktype is discussed. The Rumba Router and Security pages do not change for each link type. Theremainder of this section outlines what you can specify on these pages.

Rumba Router pageThe table below describes the parameters of the Rumba Router page in the Connection Configurationdialog box.


Parameter Description

AS/400 Information Use this group box to select or edit an existingconfiguration, or add a new configuration to the SystemName list. Configurations are not displayed in theSystem Name list until you have added them.

System Name Lists all the currently configured systems. Click the downarrow to select a system.

Set Default Designates the selected system as your defaultconnection, which will be used automatically unlessanother system is selected before connecting. TheDefault System is displayed in the System Name list withan asterisk (*).

Add Configures a new connection. The new connection will bedisplayed in the System Name list after you have addedit.

Remove Deletes a configured connection. If you delete the defaultsystem, you must select or configure a new systembefore connecting.

Properties Opens the Link Configuration dialog box for theselected connection. You can edit the availableparameters and save the changes to the configuration.

Session Information Use the controls in this group to specify how userinformation for this session is specified.

Auto sign-on When you check this box, your connection information isused for the host sign-on.

Device Name You can add an optional device name that will overridethe default device name used for this session.

In most cases, the device name defaults to your PCsystem name followed by S1 or P1. Instead of using thedefault, you can enter a device name which the AS/400uses to recognize this session.

PC Information Lists the information that is used when connecting yourPC with the AS/400.

PC Name Add the name you use to log on to your network. Thiscorresponds to the controller ID configured on the AS/400, and can be up to eight characters, including A-Z,0-9, @, #, and $.

Network Name Add the name of the network you are using to connect.For example, you may be using APPN.

On the AS/400, this corresponds to the local network ID,and can be up to eight characters, including A-Z, 0-9, @,#, and $. This identifies the AS/400 on the network.

You can find step-by-step procedures for configuring individual interfaces and link/connection types in theonline Help.

The interface Help files are a self-contained unit with information on requisite stacks, configurationprocedures, and troubleshooting information (including most error messages associated with an interface).When necessary, the Help also assists you in locating values for interface parameters defining the local PCand the remote host.


Security pageThe table below describes the parameters on the Security page of the Connection Configuration dialogbox.


Sign-on Features

Use Common Sign-on Uses the specified user ID and password as sign-oninformation for all systems.

AS/400 Sign-ons Lists the currently known AS/400 systems for which youhave configured security settings. You must add systemson the Interfaces page before you can configure securitysettings for them.

Add Sets up security for a new system.

Change Changes the security settings for the selected system.

Delete Deletes the security settings for the selected system.

Enable Caching of User IDs and Passwords Enables the storing of the user ID and password for thecurrently configured system until you reboot your PC. Ifyou check this option, you do not have to enter your userID and password for subsequent connections unless youreboot.

Rumba Router link typesTo configure an AS/400 Rumba Router link, you use the Link Configuration dialog box. To open thedialog box:

1. Select Connection > Configure. The Connection Configuration dialog box appears.2. In the Installed Interfaces list, select Rumber Router.3. On the Rumber Router page, select the system name from the drop-down list.4. Click Properties. The Link Configuration dialog box appears.


AS/400 Link page

The table below describes the parameters on the AS/400 Link page of the Link Configuration dialog box.


AS/400 Information

System Name Displays the alias for the AS/400. This name is added tothe list of configured connections on the Rumba Routerpage.

For example, if you connect to a computer calledS1001234, you could call the computer Bill instead ofS1001234. By default, this name is used as the LU Nameon the Advanced page, although you can change this atany time.

To change the System Name or other connectionparameters later, select it from the System page, thenclick Properties. If you are going through an adjacentnetwork node (system) via an APPN connection toanother system, enter the name of the target system.

Link Type Displays the link types you can use to connect. You mustselect a link type to complete the connectionconfiguration.

Your choice of link type depends on your hardware andsoftware configuration, as well as the type of connection



you need. If you do not know which link type to use,check with your system administrator.

Advanced tab

The table beow describes the parameters on the Advanced page of the Link Configuration dialog box.


LU Name Displays the name of the AS/400’s logical unit. This is notan alias. This is the actual name of the AS/400 and isused to make the connection. The LU Name correspondsto the System Name on the Rumba Router page. TheSystem Name, however, can be an alias, while the LUName is always the actual name of the AS/400.

This name can be up to eight characters, including A-Z,0-9, @, #, and $.

Network Name Identifies the network you are connecting over. TheNetwork Name corresponds to the local network ID onthe AS/400, and can be up to eight characters, includingA-Z, 0-9, @, #, and $.

This name is used to identify the AS/400 on the network.

Link typesThe table below describes types of link that the Rumba Router supports.


Link Type Function

APPN Connects to an AS/400 host by using an existing networkconnection as a node. For example, an APPN connectionbetween your PC and an AS/400 host can be used toaccess another AS/400 host that does not have a directphysical connection to your PC.

MPTN (SNA over TCP/IP) Connects to an AS/400 host using SNA or APPC tocommunicate over TCP/IP networks. The full capability ofthe Rumba APPC engine is used over an existing TCP/IPbackbone, linking client workstations to the host andproviding transparent access to functions such as AS/400printing and file transfer.

Native TCP supportRumba AS/400 software supports access via native TCP for a number of client applications. With theimplementation of this feature, Rumba provides support for the complete range of client applications.Companies moving to TCP/IP networking can still give their users access to key AS/400 applications whichare important for user productivity.

Rumba TCP architectureThe figure below shows the data flow from your workstation to your AS/400:

Rumba ’s Winsock support allows you to use your existing TCP/IP connection as the link between theAS/400 File Transfer tool or Submit Remote Command and your host.

Rumba AS/400 Display and AS/400 Printer also provide display and printer support directly over TCP/IP.


Supported Rumba componentsThe table below describes the functions performed by the Rumba components that use native TCP.

Component Function

Display

Rumba AS/400 Edition Display & TN5250 interface Presents the traditional AS/400 display terminal in aMicrosoft Windows application: the Rumba window.


Printing

Rumba AS/400 Printer Includes standard features such as AS/400 printerqueues, PC printer queues, and print log.

Note: Printing with TCP/IP is now available usingTN5250.

File Transfer

AS/400 File Transfer Transfers files or selected data between the AS/400 hostand your PC.

Configuring a TCP connectionThe procedure for configuring your host connection depends on which desktop application you use:

• If you plan to use Data Access, use the 32 bit ODBC program, in Windows Control Panel, to define andmanage a data source for the Rumba AS/400 Optimized Server ODBC driver. If you need to configure aRumba APPC connection, click Configure Rumba APPC.

• If you plan to use TN5250, use the Connection Configuration dialog box to configure a Rumba RouterTN5250 host link.

Trace support for TCP applicationsTo obtain trace data from your host connection, use the Rumba Trace tool.

For more information, see Rumba Trace tool.

Configuring an MPTN connectionThe options you can specify on the MPTN Configuration page of the Link Configuration dialog box varya great deal depending on which link type you use. This section discusses the options you specify toconfigure a host connection using the Rumba Router and an MPTN link type.

About MTPNIn this guide, the MPTN interface is described as a LAN direct connection type.

Multi-Protocol Transport Networking (MPTN) is an open architecture that allows integration of multiple-vendor and multiple-protocol environments.

The primary advantage of MPTN is that you can use either SNA or APPC to communicate over TCP/IPnetworks. This means that you can use the full capability of the Rumba APPC engine over your existingTCP/IP backbone. Effectively, this links your client workstation directly to the AS/400, providing transparentaccess to functionality, such as AS/400 printer and file transfer.


Rumba MPTN supports various APIs:

• EHNAPPC• CPIC• APPC

Various applications work with Rumba MPTN:

• Database applications• Printer configurations• AS/400 Display• AS/400 File Transfer

AS/400 considerationsBefore you can connect to an AS/400 using the MPTN interface, the AS/400 must be set up to use TCP/IP.For your AS/400 to communicate using TCP/IP, it must be running OS/400, Version 3.0, Release 1 (orlater).

Note: This is an absolute requirement. Earlier versions of the operating system do not allow you toproperly configure TCP/IP addresses for either your AS/400 or your client workstations.

MPTN parameters

The table below describes the parameters on the MPTN Configuration page of the Link Configurationdialog box.



TCP/IP Domain Name

Remote Host Name Type the remote host name or IP address you want toaccess.

Security

Use Host APPN Remote Location List When checked, the system name sent with yourconnection request is the Link Name/Remote LU Nameyou entered for this workstation. When unchecked, thesystem name sent with your connection request is MPTN.

You can use this security option when you configure aconnection to an AS/400 host that uses APPN RemoteLocation List security.

MPTN Options

KeepAlive Specifies whether host KeepAlive settings are negotiatedas part of the connection process.

Configuring a Microsoft SNA Server connectionIn this guide, the Microsoft SNA Server interface is described as a LAN gateway connection type.

Before running Rumba software with the Microsoft SNA Server interface, you must:

• Run the Microsoft-supplied configuration utility and configure the workstation as an APPC client.• Run the supplied snabase.exe utility to start communication between the workstation and the

Microsoft SNA Server.

DiagnosticsYou can use the following tools to diagnose connection problems that your users might encounter whentrying to establish a host connection:

RumbaTrace tool

Traces and records SNA and link layer communication sessions. These trace options canhave an impact on your system performance, so it is best to use them as a filter to siftthrough your communication sessions when isolating a problem.

RumbaEventViewer

Works in the background collecting information at timed intervals that you can set, andkeeps an event log organized by Data, Time, Source, Event ID, Type, and Computer.

Note: The Rumba Event Viewer is very similar in appearance and functionality tothe Windows Event Logger.

Configuring the AS/400 Communications toolYou use the Rumba AS/400 Communications tool to configure host connections for:

• AS/400 File Transfer• Shared Folders application and API• Data Queues API• Submit Remote Command API• Virtual Print application and API


Configurations are saved as a file with an .ehn extension. You can create multiple configuration files foreach interface that you use.

Connecting to the hostThe connection is configured from the Connection menu.

1. Select the Connection > Configure.

2. Select the interface to use.

3. Click Properties and configure the interface, if required.

4. Click Connect. After connecting to the host, you can save your settings as a profile.

Interface page

The table below describes the parameters on the Interface page of the Rumba AS/400 Communicationsdialog box.

Procedure Description

Communications Interfaces Lists the installed communication interfaces. Select whichtype of communication interface to use when connectingthis profile to the host.

Configure Configures the selected interface (displays the RumbaRouter dialog box). If the interface has already beenconfigured, you do not need to do so again, unless youwant to make changes.

Procedures for using the Rumba Router and configuring other communication interfaces can be found in:

Using the RUMBA Router to Configure an APPC Link

Security tab


Security page

The table below describes the parameters on the Security page of the Rumba AS/400 Communicationsdialog box.


Use Common Sign-on Uses the specified User ID and Password as sign-oninformation for all systems.

AS/400 Sign-ons Lists the current AS/400 systems you have configuredsecurity settings for. You must add systems on theInterfaces page before you can configure securitysettings for them.

Add Sets up security for a new system (displays the AddSystem Sign-on dialog box).

Change Changes the security settings for the selected system.

Delete Deletes the security settings for the selected system.

Enable Caching of User ID’s and Passwords Enables storing of the user ID and password for thecurrently configured system until you reboot your PC. Ifyou check Enable Caching of User IDs andPasswords, you not have to enter your user ID andpassword for subsequent connections, unless you reboot.

Add System Sign-on dialog box

Parameter Name Description

AS/400 System Name Lists the selected system name.

User ID Becomes the user ID that is required when signing on tothe selected system.

Password Becomes the password that is required when signing onto the selected system. This is optional, unless a



password is required by the system you are connectingwith.

Verify Password Verifies the correct spelling of your password. An errormessage is displayed if this password does not match thefirst password you entered.

OK Saves any changes you have made and closes the dialogbox.

Cancel Ignores any changes you have made and closes thedialog box.

Reset Removes changes and restores the original settings.

Character pageThe table below describes the parameters on the Character page of the Rumba AS/400Communications dialog box.


Host Character and Set/Code Page Displays all the character sets and corresponding codepages available for the AS/400 display.

Diagnostics pageThe table below describes the parameters on the Diagnostics page of the Rumba AS/400Communications dialog box.


Display EHNAPPC Error Messages Displays additional diagnostic error message boxes whena communications error occurs. These do not replacestandard error messages.


AS/400 File TransferThis section provides a general overview of the Rumba AS/400 File Transfer program, together withreference information.

Rumba AS/400 File Transfer sends data between the host and the PC. Users can run AS/400 File Transferto send host files or selected host data to the PC, work with the data in a PC application, then run AS/400File Transfer to send the modified PC data back to the AS/400.

In addition to AS/400 File Transfer, you can also transfer files using Mainframe Passthrough.

For detailed information on configuring individual and batch file transfers, see the online Help.

AS/400 File Transfer featuresAS/400 File Transfer provides multiple options for transferring data between the AS/400 host and the PC.You can:

• Create, open, and save file transfer settings in a profile• Run individual or multiple (batch) file transfers• Transfer text or database files from the PC to the AS/400• Use drag-and-drop to transfer host data to the PC display, the printer, or to a PC file• Transfer complete host files to the PC or use SQL to transfer only the information you need• Display libraries you can access on the host, and add libraries for the current file transfer session• Specify decimal, date, and time formats for the transferred data• Remove End-of-File (EOF) characters from host files before sending to the PC• Specify transfer options such as Run minimized, Monitor percent complete, Notify when complete,

Close when complete, Truncate records, Truncate spaces, and Auto Run.• Forward host files to an e-mail address

InstallationAS/400 File Transfer is included in the default installation of Rumba AS/400 Edition. When performing acustom installation of Rumba AS/400 Edition, you can select or deselect the AS/400 File Transfer option.

After installing AS/400 File Transfer on a workstation, you can create and distribute customized file transferprofiles that your users can run easily.

Using profilesYou can simplify the file transfer process for your users by creating and distributing profiles for all datatransfers that need to be run regularly. For example, users might need to create weekly reports orspreadsheets based on host data. To automate the file transfer program, go through the following steps:

1. Analyze the problem.

Which users transfer data to and from the host on a frequent or regular basis? What kinds of transferreddata do they need? How would they best benefit from an automated file transfer procedure?

2. Design individual file transfer profiles.

Based on your analysis, create customized file transfer profiles to meet the individual needs of yourusers. This includes configuring:

AS/400 File Transfer | 73

• The default communications interface for AS/400 File Transfer• Transfer options such as Run minimized, Notify when complete, and Monitor percent complete• The location and format of the data files on the PC and the host

3. Use SQL statements if appropriate.

When sending AS/400 data to the PC, you can use SQL statements to transfer only the AS/400 datathat users need, instead of transferring complete files. You can also sort, group, summarize, andperform mathematical calculations on the transferred data.

4. Create batch transfers that run multiple file transfers in a single step.

You can group individual file transfer profiles in a batch profile so users can run the specified transfersin a single step. Batch transfers can also be scheduled to run once, or on a daily, weekly, or monthlybasis.

5. Use the Auto Run option to run file transfers from the Windows Desktop.

When you save individual or batch transfer profiles with the Auto Run option, users can run their filetransfer profile by simply double-clicking a shortcut on the Windows Desktop.

User filesThe table below describes the different types of user file that are associated with Rumba AS/400 FileTransfer and which are stored in the user’s private directory:

File name Description

.btf Batch transfer profile for multiple file transfers

.fdf File description file (required when sending database filesfrom the PC to the AS/400)

.rto Transfer profile for a single file transfer

.tfr PC Support/Client Access file transfer profile (upload)

.tto PC Support/Client Access file transfer profile (download)

Changing the library list on the AS/400 hostWhen AS/400 File Transfer starts, Rumba reads the QDFTJOBD (default job description) file on the AS/400and displays the list of libraries included in this file. To display other host libraries which your users haveaccess to, you must change the QDFTJOBD file. You can change the file for the entire system or for asingle user.

To change the QDFTJOBD file of a single user:

1. Copy the QDFTJOBD file into a new host library.2. Change the library list as needed in the copied QDFTJOBD file.3. Update the user profile to reflect the new QDFTJOBD file. Generally, the host uses the QDFTJOBD file in

the QGPL library by default.

To change the QDFTJOBD file for the entire system, follow only the instructions Changing the library list inthe QDFTJOBD file.

If you need to change the QDFTJOBD file during a file transfer session, select Transfer > RequestLibraries to update the current library list.

74 | AS/400 File Transfer

Copying the QDFTJOBD file1. At the AS/400 command line, type WRKJOBD, then press F4. The Work with Job Descriptions screen

appears.

2. At Job Description, type QDFTJOBD.

3. At Library, type QGPL

4. Press Enter.

5. Under Opt, type 3 to copy the file, then press Enter.

The Create Duplicate Object screen appears.

6. At To Library, type the new library name for the copied file, then press Enter.

Changing the library list in the QDFTJOBD file1. At the AS/400 command line, type WRKJOBD, then press F4. The Work with Job Descriptions screen

appears.

2. At Job Description, type QDFTJOBD.

3. At Library, type the name of the new library containing the copied QDFTJOBD file.

4. Press Enter.

5. Under Opt, type 2 to make changes to the file, then press Enter.

Te Change Job Description screen appears.

6. Press F10 and Page Down.

7. Under Initial Library List, at + for more values, type the plus sign (+) and type the names of the hostlibraries you want to list.

8. Press Enter twice.

Updating the user profile1. At the AS/400 command line, type CHGUSRPRF, then press Enter.

2. At User Profile, type the name of the profile to change.

3. Press F10, then press Page Down twice.

4. Under Job Description, at Library, type the name of the library containing the new QDFTJOBD file,then press Enter.

Creating a PC description fileWhen sending a PC database file to the AS/400, file and field descriptions for both the AS/400 system andthe PC file are required. The host uses this information to correctly identify and interpret the field data.

The PC description file (.fdf) contains information describing the PC database file. It is a text file thatidentifies the file data type (such as text or DIF), and contains field data including the name, data type, andlength of each field in the transferred file.

When transferring data from the AS/400, you can create a PC description file automatically by checkingSave description file in the To PC - Options dialog box:


Conversely, the PC description file is required when sending a PC database file to the host. If necessary,you can use a text editor to create a PC description file, following these conventions:

• Use ASCII format.• Use a carriage return and line feed to end each record.• Tab characters can be used, but they will be treated as spaces.• Place an End-of-File (EOF) character at the end of the file.• Recommended naming convention: Use the same name as the PC database file you are transferring,

but with an .fdf extension.

Structure of the PC description fileThe PC description file contains four types of information that describe the PC database file:

• PCFDF• PCFT file type• PCFO (optional time, date, and decimal formats)• PCFL entries (field name, data type, length) for each database field

These information types are described below.

PCFDFIdentifies this file as a description file.

PCFT file typeIdentifies the file type of the PC database file.


Indicator File type

1 ASCII

3 BASIC sequential (CSV)

5 Data Interchange Format (DIF)

6 No-conversion file

7 Reserved (DBCS version only)

8 DOS random type 2

9 Binary Interchange Format (BIFF)

10 Tab-delimited text

PCFOOptional PC time, date, and decimal format entries.

Indicator Time format name Time format

1 HMS hh:mm:ss

2 International StandardsOrganization (ISO)

hh.mm.ss

3 USA standard (USA) hh:mm AM or PM

4 European (EUR) hh.mm.ss

5 Japan IndustrialStandard, Christian Era(JIS)

hh.mm.ss

6 DDS Format given by AS/400file attributes

7 DFT Host job default

* Unspecified Host job default

Indicator Time Separator

1 Colon (:)

2 Period (.)

3 Comma (,)

4 Blank ( )

5 Null (N)

6 Default (D) (host)

* Unspecified (host job default)

Indicator Date format name Date format

1 MDY mm/dd/yy

2 DMY dd/mm/yy

3 YMD yy/mm/dd

4 Julian yy/ddd

5 ISO yyyy-mm-dd

6 USA mm/dd/yyyy


Indicator Date format name Date format

7 EUR dd.mm.yyyy

8 JIS yyyy-mm-dd

9 DDS Format given by AS/400file attribute

10 DFT Host job default

* Unspecified Host job default

Indicator Date Separator

1 Slash (/)

2 Dash (--)

3 Period (.)

4 Comma (,)

5 Blank ( )

6 Null (N)

7 Default (D) (host)

* Unspecified (host job default)

Indicator Decimal Separator

1 Period (.)

2 Comma (,)

3 Default (D) (PC country default)

* Unspecified (PC default used)

PCFL entriesDescribes the database fields. Include one PCFL entry for each field in the database. Eachentry consists of:

• Personal Computer Field Length (PCFL)• The field name (maximum 10 characters)• A number designating the data type• The field length in characters• PCFL entries

Indicator Data type

1 ASCII

2 ASCII numeric

3 Hexadecimal

4 Binary

5 Zoned

6 Packed

7 BASIC integer

8 BASIC single-precision floating point

9 BASIC double-precision floating point


Indicator Data type

10 EBCDIC

11 EBCDIC zoned

12 EBCDIC packed

Sample PC description fileThe following is a sample PC description file with commentary:

File entry Comment

PCFDF PC description file

PCFT 9 PC file in BIFF format

PCFO 7,6,10,7,*

Option Settings

Host default date and time formats

PCFL BINARY 9 7/2 The first field, BINARY, is double-precision floating pointand 7 characters in length, precise to 2 decimal places.

PCFL CHAR 1 10 The second field, CHAR, is an ASCII field and has alength of 10 characters.

PCFL ZONED 9 8/4 (The other fields in the database are interpreted asabove.)

PCFL PACKED 9 11/2

PCFL HEX 3 10

PCFL DATE 1 8

PCFL TIME 1 8

Using SQL: ExamplesWhen transferring data from the AS/400 host to the PC, you can use the system default to transfercomplete files, or you can use SQL (Structured Query Language) to send specific AS/400 data. SQL is astandardized query language for requesting information from a host database. You can use SQL to transferdata from specified fields and records in one or more host files, sort the transferred data, and performsimple calculations on the transferred data.

This section contains three short examples of how to use SQL to query data. The examples demonstratevarious query keywords using sample data from an imaginary grocery store. There are three examplequeries:

• Example 1 is a simple query using SELECT, WHERE, and ORDER BY.• Example 2 selects data from three files using JOIN BY.• Example 3 transfers summary records using GROUP BY and HAVING.

To build a query, you must first specify the AS/400 data file(s) in the Lib/File(Member) box on the mainAS/400 File Transfer screen. These examples use three sample AS/400 files named PRODUCT, SUPPLIER,and SUPPROD in a library named GROCERY. The first few records of each file are listed in the followingtables.

ProdCat ProdID ProdDesc ProdName ProdQuant

100570265 129930113 Wild Berry Summerbrook Wild Berry Seltzer 84


ProdCat ProdID ProdDesc ProdName ProdQuant

100570265 129930513 Apple-Cran Summerbrook Apple-Cran Seltzer -9

100570265 129935223 Black Currant Olympia Black Currant Seltzer 125

100570267 129935423 Sparkling Lemonade Olympia Sparkling Lemonade 7

100570262 761837634 Cherry Lime Olympia Cherry Lime Soda 54

100570263 761831637 Cranberry Ice Tea Crystal Falls Cranberry Ice Tea 302

100570263 761831635 Diet Peach Ice Tea Crystal Falls Diet Peach Tea 79

100570263 761831636 Diet Rasp Ice Tea Crystal Falls Diet Rasp Ice Tea 110

100570263 761831638 Lemon Ice Tea Crystal Falls Lemon Ice Tea 218

100570100 165712111 Mineral Water Whisper Rain Mineral Water 22

100570262 165712115 Mango Passion soda Dave’s Mango Passion soda -22

Example 1: Using SELECT, WHERE, and ORDER BYTo transfer a list of all available types of tea drinks sorted alphabetically:

1. Specify the GROCERY/PRODUCT file in the Lib/File(Member) field on the main file transfer screen, thenopen the From AS/400 - Options dialog box:

2. Verify that the Select field on the Overview page contains an asterisk (*). This indicates that all fieldsin the PRODUCT file will be transferred.

3. To transfer all records containing the string Tea, type the following string in the Where field:

PRODNAME LIKE ‘%Tea%’

The % character is a wildcard indicating any number of characters:


4. To sort the data in ascending order by the type of drink, type the following string in the Order By field:

PRODDESC

5. Click Apply to update the query fields:

SELECT *FROM grocery/productWHERE (PRODNAME LIKE ‘%Tea%’)ORDER BY PRODDESC

The resulting records are:

ProdID ProdDesc ProdName ProdQuant

100570263 761831637 Cranberry Ice Tea Crystal Falls Cranberry Ice Tea 302

100570263 761831635 Diet Peach Ice Tea Crystal Falls Diet Peach Tea 79

100570263 761831636 Diet Rasp Ice Tea Crystal Falls Diet Rasp Ice Tea 110

100570263 761831638 Lemon Ice Tea Crystal Falls Lemon Ice Tea 218

Example 2: Querying multiple files with JOIN BYThis query finds the suppliers and prices for a given product. Multiple files are joined so they can bequeried as if they were one file. This is necessary because the GROCERY library stores data in separatefiles linked by common fields, rather than using one large file: The PRODUCT and SUPPROD files share theProdID field, and the SUPPROD and SUPPLIER files share the SupID field.


With JOIN BY, the relationships between files become part of the query. Without joining the files, youwould need three queries to get the same result: one for product ID, one for product cost, and one forsupplier name.

To find the suppliers and prices for Dave’s Mango Passion soda:

1. Specify the GROCERY/PRODUCT, GROCERY/SUPPROD, and GROCERY/SUPPLIER files in the Lib/File(Member) field on the main file transfer screen, then open the From AS/400 - Options dialog box.

2. To transfer only the product name, product cost, and supplier name fields, type the following string inthe Select field on the Overview page:

T1.ProdName, T2.ProdCost, T3.SupName

3. To join records in the three files by the product ID and supplier ID, type the following string in the JoinBy field:

T1.PRODID = T2.PRODID AND T2.SUPID = T3.SUPID

4. To search all records with the string “Mango Passion”, type the following string in the Where field:

T1.PRODNAME = 'Dave’s Mango Passion soda'

5. Click Apply to update the query fields.

The Query box at the top of the Overview page displays the complete query statement:

SELECT T1.ProdName, T2.Prodcost, T3.SupNameFROM grocery/product, grocery/supprod, grocery/supplierWHERE (T1.PRODID=T2.PRODID AND T2.SUPID=T3.SUPID) AND (T1.PRODNAME=’Dave’s Mango Passion soda’)


ProdCost SupName

Dave’s Mango Passion soda 3.00 Kolb Bros.

Dave’s Mango Passion soda 2.90 D & C Distributors

Dave’s Mango Passion soda 2.85 Silves Wholesale

Example 3: Summarizing records with GROUP BYWhat is the least expensive mineral water product? To answer this question, you must obtain the productcosts from multiple suppliers for all mineral water products in each vendor's product line, then average thecosts, group the data by vendor, and sort the data by cost.

With SQL, you can use summary records to obtain the answer by running a single query. The PRODUCT fileincludes a ProdCat (product category) field in which all mineral water products are identified by the value100570100. The ProdName field contains the vendor name.

To transfer a summary record for each product name:

1. Specify the GROCERY/PRODUCT, GROCERY/SUPPROD, and GROCERY/SUPPLIER files in the Lib/File(Member) field on the main file transfer screen, then open the From AS/400 - Options dialog box.

2. To transfer a summary record of the average cost and the product name field, type this string in theSelect field on the Overview page:

AVG(T2.PRODCOST), T1.PRODNAME

3. To join records by product ID and supplier ID, type the following string in the Join By field:

T1.PRODID = T2.PRODID AND T2.SUPID = T3.SUPID

4. To search records that are mineral water products, type the following string in the Where field:

T1.PRODCAT =100570100


5. To perform summary calculations on records of the same product name, type the following string in theGroup By field:

T1.PRODNAME

6. To sort the results from lowest to highest product cost, type the following string in the Order By box:

AVG(T2.PRODCOST)

7. Click Apply to update the query fields.

The Query box at the top of the Overview page displays the complete query statement:

SELECT AVG(T2.PRODCOST), T1.PRODNAMEFROM grocery/product, grocery/supprod, grocery/supplierWHERE (T1.PRODID=T2.PRODID AND T2.SUPID=T3.SUPID) AND (T1.PRODCAT=’100570100’)GROUP BY T1.PRODNAMEORDER BY AVG(T2.PRODCOST)


ProdCost

Whisper Rain Mineral Water 3.00

Maple Falls Mineral Water 3.17

Mt. Baker Sparkling Water 3.35

Panda Mineral Water 3.62

Panda Sparkling Lemon Essence 3.81

Panda Sparkling Lime Essence 3.81


AS/400 Client ApplicationAn additional feature available in Rumba Office and Rumba AS/400 Edition is the AS/400 ClientApplication: Rumba Submit Remote Command (application and API)

The AS/400 Client Application brings many powerful features and possibilities to your desktop. RumbaSubmit Remote Command allows you to start and control non-interactive programs on your AS/400 hostsystem without opening a display session.

The associated AS/400 Client APIs are development tools. With these APIs and a high-level programminglanguage such as C, C++, or Visual Basic, you can develop custom PC applications which incorporate thefunctionality of the Rumba AS/400 Client Application. Before you can use the AS/400 Client APIs, you mustinstall the Legacy API help and header files.

AS/400 Client installation and availabilityThe AS/400 Client Application is included under an Express installation of Rumba AS/400 Edition.However, you can select or deselect the application by performing a Custom installation. The AS/400Client Application is listed under the AS/400 branch in the Select Features dialog box of the installationprogram.

Before startingBefore using the AS/400 Client application, you must configure an interface to connect with an AS/400 viathe Rumba AS/400 Communications tool or the APPC Configuration tool. These tools reside in the RumbaTools folder. For instructions on using these tools, see Connection Tools.

Note: If you have already configured an interface with the Rumba AS/400 Display or Printer, you donot need to reconfigure the interface with either of the tools.

Interfaces supportedThe Rumba AS/400 Client Application requires an interface that supports full LU 6.2 capabilities. Theseinterfaces include:

• Rumba Router (only MPTN supported).• Microsoft SNA Server - All connection subtypes for the Microsoft SNA Server Client are supported.

Note: The Microsoft SNA Server Client software must already be installed and configured, and theMicrosoft SNA Server itself must be correctly configured and functional.

• TCP/IP - If your AS/400 operating system supports Optimized Server (V3 R1 or higher), you canconnect Rumba AS/400 Client Applications over TCP/IP.

Rumba Submit Remote CommandUse the Rumba Submit Remote Command tool to start and control non-interactive programs on an AS/400host from your PC without opening an AS/400 display session. Commands can be sent individually ortogether, and they can be saved in an ASCII file for re-submission. Return codes are received but programdata cannot be returned from the host system.

84 | AS/400 Client Application

For an example of using Submit Remote Command, imagine your accounts receivable department prints agroup of reports every morning which requires them to enter a series of AS/400 commands. You canstreamline the process in the following way:

1. Use the Rumba Submit Remote Command window to create an ASCII file of AS/400 commands.2. Click Send All.

Note: If you already have a command file, open it in the Rumba Submit Remote Command window,then click Send All.

The Submit Remote Command utility also has a command line interface which allows you, for example, toexecute Submit Remote Command from a PC batch file and send AS/400 commands in a specified .txtfile.

The Rumba Submit Remote Command tool is located under Start > Programs > Micro Focus Rumba >Rumba Tools. Submit Remote Command is also a legacy API and available as an ActiveX control in theRumba ObjectX Development Kit.

AS/400 Client Application | 85

Mainframe File TransferThis section provides a general overview of the Rumba Mainframe File Transfer program. For detailedinformation, refer to the online Help.

Mainframe file transfer featuresMainframe file transfer copies files between your PC and the mainframe. The Transfer > Send andTransfer > Receive commands open a setup window where you specify the file type, transfer protocol,and host environment for the file transfer. You can also choose to have Rumba software initiate the filetransfer protocol.

Rumba for the mainframe works transparently with most IBM host operating systems, including CICS,TSO, and VM/CMS. This allows an application on one platform to access and use data on anotherplatform.

Rumba simplifies the file transfer process by using typical Windows menus and dialog boxes. It reads andlists PC and host files, and lets you transfer files in the background. You can also perform file transfersusing the configurable tool bar.

To start a transfer, Rumba submits a command to a host file transfer program. The most common hostprogram used is called IND$FILE.

Mainframe file transfer provides a number of features, such as support for:

• ASCII or binary transfers• Write Structured Field or Buffered data streams• EBCDIC-to-ASCII translation• Data compression• DOS-based, batch, and drag-and-drop file transfer

Sending and receiving filesTransferring files between a PC and mainfame is straightforward once you have configured your PC.Unless you want to change the way you transfer files, you do not have to reconfigure your machine eachtime you want to send or receive files.

Configuring your PC1. Connect to the host.

2. Click Transfer > Configure .

3. In the File Transfer Configuration dialog box, select TSO, CMS, or CICS as the destination hostenvironment.

86 | Mainframe File Transfer

Note: If you click Templates, the File Transfer Template Configuration dialog box appears. Formore information on how to set up a template, see Using file transfer templates.

After configuring your PC (and setting up a template, if required), you are ready to transfer files.

Sending a file to the host1. Connect to the host.

2. Click Transfer > Send .

The Transfer - PC to Host dialog box appears.

3. In the Host File frame, specify the required host file information. The fields vary, depending on thedestination host environment.

4. In the PC File frame, specify the PC file to send to the host.

5. In the Data Type frame, click the appropriate data type options.

6. Click Transfer to send the file, or click Accept to save the settings for future use.

Receiving a file from the host:1. Connect to the host.

2. Click File > Receive .

3. In the Host File frame, select the host file you to transfer to your PC.

4. In the PC File frame, select an existing destination file name or enter a new destination file name, andthen select a PC directory.

5. In the Data Type frame, click the appropriate data type options.

6. Click Transfer to send the file, or click Accept to save the settings for future transfers.

Using file transfer templatesTo maximize user productivity, you can use file transfer templates to set up and save frequently used filetransfer settings rather than repeatedly configuring the same types of file transfer.

You may need to transfer files on a regular basis, and Rumba provides an efficient way of making theprocess easier. Use file transfer templates to set up and save detailed send or receive instructions forspecific files. Saving these instructions as templates makes them available for repeated use. Rumba

Mainframe File Transfer | 87

supports DOS-type wildcard characters in your file names and extensions, increasing your ability to matchlarger sets of data on the host or PC with one template.

Tip: When you set up a send template, it is good practice to set up a corresponding receive templatethat reverses the steps specified in the send template.

Creating a TSO templateTo create a TSO file transfer template:

1. Open the File Transfer Configuration dialog box.

2. In the Host Environment frame, select TSO.

3. Ensure that Enable Templates is checked.

4. Click Templates.

The TSO File Transfer Template Configuration dialog box appears.

5. Click Send or Receive, depending on the type of template you are creating.

6. In the Name Conversionframe, you can either modify a default template or create a new one. If youtype a new PC file name, Rumba saves a new template with that name. If you do not change the PC filename, but modify its template settings, Rumba saves the settings changes in the default template.

7. When you have finished, click OK.

The template is now available when you perform a TSO file transfer operation.

Creating a CMS templateTo create a CMS file transfer template:

1. Open the File Transfer Configuration dialog box.

2. In the Host Environment frame, select CMS.


4. Click the Templates button.

The CMS File Transfer Template Configuration dialog box appears.



6. In the Name Conversion frame, you can either modify a default template or create a new one. If youtype a new PC file name, Rumba saves a new template with that name. If you do not change the PC filename, but modify its template settings, Rumba saves the settings changes in the default template.


The template is now available when you perform a CMS file transfer operation.

Creating a CICS templateTo create a CICS file transfer template:

1. Configure a file transfer.

2. In the Host Environment frame, select CICS.


4. Click Templates.

The CICS File Transfer Template Configuration dialog box appears.


6. In the Name Conversion frame, you can either modify a default template or create a new one. If youtype a new PC file name, Rumba saves a new template with that name. If you do not change the PC filename, but modify its template settings, Rumba saves the settings changes in the default template.


The template is now available when you perform a CICS file transfer operation.

Batch file transfersYou can use batch files to transfer several files between your PC and the mainframe host. A batch fileconsists of two main components: a batch list, and send or receive commands. The batch list groups sendand receive commands that you can run from your batch file. You can have several batch lists within onebatch file, and several commands within each batch list.

If you only need one batch file, you can use the default batch file DEFAULT.FTB. You can also use dragand drop for multiple file transfers.


Creating a batch fileTo create a batch file:

1. Select Transfer > Batch .

If no batch files are defined, a New Batch List dialog box appears. Otherwise, in the File TransferBatch dialog box, click New in the Batch File frame.

2. Specify a name for the new batch file, then click OK.

The new batch file name appears in the Name list.

3. In the Commands In List frame, click New.

The File Transfer dialog box appears.

4. Click Send to send files to the host, or Receive to receive files from the host.


5. Select the files to transfer, then click OK. You can use file extensions and wild cards to transfer multiplefiles with a single command.

6. Repeat steps 3 - 5 to add transfer commands as needed.

7. Click Accept to save your settings, or Transfer to save your settings and run the batch file transfer.

Running a batch file transferTo run a batch file transfer:

1. Open your Rumba profile and connect to the host.

2. Click Transfer > Batch .

3. Select the batch file you want to use. Batch files have an .ftb extension.

4. Click Open.

5. To run individual commands in a batch file, select the command you want to start, then click Transfer.

6. To run all commands in a batch file, click Transfer.

File transfer registry settingsWhen you install an upgrade version of Rumba for the Mainframe over an existing 16-bit version, theinstallation program converts settings that were previously in the rumba.ini file into Windows registryentries

The table below lists the old file transfer rumba.ini settings, the new Windows Registry entry, anddescribes the purpose of each setting.

This rumba.ini setting Converts to this Windows registryentry

Purpose

[FTX] Blank Screen BlankScreen (DWORD) Specifies whether the screen shouldbe blank while Rumba displays theFile Transfer Configuration dialogbox. When the dialog box firstappears, the screen is frozen. When


This rumba.ini setting Converts to this Windows registryentry

Purpose

the dialog box closes, the screenrefreshes with the current buffercontents.

[FTX] NOPA1 NOPA1 (DWORD) Disables the PA1 key from beingautomatically sent to the hostfollowing a TSO file transfer or file listcommand. Some host applications,such as session managers, reservethe PA1 key for special functions.Enabling the NOPA1 setting preventsRumba from interfering with thesehost applications. NOPA1=0 meansdisabled. NOPA1=1 means enabled.

Note: For compatibility witholder versions of Rumba, thevalue NOPA1=2 is supportedas an alternative for theListcatWithATTN setting.

[FTX] ListcatWith ATTN ListcatWith ATTN (DWORD) Overrides the default behavior ofsending a PA1 following a LISTCATcommand. Rumba issues theLISTCAT command internally togenerate the file list in the FileTransfer dialog box. WhenListcatWithATTN is specified,the LISTCAT command isterminated by sending an Attentionkey, rather than a PA1, to the host.To disable the setting, assign thevalue 0. To enable the setting, assignthe value 1.

[FTX]IND_Timeout IND_Timeout (DWORD) Adjusts file transfer responsivenessby specifying the amount of time towait before timing out during a filetransfer command. The settingspecifies the timeout in milliseconds.

[FTX] List_Timeout List_Timeout (DWORD) Adjusts file transfer responsivenessby specifying the amount of time towait before timing out during a file listcommand. The setting specifies thetimeout in milliseconds.

Using macros to transfer filesYou can use the Rumba Macro Editor to create macros to automate and simplify file transfer proceduresfor your users.

Creating a file transfer macroTo create a file transfer macro:

1. Select Tools > Edit Macro .


2. On the lower toolbar, click the File Transfer Send icon or the File Transfer Receive icon depending onwhether you want to send or receive a file.

3. Configure the file transfer as needed, then click OK.

4. On the Macro Editor toolbar, select File > Save.

5. Give the macro a name, then click OK.

IND$FILE TRANSxx codesThe most common host file transfer program is IBM’s IND$FILE. This program uses a set of TRANSxxcodes, which convey information about particular key file transfer transactions. The table below describesthe various codes used by the IND$FILE program.

TRANSXX code Descriiption

TRANS00 Error in file transfer: filetransfer canceled

Indicates that an error occurred in the file transferoperation that was detected by the CICS file transfertransaction. This may be an error in the data beingtransferred, or an unidentified system error. Examine thefile for incorrect format or bad data, and check theinstallation procedure and the setup of all thecomponents involved. Try the file transfer again.

TRANS01 File Transfer command beingprocessed

Informs you that the file transfer transaction is currentlybeing processed.

TRANS02 Number of bytes of filetransferred so far ===> xxxx

The file transfer transaction is currently being processed,and this code informs you of the number of bytes ofinformation transferred so far.

TRANS03 File transfer complete The file transfer transaction has completed normally andthe file has been transferred without any errors detected.Examine the data in the file to determine if the operationwas implemented correctly.

TRANS04 File transfer complete, withrecords segmented

The file transfer transaction completed successfully, butat least one of the records of data sent to the host waslonger than the maximum allowed (32767). The recordhas been broken into more than one segment, each ofwhich appears as a separate item in the TemporaryStorage queue. The error may have occurred becausethe CRLF option was used when the file did not containlogical records.

Check the contents of the file being uploaded, and theoptions used, then try the file transfer transaction again.Alternatively, use the

BINARY

option to transfer the data “as is” from the 3270 to thehost without interpretation. Interpret the data in the host.

TRANS05 Personal computer filespecincorrect:

File transfer has been canceled. The PC file specified isincorrect. Verify the file and try the file transfer transactionagain.

TRANS06 Command incomplete: File transfer canceled. The file transfer command enteredwas incomplete. Verify the command and try the filetransfer transaction again.



TRANS07 Cannot link to host: File transfer canceled A link cannot be established withthe host. Check the status of the host, or refer to the userfor more information.

TRANS09 Error reading file fromdamaged personal computer disk: filetransfer canceled

The specified PC file resides on a damaged disk. Copythe file to an undamaged medium and try the file transfertransaction again. .

TRANS10 Host has not responded withintimeout period

The host did not respond within the allotted amount oftime. Check the status of the host, or refer to the userguide for more information.

TRANS11 Lost contact with host: filetransfer canceled

Re-establish a host connection and try the file transfertransaction again.

TRANS12 Error writing to damaged orfull personal computer disk: filetransfer canceled

The specified PC disk is damaged or full. Examine thedisk for damage and ensure that it contains enoughspace to receive the transferred data. Try the file transfertransaction again.

TRANS13 Error writing file to host:file transfer canceled

An error occurred while writing the file to the host. Referto the user’s guide for more information.

TRANS14 Error reading file from host:file transfer canceled

An error occurred while reading the file from the host.Refer to the user guide for more information.

TRANS15 Host storage unavailable: filetransfer canceled

The CICS file transfer transaction could not obtainenough storage in which to place its own control blocks,I/O buffers, or save areas. Make more storage availableto the transaction and try the operation again.

TRANS16 Incorrect request code: filetransfer canceled

The command that started the file transfer operation didnot specify GET or PUT. The command is rejected.Check the parameters used to invoke the file transferoperation and correct them. Re-attempt the File Transfertransaction.

TRANS17 Invalid file name: filetransfer canceled

The file name specified is invalid. Verify the file name andtry the file transfer transaction again.

TRANS18 Incorrect option specified:file transfer canceled

An incorrect file transfer option was specified. Verify alloptions selected and try the file transfer transactionagain.

TRANS19 Error handling host file: filetransfer canceled

An error occurred while handling the host file. Refer to theuser guide for more information.

TRANS21 Not enough personal computermemory available: file transfercanceled

Not enough memory is available on your PC to proceedwith the file transfer. Close one or more applications andtry the file transfer transaction again.

TRANS22 Host session identifierincorrect: file transfer canceled

The host session identifier specified is incorrect. Verifythe identifier and try the file transfer transaction again.

TRANS23 Activity specified not a hostsession: file transfer canceled

The activity specified is not a host session. Verify theactivity and try the file transfer transaction again.

TRANS24 Autokey operation in progress: file transfer canceled Waitfor the autokey operation to complete, then try the filetransfer transaction again.



TRANS25 Keyboard inhibited: filetransfer canceled

The keyboard has been inhibited. Refer to the user guidefor more information.

TRANS26 Unrecoverable system error:file transfer canceled

An unrecoverable system error occurred. Check theinstallation procedure and the setup of all thecomponents involved. Try the file transfer transactionagain.

TRANS27 Communication sequence withhost disrupted: file transfer canceled

Communication between your PC and the host wasdisrupted. Re-establish a host connection and try the filetransfer transaction again.


HP and UNIX File TransferRumba software, the PC-to-host connectivity system, gives you easy, complete, and transparent access tohost applications. PC users working in the Microsoft Windows environment, and using Rumba HP andUNIX software, can communicate with HP and UNIX hosts and host applications. Rumba softwarecombines the convenience, ease of use, and versatility of PCs with the power of HP and UNIX hosts andhost applications.

How to Transfer Files Using Rumba HP and UNIXUsing the Rumba HP file transfer feature, you can copy files from a PC to an HP host or from an HP hostto a PC.

Similarly, using the Rumba UNIX file transfer feature, you can copy files from a PC to a UNIX or VMS host,or from a UNIX or VMS host to a PC. Rumba software works transparently with any UNIX or VMS hostoperating system.

Rumba software simplifies the file transfer setup process by using typical Windows menus and dialogboxes. It reads and lists PC and host files, and lets you transfer files in the background. You can alsoperform file transfers using the configurable toolbar.

Understanding the file transfer processRumba software uses protocol-driven transfer methods. This means that files are transferred using a set ofrules known as a protocol. The specific details of the protocols are not important to users, but the protocolsspecified on the PC must match that used by the host computer. For example, Rumba software will notwork if the host is attempting to transfer using the Kermit file transfer protocol and the user selects Text asthe transfer protocol to be used. To minimize such conflicts, Micro Focus strongly recommends that userstake advantage of the Rumba Initiated and Macro options.

Even using Rumba Initiated, the user must know which protocols are supported by the host. If the protocolchosen by the user is not supported by the host, the Rumba software will not work. Also, the host must beat a command prompt, ready to accept the transfer command before you attempt a file transfer.

Here is an overview of the steps you must follow to transfer files:

1. On the Home tab, click Send or Receive. (In the Classic interface, click Transfer > Send to send a filefrom your PC to the host, or Transfer > Receive to receive a file from the host.)

2. On the Setup tab, specify the file type, transfer protocol, and host environment. You can also haveRumba software initiate the file transfer operation by checking the Rumba Initiated box. For example,“sz” is used for sending files to the host via Zmodem.

When this option is checked, you may specify the name of the host’s transfer program which Rumbasoftware will use when automatically initiating the transfer.

If Rumba Initiated is selected, the software provides some standard commands based on the protocolselected. If the local setup is different, commands can be entered that are specific to the site. Whateveris entered in the To Host Program Name or From Host Program Name fields is sent to the host exactlyas it is typed.

Note: If the host is a VMS system and the full program name is given, Rumba software defines aforeign command to start the program.

The default setting for Rumba Initiated is Off. The Rumba Initiated option is not available for Text filetransfers or when Other is selected in the Host Environment box.

96 | HP and UNIX File Transfer

When you choose a file transfer protocol, Rumba software displays a configuration tab corresponding tothat protocol. For example, if you choose the Text transfer protocol, the Text Configuration tab isdisplayed.

3. Click the tab that is associated with the transfer protocol you have chosen, and then specify theinformation needed by the transfer protocol.

4. Click the Files to Transfer tab and select the files you want to transfer.

Note: If Rumba Initiated is checked, and the correct host is not specified, you will not see any hostfile information when you view the Files to Transfer tab.

5. Click OK.

MPE file transfersFor Rumba HP only, file transfer capabilities are now available for systems using the MPE hostenvironment. While you’re connected in MPE mode, HPXFER is the only protocol available. MPE filetransfers are always Rumba Initiated.

MPE file transfers require special setup by the host administrator. Follow these steps to set up MPE filetransfers:

1. In the registry, create a new value:

HKEY_LOCAL_MACHINE\SOFTWARE\WallData\

Office\HP\MPEBOOTSTRAP

The type of the value is DWORD and the value should be set to 1.

2. When the File Transfer dialog is invoked in Rumba software, a new button labeled BootStrap will bevisible. Clicking this button will cause the WALLXFER.BIN file to be transferred to the MPE system.

3. After the WALLXFER.BIN file is on the host, the administrator should set its file permissions to execute(“X”) and move it to the PUB.SYS group.

4. Once the file has been transferred for the first time, the BootStrap functionality should be disabled bydeleting the registry key or changing its value to 0.

Note: This procedure needs to be done once for each MPE system with which you will be transferringfiles.

Using compatible file transfer protocol versionsRumba software may have trouble supporting certain freeware or shareware versions of a given filetransfer protocol. For example, there are many public domain versions of Xmodem and Ymodem which areknown to improperly implement the protocols. Make sure that you are using a file transfer protocol versionthat is current and well-supported by a known and reputable vendor.

8-bit binary transparent communicationsIt is necessary to perform file transfers using an 8-bit “binary transparent” protocol. A transparent channelis a communication method and medium that does not use any of the byte values for control of the channelitself. An 8-bit channel does not use any of the bits in an 8-bit character set for control of the channel (forparity, for example) and can transmit all 256 codes in the character set. An example of a channel that doesnot meet this criteria is a CompuServe“ connection using 7 bits and Even parity. This is important whentransferring data that contains anything that is not printable text in the data stream. If the channel you areusing is not transparent, the Kermit protocol performs the most reliable file transfer; channels less than 8-bits wide are not supported.

HP and UNIX File Transfer | 97

Using Rumba Macros to Transfer FilesBecause many Rumba software users are not familiar with file transfer procedures, it’s a good idea toconfigure macros they can use for the file transfers they commonly perform. The Rumba macro utilityallows you to automate many Rumba software functions, including file transfers.

To create a file transfer macro:

1. On the Tools tab in the Macros group, click Edit to open the Macro Editor. (In the Classic interface, clickTools > Edit Macro.)

2. Click the file transfer send button or the file transfer receive button.3. Configure the file transfer and click OK.4. Choose Save from the Macro Editor File menu, give the macro a name, and click OK.

98 | HP and UNIX File Transfer

AS/400 and Mainframe PrintersThis section provides a general overview of Rumba for both the AS/400 and Mainframe printer.

AS/400 and Mainframe printer featuresWith the Rumba printer, you can route jobs from your printer queue to the Windows printer of your choice.You can also:

• Preview documents before printing• Save documents to print later• Print to a file• Change page layout, formatting, and printer properties• Use the PC Printer Queues display, and the AS/400 Printer Queues display, to monitor and control

printers and print jobs• Use the Print Log display to monitor completed print jobs• Use advanced printer features such as font mapping and character translation• Install the Rumba AS/400 printer as a Windows system service

Printing AS/400 and mainframe documents on a PCprinter

When you have configured and connected the Rumba printer, you can send host print jobs to your currentWindows printer by simply opening the host application, and then printing the document as usual. You canalso preview documents and save them to print later, print to a file, or change the page layout, formatting,and printer properties.

If you attempt a Rumba printer operation, but have not installed a Windows printer, the Printer Wizardautomatically prompts you to install a Windows printer, and guides you through the installation process.Normally, you add printers by clicking the Printers icon in your Windows Control Panel.

Help topic: Working with data > The Rumba AS/400 and Mainframe Printers > Printing

Viewing documents before printingYou can use Print Preview to review page layout and formatting, change Windows printer properties, orsave documents to print later. When Print Preview is active, a picture of each printed document displays onthe screen before the document is sent to the printer.

Monitoring and controlling printers and print jobsYou can control the behavior of the Rumba mainframe printer by using Direct printing, Printer sharing, andEnd print job. You can also monitor your printers and print jobs with the Printer Queues display, and usethe PC Printer Queues display to:

• Monitor and control current print jobs• Control your Windows printers

AS/400 and Mainframe Printers | 99


AS/400 Printer QueuesThe AS/400 Printer Queues feature is available only on hosts with operating systems of OS/400 V3R1 orlater. This display lists the AS/400 printer queues to which you have access, along with the print jobs ineach printer queue, and the status of each job.

You can:

• Customize the display to list only the print jobs you are interested in.• Toggle this display on and off by choosing AS/400 Printer Queues on the View menu.

Note: AS/400 Printer Queues will not work if the transaction program (TP) on the host has not beenstarted. The command to start all host servers is: strhostsvr *all The command to start theNetwork Print Server TP is: strhostsvr *netprt

Direct printingWith Direct printing, you can print both unlimited characters per line, and graphic data streams withoutinterpretation by the printer driver. Host data is translated from EBCDIC to ASCII and sent directly to theprinter, bypassing the printer driver.

Note: When Direct printing is active, Print Preview does not work. The print job will go to the printerwithout any preview.

Printer sharing and End print jobUse the Printer sharing option (default) or the End print job option to specify how Rumba software willrecognize the end of a host print job.

With Printer sharing, the current print job is released when Rumba software receives the Change DirectionIndicator (CDI) that is usually sent with the SNA End Bracket command to indicate the end of a print job.

You can use Printer sharing for most host print applications. However, some host applications do not sendan Unbind command to signal the end of the print job. If you encounter pagination problems, or if host printjobs terminate before document printing is complete, then use the End print job option.

With End print job, if the host does not send an Unbind command at the end of the print job, Rumbasoftware will wait for the user-specified timeout period, and then release the print job if data is not received.

PC Printer QueuesThis display lists the printer queues for all network and local printers set up in your Windows PrintManager. Information is displayed for all print jobs (not only jobs from the host) and for all users. See theonline help for procedures on using this display to:

• Pause, resume, restart, cancel, and purge print jobs• Add, delete, and change printers• Change Windows printer properties

Viewing print job historyThe Print Log display lists documents that have printed on the PC printer, including documents printedfrom host as well as from PC applications, saved print previews, documents that did not print due to errors,and held or canceled documents. Information displayed includes:

• Name of the host system

100 | AS/400 and Mainframe Printers

• Device name of the PC printer• PC printer type• Status of the print job, or location if the print job was saved• Number of pages• Date and time the job was processed

Formatting printed documentsThe way a printed document looks is affected by the capabilities of the target PC printer, the printer driver,Rumba software formatting options, and host print file values. You can use the format specified by thehost, the default Windows format for the PC printer (LU1 print jobs only), or you can customize the formatby specifying options such as text styles, page orientation, scaling, margins, spacing, and print quality.


Host Print TransformThe Host Print Transform feature is available only on hosts with operating systems of OS/400 V2R3 orlater. Host Print Transform changes the AS/400 print data to the ASCII format needed by a particular PCprinter before the data is sent to the Rumba AS/400 printer. The Rumba AS/400 printer then passes thedata directly to the PC printer. In this way, the Rumba printer and Windows printer drivers are minimallyinvolved in the process.

To use Host Print Transform, follow these steps before connecting the Rumba AS/400 printer:

1. From the Connection menu, choose Configure, then select Rumba Router from the list of installedinterfaces.

2. On the Rumba Router tab, click the Transform button.3. Click the Host Transform Enabled option, then change the configuration parameters as needed.

You can also configure Host Print Transform directly on the AS/400 host.

Font mappingWhen a host document is sent to the PC printer, it includes both text and format information. The formatinformation includes the font size and style of the printed document. When the document prints, the closestmatching font is selected from those available on the PC printer.

From the Options menu, select Font Mapping.

From the Font Mapping dialog box, you can select a specific Windows font, type size, and style for eachfont sent from the host. You can also:

• Create multiple font map files and associate each with a different profile, to be used with differentprinters

• Use only PC printer fonts, to speed printing

Help topic: Working with data > The Rumba AS/400 Printer > Printing > Advanced printer features

Character translationWhen printing host documents on a PC printer, host EBCDIC characters are translated to ANSI characters.Each national language has its own unique character translation table. By default, your charactertranslation table is associated with the Host Character Set you selected when configuring your printerprofile.

AS/400 and Mainframe Printers | 101

If your application requires that characters be translated differently than the default table, you can create acustomized translation table to meet your needs. The customized table is saved in association with yourprinter profile. You can also create multiple customized translation tables to use with different profiles.

Help topic: Working with data > The Rumba AS/400 Printer > Printing > Advanced printer features

102 | AS/400 and Mainframe Printers

Rumba Telnet EditionRumba Telnet Edition represents the total TCP/IP solution. Rumba software supports every TCP/IPnetwork application: connections to multiple hosts, printing, file transfer and file system sharing, andworking in the Internet.

This section introduces you to Rumba Telnet Edition and provides an overview of core Rumba TelnetEdition capabilities.

Rumba applications for TCP/IP networksThe Telnet edition of Rumba supports every TCP/IP network application: connections to multiple hosts,printing, file transfer and file system sharing, and working over the Internet. The following tables describethe functions performed by the Rumba host applications (AS/400, Mainframe, UNIX, and HP).

For AS/400 hostsWith the Telnet edition of Rumba you can view AS/400 host applications using two different methods, printhost applications, perform a variety of file transfers, and seamlessly share AS/400-based file systems withworkstations.

The following provides brief descriptions of Rumba AS/400 host applications grouped by function.

• Display

Rumba AS/400 Display presents the traditional AS/400 display in a Microsoft Windows application: theRumba window. Includes support for the Text-Assist function of OfficeVision/400.

Users can run multiple host sessions, displaying and working with host applications simultaneously.• Printing

Rumba AS/400 Printer (3812 emulation) enables you to route jobs from your AS/400 printer queue to aWindows printer of your choice.

For Mainframe hostsWith Rumba Telnet Edition, you can view and print mainframe host applications using two differentmethods, perform a variety of file transfers, and seamlessly share mainframe-based file systems withworkstations.

The following provides brief descriptions of Rumba applications grouped by function.

• Display

Rumba Mainframe Display presents the traditional mainframe display (3278/79) in a Microsoft Windowsapplication: the Rumba window. Includes GDDM.

Users can run multiple host sessions, displaying and working with PC and host applicationssimultaneously.

• Printing

Rumba Mainframe Printer (3287 emulation) presents the traditional IBM 3287 printer functionality in aMicrosoft Windows application.

• File transfer

Rumba Telnet Edition | 103

Rumba Mainframe Display Supports many host file transfer programs including IND$FILE.

Supports ASCII or binary transfers, Write Structured Field or Buffered data streams, EBCDIC-to-ASCIItranslation, and data compression.

For UNIX hostsWith the Telnet edition of Rumba you can view and print UNIX host applications using two differentmethods, perform a variety of file transfers, and seamlessly share UNIX-based file systems withworkstations.


• Display

Rumba UNIX Display presents the traditional VT display in a Microsoft Windows application supportingthe whole range of VT terminals from VT 52 to VT 420 as well as VT340 ReGIS, Sixel, and Tektronix4010/4014 graphics support.

Users can run multiple host sessions, displaying and working with host applications simultaneously.• Printing

Rumba for UNIX Display/Terminal-routed printing prints the display screen, selected text, and full colorgraphics, or routes print jobs from the host printer through your Windows print driver.

• File transfer

Rumba for UNIX Display supports Kermit, Text, and X-, Y-, Z-Modem file transfer protocols.

For HP hostsWith Rumba Telnet Edition you can view HP host applications, print HP applications using two differentmethods, perform a variety of file transfers, and seamlessly share HP-based file systems with workstations.


• Display

Rumba for HP Display presents the traditional HP terminal types in a Microsoft Windows application.

Users can run multiple host sessions, displaying and working with host applications simultaneously.• File transfer and file system sharing

Rumba for HP Display supports Kermit, Text, and X-, Y-, Z-Modem file transfer protocols for UNIXoperating systems.

MPE native file transfer provides a client server file transfer solution allowing users to transfer files to orfrom a HP 3000 using a proprietary Z-modem based protocol. The server side application can bedownloaded to the host via the Rumba host link.

Getting connectedThe procedure for connecting to a remote host or source depends on which application you use. Refer tothe Connecting to a host section of the help for information on configuring a connection.

If you plan to use: Reference

Rumba AS/400 Display Use the Connection Configuration dialog box to configurea Rumba Router TN5250 host link.

104 | Rumba Telnet Edition

If you plan to use: Reference

Rumba Mainframe Display or Printer Use the Connection Configuration dialog box to configurethe TN3270E interface.

Rumba UNIX Display Use the Connection Configuration dialog box to configurean interface.

Rumba HP Display Use the Connection Configuration dialog box to configurethe appropriate interface.

Rumba Telnet Edition | 105

Automating RumbaBy automating complex and common tasks, both you and your users can make Rumba do more for you.You can use either macros or scripts to simplify your work. Macros record a series of actions, such askeystrokes and commands to automate tasks.

If you choose to install the separate Script Editor you can use scripts to automatically manipulate sessions.For example, you could write a script to open a new session and connect to a host.

This section provides you with background information on using macros. Detailed information on theRumba Script Editor can be found in its online help.

Note: One of the easiest and most effective ways to familiarize yourself with Rumba Script Editor/Player capabilities is to run the demo scripts provided with this application. Run one of the script files(such as, demo.csf) to see how a script works. You can also copy a sample script file and edit it tosuit your needs.

Use macros in conjunction with hotspots, custom toolbar buttons, and keyboard shortcuts to completetedious log-on procedures and other common tasks with a single mouse click or key stroke.

For example, distributing macro files and Hotspot libraries to your users provides them with valuableproduction tools that they do not even have to take the time to create.

Creating macrosMacros record a series of actions, such as keystrokes and commands. Once you record a macro, you canplay it back to automate routine tasks. For example, with the click of a button, a macro can connect yourPC to a host, test the return strings, and then start an application.

There are two ways to create a macro:

• Choose Record Macro from the Tools menu or click the icon, and then perform your keystrokes andcommands. Be sure to save the sequence as a macro file after recording.

• Choose Edit Macro from the Tools menu, and then build a sequence of commands with the MacroEditor.

To combine the speed of recording macros with the power of written command lines, record the basics,and then use the Macro Editor to edit and add to the macro sequence. For details about macro commands,see Macro Commands.

Connect and disconnect macrosConnect macros run automatically each time you connect to a host. For example, the connect macro couldcontain commands to enter a User ID and password, choose menu items, and open a host application.You can distribute to your users macros that automatically log them on and take them to the correct hostapplication.

In order for a connect macro to work, the communications interface must be properly configured, and themacro must be saved from within the profile with which it is to be used.

Disconnect macros run automatically each time you disconnect from the host. For example, the disconnectmacro could run another program on the connected host before logging out. It is important to note that, ifyou have a disconnect macro defined, you do not disconnect from the host until after the macro has beenperformed. If you are disconnected from the host because the physical connection has been broken, thenthe disconnect macro does not run.

106 | Automating Rumba

Specifying connect and disconnect macrosAny given profile can have only one connect and one disconnect macro. To specify that a macroautomatically runs upon connecting or disconnecting:

1. From the Tools menu, choose Edit Macro. This opens the Macro Editor dialog box.

2. Select a macro from the Macro Name box.

3. Under the Play Macro On area, check either the Connect or Disconnect box.

4. Select Save from the File menu to save the macro, and close the Macro Editor.

Help topic: Simplifying your work > Automating Tasks > Macros > Creating andediting macros

Macro EditorRecording keystrokes and commands may not always produce the macros you need to accomplishcomplex tasks. When it does not, use the Macro Editor to work with all the macro commands and createcomplex macros using advanced macro features. Appendix A shows the various commands available foreach host.

You cannot record many of the macro commands, such as Pause Macro, Goto Label, Compare Values,Message, and Prompt, because they are not commands or keystrokes. For example, you may need amacro that pauses between two macro commands to give the host enough time to respond.

Copying data between applicationsYou can use Copy From and Paste To commands in the Macro Editor to designate an area of a displayscreen to be copied from one application and pasted into another application. In order to do this you needto specify the application and the location (in terms of rows and columns) from which the data should becopied, and the application and location to which it should be pasted.

Note: If you select Microsoft Excel 97 as the application type when using either the Copy From orPaste To macro, the dialog box changes and you must provide additional information in the File andWorksheet fields.

Automating Rumba | 107

Using variablesVariables are one of the most powerful macro features. Using variables is like writing your own macro-driven application. With variables, you can create interactive macros that respond to user input andperform specific sets of commands.

To open the Variable Setup dialog box:

1. From the Tools Menu choose Edit Macro to open the Macro Editor dialog box.2. Right-click in the macro display area.3. Choose Variable Setup from the popup menu.

In the Variable Setup dialog box, you can select a variable, such as a password or user ID, and define itsvalue based on host screen information, static text, and user input. The variable values are available forthe Type, Message, Compare Values, Goto Label, and Prompt commands.

For example, you could create a prompt dialog box to request a password from a user, and then save it asa variable. The variable containing the user's password is then available for any Type, Compare Value,and Message commands you have included in the macro sequence. For example, you could use aCompare Values command to check the password, and then end the macro or even disconnect the PCfrom the host

Using variables example

The following example shows you how to define a screen variable and use it to execute specific actionsbased on a variable returned by PROFS.

This is a long example, which contains examples of creating several different kinds of macro commands. Ifyou are unfamiliar with macros, we recommend that you create the macro contained in the example tofamiliarize yourself with the macro editor and macro command syntax.

1. Choose Edit Macro from the Tools menu.2. Name the Macro Flow Example.3. Right-click in the macro display area, and choose Variable Setup from the popup menu to open the

Variable Setup dialog box. Click the Variables list box, and choose Variable for screen text.4. From the Variable Types box, choose Screen Variable, if it is not already selected.5. Click the Screen Variable tab.

6. Change the Get text from Column value to 78.7. In the Get how much text? area, click This many characters, and type 3 in the box.8. Click OK to save the settings.

This gets 3 characters from the screen at row 1, column 78 and saves them as a variable that yourmacro can use.

The following steps reference buttons on the toolbar above the macro display area.


1. Open the Goto Label dialog box. Select Variable for screen text from the label list, and click OK.

2. Open the Message dialog box. Type Screen Unknown and click OK.3. Open the Goto Label dialog box. Type Macro End and click OK.4. Open the Label dialog box. Type A00 and click OK.5. Open the Message dialog box. Type PROFS Main Screen and click OK.6. Open the Receive dialog box.7. Type Mail Waiting in the Find text box.8. Under Screen Position, click Only at row, column, and type 24 and 69 in the Row and Column boxes.9. Under Timeout, click Seconds, and type 30 in the box.10.In the Otherwise box, type NoMail, and click OK.11.Open the Message dialog box. Type You have Mail and click OK.12.Open the Label dialog box. Type NoMail and click OK.13.Open the Goto Label dialog box. Type Macro End and click OK.14.Open the Label dialog box. Type C00 and click OK.15.Open the Message dialog box. Type You are on the Open Mail Screen and click OK.16.Open the Goto Label dialog box. Type Macro End and click OK.17.Open the Label dialog box. Type E01 and click OK.18.Open the Message dialog box. Type You are reading a message and click OK.19.Open the Label dialog box. Type Macro End and click OK.20.Add Exit Macro to end of macro.

Your completed macro should look like this:

21.Choose Save from the File menu, and close the Macro Editor

This macro looks at the current PROFS screen and returns a message box containing a description ofwhat was found. You can use this macro as a model to test different macro functions.


Running MacrosThis section assumes that you have created your macros. It tells you and your users how to run thestandard Rumba macros and your custom macros in any of the several ways.

Running standard or custom macros• From the Tools Menu, choose Run Macro or click the icon, and then select the macro you want to run.• Associate a macro with a Hotspot, and then click the Hotspot text on the host screen to run the macro.• Assign a macro to a toolbar button, and then click the button to run the macro.• Link a macro to a keystroke, and then type the keys to run the macro.• Macros can also be run from other macros. When editing the Run application command, select Macro

Files from the Files of Type list. Choose the macro you want to run. When the macro comes to thiscommand, it pauses, runs the new macro, and then runs the remainder of the originating macro.

Each host application type has a default macro directory.

Macros as HotspotsHotspots are words or sentences on the host screen that run macros when clicked. Hotspots add point-and-click capability to host screens, making them more like the other Windows applications. Instead ofrequiring users to master complicated command line statements, you can distribute Hotspot libraries toenable users to click through host screens with fewer errors and more efficiency.

You can find procedures for creating and editing Hotspots in the online help.

Help topic: Simplifying your work > Automating tasks > Using hotspots on host screens > Creatingand editing hotspots

What are HotspotsYou can make any non-protected text on a host screen into a Hotspot and associate that text with anymacro. The host screen shows Hotspots as 3D buttons (see below). When you click a Hotspot button, themacro runs.

For example, you could make the text in a list of options into Hotspots that automatically enter theappropriate option when clicked.


Hotspots are saved in libraries with an .hsp extension. You can create multiple libraries with distinctconfigurations. To use different collections of Hotspots, or to run different macros with the same Hotspottext, users just select the corresponding library.

Creating and distributing Hotspot librariesYou can create whole libraries of Hotspots and distribute them to users. When the user enables Hotspots,the macro runs when the user clicks the Hotspot. The macros used in your Hotspots are saved with theHotspot library, so you do not need to distribute the .hsd files to your users.

Macros on your toolbarsMacros can be linked to toolbar buttons, and incorporated into your standard Rumba Toolbar or placed oncustom toolbars. With custom toolbar macros, your users can accomplish complex key sequences andcommands without errors and without even touching their keyboards.

Help topic: Simplifying your work > Automating tasks > Working with Macros > To assign a macro toa toolbar button

Keyboard macrosIf your users do not like switching between keyboard and mouse as they work, they can link macros tokeystrokes. Without even taking their hands off the keyboard, your users can run the macros you distributewhich create shortcut keys for complex key sequences.

Distributing Keyboard filesThe keyboard files are located in the private directory\hostname\keyboard directory as .map files.To distribute keyboard files, you must distribute the .map file and any corresponding macro files (.rmc& .mac) that are linked to mapped keys. The macro files are located in the private directory\hostname\macros directory.


Macro CommandsThe macro commands available for each host type differ slightly. The following tables list the macrocommands available for each host. Each table lists the macro command, followed by a brief description ofits function.

Mainframe macro commandsAn asterisk (*) indicates macro commands that you cannot record, but can create and edit in the MacroEditor.

Macro Command: Use to:

Connect Connect the PC to the mainframe host

*Compare Values Compare two character strings or variables, and performthe specified commands based on the results

Cursor Position Position the cursor on the host screen

Disconnect Disconnect the PC from the mainframe host

Exit Macro End the macro sequence

File Transfer Receive Receive the specified file transfer

File Transfer Send Send the specified file transfer

*Goto Label Jump to the specified Label command in the macrosequence

Keystroke Send a function key to the host application

*Label Create a marker in the macro sequence to which a GotoLabel command can jump

*Message Show a dialog box with the specified message

*Pause Macro Pause the macro sequence for the specified number ofseconds

*Prompt Create a dialog box that prompts the user for input

Receive Search the host screen for the specified characters

*Run Application Run an application on the local PC

Copy From Copy selected areas of a display screen to the clipboardfor pasting into an application or display screen

Paste To Paste clipboard information to an open application orsession.

Type Send the specified characters or variable to the hostscreen

AS/400 macro commandsAn asterisk (*) indicates macro commands that you cannot record, but can create and edit in the MacroEditor.


Macro command: Use to:

Connect Connect the PC to the AS/400 host


Cursor Position Position the cursor on the host screen

Disconnect Disconnect the PC from the AS/400 host









Copy From Copy selected areas of a display screen to the clipboardfor pasting into an application or display screen

Paste To Paste clipboard information to an open application orsession.



HP and UNIX macro commandsAn asterisk (*) indicates macro commands that you cannot record, but can create and edit in the MacroEditor.


Connect Connect the PC to the UNIX or HP host


Disconnect Disconnect the PC from the UNIX or HP host


File Transfer Receive Receive the specified file transfer

File Transfer Send Send the specified file transfer





Connection ToolsWith Rumba Tools, you have a set of utilities designed to boost your productivity. This section providesoverviews and tips for the most commonly used Rumba Tools.

• Rumba APPC Configuration utility• Administrator Override File• Rumba AS/400 Communications utility• Rumba Communication Monitor

Note: For details on additional Rumba Administrative Tools, see the Rumba Utilities and Advancedsections in the online help.

The following summarizes the purpose and supported hosts for each of these administrator utility.

• Rumba APPC Configuration utility

Simplify the process of creating connections throughout your network.

Applies to mainframe and AS/400.• Rumba Administrator Override File

Implement a single configuration file for multiple users and reduce the time required for setting up andtroubleshooting workstations.

Applies to mainframe and AS/400.• Rumba AS/400 Communications utility

Simplify the process of creating communication sessions throughout your network.

Applies to AS/400.• Rumba Communication Monitor

A workstation-connection monitor you can use to analyze the current status of each configured link.

Applies to mainframe and AS/400.• Rumba Trace Console

Simplify the mechanics of tracing communication sessions to improve your efficiency in troubleshootingand solving network problems.

Applies to mainframe, AS/400 and HP UNIX.

Rumba APPC Configuration toolThe APPC Configuration tool assists you in building a configuration file for the Rumba SNA engine. Thisconfiguration file defines the elements listed below. Each of these elements is discussed in this section.

• Connections• AS/400 modes• Remote and local logical units• CPI-C side information file• Transaction programs• Conversation security

The following figure illustrates the Rumba APPC Configuration utility main display:

Connection Tools | 115

Because the Rumba APPC Configuration utility uses a feature-rich graphical user interface, when youmake an addition, change, or deletion you only need to select a box and click a button.

The Rumba APPC Configuration utility saves configuration parameters in a file with a .cfg extension. Youcan save as many configurations as you need for distribution later, or you can build an administratoroverride configuration file for your users.

With the Rumba APPC Configuration utility, you can set values for different local and remote environments.For Common Programming Interface-Communications, you can add or modify side information entries.You also have the option of assigning User IDs and Passwords to incoming remote transaction programs.

ConnectionsUse the Rumba APPC Configuration utility to name connections and add interfaces quickly and withouterror.

Working in the background, the Rumba APPC Configuration utility creates a local LU name (logical unitname) for your connection from your network name and control point name. As a default, the RumbaAPPC Configuration utility inserts your computer name for the control point name.

The Rumba APPC Configuration utility allows you to easily add an interface connection. The Rumba APPCConfiguration utility’s Connections box uses a simple graphics scheme that allows you to visually identifythe interface used for your connection.

International character set translationThe Rumba APPC Configuration utility works with the international character set specified in the regionalsettings for your workstation. This translation is accomplished using tables that reside in the Program Files\Micro Focus\Rumba\System\Charsets directory after Rumba software is installed.

These tables (referred to as codepage tables) work with Rumba software as follows:

116 | Connection Tools

• The character set that Rumba software uses is determined by the country that is specified on theRegional Settings Properties dialog box. Access this dialog box via the Windows Control Panel.

• EBCDIC to ANSI translation (or mapping) for your workstation is based on the codepage table currentlyin use.

• The Program Files\Micro Focus\Rumba\System\Charsets directory contains files namedchr2exxx.gen, where “XXX” is the locale code (for example, 037 is the code for USA).

To modify the character mapping for a specific language, modify the corresponding chr2exxx.gen file usinga regular text editor. There are no registry settings or .ini file settings to make or change.

AS/400 modesAS/400 mode descriptions define a number of session characteristics. These characteristics include the:

• Maximum number of sessions• Maximum number of conversations• Pacing values for request and response units

By using the mode description as an APPC system object, you can reduce the number of separateconfiguration definitions. The Rumba APPC Configuration utility offers several pre-configured modes.When in doubt, QPCSUPP is the AS/400 default, although #BATCH offers the best compromise incommunication performance and cost.

Remote and local logical unitsThe Rumba APPC Configuration utility simplifies the task of managing remote and local logical units. Alocal logical unit (LU) represents the local workstation, while the remote logical unit represents the localworkstation conversation partner.

• Logical unit properties

Because the concept of the LU has evolved, it is easier to understand the LU by looking at itsproperties:

• Sessions have LUs at each end• To establish a session, a client must have the server’s LU name, which is known as the Remote LU• In a hierarchical network, an LU has a defined global address that it uses to route data• You can assign different LU names to a host’s different subsystems

Note: An LU name does not signify a machine or program name, it designates the role a machineor program has within a network. For example, an LU name can designate a network server.

• Logical unit configuration tips

Here are a few tips to consider when you use the Rumba APPC Configuration utility to add or changelogical units:

• For a computer client, the LU name default can be the computer name. The Rumba APPCConfiguration utility does this automatically in the configuration process.

• For a server, consider using an LU name alias based on the function, rather than the computername. This minimizes disruption if the function is moved to another computer.

• When you are connected to a subarea SNA network, finding an LU name is problematic becauseyou do not have network node services. In this case, you must configure a remote LU and associateit with a route.

CPI-C side information fileThe Rumba APPC Configuration utility gives you a powerful tool that you can use to easily create and editside information files. Previously, when using APPC/LU 6.2 verbs, application programmers had to supply


the parameters that described the network environment. With CPI-C, these parameters are called out froma side information file.

The Rumba APPC Configuration utility uses a straightforward process to create a side information file. Onething to remember is that the side information file is the last part of the configuration process. First youmust define the:

• Network environment• Session characteristics• Remote LU information

Transaction programsYou can add a transaction program by naming and associating it with an executable file or command line.This transaction program (TP) can then have:

• A path to the executable program• An auto-start option• Optimum security• Queueing• Timeouts• PreLaunch Counts

The transaction programs you add with the Rumba APPC Configuration utility should fulfill the APPC/LU6.2 requirements of:

• Being invoked by the LU 6.2 ATTACH call• Using conversations to communicate with a remote transaction program• Establishing many conversations with one or more remote transaction programs using distinct sessions

Conversation securityIf you have secured the local transaction program (TP), use the Rumba APPC Configuration utility’sConversation Security feature to assign user IDs and passwords to incoming TPs.

When an incoming TP attempts to allocate a conversation with the local TP, the local TP reads the User IDand password. If there is a match, the incoming TP is allowed to access the local TP.

Administrator Override FileA high priority for any system administrator is the standardization of system configurations. When youcreate an administrator override file, you provide a set of well-defined parameters that each user canaccess. This tool can significantly reduce the time spent setting up and troubleshooting workstations.

Administrator override file definitionHow does the administrator override file work? An administrator override (Admin Override) file is aconfiguration file you create and then place on the network. Your users can access this administratoroverride file for connection information to SNA-type machines. If the connection information changes, youcan use the administrator override feature to make one central change.

For example, when you introduce a new AS/400 to your network, you only have to add the AS/400information to one administrator override configuration file on your network. The next time a user pulls upthe configuration dialog in the AS/400 display or Rumba APPC Configuration utility, the new AS/400appears, configured and ready to go.


Note: The administrator override file does not contain the control point name that will be used for theconnection; this name comes from the user’s machine.

Administrator override file functionHow does the administrator override file work? The Rumba SNA engine, AS/400 Display, and RumbaAPPC Configuration utility all have the ability to look at two configuration files at the same time and extract,as necessary, pertinent information from each file.

Note: Mainframe connection definitions are not supported by the administrator override file. Tounderstand why this is the case, consider the following:

• Connection definitions for the Rumba Router and AS/400 Display are sharable objects. That is, theparameters for an AS/400 connection definition and the AS/400 Remote LU Definition can becommon to all users globally. The configuration parameters that are specific to a singleworkstation are located in the local LU definition.

• Connection definitions for a mainframe connection are not sharable objects. As an example, for aMainframe Display DLC connection, each user must have an individual and unique PUID as partof the connection definition. If you tried to create an administrator override file for this connection,all users would share a single block ID and PUID, and only one user could connect at a time.

Basically, when you configure connections to an SNA-type server, the Control Point Name (also known asthe “PC Name” in the AS/400 environment) is what makes one workstation unique from anotherworkstation. The administrator override file contains the link information; this includes the network name,destination address, remote LU, side information, and more. Use the local configuration file to storeinformation applicable only to the workstation.

Local connection configurationIf the administrator override file is set, can you still configure connections locally? Yes! You can enableAdmin Override through the Rumba APPC Configuration utility and still create link configurations that youstore on the workstation in a local configuration file. However, there are restrictions. You are able toconfigure local connections only when they have a different connection name and remote LU alias fromany other link residing in the administrator override file. The reason for this is described in the followingsection on the precedence of configuration files.

Also, similar to document printing, the AS/400 display shows only connections configured in theadministrator override file, and the user can connect only to these administrator override configuredconnections.

Configuration files precedenceThe locally-administered configuration file is referenced in the registry as HKEY_LOCAL_MACHINE\Software\WALLDATA\ConfigFile

The configuration files exist so users can provide their configuration preferences within thecommunications environment.

The system-administered configuration file is referenced in the registry key as HKEY_LOCAL_MACHINE\Software\WALLDATA\Sna\AdminOverrideConfigFile.

You can use the administrator override configuration file as a set of configuration elements that willoverride all other configurations. Any configuration element you specify within AdminOverride-ConfigFile will then take precedence over the corresponding element contained in ConfigFile. Thismeans that if collisions occur between the elements of the ConfigFile andAdminOverrideConfigFile, the winner will be the AdminOverrideConfigFile.


For example: if ConfigFile contains an MPTN link definition named NETRED andAdminOverrideConfigFile contains an SDLC link definition named NETRED, thenAdminOverrideConfigFile’s SDLC link definition will replace the ConfigFile’s MPTN link definition.

Administrator override file creationCreating an administrator override file that multiple users can access is not very different than creating alocal configuration file for one user. The only difference is that you store the administrator override file on ashared network drive.

1. From any machine that already has Rumba software installed, configure the necessary connectionsusing the Rumba APPC Configuration utility.

2. Save the file as you normally would for a local machine (note the file name in the title bar).3. Make sure that each connection is valid by connecting to each link configured.4. Once you are confident that you have a working configuration file, copy the file to a shared directory on

the network. Make sure that each intended user has access to this drive.

Note: Change the Administration Override configuration file’s attributes to Read Only: this will preventa user from accidentally corrupting the file.

Editing existing administrator override filesIf an administrator override configuration file is already in place and is currently being accessed by users,we recommend the following as the safest editing method.

1. Using a file manager utility, copy the current administrator override configuration file and rename it.2. Take off the Read-only attribute if it is present, so that the changes you make can be saved.3. From the Rumba APPC Configuration utility menu bar, choose Open. Select your newly created file.

Make changes as necessary.4. Save your new administrator override configuration file.5. Once you are confident that you have a working configuration file, copy the file to a shared directory on

the network and replace the existing administrator override configuration file.

Note: Change the Administration Override configuration file’s attributes to Read Only: this will preventa user from accidentally corrupting the file.

To set user access to administrator override file1. From the Rumba Administrative Tools program group, start the Rumba APPC Configuration utility.

2. From the File menu, choose Advanced.

3. Click Use Administrator Override Configuration.

4. Enter the full path of the Configuration file that you want the users to access. You can also use theBrowse feature to find the file and its path name.

You can ensure that the next person will get the same configuration by using the setting “Makeconfiguration available to all users of this machine.” This will use the \\HKEY\LOCAL_MACHINE\registry instead of the \\HKEY\CURRENT_USER registry.

5. From the File menu, choose Save.

6. Close the Rumba APPC Configuration utility.

When you specify the path, we strongly recommend that you use the Universal Naming Convention (UNC)instead of a mapped drive letter. If you use the UNC, the connection is not reliant on a mapped drive letterthat could be overwritten or corrupted.

Note: If you use the Browse feature, the path is returned in UNC format.


If the Rumba APPC Configuration utility cannot find the file you specified in the path for theadministrator override file, a warning is displayed. The situation may be that the workstation is notcurrently attached to the network, or that the user does not have permission to access the server thatyou specified in the path. If this is the case and you are confident that the path is correct, choose tocontinue and exit.

From the operating system’s ComputerName, the Rumba APPC Configuration utility extracts adefault Control Point Name for the local configuration file. If you wish, you can specify another ControlPoint Name by simply altering the field. Any changes you make to the Control Point Name are alsoautomatically made to the Local LU name.

It is necessary that you use a .cfg extension on the file name. If you do not specify an extension, theRumba APPC Configuration utility will append .cfg to the file name. The Rumba APPC Configurationutility supports both 8.3 format file names and long file names.

Assessing workstation setupIs the workstation you just set up configured properly? The best tool to use in determining if you have setup the workstation correctly is the Rumba Communications Monitor.

If you selected the APPC Client package install, the Rumba Communications Monitor is installed with aprogram icon in the Rumba Administrative Tools program group. If the APPC Client was not installed, theprogram will still be installed, but no icon is placed in the group. If this is the case, you can run the programfrom the Program Files\Micro Focus\Rumba\System subdirectory. The file name is nof.exe.

The Rumba Communications Monitor starts the Rumba SNA engine and displays the information that theRumba SNA engine interprets. If the Rumba Communications Monitor displays the connections that youconfigured in the administrator override file, then you are off to a good start.

Administrator override file limitationsWhile the Rumba SNA engine has the ability to use Rumba administrator override configuration files, theRumba AS/400 display and AS/400 printer are the only display-type services that currently use this feature.

The AS/400 Connection Configuration dialog allows the user to see and connect only to links that youconfigured in an administrator override configuration file. Local files cannot be accessed.

Note: If your company creates transaction programs that use the Rumba SNA engine, then theadministrator override file should work fine.

Configuration-free workstationsWith the Rumba Administrative Tools, you can have self-configuring workstations. By using SMS or abatch file, each new workstation will look for its:

• Administrator override file• Local configuration file

Rumba AS/400 Communications UtilityYou can use the Rumba AS/400 Communications Utility to locate other AS/400 systems and to configureor change host connections and link interfaces for the:

• Application Program Interface (API)• Submit Remote Command application and API


AS/400 Communications Utility overviewWith this utility, the configuration settings are saved in a .ehn file. You can save multiple configurationsunder different .ehn file names for later use. The .ehn configuration file can be especially useful when youare setting up data queues for end users who do not have Rumba AS/400 display or printer capability.

The figure below illustrates the main dialog box of the AS/400 Communications Utility.

The table below maps the major tasks you perform with the AS/400 Communications Config utility to theappropriate tab on the dialog box.

Table 14: Configuration summary

To: Go to the:

Configure communication interfaces Interface tab

Configure link interfaces Interface tab

Add AS/400 sign-ons Security tab

Select a foreign language’s host character set Character tab

Display APPC error messages Diagnostics tab

Note: If you use Rumba AS/400 Communications to configure EHNAPPC, then all non-display andnon-printer sessions will use the same configuration parameters.

For example, if you configure EHNAPPC to connect to BIGSYS via APPC token ring for DataQueues, all other hosts (except for Display, Printer, and possibly RDA) will connect via APPC tokenring.

AS/400 Communications Utility link configurationTo use the Rumba AS/400 Communications Utility to configure links:

1. Click the Interface tab.

2. Select a communications interface, then click Configure.

For specific information on configuring, refer to the help section for the selected interface, found underConnecting to a host.

3. Select a system name, then click Add.

4. Select a link.


5. Click the link interface tab, then add or change configuration values as needed.

6. From the File menu, choose Save, or click the Save icon.

By default, the configuration is saved as an .ehn file.

Click the Advanced tab to specify a logical unit with a name different than your system’s.

Communication MonitorThe Rumba Communication Monitor is a valuable utility that helps you monitor, troubleshoot, and optimizeyour network. Also, you can view non-configured system links.

The Rumba Communication Monitor displays what the Rumba SNA engine finds. The left pane shows thatthe APPN link is not connected and the right pane gives detailed information about the link.

Note: Even though you can use the Rumba Communication Monitor to start and stop links (either bythe menu or by right clicking your mouse), we recommend that in normal circumstances (when youhave a transaction program in process or an open Rumba Display session) you start and stop linksand sessions from your Rumba display session.


Diagnostic and Development ToolsThe diagnostic tools available in the Rumba Administrative Tools folder provide you with a set of powerfuland cost-effective features that are designed to boost your productivity. This section gives you overviewsand tips for the Rumba Trace Console and Rumba Development tools.

Rumba Trace toolThe Rumba Trace tool is a valuable tool that combines several trace options in a common utility. When youare troubleshooting a problem for a user, you can ask the user to trace and record communicationsessions with the Rumba Trace tool. Later, you can selectively play back the binary data file totroubleshoot the problem. This section discusses the following aspects of working with the Rumba Tracetool:

• Application program interface options• Difficult troubleshooting tasks• Display software code version• Playback display and printer data stream trace

By default, all application program interfaces (APIs) are selected for trace, but you can limit trace data andselect only the APIs you want to trace. There are two guidelines for this decision:

• Trace options can have an impact on system performance, so you may want to use the trace APIs asfilters when isolating a known problem.

• When diagnosing a problem, it often requires many types of trace information to effectively investigatethe system state. You may want to select all APIs (default) to capture all available information and directoutput to an unformatted file to send to Micro Focus Technical Support.

Application program interface optionsThe Rumba Trace Console gives you the following API options:

• Mainframe Display Data Stream (DSA)• Mainframe Printer Data Stream (DSA)• AS/400 Display Data Stream (DSA)• AS/400 Printer Data Stream (DSA)• UNIX/HP Display Data Stream (DSA)• SNA Communications (includes APPC, CPI-C, LU 6.2, ACSSVC, and SNA)• Micro Focus EHNAPPC (a standard AS/400 interface for APPC)• Link Layer Communications for all network architecture drivers• Rumba Display APIs (includes DDE, EHLLAPI, and WinHLLAPI)• Host System APIs (includes Submit Remote Command)• Rumba Event Viewer

Note: To view trace data while running the trace, be sure that the Display option is checked on theOptions menu. This is the default setting.

Be aware that only 1000 lines of the most recent data is displayed. Also, note that the formatted file isdistinct from the display file and carries more data. When large amounts of trace data are beingsaved, a larger trace buffer size tends to prevent trace buffer overruns. The default size is 8 MB.

124 | Diagnostic and Development Tools

Difficult troubleshooting tasksWhen there is a network problem, but you do not know what to trace, you can trace all APIs and save thedata in a binary file. Later, this data can be replayed, and you or your support engineers can analyze thesequence of data from API-to-API. With this sequence in hand, you can isolate where the problem isoccurring and then replay the specific API data.

1. Open the Rumba Trace utility.2. From the Rumba Trace Options menu, choose Configuration.

The Configure Tracing Parameters dialog box will be displayed.3. Click Select All.4. Click the Output tab, and then select the Binary File box.5. In the text box under Binary Output, type the path and file name to which you want to save the API

data flow (use the extension *.bin).6. Click OK to close the Configure Tracing Parameters dialog box.7. Reproduce the problem that you are trying to troubleshoot. (For instance, attempt to run the Rumba

software application that is failing to connect properly.)8. From the Rumba Trace Options menu, choose Configuration.9. On the Output tab, clear the Binary File box (turns off the binary option).10.Click the API Selection tab, choose the APIs you want to analyze.11.Click the Advanced tab. Under Binary File Replay, type in the name of the file you saved (or you can

use the browse button to navigate to it).12.Click Replay Now to view the API data flow.

Display software code versionThe Rumba Trace Console contains a useful feature that can give you an all-inclusive software codeversion report that covers .cfg, .dll, .exe, and .ini files.

1. From the Trace menu, choose Options.2. Choose Code Version Snapshot.

If you use this feature, you may want to run it either before or after you complete your trace, because thisreport is extensive and takes time to run.

Playback display and printer data stream traceYou can use Rumba Trace Console to record the AS/400 or Mainframe Display and Printer Data Streams,and then analyze and change this data, including adding rules of behavior on key actions and changinglabels. This feature is especially useful for troubleshooting problems, or when you need to create ademonstration host for training or marketing purposes.

1. Open the Rumba Trace utility.2. From the Rumba Trace Options menu, choose Configuration.3. On the API Selection tab, select a single Display or Printer Data Stream to record.4. Click the Output tab, select the Formatted File box, and then type in the path and name of the file you

want to create (use the extension *.fmt)5. Click OK to close the Configure Tracing Options dialog box.6. Reproduce the problem or demonstrate the Rumba software feature you want to record.7. Close the Rumba Trace utility and then start a Rumba Display or Printer session.8. From the Connection menu, choose Configure, select Demo Host from the Installed Interfaces box,

and then click the Demo Host tab.

Diagnostic and Development Tools | 125

9. In the Script file box, type in the path and name of the file you saved (or you can use the Browsebutton to navigate to it).

10.Click Reconnect to demonstrate the feature or problem you recorded.

Note: The Demo Host can play back only one output file at a time, so make sure that you only chooseone at a time on the API Selection tab of the Configure Tracing Options dialog box.

Rumba TracerRumba Tracer allows users to record information about a program's execution. This information is typicallyused by programmers for debugging purpose. Depending on the type and detail of information contained ina trace log, the information is also used by experienced system administrators or technical supportpersonnel, and software monitoring tools to diagnose common problems with software.

Trace files can be produced by Rumba software components which have been provided with additionalcode for generating binary output trace files. The file can be viewed using the TraceView and tracefmtutilities, which are part of the Windows Driver Kit (WDK), formerly known as the Driver Development Kit(DDK). Only TraceView and tracefmt need to be installed from the WDK.

TraceView A graphical viewer for viewing trace files. In addition to trace files, it requires debuginformation in the shape of .tmf files generated by the Rumba.

Tracefmt Converts binary trace files to text files which can be viewed by any text viewer.

To start tracing:, run command line:

1. Open a command window.2. At the system prompt, enter:

RumbaTrace.cmd start

3. To stop tracing, enter:

RumbaTrace.cmd stop

The binary output trace file is stored in the %temp% folder.

The RumbaTrace.cmd script is part of the Rumba installation and is stored in the Rumba System folder.

Rumba does not require restarting after running RumbaTrace.cmd.

Development ToolsMicro Focus provides the following development tools:

• Rumba Development Edition for .NET FrameWork (RDE .NET):

A set of controls and components that enable developers to build applications which incorporate Rumbadisplays. The Rumba Developer Edition object module was restructured to be more intuitive. It is nowfully integrated into the .NET C# managed code environment exposed through pre-built .Net binaries.The interface introduces a much clearer objects hierarchy with some enumerations extensions forstronger parameters typing, shorter paths to methods and more sharing between session types.

• Rumba Development Add-in for Visual Studio (provided separately):

Provides objects for developers to use in .NET code to add mainframe and AS/400 printing, HLLAPI,macros and FTX functionality to your Visual Studio projects. RDE .NET controls appear in the MicrosoftVisual Studio Toolbox as Mainframe, AS/400, UNIX and HP displays.

The add-in provides objects for developers to use in .NET code to add mainframe and AS/400 printing,HLLAPI,macros and FTX functionality to your Visual Studio projects. The add-in also provides:

126 | Diagnostic and Development Tools

http://msdn.microsoft.com/en-us/windows/hardware/gg487463

• Rumba project templates for different session types• Integration with the Visual Studio Toolbox for adding Rumba RDE.NET functionality with easy drag

anddrop.• A menu item that allows ne-click loading of dozens of examples with full source code included.• Visual Studio code snippets for writing program code more quickly, easily and reliably.• ‘Intellisense’ support whichprovides auto-completion help information and short descriptions for all

properties, methods, interfaces, and enumerations.• RDE Tracer to monitors calls to RDE properties, methods and events for easy application tracking. A

tracer class has been added to each display control, which has two methods: start and stop. Oncestarted, all RDE methods, properties and events used by developers are logged to a log file,together with their respective parameters and returns values, for easy understanding of the RDEprocedures at run time.

• Full documentation of the RDE.NET API with a description of building you first RDE.NET application.

Note: Although RDE controls appear in the Visual Studio Toolbox for Visual Basic, C# and Visual C++ projects, they can be used only for C# and Visual Basic projects .

Diagnostic and Development Tools | 127

Contacting Micro FocusMicro Focus is committed to providing world-class technical support and consulting services. Micro Focusprovides worldwide support, delivering timely, reliable service to ensure every customer's businesssuccess.

All customers who are under a maintenance and support contract, as well as prospective customers whoare evaluating products are eligible for customer support. Our highly trained staff respond to your requestsas quickly and professionally as possible.

Visit http://supportline.microfocus.com/assistedservices.asp to communicate directly with Micro FocusSupportLine to resolve your issues or email [email protected].

Visit Micro Focus SupportLine at http://supportline.microfocus.com for up-to-date support news and accessto other support information. First time users may be required to register to the site.

Information Needed by Micro Focus SupportLineWhen contacting Micro Focus SupportLine, please include the following information if possible. The moreinformation you can give, the better Micro Focus SupportLine can help you.

• The name and version number of all products that you think might be causing an issue.• Your computer make and model.• System information such as operating system name and version, processors, and memory details.• Any detailed description of the issue, including steps to reproduce the issue.• Exact wording of any error messages involved.• Your serial number.

To find out these numbers, look in the subject line and body of your Electronic Product Delivery Noticeemail that you received from Micro Focus.

128 | Contacting Micro Focus

http://supportline.microfocus.com/assistedservices.asp

http://supportline.microfocus.com

PDF FeedbackWe welcome your feedback regarding Micro Focus documentation.

Send feedback about this Help documentation.

Click the above link to email your comments to Micro Focus.

PDF Feedback | 129

mailto:[email protected]?subject=Rumba Documentation Feedback