0RMC InfoExpress UG

Micro Focus
RM/COBOL
RM/InfoExpress User’s Guide

Micro Focus
The Lawn
22-30 Old Bath Road
Newbury, Berkshire RG14 1QN
UK
http://www.microfocus.com
© Copyright 2017-2020 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are as
may be set forth in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial
errors or omissions contained herein. The information contained herein is subject to change without notice.
Revised 2020-05-06 for version 12.17

Contents
Preface ...................................................................................................... 1
Welcome to RM/InfoExpress..................................................................................................... 1
About Your Documentation ....................................................................................................... 1
Related Publications................................................................................................................... 2
Conventions and Symbols.......................................................................................................... 3
Customer Care ........................................................................................................................... 3
Support Guidelines ............................................................................................................. 4
Test Cases ........................................................................................................................... 4
Chapter 1: Installation and Verification ................................................ 7

System Requirements................................................................................................................. 7
RM/InfoExpress Server Program........................................................................................ 7
Required Hardware ...................................................................................................... 7
Required Software ....................................................................................................... 8
RM/InfoExpress Client Program ........................................................................................ 8
Setup and Installation ................................................................................................................. 8
RM/InfoExpress Servers ..................................................................................................... 9
Setting Up the TCP/IP Package for RM/InfoExpress Servers on Windows and UNIX
..................................................................................................................................... 9
Installing RM/InfoExpress Server on Windows ........................................................ 10
Electronic Software Delivery Installation for Windows..................................... 10
CD-ROM Installation ......................................................................................... 11
Installing RM/InfoExpress Server on UNIX ............................................................. 13
Electronic Software Delivery Installation for UNIX .......................................... 13
CD-ROM Installation ......................................................................................... 14
Loading the License File .................................................................................... 14
Mounting the Diskette as an MS-DOS File System .................................... 14
Transferring the Micro Focus License File via FTP from a Windows Client
..................................................................................................................... 15
Loading the Distribution Media ......................................................................... 16
Performing the Installation ................................................................................. 17
Unloading the Distribution Media ...................................................................... 17
RM/InfoExpress Clients ................................................................................................... 18
Setting Up the TCP/IP Package for RM/InfoExpress Clients on Windows and UNIX
................................................................................................................................... 18
Installing RM/InfoExpress Clients on Windows and UNIX ..................................... 18
Verification .............................................................................................................................. 19
Verifying the RM/InfoExpress Server .............................................................................. 19
Windows Server ........................................................................................................ 19
UNIX Server .............................................................................................................. 20
Verifying the RM/InfoExpress Windows Client .............................................................. 21
Verifying RM/InfoExpress Windows Client and Server Communication ........................ 21
Verifying the RM/InfoExpress UNIX Client .................................................................... 24
Verifying RM/InfoExpress UNIX Client and Server Communication ............................. 24
Chapter 2: Configuring and Running the RM/InfoExpress Server ... 27

Server Configuration Options .................................................................................................. 27
Starting the RM/InfoExpress UNIX Server Program .............................................................. 27
UNIX Server Command Line Options ............................................................................. 28
UNIX Server Display Command Line Option .................................................................. 29
Starting and Stopping the RM/InfoExpress Windows Server Program ................................... 29
Starting the Server ............................................................................................................ 29
Stopping the Server........................................................................................................... 30
Configuring the RM/InfoExpress Windows Server Program ........................................... 31
Starting the Server Automatically ............................................................................. 31
Running Under a Specific Log On Account .............................................................. 31
Windows Server Command Line Options ........................................................................ 31
Windows Server Display Command Line Option ............................................................ 32
Chapter 3: Using RM/InfoExpress with RM/COBOL for Windows

Programs ................................................................................................ 33
Accessing the RM/InfoExpress Windows Client Program ...................................................... 33
Pointing to Network Data Files ................................................................................................ 33
Specifying Synonyms ....................................................................................................... 34
Specifying RUNPATH Environment Variables ............................................................... 35
Specifying Explicit Pathnames in the RM/COBOL Program ........................................... 35
Specifying Complete Pathnames Using RM/COBOL Data-Names ................................. 35
Executing RM/COBOL Programs ........................................................................................... 36
Chapter 4: Using RM/InfoExpress with RM/COBOL for UNIX

Programs ................................................................................................ 37
Accessing the RM/InfoExpress UNIX Client Program ........................................................... 37
Pointing to Network Data Files ................................................................................................ 37
Specifying Synonyms ....................................................................................................... 38
Specifying RUNPATH Environment Variables ............................................................... 38
Specifying Explicit Pathnames in the RM/COBOL Program ........................................... 38
Specifying Complete Pathnames Using RM/COBOL Data-Names ................................. 39
Executing RM/COBOL Programs ........................................................................................... 39
Chapter 5: RM/InfoExpress Server Operations .................................. 41

Keyboard Functions ................................................................................................................. 41
Server Display Screen Format ................................................................................................. 42
Server Display Commands ...................................................................................................... 42
Client Information ............................................................................................................ 44
File Information ................................................................................................................ 45
Open Log Information ...................................................................................................... 47
Error Log Information ...................................................................................................... 48
Termination of Communication Activity .......................................................................... 49
Termination of Server Display .................................................................................. 50
Termination of Client Communications .................................................................... 50
Termination of the Server .......................................................................................... 50
Quit When Idle ................................................................................................... 50
Quit in a While ................................................................................................... 51
Quit Now ............................................................................................................ 51
ii RM/InfoExpress User's Guide

Chapter 6: File Security on the RM/InfoExpress UNIX Server .......... 53
UNIX System Security ............................................................................................................ 53
RM/InfoExpress File Security ................................................................................................. 53
RM/InfoExpress UNIX Server Security Levels................................................................ 54
Server-User-Name ..................................................................................................... 55
Default Server User ................................................................................................... 55
.rhosts File Entry........................................................................................................ 56
ixpwfile File Entry ..................................................................................................... 56
User Password ........................................................................................................... 57
Additional Parameters Needed for Non-UNIX Clients .................................................... 57
Client Validation by the Server at Different Security Levels ........................................... 57
Server Compatibility with Older and Newer Clients ........................................................ 57
Older Clients with the New Server ............................................................................ 57
New Clients with an Older Server ............................................................................. 57
Setting Up the Network to Run RM/InfoExpress with Security Enabled ......................... 58
Setup for Running RM/InfoExpress at Server Security Level 0 ................................ 59
Setup Differences Between Server Security Levels .................................................. 64
Appendix A: Messages......................................................................... 67
Error Message Types ............................................................................................................... 67
Permanent Error Types ............................................................................................................ 68
RM/InfoExpress API-Generated Error Codes ......................................................................... 69
RM/InfoExpress-Generated Error Codes ................................................................................. 71
RM/InfoExpress WinSock Error Codes ................................................................................... 75
RM/InfoExpress Windows Sockets Interface Error Codes ...................................................... 77
RM/InfoExpress BSD Sockets Interface Error Codes ............................................................. 78
Appendix B: Limits and Ranges .......................................................... 79

Limits and Ranges ................................................................................................................... 79
Appendix C: Troubleshooting RM/InfoExpress ................................. 81

Failure to Locate File or Path................................................................................................... 81
RM/InfoExpress Client Entries Not Terminating .................................................................... 81
Removing IPC Objects After Server Failure ........................................................................... 82
Appendix D: Configuring RM/InfoExpress ......................................... 83

Configuration Files and Options .............................................................................................. 83
Sample Configuration File ................................................................................................ 84
Common Configuration Options .............................................................................................. 85
Client-Specific Configuration Options .................................................................................... 87
Sample RM/InfoExpress Windows Client Configuration File ......................................... 90
Common Server-Specific Configuration Options .................................................................... 90
UNIX Server-Specific Configuration Options ......................................................................... 92
Sample RM/InfoExpress UNIX Server Configuration File .............................................. 93
Windows Server-Specific Configuration Options.................................................................... 93
Sample RM/InfoExpress Windows Server Configuration File ......................................... 94
RM/InfoExpress User's Guide iii

Appendix E: RM/InfoExpress Security Parameter File Update Utility
................................................................................................................. 97
Using the Utility....................................................................................................................... 97
Adding a New Entry ................................................................................................................ 98
Modifying an Existing Entry ................................................................................................... 99
Deleting an Existing Entry ....................................................................................................... 99
Listing All Entries .................................................................................................................. 100
Appendix F: Using RM/InfoExpress with Relativity ......................... 103

Changes to Relativity Configuration for 32-Bit Windows Clients ........................................ 103
Create a Configuration File............................................................................................. 103
Configure Relativity to Use RM/InfoExpress ................................................................. 104
Appendix G: Summary of Enhancements ........................................ 107

Version 12 Enhancements...................................................................................................... 107
Version 9 Enhancements........................................................................................................ 108
Version 8 Enhancements........................................................................................................ 108
Support for Large Files ................................................................................................... 108
Atomic I/O Support for File Version Level 4 ................................................................. 109
Limited Automatic Session Reconnection ...................................................................... 109
Client Path Prefix Inclusion and Exclusion .................................................................... 110
Version 2.1 Enhancements..................................................................................................... 110
RM/InfoExpress Server Now Supported on Windows NT Version 4.0 ......................... 110
File Security on the RM/InfoExpress UNIX Server ....................................................... 110
New Utility to Update RM/InfoExpress Parameter File ................................................. 110
Improved Server Screens ................................................................................................ 110
Optional Message Compression ..................................................................................... 111
Optional Message Encoding ........................................................................................... 111
Initialization File Support ............................................................................................... 111
-m Server Option Obsolete ............................................................................................. 111
Use Count Check by the Server ...................................................................................... 111
New File Count Option ................................................................................................... 111
New Option to Handle the Display of Long Filenames .................................................. 111
Version 2.0.2 Enhancements.................................................................................................. 112
New Server Option Enables the RM/plusDB Interface .................................................. 112
Version 2.0 Enhancements..................................................................................................... 112
RM/InfoExpress UNIX Server Filename Case-Sensitivity ............................................. 112
RM/InfoExpress UNIX Server Configuration Option .................................................... 112
RM/InfoExpress UNIX Server Runs as a Daemon ......................................................... 112
RM/InfoExpress Screen Handler Program ..................................................................... 112
Changes in the Default Behavior ............................................................................. 113
New Screens ............................................................................................................ 113
More COBOL Information Added to Existing Screens .................................................. 113
Improved Error Handling................................................................................................ 113
KEEPSESSION Configuration Option ........................................................................... 113
Index ..................................................................................................... 115
iv RM/InfoExpress User's Guide

List of Figures
Figure 1: RM/InfoExpress Client WinSock Info Message Box .............................................. 21
Figure 2: Server Display Screen Format ................................................................................. 42
Figure 3: Server Display Main Screen .................................................................................... 43
Figure 4: Client Information Screen ....................................................................................... 44
Figure 5: Client Files Screen ................................................................................................... 45
Figure 6: File Information Screen ........................................................................................... 46
Figure 7: File Clients Screen ................................................................................................... 46
Figure 8: Open Log Screen ..................................................................................................... 47
Figure 9: Open Log Screen (Toggled) .................................................................................... 48
Figure 10: Error Log Screen ................................................................................................... 48
Figure 11: Error Log Screen (Toggled) .................................................................................. 49
Figure 12: Terminate Command Line ..................................................................................... 49
Figure 13: Quit Command Line .............................................................................................. 50
Figure 14: Quit in a While Command Line ............................................................................ 51
Figure 15: Security Parameter File Update Utility Main Screen ............................................ 98
Figure 16: Add Entry Screen .................................................................................................. 98
Figure 17: Modify Entry Screen ............................................................................................. 99
Figure 18: Delete Entry Screen ............................................................................................. 100
Figure 19: List Entries Screen ............................................................................................... 100
List of Tables
Table 1: RM/InfoExpress UNIX Server Security Levels........................................................ 54
Table 2: Summary of Setup Differences Between Server Security Levels ............................. 64
Table 3: Error Types and Associated Error Codes .................................................................. 68
Table 4: Error Codes Generated by Windows Sockets ........................................................... 75
Table 5: Error Codes Generated by the RM/InfoExpress Windows Sockets Interface........... 77
Table 6: Error Codes Generated by the RM/InfoExpress BSD Windows Sockets Interface .. 78
RM/InfoExpress User's Guide v

Welcome to RM/InfoExpress
Preface
Preface
Welcome to RM/InfoExpress
RM/InfoExpress is a file management system designed to optimize RM/COBOL data
file access on various local area networks (LANs) and wide area networks (WANs).
Implementation is available for TCP/IP (Transmission Control Protocol/Internet Protocol).
The RM/InfoExpress User’s Guide is intended for commercial application developers who
have a basic understanding of RM/COBOL, Microsoft Windows, UNIX, and TCP/IP. The
information in this preface outlines the contents of this manual, defines typographic and
programming conventions used in the documentation, and provides information about
obtaining Customer Care.
The new features and significant changes for the most recent release of RM/InfoExpress are
described in Appendix G: Summary of Enhancements (on page 107).
Note The term “Windows” in this document refers to Microsoft 32-bit Windows operating
systems, including Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows
Vista, or Windows Server 2008, unless specifically stated otherwise.
About Your Documentation

The RM/InfoExpress documentation consists of a user’s guide, which is distributed
electronically in Portable Document Format (PDF) as part of the RM/InfoExpress software
distribution. It is also available on the Micro Focus web site at
https://supportline.microfocus.com.
Note To view and print PDF files requires, you need to install Adobe Acrobat Reader, a free
program available from Adobe’s web site at http://www.adobe.com.
This user’s guide is divided into the following parts:
Chapter 1—Installation and Verification lists hardware and software requirements, and
provides procedures for installing RM/InfoExpress on both clients and servers for a specific
LAN or WAN type. Also included are procedures for verifying that both client and server
software are properly installed and communicating with one another.
Chapter 2—Configuring and Running the RM/InfoExpress Server describes the
procedures required to configure and run RM/InfoExpress servers for UNIX and Windows.
RM/InfoExpress User's Guide 1

Related Publications
Preface
Chapter 3—Using RM/InfoExpress with RM/COBOL for Windows Programs describes

how to access the RM/InfoExpress Windows client program, how RM/COBOL for Windows
programs point to network data files, and explains how to execute RM/COBOL for Windows
programs for use with RM/InfoExpress.
Chapter 4—Using RM/InfoExpress with RM/COBOL for UNIX describes how to access
the RM/InfoExpress UNIX client program, how RM/COBOL for UNIX programs point to
network data files, and how to execute RM/COBOL for UNIX programs for use with
RM/InfoExpress.
Chapter 5—RM/InfoExpress Server Operations describes the RM/InfoExpress server
commands. This chapter also describes the information displayed by the server during
RM/InfoExpress execution.
Chapter 6—File Security on the RM/InfoExpress UNIX Server describes the
implementation of file security on the RM/InfoExpress UNIX server.
Appendix A—Messages lists and defines the information and error messages that may be
generated during an RM/InfoExpress session.
Appendix B—Limits and Ranges lists the logical and physical limits and ranges of
RM/InfoExpress.
Appendix C—Troubleshooting RM/InfoExpress describes problems that you may
encounter during an RM/InfoExpress session and provides solutions.
Appendix D—Configuring RM/InfoExpress describes various configuration parameters for
RM/InfoExpress client and server components.
Appendix E—RM/InfoExpress Security Parameter File Update Utility describes how to
use the utility program (ixsecure.cob) to update the parameter file (ixpwfile) with security-
related information that is used by the server to authenticate the clients.
Appendix F—Using RM/InfoExpress with Relativity describes how to access Relativity
files using RM/InfoExpress.
Appendix G—Summary of Enhancements provides an overview of the new features in the
current release, and reviews the changes and enhancements that were added to earlier releases
of RM/InfoExpress.
The RM/InfoExpress User’s Guide also includes an index.
Related Publications
The following documents contain information necessary for a complete understanding of
RM/InfoExpress as used in conjunction with a specific operating system and a local area
network (LAN) or wide area network (WAN):
• RM/COBOL User’s Guide
• Relativity Installation Guides
Contact the appropriate vendor for other publications:

Microsoft products are available from Microsoft Corporation.
2 RM/InfoExpress User's Guide

Conventions and Symbols
Preface
Conventions and Symbols

The following symbols and conventions are used or followed throughout this manual.
1. Text that you enter or that is displayed on your screen is indented and appears in a
monospaced font. This type style is also used for sample command lines, program code
and file listing examples, and sample sessions.
2. Variable information, for which you substitute a specific value, is printed in italics. For
example:
runcobol name [options]
Italic type also identifies the titles of other manuals and the chapter names in this guide,
and occasionally it is used for emphasis.
3. Program names, directory names, filenames, and commands appear in bold type and
lowercase text. You can type program names, directory names, filenames, and
commands in uppercase or lowercase letters, except where otherwise stated.
Bold type is also used for emphasis on some types of lists, and for anything you must
type exactly as it appears.
4. Key combinations are connected by a plus sign (+), for example, Ctrl + X. This notation
indicates that you press and hold down the first key while you press the second key. For
example, “press Ctrl + X” indicates to press and hold down the Ctrl key while pressing
the X key. Then release both keys.
5. RM/COBOL Compile and Runtime Command line options may be specified either with
or without a hyphen. If any option on a command line is preceded by a hyphen, then a
leading hyphen is required for all options. When assigning a value to an option, the equal
sign is optional if leading hyphens are used.
6. Note the distinction of the following terminology:
• The term “window” refers to a delineated area of the screen, normally smaller than
the full screen.
• In this document, the term “Windows” refers to the following Microsoft 32-bit
Windows operating systems: Microsoft Windows 2000, Windows XP, Windows
Server 2003, Windows Vista, or Windows Server 2008, unless specifically stated
otherwise.
Note
• Beginning with version 11, RM/InfoExpress no longer supports earlier Microsoft
Windows operating systems, including Microsoft Windows 98, Windows 98 SE,
Windows Me, and Windows NT 4.0.
Additionally, in this document, any references to those versions, or to the shorthand
notation “Windows 9x-class” or “Windows NT-class” referring to those operating
systems, are included for historical purposes only.
Customer Care
Micro Focus is dedicated to helping you achieve the highest possible performance from the
Micro Focus family of products, including RM/COBOL. The Micro Focus Customer Care

Customer Care
Preface
team is committed to providing you prompt and professional service when you have problems
or questions about your Micro Focus products.
Support is subject to Micro Focus’ prices, terms, and conditions in place at the time the
service is requested.
While it is not possible to maintain and support specific releases of all software indefinitely,
we offer priority support for the most current release of each product. For customers who
elect not to upgrade to the most current release of the products, support is provided on a
limited basis, as time and resources allow.
Support Guidelines
When you need assistance, you can expedite your call by having the following information
available for the Micro Focus Customer Care representative:
1. Company name and contact information.
2. Micro Focus RM/COBOL product serial number (found in the Electronic Software
Delivery email, on the media label, or in the product banner message).
3. Product version number.
4. Operating system and version number.
5. Hardware, related equipment, and terminal type.
6. Exact message appearing on screen.
7. Concise explanation of the problem and process involved when the problem occurred.
Test Cases
You may be asked for an example (test case) that demonstrates the problem. Please
remember the following guidelines when submitting a test case:
• The smaller the test case is, the faster we will be able to isolate the cause of the problem.
• Do not send full applications.
• Reduce the test case to the smallest possible combination of components required to
reproduce the problem.
• If you have very large data files, write a small program to read in your current data files
and to create new data files with as few records as necessary to reproduce the problem.
• Test the test case before sending it to us to ensure that you have included all the
necessary components to recompile and run the test case. You may need to include an
RM/COBOL configuration file.
When submitting your test case, please include the following items:
1. README text file that explains the problems. This file must include information
regarding the hardware, operating system, and versions of all relevant software (including
the operating system and all Micro Focus products). It must also include step-by-step
instructions to reproduce the behavior.
2. Program source files. We require source for any program that is called during the
course of the test case. Be sure to include any copy files necessary for recompilation.

Customer Care
Preface
3. Data files required by the programs. These files should be as small as possible to
reproduce the problem described in the test case.

System Requirements
Chapter 1: Installation and Verification
Chapter 1: Installation and

Verification
This chapter lists the hardware and software required to use RM/InfoExpress for TCP/IP
(Transmission Control Protocol/Internet Protocol), detailing the differences between the
server and client program requirements. Chapter 1 also provides instructions for setting up
and installing RM/InfoExpress on Windows and UNIX, and outlines procedures for verifying
that RM/InfoExpress is properly installed.
System Requirements
This section describes the requirements necessary for installing the RM/InfoExpress server
and client components. The version of RM/InfoExpress that you have purchased is for a
particular combination of hardware and operating systems. Several items listed below vary
depending on the actual version of the product that you have purchased.
Before you can use RM/InfoExpress, your personal computer configuration must meet or
exceed the requirements set forth in this section.
RM/InfoExpress Server Program

The following sections list the minimum hardware and software requirements for running the
RM/InfoExpress server program.
Required Hardware
One of the following hardware systems is required to install the RM/InfoExpress server
program:
• An IBM PC or compatible machine capable of running Microsoft Windows 2000 Server
(SP3 or later), Microsoft Windows Server 2003, or Microsoft Windows Server 2008.
• A machine capable of running a supported UNIX or Linux operating system.
Note Most Micro Focusproducts are distributed electronically. If you elect to receive
physical media, an optical drive capable of reading a CD-ROM (for the product) and a 3.5”
floppy drive (for the license) are required at installation time.

Setup and Installation
Required Software
The RM/InfoExpress server program is supported on the following operating systems:
• Microsoft 32-bit Windows servers:
− Windows 2000 Server (SP3 or later)
− Windows Server 2003
− Windows Server 2008
• UNIX (or UNIX-based) servers:
− HP-UX 11
− IBM AIX 5.2
− Intel UNIX System V Release 4
− Linux (2.6 kernel or later, 32-bit and 64-bit)
− SCO OpenServer 5
− SCO SVR5 (UnixWare 7.1.1 or later and SCO OpenServer 6)
− Sun Solaris SPARC (2.9) and Intel x86 (2.9)
RM/InfoExpress consists of two server programs:

• The RM/InfoExpress for Microsoft 32-bit Windows server software contains the
following files:
− the main program, rmsrvtcp.exe
− the server display (or screen handler) program, rmdistcp.exe
• The RM/InfoExpress for UNIX server software contains the following files:
− the main program, rmservertcp
− the server display (or screen handler) program, rmdisptcp
− a file security parameter file update utility program, ixsecure.cob
RM/InfoExpress Client Program

By default, the RM/InfoExpress client program (rmtcp32.dll on Windows or librminfox.so
on UNIX) is installed by the standard installation procedure for RM/COBOL for Windows
and RM/COBOL for UNIX. The hardware and software system requirements for the
RM/InfoExpress client program are exactly the same as the system requirements for the
RM/COBOL runtime system (runcobol). For more information, see the appropriate chapters
on installation and system considerations for UNIX and Microsoft Windows in the
RM/COBOL User's Guide.

The section includes setup guidelines and instructions for installing the RM/InfoExpress
server and client components.

The RM/InfoExpress for TCP/IP media contains a number of individual files and programs.
The media contains a README file, which lists the actual files and programs delivered. For
a list of known problems and recovery tips, refer to the section “Problems in This Release” in
the README file.
Note The RM/InfoExpress server software should be installed only on the machine on which
it is to run. If appropriately licensed, the RM/COBOL runtime system with the
RM/InfoExpress client software may be installed on a UNIX server machine or a Windows
server machine.
RM/InfoExpress Servers
This section describes how to set up and install the RM/InfoExpress server software on 32-bit
Windows servers and UNIX server machines.
Setting Up the TCP/IP Package for RM/InfoExpress Servers on

Windows and UNIX
Before you install the RM/InfoExpress server program, you must first ensure that the
complete TCP/IP package has been installed and set up on your Windows and UNIX server
machines.
Make certain that the hosts and services files are included. On Windows, these files are
usually in the \windows-directory\system32\drivers\ directory, where windows-directory is
the name of the directory where Windows is installed. On UNIX, the files are usually named
/etc/hosts and /etc/services.
• The hosts file lists the IP (Internet Protocol) addresses and host name(s) of all machines
(clients and servers) that are connected to your network. As an alternative to using a
hosts file on every machine, you can use DSN (Domain Name Service). One machine or
a few machines run DNS; all of the other machines on the network access DNS to resolve
names to IP addresses.
CAUTION On some machines, the RM/InfoExpress server program may terminate
with a “Signal (11) caught” (segmentation fault) error message when accessed by a
client if the /etc/hosts file on the server machine does not contain the entries required
by RM/InfoExpress. The client would most likely receive a “COBOL I/O error 30,
Runtime Library error 12006.” The solution to the problem is to add the entries to the
/etc/hosts file.
• The services file lists the service name and port number/protocol of all available services.
The rmaddsvc program will update the services file during setup in order to add the
following line:
RMCFileServer 21069/tcp
No other line may contain RMCFileServer (in any mixture of uppercase or lowercase
letters), and no other line may contain the port number 21069. If port number 21069 is
already in use, select another unused port number. We recommend that you choose a
port number between 5000 and 32000.
Note The user must ensure that the RMCFileServer line in the services file is identical
on every machine (clients and servers) on the network.

Installing RM/InfoExpress Server on Windows

You can install the RM/InfoExpress server program on Windows by using the following
methods:
• Electronic Software Delivery Installation for Windows (as described below)
• CD-ROM Installation (on page 11)
To verify that the installation was successful, see Verifying the RM/InfoExpress Server
(on page 19) and Verifying RM/InfoExpress Windows Client and Server Communication (on
page 21).
Electronic Software Delivery Installation for Windows
Note You must have an Internet connection and an Internet browser installed to proceed with
this latter method of installation.
The email containing notification of your Electronic Software Delivery contains an
attachment, a file named liant.lic. This file is a license certificate authorizing you to install
the purchased software. We recommend that you create a directory on your machine to store
the license certificates for your Micro Focus products and save the liant.lic attachment to this
directory with a name that is meaningful to you.
The RM/InfoExpress server program is available as a download from the Micro Focus
Electronic Software Delivery web site in two formats: Windows Self-Extracting EXE and
ISO CD Image. From the web site, simply follow the download and decompress instructions
for the file format selected, and then perform the installation instructions for that format, as
outlined below.
• Windows Self-Extracting EXE. After downloading and decompressing the
deliverables, and creating the installation components directory from the Windows
Self-Extracting EXE format, follow these steps to install the RM/InfoExpress server
program on Windows:
Note When the Windows Self-Extracting EXE is decompressed and the installation
components directory is created, the RM-Install program should start automatically. If
this is the case, proceed to step 6. Otherwise, begin with step 1. Be sure to login as
Administrator and close any other applications that may be running before you begin.
1. Place a copy of your RM/InfoExpress license certificate, liant.lic, in the directory
containing the installation components.
2. Click Start, and then click Run. In the Run dialog box, click the Browse button.
3. In the Browse dialog box, navigate to the directory containing the installation
components.
4. Click on the file, RM-Install, and then click Open.
5. In the Run dialog box, click OK.
6. The RM-Install program begins executing. Follow the instructions presented on the
screen and press the Next button to advance through the various pages.
7. On the Software License Agreement page, you must click “I accept the terms in the
license agreement” in order to continue with the installation.
8. On the License Certificates page, the license certificate file for the product being
installed is displayed. Do one of the following:

• If the license certificate for RM/InfoExpress server software being installed is

present in the list area, press the Next button.
• If the license certificate for the RM/InfoExpress server software being installed
is not present in the list area:
a. Press the Add button.
b. In the Select License Certificates dialog box, navigate to the directory
containing the license certificate file for the RM/InfoExpress server
software being installed and select the filename for the license certificate.
(This license file, named liant.lic, is attached to the original electronic
software delivery email for the product.)
c. Press the Open button and then press Next.
9. On the Installation Type page, do one of the following:
• Select the “Standard Installation” option to install all the components of all the
license certificates listed on the License Certificates page immediately, using
their default settings. Press the Install button.
• Select the “Custom Installation” option to select specific components (for those
products with multiple components) of all license certificates listed on the
License Certificates page, and install them, changing their default installation
settings, as necessary.
Follow the custom installation instructions presented on the remaining pages.
On the Ready to Begin Installations page, press the Install button.
When the installation for the RM/InfoExpress server components starts, follow
the additional instructions presented by the installation program.
10. When either the standard or custom installation is complete, click the Finished
button on the Installation Status page.
Note The RM/InfoExpress server is installed and run as a Windows service.
• ISO CD Image. The download format for ISO CD Image contains the full
RM/InfoExpress product CD. Use CD-ROM Burning software, such as Nero
(http://www.nero.com) or Roxio’s Easy CD Creator (http://www.roxio.com), to create the
physical CD-ROM media. Follow the instructions described in CD-ROM Installation
(on page 11) to install your product.
CD-ROM Installation
After downloading and decompressing the deliverables, and creating the installation
components directory from the ISO CD Image format, follow these steps to install the
RM/InfoExpress server program on Windows:
1. Log in as Administrator. Micro Focus also recommends that you close any other
applications that may be running.
2. Insert the RM/InfoExpress Server Program CD-ROM in the appropriate CD-ROM drive.
3. Do one of the following:
• If the installation program starts automatically, proceed to Step 4.
• If the installation program does not start automatically, click Start, and then click
Run. In the Open text box of the Run dialog box, type the following:

d:RM-Install
where, d is the drive letter of the CD-ROM drive. Click OK.

4. The RM-Install program begins executing. Follow the instructions presented on the
screen and press the Next button to advance through the various pages.
5. On the Software License Agreement page, you must click “I accept the terms in the
license agreement” in order to continue with the installation.
6. On the License Certificates page, the license certificate for the product being installed is
displayed. Do one of the following:
• If the license certificate for the RM/InfoExpress server software being installed is
present in the list area, press the Next button.
• If license certificates for any products you do not wish to install are present in the list
area, select them and press the Remove button. Then, press the Next button.
• If the license certificate for the RM/InfoExpress server software being installed is not
present in the list area:
a. Press the Add button.
b. In the Select License Certificates dialog box, navigate to the directory
containing the license certificate file for the RM/InfoExpress server software
being installed and select the filename for the license certificate.
This license file, usually named liant.lic, is included on the license diskette that
came as part of the installation media.
c. Press the Open button and then press Next.
Note The liant.lic license certificate file can be copied from the diskette to a
location on a hard drive and that location can be specified during installation. We
recommend that you create a separate directory on your machine to store the license
certificate files for all of your Micro Focus products and save those files with a name
that is meaningful to you.
7. On the Installation Type page, do one of the following:
• Select the “Standard Installation” option to install all the components of all the
license certificates listed on the License Certificates page immediately, using their
default settings. Press the Install button.
• Select the “Custom Installation” option to select specific components (for those
products with multiple components) of all license certificates listed on the License
Certificates page, and install them, changing their default installation settings, as
necessary.
Follow the custom installation instructions presented on the remaining pages. On the
Ready to Begin Installations page, press the Install button.
When the installation for the RM/InfoExpress components starts, follow the
additional instructions presented by the installation program.
8. When either the standard or custom installation is complete, click the Finished button on
the Installation Status page.
Note The RM/InfoExpress server is installed and run as a Windows service.

Installing RM/InfoExpress Server on UNIX

You can install the RM/InfoExpress server program on UNIX by using the following
methods:
• Electronic Software Delivery Installation for UNIX (as described below)
• CD-ROM Installation (on page 14)
To verify that the installation was successful, see Verifying the RM/InfoExpress Server
(on page 19) and Verifying RM/InfoExpress UNIX Client and Server Communication (on
page 24).
Electronic Software Delivery Installation for UNIX
Note You must have an Internet connection and an Internet browser installed to proceed with
this latter method of installation.
The email containing notification of your Electronic Software Delivery contains an
attachment, a file named liant.lic. This file is a license certificate authorizing you to install
the purchased software. We recommend that you create a directory on your machine to store
the license certificates for your Micro Focus products and save the liant.lic attachment to this
directory with a name that is meaningful to you.
The RM/InfoExpress server program is available as a download from the Micro Focus
Electronic Software Delivery web site in two formats: UNIX GUNZIP TAR and ISO CD
Image. From the web site, simply follow the download and decompress instructions for the
file format selected, and then perform the installation instructions for that format, as outlined
below.
• UNIX GUNZIP TAR. After downloading and decompressing the deliverables, and
creating the installation components directory from the UNIX GUNZIP TAR format,
follow these steps to install the RM/InfoExpress server program on UNIX:
1. Place a copy of your RM/InfoExpress license certificate, liant.lic, in the directory
containing the installation components.
2. Change to the directory containing the installation components. For example, enter:
cd /RMStage
3. Execute the installation script using the following command:
sh ./install.sh
4. Follow the prompts and instructions on the screen to complete the installation.
Messages are displayed periodically indicating the status of the installation.

RM/InfoExpress is distributed with a default configuration that will satisfy your system
requirements. Additional configuration options for your system are discussed in
Appendix D: Configuring RM/InfoExpress (see page 83).
• ISO CD Image. The download format for ISO CD Image contains the full
RM/InfoExpress product CD. Use CD-ROM Burning software, such as Nero
(http://www.nero.com) or Roxio’s Easy CD Creator (http://www.roxio.com), to create the
physical CD-ROM media. Follow the instructions described in CD-ROM Installation
(see the following section) to install your product.

CD-ROM Installation
There are four main steps to installing the RM/InfoExpress server program for UNIX from the
downloaded format of the ISO CD image:
1. Load the license file (see the following topic).
2. Load the distribution media (see page 16).
3. Perform the installation (see page 17).
4. Unload the distribution media (see page 17).
Loading the License File
The Micro Focus license file, liant.lic, is a normal text file distributed on an MS-DOS-
formatted diskette. This file is a license certificate authorizing you to install the purchased
software. Not all UNIX operating systems, however, can read an MS-DOS-formatted
diskette, and not all UNIX server machines have diskette drives. To make the license file
available to the RM/InfoExpress server for UNIX installation script, two techniques are
provided:
1. Mounting the diskette as an MS-DOS file system (see the following topic).
2. Transferring the Micro Focus license file via FTP from a Windows client (see page 15).
Mounting the Diskette as an MS-DOS File System
Use this option to load the license file if the UNIX operating system supports MS-DOS file
systems and your hardware has a diskette drive installed. Instructions for specific platforms
and versions of UNIX are provided. In the examples below, the license certificate file,
liant.lic, is placed in the directory /tmp. We recommend, however, that you create a
directory on your machine to store the license certificates for your Micro Focus products and
save the liant.lic file to this directory with a name that is meaningful to you.
• HP-UX 11, IBM AIX 5.2, and Intel UNIX System V Release 4. These platforms do not
support mounting MS-DOS diskettes. To transfer the license file to the UNIX server, use
the FTP instructions (see page 15).
• Linux (kernel 2.6)

a. Insert the diskette into the diskette drive.
b. Log in as root and enter:
mount –t msdos /dev/fd0H1440 /mnt/floppy
c. Copy the license file to the /tmp directory:
cp /mnt/floppy/liant.lic /tmp/liant.lic
d. Dismount the diskette with the following command and then remove the diskette
from the diskette drive:
umount /mnt/floppy
• SCO OpenServer 5


mount –f DOS,lower /dev/fd0 /floppy
Note It may be necessary to create the mount directory, /floppy, before executing
this command.
cp /floppy/liant.lic /tmp/liant.lic
umount /floppy
• SCO SVR5 (UnixWare 7.1.1 or later and SCO OpenServer 6)

mount –F dosfs /dev/dsk/f0q18dt /Disk_A
cp /Disk_A/liant.lic /tmp/liant.lic
umount /Disk_A
• Sun Solaris SPARC (2.9) and Intel x86 (2.9)

volcheck
cp /floppy/liant/liant.lic /tmp/liant.lic
eject floppy
Transferring the Micro Focus License File via FTP from a Windows Client
To transfer the Micro Focus license file, liant.lic, from a Windows client to the UNIX server,
use one of the many graphical FTP utilities available on Windows and transfer the liant.lic

file as a text file. You can also follow the procedure described below. We recommend that
you create a directory on your machine to store the license certificates for your Micro Focus
products and save the liant.lic file to this directory with a name that is meaningful to you
1. On the Windows client, insert the diskette into the diskette drive.
These instructions assume that this is drive A. If it is another drive, change the drive
letter to the appropriate letter in the remaining instructions.
2. Open a Command Prompt window by clicking Start on the task bar, point to Programs,
point to Accessories, and then click Command Prompt.
3. Connect to the UNIX server by entering:
ftp UnixServerName
where, UnixServerName is the network name of your UNIX server.

4. Change the directory to the /tmp directory:
cd /tmp
5. Specify a text file transfer:
ascii
6. Send the license file to the UNIX server:
send A:\LIANT.LIC liant.lic
7. Disconnect from the UNIX server:
bye
8. Close the Command Prompt window with the following command and then remove the
diskette form the diskette drive:
Exit
Loading the Distribution Media
To load the distribution media on the UNIX machine:

1. Insert the RM/InfoExpress server for UNIX CD in the appropriate CD-ROM drive.
2. Log in as root.
3. Enter the appropriate mount command for your system. See the examples listed below.
Notes
• In the list that follows, /cdrom is used as the mount directory name for all the UNIX
operating systems. Some UNIX systems, however, already have an established mount
directory for the CD-ROM. In this case, substitute the standard mount directory name for
/cdrom in the following list and in the subsequent instructions.
• The device names below are examples. The actual device name is dependent on the
hardware configuration of your UNIX server. It may be necessary to substitute the

proper value for your system. If needed, consult your UNIX System Administrator for
more details.
System Mount Command
HP-UX 11 mount –F cdfs –o ro,cdcase /dev/dsk/c0t4d0 /cdrom
IBM AIX 5.2 mount –o ro –v cdrfs /dev/cd0 /cdrom
Intel UNIX System V mount –o ro –F cdfs /dev/cdrom/c0t4l0 /cdrom

Release 4
Linux (2.6 kernel) mount –o ro –t iso9660 /dev/cdrom /mnt/cdrom
SCO OpenServer 5 mount –o ro –f ISO9660,lower /dev/cd0 /cdrom
SCO SVR5 mount –F cdfs –o ro /dev/cdrom/c1b0t0l0 /CD-ROM_1

(UnixWare 7.1.1 or later
and SCO OpenServer 6)
Sun Solaris SPARC (2.9) If Solaris does not automatically load the CD-ROM, log in as root
and Intel x86 (2.9) and enter: volcheck
Performing the Installation
After the CD-ROM has been successfully mounted, you will need to do the following:
1. Change the directory to the mount point for the CD-ROM. For example, enter:
cd /cdrom
2. From the mount point, execute the installation script using the following command:
sh ./install.sh
3. Follow the prompts and instructions on the screen to complete the installation.
Messages are displayed periodically indicating the status of the installation.
Unloading the Distribution Media
To unload (remove) the distribution media from the hardware:

1. Change your directory to a location other than the CD-ROM mount point directory, as
described in Loading the Distribution Media (on page 16).
2. Enter the appropriate command for your system. See the examples listed below.
3. Remove the distribution media from the CD-ROM drive.
System Umount Command
HP-UX 11 umount /cdrom

IBM AIX 5.2
Intel UNIX System V Release 4
SCO OpenServer 5

Linux (2.6 kernel or later) umount /mnt/cdrom
SCO SVR5 (UnixWare 7.1.1 or later umount /CD-ROM_1

and SCO OpenServer 6)
Sun Solaris SPARC (2.9) eject cdrom

and Intel x86 (2.9)
RM/InfoExpress Clients
This section describes how to set up and install the RM/InfoExpress client software on
Windows and UNIX workstations.
Setting Up the TCP/IP Package for RM/InfoExpress Clients on

Windows and UNIX
In order for RM/InfoExpress clients to access the RM/InfoExpress server, you must make
sure that you have installed and configured the TCP/IP communication protocol package
correctly on 32-bit Windows and UNIX client workstations.
For both Windows and UNIX implementations, you may need to modify the hosts file and
services file:
• The hosts file lists the IP (Internet Protocol) addresses and host name(s) of all machines
(clients and servers) that are connected to your network. As an alternative to using a
hosts file on every machine, you can use DNS (Domain Name Service). One machine or
a few machines run DNS; all of the other machines on the network access DNS to resolve
names to IP addresses.
• The services file lists the service name and port number/protocol of all available services.
On Windows, you must locate and edit the services file for your Windows Sockets
implementation to add the following line, whereas on UNIX, the rmaddsvc program will
automatically update the services file during setup:
RMCFileServer 21069/tcp
Verify that no other line contains RMCFileServer (in any mixture of uppercase or
lowercase letters) and that no other line contains the port number 21069. If port number
21069 is already in use, select another unused port number. We recommend that you
choose a port number between 5000 and 32000.
Note The user must ensure that the RMCFileServer line in the services file is identical
on every machine (clients and servers) on the network.
Installing RM/InfoExpress Clients on Windows and UNIX

The RM/InfoExpress Windows 32-bit client program (rmtcp32.dll) is installed by default
when you select the “Standard Installation” option when installing RM/COBOL for Windows.
However, if you did not install it, run the RM/COBOL installation procedure again, selecting
the “Custom Installation” option to install only the RM/InfoExpress Client feature. If you
wish to run the client verification program, choose the Verification Suite option also. To

Verification
verify that the installation was successful, see Verifying the RM/InfoExpress Windows Client
(on page 21).
The RM/InfoExpress UNIX client program (librminfox.so) is installed by default with
RM/COBOL for UNIX. The RM/COBOL for UNIX runtime uses the librminfox.so support
module (a shared object) to provide access to the RM/InfoExpress server. To verify that the
installation was successful, see Verifying RM/InfoExpress UNIX Client and Server
Communication (on page 24).
Verification
For both the RM/InfoExpress client and server software components, the first step in system
verification is to confirm that the TCP/IP network software is running correctly on the client
machine as well as the server machine.
For RM/InfoExpress client verification, follow all the vendor’s recommendations making sure
you have properly configured the TCP/IP network and that the software is running correctly.
System utilities, such as ping, can help ensure proper configuration and/or communication
between the client and server machines.
Verifying the RM/InfoExpress Server

The following procedures verify that the RM/InfoExpress server programs have been installed
correctly for 32-bit Windows and UNIX operating systems, and that they can run properly.
Note Only one RM/InfoExpress server program may be active on any given server machine.
Windows Server
The RM/InfoExpress server for Windows is installed as, and is intended to be run as, a
Windows service, under the direction of the Windows Service Control Manager (SCM).
Initially, the server is configured to be started and stopped manually. However, it can easily
be reconfigured to start automatically when Windows is initialized, as described in
Configuring the RM/InfoExpress Windows Server Program (on page 31).
Note For information on specifying server configuration options on Windows, see the
following topics:
• Windows Server Command Line Options (on page 31)
• Windows Server Display Command Line Option (on page 32)
• Appendix D: Configuring RM/InfoExpress (on page 83)
To start the RM/InfoExpress server for Windows:

1. Click Start on the task bar.
2. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, start the
Windows Service Control Manager:
a. Click Run.
b. In the Open text box of the Run dialog box, type the following and then click OK:

Verification
services.msc
c. Select RM/InfoExpress Server in the list of services.

d. To start the service, press the Start the service link located to the left, or right-click
over the service name and select Start from the pop-up menu.
These actions will launch the RM/InfoExpress server program for Windows, which
initially runs under the System account and has access to any resources that this account
is permitted to use. (Most systems log on to a System account, rather than a user
account.) To change the account under which the server program runs, see Configuring
the RM/InfoExpress Windows Server Program (on page 31).
3. In the RM/InfoExpress folder, double-click the rmdistcp icon to start the
RM/InfoExpress server display program.
The RM/InfoExpress server main screen is displayed, as illustrated in Figure 3: Server
Display Main Screen (see page 42). The server is ready to process requests from client
machines.
Note The RM/InfoExpress Windows server display program, rmdistcp.exe, monitors
the server activity and does not affect the communication between the client and server.
If the server main screen does not appear, check that no other RM/InfoExpress server program
is already running on the machine. If other messages are displayed, contact Micro Focus
Customer Care.
Note The RM/InfoExpress Windows server program can also be launched in user mode using
the icon created by default in the RM/InfoExpress program folder. To start the server, simply
double-click on the RM/InfoExpress Windows server icon. The server will run using the
current account and will be terminated when you log out. When launched in this mode, there
is also a small, 10- to 20-second delay before the server becomes active.
UNIX Server
On the UNIX server machine, start the RM/InfoExpress UNIX server and server display
programs, rmservertcp and rmdisptcp, by entering the following commands:
/usr/rminfox/rmservertcp
/usr/rminfox/rmdisptcp -t

Display Main Screen (see page 42). The server is ready to process requests from client
machines. If the server main screen does not appear, check that no other RM/InfoExpress
server program is already running on the machine. If other messages are displayed, contact
Micro Focus Customer Care.
Note For information on specifying server configuration options on UNIX, see the
following topics:
• UNIX Server Command Line Options (on page 28)
• UNIX Server Display Command Line Option (on page 29)
• Appendix D: Configuring RM/InfoExpress (on page 83)

Verification
Verifying the RM/InfoExpress Windows Client

If you choose both the RM/InfoExpress Client and Verification Suite features when installing
RM/COBOL for Windows, a program-item icon labeled ixverify is created in the
RM/COBOL program folder. Choose this icon to invoke the RM/InfoExpress Windows
client verification program. The RM/InfoExpress Client WinSock Info message box is
displayed in the center of the screen, as illustrated in Figure 1.
Figure 1: RM/InfoExpress Client WinSock Info Message Box
If no message box appears, the RM/InfoExpress Windows client software is not properly
installed or started. Check that the RM/InfoExpress Windows client DLL file (rmtcp32.dll)
exists in your application installation directory.
Note This client verification does not attempt to connect to any server. It simply verifies that
the Windows Sockets implementation is sufficient to allow the RM/InfoExpress Windows
client DLL to be loaded and run.
Verifying RM/InfoExpress Windows Client and Server

Communication
The following procedures verify that the RM/InfoExpress Windows client program can
correctly communicate with the RM/InfoExpress server program using the TCP/IP
communication protocol. We recommend that you first read Chapter 3: Installation and
System Considerations for Microsoft Windows, in the RM/COBOL User’s Guide, for more
information.
1. Start the RM/InfoExpress server program running on the server machine, as described in
Verifying the RM/InfoExpress Server (on page 19).
2. Select the RM/COBOL folder from the Windows desktop.
3. Copy the RM/COBOL Runtime folder icon to a new icon:
a. Choose the RM/COBOL Runtime icon by clicking the mouse pointer on the icon.
b. Right-click the RM/COBOL Runtime icon and choose the Copy option from the
menu.
c. Move the mouse pointer to a new location, right-click, and choose the Paste option
from the menu.
Note An alternative procedure to Steps 3 (b) and (c) is to hold down the Ctrl key and the
mouse button simultaneously while dragging the icon to a new location. Then select the
copied icon by clicking on it.
4. Modify the properties of the copied icon:

Verification
a. Right-click on the copy of the RM/COBOL Runtime icon and choose the Rename
option from the menu.
b. Type a new name for the icon (for example, IXDEMO) and press Enter.
c. Right-click on the renamed copy of the RM/COBOL Runtime icon and choose the
Properties option from the menu. The Properties dialog box is displayed.
d. Select the Shortcut tab.
e. Press End to enter input at the end of the existing command and then press
Backspace to erase the question mark.
f. Do one of the following:
• For a UNIX server, enter the following:
\\server\usr\rminfox\infoxdmo x=rmtcp32.cfg
• For a Windows server, enter the following:
\\server\infoxdmo x=rmtcp32.cfg
Note You may type either backslashes (\) or forward slashes (/) to separate the
edgenames of the path, but do not mix them. Notice the double backslashes or
double forward slashes at the beginning. Substitute the actual machine name of your
server machine (where the RM/InfoExpress server program is running as described
in Step 1) for server. This name is usually displayed as Machine ID at the bottom of
the server main screen, but it is whatever name is specified in your hosts file or
known to your DNS that maps to the IP address of the UNIX server machine.
• Under UNIX, the rest of the pathname assumes that RM/InfoExpress was
installed into /usr/rminfox during the server installation procedure. If it was
installed elsewhere, substitute the correct pathname.
• Under Windows, RM/InfoExpress is normally installed in the
\Program Files\Micro Focus\RM\RMInfoExpressv12 directory, which is the
server’s current directory.
Step 4 (f) also adds a configuration record file to the runcobol command. This
configuration record file (rmtcp32.cfg) is used by ixverify. It must reside in the
directory named in the Working Directory text box shown in the Program Item
Properties dialog box. This file should contain the following information:
EXTERNAL-ACCESS-METHOD CREATE-FILES=YES NAME=RMTCP32 OPTIONS='I'
If you make an error, click Cancel and return to the beginning of Step 4.
g. Click OK or press Enter to complete the modification. The dialog box closes and the
new icon appears.
5. Run the new icon by double-clicking on it or pressing Enter with the icon selected.
6. The RM/InfoExpress Client WinSock Info message box is displayed on the screen, as
described in Verifying the RM/InfoExpress Windows Client (on page 21).
Note This message box is displayed because the OPTIONS=‘I’ keyword is specified
on the EXTERNAL-ACCESS-METHOD configuration record in the rmtcp32.cfg file.
In a production environment, omit OPTIONS=‘I’ so that the message box will not
be displayed.
7. Click OK or press Enter to acknowledge the message box.

Verification
The infoxdmo verification program window displays the following information:
RM/InfoExpress Verification Program

1. RM/COBOL File Test
2. RM/InfoExpress File Test
3. Exit Program
Enter test number
a. If a return code 252 error (STOP sign) box is displayed, the infoxdmo verification
program could not be loaded from the server.
b. If a “COBOL I/O error 30, Runtime Library error 11004” is displayed, the server
name has probably been entered incorrectly. Click OK or press Enter. Return to
Step 5 and then specify the correct server name in Step 6. If the server name was
correct, check that the hosts file (or DNS) contains the server name and that the
services file contains the proper RMCFileServer line (see page 18).
c. If “COBOL procedure error 204” is displayed, the server name is correct but the
remaining path is incorrect. Click OK or press Enter. Return to Step 5 and then
specify the correct pathname in Step 6.
d. Other return code values and other error codes are described in the RM/COBOL
User’s Guide, and in Appendix A: Messages (see page 67) of this manual. If an
error message occurs, check the following:
• The status of the RM/InfoExpress server. (Is it still running?)
• The pathname on the server machine of the infoxdmo verification program.
• The server name in your hosts file.
• The RMCFileServer entry in your services file.
If you cannot determine the cause of the problem and correct it, contact Micro Focus
Customer Care.
8. At the “Enter test number” prompt, type 2 and press Enter. The following prompt is
displayed:
Enter remote directory where files are to be created.
9. Enter the name of the directory on the RM/InfoExpress server where the files are to be
created. For example:
\\server\usr\rminfox
The directory must already exist on the server machine, and the RM/InfoExpress server
user must have read and write permissions to it.
The infoxdmo verification program creates one indexed file (inxfl) and performs five
tests: write sequential, read sequential, read random, rewrite random, and delete random.
Timing information for each test is shown.
10. When the five tests are complete, the “Type any key to continue . . .” prompt is
displayed. At this point, RM/InfoExpress Windows client and server communication
verification is successfully complete.
You may run other tests in the verification program, run test number 2 specifying a different
server, or exit the program.

Verification
Verifying the RM/InfoExpress UNIX Client

To verify that the RM/InfoExpress UNIX client shared object program can be loaded, execute
the RM/COBOL runtime with the -v option to display the banner with a list of support
modules loaded by the RM/COBOL runtime system.
runcobol xxx –v
The shared object, librminfox.so, should be listed under the “Dynamic libraries loaded”
section, as illustrated below.
RM/COBOL Runtime - Version nn.nn for IBM AIX.

RM/COBOL Runtime System issued to any Company Name.
Configured for one user.
Copyright (c) 1985-2nnn by Micro Focus. All rights reserved.
Registration Number: 8C-1000-15537-0001
RM/COBOL: Dynamic libraries loaded:

($EXEDIR=.)
$EXEDIR/librmterm.so - Terminfo Terminal Interface - Version nn.nn.
$EXEDIR/librminfox.so - RM/InfoExpress Client - Version nn.nn.
If the librminfox.so shared object does not appear in the Dynamic libraries loaded list, then
the RM/InfoExpress UNIX client is not properly installed. Check that the RM/InfoExpress
UNIX client shared object (librminfox.so) exists in the same directory as the RM/COBOL
runtime (runcobol).
Verifying RM/InfoExpress UNIX Client and Server

Communication
The following procedures verify that the RM/InfoExpress UNIX client program can correctly
communicate with the RM/InfoExpress server program using the TCP/IP communication
protocol. We recommend that you first read Chapter 2: Installation and System
Considerations for UNIX, in the RM/COBOL User’s Guide, for more information.
1. Start the RM/InfoExpress server program running on the server machine, as described in
Verifying the RM/InfoExpress Server (on page 19).
2. Run the verification program, infoxdmo, using the RM/InfoExpress UNIX client
program, librminfox.so, by entering the following command:
runcobol infoxdmo
The shared object, librminfox.so, will be loaded automatically by the RM/COBOL

runtime system (runcobol).
3. Check that your PATH environment variable is set to point to the directory where
librminfox.so and runcobol are installed, and the RUNPATH environment variable is
pointing to the directory where infoxdmo.cob is present.
Note The infoxdmo.cob utility program may reside on your UNIX or Windows server
machine. You can load the program across the network by specifying the server path in
the RUNPATH environment variable. For example: RUNPATH=//server/path.
Remember, however, when setting environment variables on UNIX, you must use

Verification
forward slashes; for example, RUNPATH=\\server\path. Under UNIX, backslashes are

treated as escape characters.
The infoxdmo verification program window displays the following information:
RM/InfoExpress Verification Program

1. RM/COBOL File Test
2. RM/InfoExpress File Test
3. Exit Program
Enter test number
a. If a “COBOL I/O error 30” is displayed, look at the explanation in Appendix A:

Messages (on page 67) or in the RM/COBOL User’s Guide, for the corresponding
error.
b. For any RM/InfoExpress error, check the following:
• The status of the RM/InfoExpress server. (Is it still running?)
• The server name in your hosts file.
• The RMCFileServer entry (see page 18) in your services file.
If you cannot determine the cause of the problem and correct it, contact Micro Focus
Customer Care for assistance.
4. At the “Enter test number” prompt, type 2 and press Enter. The following prompt is
displayed:
Enter remote directory where files are to be created.
5. Enter the name of the directory on the RM/InfoExpress server where the files are to be
created. For example:
//server/usr/rminfox
Note You may type either backslashes (\) or forward slashes (/) to separate the
edgenames of the path, but do not mix them. Notice the double backslashes or double
forward slashes at the beginning. Substitute the actual machine name (in uppercase) of
your server machine (where the RM/InfoExpress server program is running as described
in Step 1) for server. This name is usually displayed as Machine ID at the bottom of the
server main screen, but it is whatever name is specified in your hosts file or known to
your DNS that maps to the Internet Protocol address of the server machine.
The directory must already exist on the server machine and the RM/InfoExpress server
must have read and write permissions to it.
The infoxdmo verification program creates one indexed file (inxfl) and performs five
tests: write sequential, read sequential, read random, rewrite random, and delete random.
Timing information for each test is shown.
6. When the five tests are complete, the “Type any key to continue...” prompt is displayed.
At this point, RM/InfoExpress client and server communication verification is complete.
You may run other tests in the verification program, run test number 2 specifying a different
server, or exit the program.

Server Configuration Options
Chapter 2: Configuring and Running the RM/InfoExpress Server
Chapter 2: Configuring and

Running the RM/InfoExpress
Server
This chapter describes the procedures required to configure and run (start) the
RM/InfoExpress servers for UNIX and Windows.
Server Configuration Options

RM/InfoExpress server configuration options can be set either in the server configuration file
(rmixsrvr.ini) or on the command line. The command line specification overrides the
configuration file setting. While Micro Focus recommends that you specify the configuration
options in the server configuration file, the ability to specify configuration options on the
command line ensures backward compatibility with previous releases, and enables special,
temporary invocations of the server without affecting the settings in the configuration file.
For example, there may be times when it would be helpful to specify the -d option in order to
create a debug file to send to Micro Focus Customer Care.
All command line options have a configuration file equivalent. However, starting with
version 2.1, all new program options must be specified in the configuration file. There is no
command line equivalent.
For more information, see Appendix D: Configuring RM/InfoExpress (on page 83).
Starting the RM/InfoExpress UNIX Server Program

On the UNIX server machine, start the RM/InfoExpress UNIX server and server display
(screen handler) programs, rmservertcp and rmdisptcp, by entering:
/usr/rminfox/rmservertcp [-option]
/usr/rminfox/rmdisptcp [-option]
Notes

Starting the RM/InfoExpress UNIX Server Program
• The RM/InfoExpress UNIX server display program, rmdisptcp, monitors the server
activity and does not affect the communication between the client and server. On some
machines, the server daemon may take a few seconds to initialize the underlying network.
If the server display (rmdisptcp) is invoked immediately after the server is started, the
server display program will wait until the network initialization is complete.
• If you start rmservertcp in a UNIX window opened using a telnet session on your
workstation, then you may not be able to close the telnet session until the server is
terminated. Always start the server from a terminal connected to the UNIX machine.

Display Main Screen (on page 42). The server is ready to process requests from client
machines. If the server main screen does not display, follow the instructions in Verifying the
RM/InfoExpress Server (on page 19).
The following sections describe the server program and server display program command
line options.
UNIX Server Command Line Options

Command line options or the RM/InfoExpress UNIX server program (rmservertcp) can be
any of the following:
• -c n|u|l. Indicates how the cases of pathnames from the clients are converted. The -c
option has three values:
− -c n. Indicates that no filename mapping is performed. This is the default value.
− -c u. Indicates that the entire filename is mapped to uppercase before the Open
request is attempted. The option may be specified as -c upper, if desired.
− -c l. Indicates that the entire filename is mapped to lowercase before the Open
request is attempted. The option may be specified as -c lower, if desired.
Note The -c command line option is equivalent to the ConvertFileName configuration
option, which is discussed in UNIX Server-Specific Configuration Options (on
page 92). The command line option overrides the configuration option.
• -d pathname. This option causes the file pathname to be created and trace information to
be written into it. After the RM/InfoExpress server program is terminated, send this file
to Micro Focus Customer Care for further investigation. Use this option only when you
are investigating a problem with the help of Micro Focus Customer Care. Under normal
conditions, using this option affects server operations negatively.
Note The -d command line option is equivalent to the InfoxDebug configuration option,
as described in Common Configuration Options (on page 85). The command line option
overrides the configuration option.
• -k dddd. Indicates the maximum number of clients to be served. If more clients are to be
served, the server should be brought down and started again. The default value is 50.
This value cannot be greater than the number of clients for which the server is licensed.
Note The -k command line option is equivalent to the UseCount configuration option,
which is described in Common Server-Specific Configuration Options (on page 90). The
command line option overrides the configuration option.
• -p nnnnn. Indicates the common buffer pool size. Do not change the default value for
this parameter unless instructed by Micro Focus Customer Care.

Starting and Stopping the RM/InfoExpress Windows Server Program
Note The -p command line option is equivalent to the FileBufferPool configuration

option, as explained in Common Server-Specific Configuration Options (on page 90).
The command line option overrides the configuration option.
• -z nnnnn. Indicates the maximum amount of data that can be handled by the TCP send
function. The default value is system-dependent and has been set by Micro Focus. Do
not specify this parameter unless instructed to do so by Micro Focus Customer Care.
Note The -z command line option is equivalent to the MaxSendSize configuration
option, which is discussed in Common Configuration Options (on page 85). The
UNIX Server Display Command Line Option

The following is an option for the RM/InfoExpress UNIX server display (screen handler)
program, rmdisptcp:
• -t. Indicates that the user is requesting to terminate the server or communication to a
particular client. If this option is not specified, the user can terminate only the server
display program. Because the server display program does not support any configuration
file, this option must be specified on the command line.
For example, the following command will allow the user to terminate the server program:
rmdisptcp -t
Starting and Stopping the RM/InfoExpress Windows

Server Program
On the Windows server machine, it is necessary to start the Windows Service Control
Manager (SCM) in the Windows Control Panel to run the RM/InfoExpress server software.
Initially, the server is configured to be started and stopped manually. However, it can easily
be reconfigured to start automatically when Windows is initialized, as described in
Configuring the RM/InfoExpress Windows Server Program (on page 31).
Note See the description of the command line options for the Windows server and the
Windows server display programs, beginning on page 32.
Starting the Server

To stop the RM/InfoExpress server for Windows:
1. Click Start on the task bar.
2. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, start the
Windows Service Control Manager:
a. Click Run.
b. In the Run dialog box, in Open, type the following and then click OK:
services.msc

c. Select RM/InfoExpress Server in the list of services.

d. To start the service, press the Start the service link located to the left, or right-click
over the service name and select Start from the pop-up menu.
These actions will launch the RM/InfoExpress server program for Windows, which
initially runs under the System account and has access to any resources that this account
is permitted to use. (Most systems log on to a System account, rather than a user
account.) To change the account under which the server program runs, see Configuring
the RM/InfoExpress Windows Server Program (on page 31).
3. In the RM/InfoExpress folder, double-click on the rmdistcp icon to start the
RM/InfoExpress server display program.
Display Main Screen (on page 42). The server is ready to process requests from client
machines. (The RM/InfoExpress Windows server display program, rmdistcp.exe,
monitors the server activity and does not affect the communication between the client
and server.)
Note Beginning in version 8, the -t command line option is automatically added to the
server display program icon. The -t option allows you to terminate a server or the
communication to a particular client when the server display program is terminated.
If the server main screen does not appear, check that no other RM/InfoExpress server program
is already running on the machine. If other messages are displayed, contact Micro Focus
Customer Care.
Note The RM/InfoExpress Windows server program also can be launched in user mode using
the icon created by default in the RM/InfoExpress program folder. To start the server, simply
double-click on the RM/InfoExpress Windows server icon. (You may wish to add command
line options to the Target command line in the Shortcut tab of the Properties dialog box for
the icon, or you may use the command line options from a DOS command line. For more
information about Windows shortcuts, see “Creating a Windows Shortcut” in Chapter 3:
Installation and System Considerations for Microsoft Windows, in the RM/COBOL User’s
Guide.) The server will run using the current account and will be terminated when you log
out. When launched in this mode, there is also a small, 10- to 20-second delay before the
server becomes active.
Stopping the Server

To stop the RM/InfoExpress server for Windows:
1. Start the Windows Service Control Manager (SCM) and find the server in the list of
services, as described previously.
2. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, click the
Stop the service link located to the left, or right-click over the service name and click
Stop from the pop-up menu.
The RM/InfoExpress server will terminate.

Note The server can also be terminated from within the RM/InfoExpress server display
program (rmdistcp.exe) when that program is started with the -t option. When halted in this
manner, it is possible that the Windows Service Control Manager (SCM) will not detect that
the server has terminated. To restart the server, first stop the service and then start the service
again, using the methods described in the previous topic.

Configuring the RM/InfoExpress Windows Server

Program
It is possible to configure the RM/InfoExpress Windows server program to load automatically
when Windows is started and to run under a specific log on account. Instructions follow for
both configurations.
Starting the Server Automatically

To configure the RM/InfoExpress server to load automatically when Windows is started:
1. Start the Windows Service Control Manager and find the server in the list of services, as
described in Starting and Stopping the RM/InfoExpress Windows Server Program (on
page 29).
2. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, right-click
over the service name and select Properties from the pop-up menu.
3. Under Startup Type, select Automatic.
The server will now be loaded automatically the next time Windows is started.
Running Under a Specific Log On Account

To configure the server to run under a specific account, take the following steps:
1. Start the Windows Service Control Manager and find the server in the list of services,
as described in Starting and Stopping the RM/InfoExpress Windows Server Program (on
page 29).
2. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, right-click
over the service name and select Properties from the pop-up menu.
3. In the Properties dialog box, select the Log On tab.
4. Under the Log On As option, select either the Local System Account option to run the
server under the default account, or enter the name and password of a selected account to
run under another account.
Note Most services log on to a System account, rather than a user account.
Windows Server Command Line Options

Command line options for the RM/InfoExpress Windows server program (rmsrvtcp.exe),
when launched from the icon or from a DOS command line, can be any of the following:
• -d pathname. This option causes the file pathname to be created and trace information to
be written into it. After the RM/InfoExpress server program is terminated, send this file
to Micro Focus Customer Care for further investigation. Use this option only when you
are investigating a problem with the help of Micro Focus Customer Care. Under normal
conditions, using this option affects server operations negatively.
Note The -d command line option is equivalent to the InfoxDebug configuration option,
as described in Common Configuration Options (on page 85). The command line option
overrides the configuration option.

• -k dddd. Indicates the maximum number of clients to be served. If more clients are to be
served, the server should be brought down and started again. The default value is 50.
This value cannot be greater than the number of clients for which the server is licensed.
Note The -k command line option is equivalent to the UseCount configuration option,
which is described in Common Server-Specific Configuration Options (on page 90). The
• -p nnnnn. Indicates the common buffer pool size. Do not change the default value for
this parameter unless instructed by Micro Focus Customer Care.
Note The -p command line option is equivalent to the FileBufferPool configuration
option, as explained in Common Server-Specific Configuration Options (on page 90).
The command line option overrides the configuration option.
• -z nnnnn. Indicates the maximum amount of data that can be handled by the TCP send
function. The default value is system-dependent and has been set by Micro Focus. Do
not specify this parameter unless instructed to do so by Micro Focus Customer Care.
Note The -z command line option is equivalent to the MaxSendSize configuration
option, which is discussed in Common Configuration Options (on page 85). The
Windows Server Display Command Line Option

The following is an option for the RM/InfoExpress Windows server display (screen handler)
program, rmdistcp.exe:
• -t. Indicates that the user is requesting to terminate the server or communication to a
particular client. If this option is not specified, the user can terminate only the screen
display program. Because the server display program does not support any configuration
file, this option must be specified on the command line.
For example, the following command will allow the user to terminate the server program:
rmdistcp.exe -t

Accessing the RM/InfoExpress Windows Client Program
Chapter 3: Using RM/InfoExpress with RM/COBOL for Windows Programs
Chapter 3: Using
RM/InfoExpress with RM/COBOL
for Windows Programs
This chapter describes the procedures required to use RM/InfoExpress with RM/COBOL for
Windows programs, including how to access the RM/InfoExpress Windows client program,
how RM/COBOL for Windows programs point to network data files, and how to execute
RM/COBOL for Windows programs for use with RM/InfoExpress.
Note For information on how to start the RM/InfoExpress server programs on either
Windows or UNIX, refer to the appropriate sections in Chapter 2: Configuring and Running
the RM/InfoExpress Server (on page 27).
Accessing the RM/InfoExpress Windows Client

Program
The RM/InfoExpress Windows client program is rmtcp32.dll. The RM/COBOL runtime
system for Windows (runcobol) invokes the client program automatically when an
EXTERNAL-ACCESS-METHOD record, specifying NAME=RMTCP32, is included in the
RM/COBOL configuration file. See the EXTERNAL-ACCESS-METHOD configuration
record section in Chapter 10: Configuration, of the RM/COBOL User’s Guide, for more
information.
Note The OPTIONS=‘I’ keyword, which causes an informative message box to be displayed,
normally should not be specified on the EXTERNAL-ACCESS-METHOD configuration
record. Other client-specific configuration options are described in Appendix D: Configuring
RM/InfoExpress (on page 83).
Pointing to Network Data Files

This section describes several different methods that can be used in an RM/COBOL for
Windows program to specify the pathnames of remote network data files, which are to be
accessed by RM/InfoExpress.

Specifying Synonyms
Generally, RM/COBOL programs contain synonyms in the file-access-name field of the
SELECT clause. For example:
SELECT INX-FILE ASSIGN TO RANDOM, "inxfl"
The synonyms are mapped to the actual pathname before executing the RM/COBOL program.
Synonym specification depends on the operating system on which the runtime system
application and the RM/InfoExpress client software are running. If you are using
RM/COBOL for Windows, synonyms are specified by setting properties.
For example, to access a file on a UNIX server from a Windows client, set the following
synonym:
inxfl=\\Unix_server\usr\infox\inxfl
In this example, the synonym inxfl points to a file inxfl in directory infox of directory usr on
a UNIX server, Unix_server. It is also possible to use DOS environment variables (created
with the DOS SET command) as synonyms if the Windows runtime system is started with a
command line from a DOS box running under Windows. For more information, refer to the
“Directory Search Sequences” section in Chapter 3: Installation and System Considerations
for Microsoft Windows, of the RM/COBOL User’s Guide.
Here are three examples using synonyms:
Example 1
inxfl=\\Unix_server\usr\infox\inxfl
Example 2
relfl=Q:\usr\infox\relfl
Example 3
inxfl=\\Win_server\SharedFiles\inxfl
where,
inxfl and relfl (specified on the left side of the SET expression) are both synonyms.
Unix_server is the name of the UNIX server accessed by RM/InfoExpress, as shown in
the hosts file or as known by DNS.
Q is a drive letter mapped to a UNIX server.
\usr\infox\inxfl and \usr\infox\relfl are the pathnames on the server.
Win_server is the name of the Windows server, as shown in the hosts file or as known
by DNS.
SharedFiles is the share name known to the Windows server running on Win_server.

In Examples 1 and 3, RM/InfoExpress is able to process the inxfl file because the pathname
begins with double backslashes (\\). It could also begin with double forward slashes (//).
In Example 2, RM/InfoExpress is unable to process the relfl file because it is not using the
appropriate naming convention. Processing, however, is handled through conventional
network access.
Thus, for RM/COBOL files specified by filename only, you may access server files by using a
synonym that points to a server directory.
Specifying RUNPATH Environment Variables

Specifying an RM/InfoExpress server in one of the RUNPATH components causes
RM/COBOL to access the file using RM/InfoExpress. For example:
RUNPATH=C:\prog;N:\data;\\Unix_server\usr\data;
\\Win_server\Shares\data
causes RM/COBOL to search for a file first in the directory prog on the local disk C; then in
the directory data on the network drive N: (assuming that drive N is mapped to a network
volume) using conventional network access; next in the subdirectory data of directory usr on
the server Unix_server using RM/InfoExpress; and lastly, in the directory data in whatever
directory is associated with the Shares share name on Win_server using RM/InfoExpress.
For more information on the RUNPATH environment variable specification, refer to the
“Locating RM/COBOL Files” section in Chapter 3 of the RM/COBOL User’s Guide.
Specifying Explicit Pathnames in the RM/COBOL

Program
You must change the pathname in the SELECT clause of the RM/COBOL program for
filenames that include drive specifiers, computer names, or directory paths, and that do not
already point to a server directory. For example:
SELECT DATA-FILE ASSIGN TO RANDOM,

"\\Unix_server\usr\infox\data.fil"
This type of pathname specification makes the program less portable, however, because
whenever the location of the file data.fil changes (from one server to another), you must
recompile the source program.
Specifying Complete Pathnames Using RM/COBOL

Data-Names
Some RM/COBOL programs use data-names to change pathnames dynamically. For
example, the SELECT statement:
SELECT INX-FILE ASSIGN TO RANDOM, DATA-FIL
In this example, DATA-FIL is the data-name defined in the DATA DIVISION, and it
contains the complete pathname of the file at the time the file was opened. These data-names

Executing RM/COBOL Programs
must include the name of a UNIX machine or the Windows server on which an
RM/InfoExpress server is running. For example, DATA-FIL could contain the following:
\\Unix_server\usr\infox\data.fil

Execute your RM/COBOL program by entering the following command line, as described in
the “System Configuration” section of Chapter 3: Installation and System Considerations for
Microsoft Windows, of the RM/COBOL User’s Guide.
runcobol name [option]
where,
name points to RM/COBOL object files.
option is any valid RM/COBOL Runtime Command option.
Before executing the runcobol command, set up the environment to create and access files on
the server machine, and create a configuration file to define the external access method.
Execute the RM/COBOL verification suite for Windows, as described in Chapter 5: System
Verification, of the RM/COBOL User’s Guide.

Accessing the RM/InfoExpress UNIX Client Program
Chapter 4: Using RM/InfoExpress with RM/COBOL for UNIX Programs
Chapter 4: Using
RM/InfoExpress with RM/COBOL
for UNIX Programs
This chapter describes the procedures required to use RM/InfoExpress with RM/COBOL for
UNIX programs, including:
• How to access the RM/InfoExpress UNIX client program.
• How RM/COBOL for UNIX programs point to network data files.
• How to execute RM/COBOL for UNIX programs for use with RM/InfoExpress.
Note For information on how to start the RM/InfoExpress server programs on either UNIX or
Windows, refer to the appropriate sections in Chapter 2: Configuring and Running the
RM/InfoExpress Server (on page 27).
Accessing the RM/InfoExpress UNIX Client Program

The RM/InfoExpress client shared object for UNIX is named librminfox.so.
By specifying the keyword NAME=NONE on the EXTERNAL-ACCESS-METHOD record
in the configuration file, you can bypass the RM/InfoExpress UNIX client code in
librminfox.so. See the EXTERNAL-ACCESS-METHOD configuration record section in
Chapter 10: Configuration, of the RM/COBOL User's Guide, for more information.

This section describes several different methods that can be used in an RM/COBOL for UNIX
program to specify the pathnames of remote network data files, which are to be accessed by
RM/InfoExpress.

Specifying Synonyms
Generally, RM/COBOL programs contain synonyms in the file-access-name field of the
SELECT clause. For example:
SELECT INX-FILE ASSIGN TO RANDOM, "inxfl"
The synonyms are mapped to the actual pathname before executing the RM/COBOL program.
Synonym specification depends on the operating system on which the runtime system
application and the RM/InfoExpress client software are running. For example, to access a file
on a UNIX server from a UNIX client, execute the following command (assuming Bourne
shell) prior to invoking the client:
inxfl=//UNIX_SERVER/usr/infox/inxfl; export inxfl
In this example, the synonym inxfl points to a file inxfl in directory infox of directory usr on
a UNIX server, UNIX_SERVER. See also the description of synonyms in the “Directory
Search Sequences” section in Chapter 2: Installation and System Considerations for UNIX, of
the RM/COBOL User’s Guide.
Specifying RUNPATH Environment Variables

Specifying an RM/InfoExpress server in one of the RUNPATH components causes
RM/COBOL to access the file using RM/InfoExpress. For example:
RUNPATH=/usr/local/infox://UNIX_SERVER/usr/data://
Win_server/Shares/data
causes RM/COBOL to search for a file first in the directory /usr/local/infox on the local disk
using conventional network access; then in the directory data in directory usr on
UNIX_SERVER using RM/InfoExpress; and lastly, in the directory data in whatever
directory is associated with the Shares share name on Win_server using RM/InfoExpress.
For more information on the RUNPATH environmental variable specification, refer to the
“Locating RM/COBOL Files” section in Chapter 2 of the RM/COBOL User’s Guide.
Specifying Explicit Pathnames in the RM/COBOL

Program
For filenames that include directory paths and that do not already point to a server directory,
you must change the pathname in the SELECT clause of the RM/COBOL program. For
example:
SELECT DATA-FILE ASSIGN TO RANDOM,

"//UNIX_SERVER/usr/infox/data.fil"
This type of pathname specification makes the program less portable, however, because
whenever the location of the file data.fil changes (from one server to another), you must
recompile the source program.

Specifying Complete Pathnames Using RM/COBOL

Data-Names
Some RM/COBOL programs use data-names to change pathnames dynamically. For
example, the SELECT statement:
SELECT INX-FILE ASSIGN TO <RANDOM> DATA-FIL
In this example, DATA-FIL is the data-name defined in the DATA DIVISION, and it
contains the complete pathname of the file at the time the file was opened. These data-names
must include the name of a UNIX machine or the Windows server on which an
RM/InfoExpress server is running. For example, DATA-FIL could contain the following:
//UNIX_SERVER/usr/infox/data.fil

Execute your RM/COBOL program by entering the following command line on the terminal
of your UNIX client machine:
librminfox name [option]
where:
name points to RM/COBOL object files.
option is any valid RM/COBOL Runtime Command option.
Before executing the librminfox command, set up the environment to create and access files
on the server machine.
Execute the RM/COBOL verification suite for UNIX, as described in Chapter 5: System
Verification, of the RM/COBOL User’s Guide.

Keyboard Functions
Chapter 5: RM/InfoExpress Server Operations
Chapter 5: RM/InfoExpress
Server Operations
The RM/InfoExpress user interface is implemented for UNIX character-based terminals and
the Windows console interface. The RM/InfoExpress server display (screen handler) program
examines information and data from the server and client, and updates the screen once every
second.
CAUTION Multiple RM/InfoExpress server display programs, with screens other than the
main screen displayed, may affect server performance. As long as a server display program is
running with its main menu selected, it does not noticeably affect server performance.
Keyboard Functions
The following list describes the keys used in the RM/InfoExpress server display program.
Keyboard Functions
Key Action
n N Any command or response may be selected by pressing the first

character of the command. Case is not important. For example: S
for Select file, t for Terminate, or a number, if appropriate.
Escape (Esc) Selects No in response to a query from the command line. Also
backtracks through a menu path.
Home Returns to the RM/InfoExpress server display main screen.
Up Arrow Moves the cursor up during client or file selection.
Down Arrow Moves the cursor down during client or file selection.
Left Arrow Moves the cursor left during the selection of menu commands and
responses.
Right Arrow Moves the cursor right during the selection of menu commands and
responses.
Page Up (PgUp) Scrolls the screen up to examine and review client and file
or Ctrl+B information.
Page Down (PgDn) Scrolls the screen down to examine and review client and file
or Ctrl+F information.

Server Display Screen Format
Keyboard Functions
Key Action
Enter Chooses the currently highlighted item for command and response
selection, and for individual client or file selection.
Server Display Screen Format

Except for the main screen (illustrated on the following page), each RM/InfoExpress server
display program screen has the same basic format, as illustrated in Figure 2.
Figure 2: Server Display Screen Format
The elements of the RM/InfoExpress server display screen are described as follows:
• Activity area. The activity area contains information related to the current activity or
server display screen.
• Command line. The command line, located at the bottom of the screen, shows
command names, user prompts, or user queries.
• Date. The date area displays the current system date.
• Product name. The product name displays the product name and version information.
• Time. The time area displays the current system time.
• Title line. The title line displays the name of the server display screen.
Server Display Commands

The first screen you see when you start the RM/InfoExpress server display program is the
RM/InfoExpress main screen, as illustrated in Figure 3.

Figure 3: Server Display Main Screen
The RM/InfoExpress server display main screen lists the current time, date, the uptime (in
days), and identifies the RM/InfoExpress server machine (in the Machine ID field). It also
provides an overview of current network activity, including the following:
• The Active clients field indicates the total number of clients currently connected to this
RM/InfoExpress server. Other programs using RM/COBOL are not shown.
Note that the active client count on the main screen of the server display program
sometimes shows a value that is more than the number of clients actually connected.
This behavior is most noticeable when sessions are established and released rapidly.
• The Open files field records a count of the number of files currently open. The first
number indicates the number of unique files that are currently opened. The second
number indicates the total number of all files currently opened by all clients. The third
number is the maximum number of open files allowed (you may increase this number by
using the FileCount option, described on page 90, in the server configuration file,
rmixsrvr.ini).
• The Dynamic load field shows the percentage of CPU utilization by the server.
• The Messages processed field indicates the number of client requests honored by
the server.
The command line at the bottom of the server display main screen contains the following
command options:
• Clients. This command lists all clients and reports on specific clients. Clients may be
selected any time the Clients field appears in the command line. For more information,
see Client Information (on page 44).
• Files. This command lists all currently open files and reports on specific files. Files may
be selected any time the Files field appears in the command line. For more information,
see File Information (on page 45).
• Log. This command provides access to two sub-screens: Open Log and Error Log.
Select log information from a command line or by pressing the letter L at any time.
For more information, see Open Log Information (on page 47) and Error Log Information
(on page 48).

• Terminate. This command provides a number of termination modes. Terminate may

be selected any time the Terminate field appears in the command line. For more
information, see also Termination of Communication Activity (on page 49).
Each command and its associated screens, prompts, and queries are described in the following
sections. To return to the server display main screen from any of the following screens, press
the letter M or choose Main from the command line.
Client Information
The Client Information screen, illustrated in Figure 4, is displayed when you choose the
Clients command from the RM/InfoExpress server display main screen.
Figure 4: Client Information Screen
The Client Information screen lists all active clients by name, the number of files each client
has open, the total number of messages processed for each client, and the type of operating
system on which the client is running. Whenever there are more clients or files than can be
displayed on a single screen, a message is displayed on the screen advising that Page Up or
Page Down may be used to request the previous or next screen.
Use the command Select Client to select a particular client in order to see information that is
more detailed. Press Enter or the letter S to choose the Select Client command. The
following prompt is displayed on the command line:
Select Client to display (using PgUp, PgDn, or Arrow keys)
Use Page Up, Page Down, or the arrow keys to select a client and press Enter. The Client
Files screen is displayed, as illustrated in Figure 5.

Figure 5: Client Files Screen
The Client Files screen shows the total number of files currently opened by the client, and the
total number of messages passed between the client and the server. For each open file, the
Client Files screen also shows the following information.
• The ORG column indicates the file organization:
− INX (Indexed)
− SEQ (Sequential)
− REL (Relative)
• The OPEN column indicates the type of open mode:
− I-O (Input/Output)
− Input
− Output
− Extend
• The ACCESS column indicates the type of access:
− Dynamic
− Sequent(ial)
− Random
• The FILENAME column indicates the absolute pathname.
File Information
The File Information screen, illustrated in Figure 6, is displayed when you choose the Files
command from the RM/InfoExpress server display main screen.

Figure 6: File Information Screen
The File Information screen lists the absolute pathname for each file and the number of times
each file has been opened. Whenever there are more clients or files than can be displayed on
a single screen, a message is displayed on the screen advising that Page Up or Page Down
may be used to request the previous or next screen.
Use the command Select File to select a particular file in order to see information that is more
detailed. Press Enter or type the letter S to choose the Select File command. The following
prompt is displayed on the command line:
Select file to display (using PgUp, PgDn or Arrow keys)
Use Page Up, Page Down, or the arrow keys to select a file and press Enter. The File Clients
screen is displayed, as illustrated in Figure 7.
Figure 7: File Clients Screen
The File Clients screen shows the number of clients that have opened this file since the server
was initiated and lists the clients that currently have the file open. In addition to the user
name of the client (USERNAME), this screen indicates the file organization (ORG), the type
of open mode (OPEN), and the type of access (ACCESS) of the client. (For more explanation
of these columns, see page 45.)

Open Log Information

The Open Log screen, illustrated in Figure 8, is displayed when you choose the Log command
from the RM/InfoExpress server display main screen, and then choose the Open Log
command or press the letter O. The Open Log screen displays information about a maximum
of 24 previous opens by the server, beginning with the latest open.
Figure 8: Open Log Screen
Note On the Open Log screen and the Error Log screen (on page 48), filenames up to 32
characters long and client names up to 12 characters long can be displayed without loss of
information. If necessary, use the DotsBias option, described in Common Server-Specific
Configuration Options (on page 90), to control which part of longer filenames is lost. To
navigate to the Error Log screen from this location, press the Esc key (to go back to the
previous screen), followed by the letter E.
The command line provides three commands: Freeze, Unfreeze, and Toggle. To choose a
command, use the arrow keys or press the first letter of the desired command.
• The Freeze command temporarily suspends the updating of the Open Log screen for that
particular server display application. However, it does not affect the logging of the new
opens into the data structures by the server.
• The Unfreeze command causes the server display program to update the Open Log
screen with the information from the server data structures.
• The Toggle command causes the information on the Open Log screen to be displayed in
a different form, illustrated in Figure 9, which is useful for Micro Focus Customer Care.

Figure 9: Open Log Screen (Toggled)
Error Log Information

The Error Log screen, illustrated in Figure 10, is displayed when you choose the Log
command from the RM/InfoExpress server display main screen, and then choose the Error
Log command or press the letter E. The Error Log screen displays a maximum of 24 errors,
beginning with the most recent error. It also lists the name of the client for which the error
was issued, the error code detected by the server, the time the error occurred, the location
within the RM/InfoExpress server code at which the error occurred, and an explanation (or
status) of the error.
Figure 10: Error Log Screen
Note On the Error Log screen and the Open Log screen (on page 47), filenames up to 32
characters long and client names up to 12 characters long can be displayed without loss of
information. If necessary, use the DotsBias option, described in Common Server-Specific
Configuration Options (on page 90), to control which part of longer filenames is lost. To
navigate to the Open Log screen from this location, press the Esc key (to go back to the
previous screen), followed by the letter O.

The command line provides three commands: Freeze, Unfreeze, and Toggle. To choose a
command, use the arrow keys or press the first letter of the desired command.
• The Freeze command temporarily suspends the updating of the Error Log screen for that
particular server display application. However, it does not affect the logging of the new
errors into the data structures by the server.
• The Unfreeze command causes the server display program to update the Error Log
screen with the information from the server data structures.
• The Toggle command causes the information on the Error Log screen to be displayed in a
different form, illustrated in Figure 11, which is useful for Micro Focus Customer Care.
Figure 11: Error Log Screen (Toggled)
Termination of Communication Activity

The Terminate command provides access to a variety of termination nodes.
When you select the Terminate command from anywhere within the RM/InfoExpress server
program, the Terminate command line is displayed, as illustrated in Figure 12.
Figure 12: Terminate Command Line
Terminate: Display Client Server
The Terminate commands are described in the next sections.

Note To avoid terminating the RM/InfoExpress server program accidentally, the default
behavior of the RM/InfoExpress server display program has changed. When you start the
screen display program, you can terminate only the screen display program itself, not the
server program or communication to a particular client. The Terminate command line on the
server display main screen will show only the Display command. However, if the -t option is
specified on the command line for the server display program, then you may also terminate
the server or communication to a particular client. The illustration in Figure 12 and the
following discussion assume that the -t option is specified for the screen display program. For
more information, see UNIX Server Display Command Line Option (on page 29) and
Windows Server Display Command Line Option (on page 32).

Termination of Server Display

It is possible to temporarily terminate the screen interface (server display program) in order to
increase the processing power of the server. Press the letter D to choose the Display
command from the Terminate command line. The server display program will be terminated
without affecting the server or any clients.
Termination of Client Communications

Termination of communications between the client and server should be requested only if the
particular client is interfering with other clients on the network (for instance, a runaway
program has left a record locked). Keep in mind that any access to open files will result in
I/O errors on shared files on the terminated client. This action does not remove the client
program.
Press the letter C to choose the Client command from the Terminate command line. The
Client Information screen (see Figure 4 on page 44) is displayed with the following prompt at
the command line:
Select Client to terminate (using PgUp, PgDn or Arrow Keys)
Use Page Up, Page Down, or the arrow keys to select a client and press Enter. The Client
Files screen is displayed (see Figure 5 on page 45) with the following prompt at the
command line:
Terminate selected Client? No Yes
Press the letter Y to terminate communication. Press Enter or Escape or the letter N to cancel
the command.
Note The use of the server display (screen handler) program is for administrative purposes
only. When invoked multiple times, only one administrator should perform operations such
as terminating clients.
Termination of the Server

To terminate the server, press the letter S from the Terminate command line. The following
command line is displayed, as illustrated in Figure 13.
Figure 13: Quit Command Line
Quit: When Idle In a while Now
The Quit commands are described in the following sections.
Quit When Idle
Press the letter W to choose the When Idle command. The following prompt is displayed:
Quit when idle?

Press the letter N or press Escape to cancel the command. Otherwise, when all clients are
idle, the following prompt is displayed:
Terminate Server Now? No Yes
Press the letter Y to terminate the server immediately. Press the letter N, Escape, or Home to
cancel the command.
Quit in a While
Press the letter I to choose the In A While command. The following command line is
displayed, as illustrated in Figure 14.
Figure 14: Quit in a While Command Line
Quit in: 3 minutes 5 minutes 10 minutes 20 minutes
When you choose one of the time options, the number of minutes will decrement as the
specified time elapses. You can cancel the termination at any time by pressing the letter N or
Escape. Otherwise, when all clients are idle, the following prompt is displayed:
cancel the command.
Quit Now
Press the letter N to choose the Now command. The following prompt is displayed:
cancel the command.
The recommended way to terminate the server is by using the command sequence (Terminate,
Server, Now, Yes) of the screen display (screen handler) program when no active client is
connected.
WARNING Never attempt to terminate one or more RM/InfoExpress UNIX server
processes using the kill command. This may cause the server to terminate without cleaning
up resources and closing open files. For example, using the kill command causes the server
to exit without removing the IPC (Inter Process Communications) objects, such as shared
memory segments and semaphores. As a result, when the server is started next time, it fails
with server error code 1 (RMIX_API_ERR_SERVER_ALREADY_EXISTS). For more
information, see Removing IPC Objects After Server Failure (on page 82) in Appendix C:
Troubleshooting.

UNIX System Security
Chapter 6: File Security on the RM/InfoExpress UNIX Server
Chapter 6: File Security on the

RM/InfoExpress UNIX Server
An important consideration in RM/InfoExpress is protecting the system and its data from
unauthorized access. This chapter describes the implementation of file security on the
RM/InfoExpress UNIX server and the authentication procedures performed by the server on
various clients to grant access to the files on the server.
UNIX System Security

The basic security features of UNIX operating systems allow a user of a UNIX server to
belong to one of three categories of file access: Owner, Group, and Others. Each category of
users can have different access permissions to files. The possible file access permissions are
read, write, and execute. For example, if only the Owner of the file has write permission, the
UNIX operating system will prevent any other user from writing to the file.
On a standalone UNIX server, the operating system validates the authenticity of the user at
login time using information stored in the system password file and other security files. In a
networked, client/server environment, however, users may log in to the UNIX server from
remote, non-UNIX clients. To validate users on these clients, UNIX uses other security
database files such as .rhosts or hosts.equiv. For more information, see .rhosts File Entry
(on page 56).
Note The RM/InfoExpress UNIX server software does not look at hosts.equiv, nor does it
use the ruserok function.
When a user on a remote client logs in to the UNIX server, the networking software on the
client passes information to the server about that user, including the server user name,
password, and client machine name. After the user has been authenticated, the user on the
remote client is allowed to access the files on the server as one of the local users of that
server. For more information on file security provided by the UNIX operating system, refer
to your UNIX system documentation.
RM/InfoExpress File Security

The implementation of file security in RM/InfoExpress uses the UNIX system security
philosophy to protect the files on the RM/InfoExpress UNIX server from unauthorized access

by users on client machines. To be able to use the file security features of RM/InfoExpress, a
security parameter file, ixpwfile, must be created on each client machine and each UNIX
server using the utility program, ixsecure.cob. For more information on this utility, see
Appendix E: RM/InfoExpress Security Parameter File Update Utility (on page 97).
On a client machine, ixpwfile contains information needed to connect the RM/InfoExpress
client to different RM/InfoExpress UNIX servers. Similarly, on the server, ixpwfile is created
by the server administrator and contains information that permits different clients to be
connected to this server. Only the server administrator should have read and write
permissions to the server security parameter file.
The client passes information obtained from ixpwfile to the server when a session is
established. The server validates this information against the server’s version of ixpwfile.
RM/InfoExpress UNIX Server Security Levels

The RM/InfoExpress UNIX server can be invoked at one of six security levels using the
configuration option, ServerSecurityLevel=number, where number has a value in the range of
0 through 5. These six security levels are described in Table 1. Refer also to Appendix D:
Configuring RM/InfoExpress (on page 83), for more information about server configuration.
If the ServerSecurityLevel option is absent in the configuration file, the server runs in
“compatibility mode”; that is, the server behaves like a version 2.0 RM/InfoExpress UNIX
server. See Server Compatibility with Older and Newer Clients (on page 57).
Note Older RM/InfoExpress clients can only connect to RM/InfoExpress servers running at
security levels “compatible”, 0, or 1.
At other security levels, the server performs various tests on the client to validate its
authenticity to access files on the server. These tests become more stringent as the security
levels increase, which means that starting the server at level 5 provides the highest level of
security to files on the server.
When the RM/InfoExpress UNIX server is run with security enabled, the server-user-name
passed from the client is used, if possible, as the User ID while accessing files. If the server-
user-name is not present (as is the case for older versions of the RM/InfoExpress client) or
invalid, the server will either run the process with the default server user or disallow the client
connection to the server. Only servers running at security level 0 or 1 will use the default
server user. A server running at security level 0 or 1 will terminate with an error if the default
server user is invalid. Servers running at security level 2 or higher will disallow the client
connection unless the server-user-name is present and valid. See Setting Up the Network to
Run RM/InfoExpress with Security Enabled (on page 58) for more information.
The RM/InfoExpress UNIX server security levels are summarized in Table 1. Terminology
used in the table is defined following the table.
Table 1: RM/InfoExpress UNIX Server Security Levels

Server Security Level Requires To
0 A valid server-user-name. Verify that server-user-name is

valid. If validation fails, server runs
the process as the default server
user.


Server Security Level Requires To
1 A valid server-user-name. Verify that server-user-name and

.rhosts entry are valid. If validation
An appropriate entry in the fails, server runs the process as the
.rhosts file default server user.
.rhosts entry are valid. If validation
An appropriate entry in the fails, client connection is
.rhosts file. disallowed.
password are valid. If validation
An appropriate entry in the fails, client connection is
ixpwfile file. disallowed.
The correct user password.
The password is normally
obtained from ixpwfile on
the client.
4 A valid server-user-name. Verify that server-user-name,
.rhosts entry, ixpwfile entry, and
An appropriate entry in the password are valid. If validation
.rhosts file. fails, client connection is
An appropriate entry in the disallowed.
ixpwfile file.
The password is normally
obtained from ixpwfile on
the client.
5 A valid server-user-name. Verifies that server-user-name,
.rhosts entry, ixpwfile entry, and
An appropriate entry in the password entered by the user are
.rhosts file. valid. If validation fails, client
An appropriate entry in the connection is disallowed.
ixpwfile file.
The user must enter the
password on the client.
Server-User-Name
In Table 1, a “valid server-user-name” means that the ixpwfile file on the client contains
an entry specifying the name of the server machine, the name of the client machine, and a
valid user-name to be used on the server. For more information, see ixpwfile File Entry
(on page 56).
Default Server User

At security level 0 or 1, the server allows the client to run as a default user on the server
when the client fails to meet the security requirements of the server. Normally, the default
server user will be allowed to access files that do not require high levels of security. The

default server user, which must be a valid user on the server, is specified using the
configuration parameter, DefaultServerUser. For more information about this parameter,
refer to UNIX Server-Specific Configuration Options (on page 92). See also the discussion
of compatibility of older clients with the new server in Server Compatibility with Older and
Newer Clients (on page 57).
.rhosts File Entry

The .rhosts file, present in each user’s home directory on the server, is used by the UNIX
operating system to validate the permissions of clients who try to access the files on the server
owned by the local user. This ASCII file contains information about the client machine and
one of its users. The following is a template for an entry line in the .rhosts file:
machine-name [user-name]
where machine-name is the node name of a client machine, and user-name is the name of the
user on that machine who, when connected to the server, will obtain the owner’s permissions
on files owned by the local user. If user-name is not found on the entry, all the users on the
client machine have permission to access files.
Note user-name refers to the name used on the client machine, not on the server machine.
The user-name may match the name used on the server machine, or it may be different.
An “appropriate entry in the .rhosts file” in Table 1 (on page 54) means that the .rhosts file
exists in server-user-name’s home directory, the .rhosts file owner is server-user-name, only
the owner has write permissions (that is, the file permissions must be “rw-r--r--”), and a line
exists in the .rhosts file specifying client machine-name and, optionally, the client user-name.
ixpwfile File Entry

To successfully establish a session with the server running at one of the six security levels,
clients must pass certain information to the server at the time the session is established. This
information is created and stored in an ixpwfile security parameter file for each client and
each server system.
Each record in the ixpwfile security parameter file consists of four fields:
{server-machine-name, client-machine-name, server-user-name, password}
where server-machine-name is the name of the machine running the RM/InfoExpress UNIX
server with which the client (client-machine-name) will establish the session. server-user-
name is the name of the user on the server by which the client is known. password is the
password string of the user (server-user-name) on the server.
For information about how to run the utility program to create and update ixpwfile, refer to
An “appropriate entry in the ixpwfile file” in Table 1 (on page 54) means that the ixpwfile
file on the server (pointed to in the rmixsrvr.ini configuration file) contains an entry
specifying the server-machine-name, client-machine-name, and server-user-name. Note
that the password should not be present in the entry on the RM/InfoExpress server. The
password is ignored.

User Password
In Table 1, “correct user password” means that the password sent by the client matches the
UNIX system password for server-user-name on the server.
Additional Parameters Needed for Non-UNIX Clients

Every UNIX and 32-bit Windows machine on the network is recognized by its node name.
There is, however, no concept of a node name on a machine running the Windows 3.1
operating system. For proper recognition, workstations running Windows 3.1 must define the
client-machine-name using the ClientName configuration parameter.
Note This discussion of the ClientName configuration parameter is for backward-
compatibility issues only as this option was provided for 16-bit Windows clients.
RM/InfoExpress no longer supports this option.
Client Validation by the Server at Different Security

Levels
At the time the connection between the client and the server is established, each client passes
information obtained from the ixpwfile security parameter file and the configuration file to
the RM/InfoExpress UNIX server. The server then validates this information using the UNIX
security database files such as etc/passwd, $HOME/.rhosts, and so forth, and the ixpwfile
security parameter file on the server.
Server Compatibility with Older and Newer Clients

The following server and client compatibility issues are discussed below.
Older Clients with the New Server

Earlier versions of RM/InfoExpress clients can communicate with the new server running in
“compatibility mode” (that is, no security level specified or at security levels 0 or 1). These
clients run as the default server user. When the server security level is 2 or greater, however,
the server rejects the client connections. One of the following error messages is displayed:
RMIX_ERR_SERVER_USERNAME_PARAM_NOT_FOUND
- or -
RMIX_ERR_USER_PASSWORD_NOT_FOUND
New Clients with an Older Server

New versions of RM/InfoExpress clients can communicate with older (pre-2.1) versions of
the RM/InfoExpress UNIX server without any problem. At the time the session is
established, the information passed by the new client will be ignored by the older server.

Setting Up the Network to Run RM/InfoExpress with

Security Enabled
The following sections provide instructions for setting up each of the six levels of file security
on the RM/InfoExpress UNIX server. (The setup differences between server security levels
are summarized in Table 2 on page 64.) In these procedures, two UNIX machines are
connected to a network and are known on that network as serverU and clientU. A third
machine running Windows, known on the network as clientW, is also connected on the same
network.
A UNIX user running RM/COBOL with the RM/InfoExpress client on machine clientU wants
to access data files on the RM/InfoExpress server running on machine serverU. On the client
machine, the user logs in as clientUser1, but on the server machine, the user logs in as
serverUser1 with password pass1. (Note that serverUser1 may be the same as or different
from clientUser1.)
Similarly, a Windows user running RM/COBOL with the RM/InfoExpress client on machine
clientW wants to access data files on the RM/InfoExpress server running on machine serverU.
On the client machine, the user is known as clientUser2, but on the server machine the user is
known as serverUser2 with password pass2. (Note that serverUser2 may be the same as or
different from clientUser2.)
It is assumed that the following software is installed and available:
• RM/COBOL with the RM/InfoExpress client on the UNIX client machine (in directory
/usr/rmcobol) and on the Windows client machine (in directory c:\rmcobol)
• RM/COBOL on the UNIX server machine (in directory /usr/rmcobol)
• RM/InfoExpress server on the UNIX server machine (in directory /usr/rminfox)
The following notes apply to the procedures for setting up RM/InfoExpress to run at each of
the six security levels:
Note 1 “create an ixpwfile” means to run runcobol ixsecure.cob with your current directory
set to where you want the ixpwfile security parameter file to reside or with the IXPWFILE
environment variable pointing to the path.
Normally, ixpwfile on the UNIX server is maintained by the RM/InfoExpress server
administrator, and only such file is present on the UNIX server machine, generally in the
/usr/rminfox directory. The ixpwfile file on a Windows client machine is normally
maintained by the owner of the Windows machine and resides in the RM/COBOL install
directory, c:\rmcobol. On a UNIX client machine, each RM/InfoExpress client has his own
copy of ixpwfile. The client or server configuration file (either rmixclnt.ini or rmixsrvr.ini)
can be used to configure other locations for ixpwfile. The environment variable IXCONFIG
may be used to specify the location and pathname of the configuration file on UNIX.
RM/COBOL with the RM/InfoExpress client will look for ixpwfile in the location specified
by the IxPwFile option in the Security section of the client configuration file. If the IxPwFile
option is not present in the configuration file, then RM/COBOL with the RM/InfoExpress
client will attempt to open file ixpwfile in the current working directory.
If the server security level is 3 or 4, passwords may be stored in the client ixpwfile;
therefore, it should reside in a secure place (with appropriate owner and restrictive
permissions on UNIX).
Note 2 “create a filename.ini file” means to use a text editor of your choice to create the
appropriate configuration file:
• /usr/rminfox/rmixsrvr.ini for a UNIX server.

• c:\windows\rmixclnt.ini for a Windows client.

• /usr/rmcobol/rmixclnt.ini for a UNIX client, if only a single client configuration file is
to be used when no user passwords are required in the security parameter file. If multiple
configuration files are required so that each UNIX user can be responsible for the UNIX
system password stored in a tradition ixpwfile file, then the configuration file should be
placed in the current working directory or located using the IXCONFIG environment
variable.
Note 3 “create a .rhosts file” means to use a text editor of your choice to create a file named
.rhosts in the home directory of serverUser. The owner of the file must be serverUser and
only the owner can have write permission. The .rhosts file entry is the following:
clientU clientUser
clientUser is optional; if not present, any client user-name on machine clientU is allowed.
clientUser is a client user-name, not a server-user-name such as serverUser. Although
clientUser and serverUser are often the same user-name, this is not required.
Note 4 Notation of the form:
serverU/clientU/serverUser1/pass1
will be used to indicate an ixpwfile entry with serverU as the server-machine-name, clientU
as the client-machine-name, serverUser1 as the server-user-name, and pass1 as the UNIX
system password for the UNIX user ID serverUser1. The password will only be present for
security levels 3 and 4.
Setup for Running RM/InfoExpress at Server Security Level 0

1. Create an ixpwfile file (see Appendix E on page 97) on each of the two client machines,
clientU and clientW.
a. On machine clientU, create an ixpwfile file and enter:
serverU / clientU / serverUser1
b. On machine clientW, create an ixpwfile file and enter:
serverU / clientW / serverUser2
2. Create a configuration (.INI) file (see Appendix D on page 83) on each of the three
machines, clientU, clientW, and serverU.
a. On machine clientU, create rmixclnt.ini and enter:
[Security]
ixpwfile=<path>
b. On machine clientW, create rmixclnt.ini and enter:
[Security]
ixpwfile=<path>
c. On machine serverU, create rmixsrvr.ini and enter:

[Security]
ServerSecurityLevel=0
DefaultServerUser=<server-user-name>
3. Start the RM/InfoExpress server on machine serverU, as described in Starting the

RM/InfoExpress UNIX Server Program (on page 27).
4. Run the application on machines clientU and clientW.

[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>
[Security]
DefaultServerUser=<server-user-name>
3. Create two .rhosts files (see page 56) on machine serverU.

a. Log in as serverUser1, create $HOME/.rhosts and enter:
clientU clientUser1
b. Log in as serverUser2, create $HOME/.rhosts and enter:
clientW clientUser2



[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>
[Security]

clientU clientUser1
clientW clientUser2


1. Create an ixpwfile file (see Appendix E on page 97) on each of three machines, clientU,
clientW, and serverU.
serverU / clientU / serverUser1 / pass1

serverU / clientW / serverUser2 / pass2
c. On machine serverU, create an ixpwfile and enter:

machines, clientU, clientW and serverU.
[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>


serverU / clientU / serverUser1 / pass1
serverU / clientW / serverUser2 / pass2
c. On machine clientW, create an ixpwfile file and enter:

[Security]
ixpwfile=<path>

[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>

clientU clientUser1
clientW clientUser2


c. On machine clientW, create an ixpwfile file and enter:

[Security]
ixpwfile=<path>
[Security]
ixpwfile=<path>

[Security]
ixpwfile=<path>

clientU clientUser1
clientW clientUser2

5. Run the application on machines clientU and clientW. The appropriate password entry
dialog box is displayed.
Setup Differences Between Server Security Levels

Table 2 summarizes the differences between the setup procedures for each server security
level and the setup for the next higher level.
Note The entry in ServerSecurityLevel=number in step 2c of each setup procedure is
incremented by one, beginning with level 1.
Table 2: Summary of Setup Differences Between Server Security Levels
Summary of Setup Differences Between Server Security Levels
Server Security Levels Setup Differences
0 and 1 Setup for level 1 adds step 3, which is the requirement for .rhosts files
1 and 2 Setup for level 2 does not support older clients (such as 16-bit
Windows clients). The DefaultServerUser=<server-user-name> entry
in level 1 step 2c is not needed because the server at level 2 refuses the
connection rather than running as <server-user-name>.
2 and 3 Setup for level 3 uses passwords rather than .rhosts files. Steps 1a
and 1b requires the entry of passwords in the client ixpwfile entries,
and level 3 step 1c is added because the server requires ixpwfile
entries (passwords are not needed here) for the clients that will
connect to it. Level 3 step 2c adds the ixpwfile=<path> entry so that
the server can access the ixpwfile file created by level 3 step 1c.
Level 2 step 3, which is the .rhosts file requirement, is not needed at
level 3.
3 and 4 Setup for level 4 adds step 3, which is the requirement for .rhosts files
4 and 5 Setup for level 5 does not require passwords in steps 1a and 1b for the
client ixpwfile entries because the server forces clients to make the
user enter the password via a dialog box on the client machine.


Error Message Types
Appendix A: Messages
This appendix lists the error messages that can occur while RM/InfoExpress is being used.
Error Message Types

Errors that can occur when using RM/InfoExpress fall into two categories:
• COBOL errors, which do not start with the value 30. These errors are described in the
appropriate RM/COBOL user’s guide.
• Non-COBOL permanent errors, which have the following format:
30, error type, error code
where,
error type is used to identify the software that generates the error.
error code is the number returned by that software.
Table 3 lists each error type, the error codes that can occur with each type, and the possible
source of the error code for errors generated by RM/InfoExpress. Other error codes
associated with error types such as UNIX and Windows can be found in the appropriate
vendor documentation.
A complete description of each error type can be found in Permanent Error Types (on
page 68). A complete description of possible error codes begins on page 69.
Notes
• For more information on error messages, refer to “Error Message Types” and “Error
Message Formats” in Appendix A: Runtime Messages, in the RM/COBOL User’s Guide.
• Earlier versions of RM/InfoExpress usually returned two errors: 255 for network-
specific errors and 254 for errors detected by RM/InfoExpress. In this version of
RM/InfoExpress, errors are returned as they occur, along with the appropriate error code.

Permanent Error Types
Table 3: Error Types and Associated Error Codes
Error Types and Associated Error Codes

Permanent Error Type Possible Error Code Possible Error Code
(Number and Description) (Number/Description) (Source)
15 - RM/InfoExpress 1 - 13 RM/InfoExpress API

Server Error
21 - 59 RM/InfoExpress
12xxx RM/InfoExpress Windows
Sockets Interface
4xx - 5xx RM/InfoExpress BSD
Sockets Interface
16 - RM/InfoExpress 21 - 59 RM/InfoExpress
Client Error
12xxx RM/InfoExpress Windows
Sockets Interface
4xx - 5xx RM/InfoExpress BSD
Sockets Interface
21 - RM/InfoExpress 10xxx - 11xxx Windows Sockets
WinSock Error
Permanent Error Types
Error type 15: RM/InfoExpress Server Error
The RM/InfoExpress server generates this type of error when it encounters an error within its
code. Errors such as incorrect File Access Protocol (FAP) message received from the client,
out-of-memory, and so forth, fall into this category.
Possible error codes for error type 15 are described in the following topics:
• RM/InfoExpress API-Generated Error Codes (on page 69)
• RM/InfoExpress-Generated Error Codes (on page 71)
• RM/InfoExpress Windows Sockets Interface Error Codes (on page 77)
• RM/InfoExpress BSD Sockets Interface Error Codes (on page 78)
Error type 16: RM/InfoExpress Client Error
The RM/InfoExpress client generates this type of error when it encounters an error within its
code. Errors such as incorrect File Access Protocol (FAP) message received from the
RM/COBOL program (runcobol), incorrect FAP response from the server, out-of-memory,
and so forth, fall into this category.
Possible error codes for error type 16 are described in the following topics:
• RM/InfoExpress-Generated Error Codes (on page 71)
• RM/InfoExpress Windows Sockets Interface Error Codes (on page 77)

RM/InfoExpress API-Generated Error Codes
• RM/InfoExpress BSD Sockets Interface Error Codes (on page 78)
Error type 21: RM/InfoExpress WinSock Error
RM/InfoExpress generates this type of error when either the Windows client program or the
Windows server program receives an error from the underlying Windows Sockets software.
Possible error codes are described in RM/InfoExpress WinSock Error Codes (on page 75).

Error codes 1 through 13 are common to the server program, the server display (screen
handler) program, and the API application.
Error code 1: RMIX_API_ERR_SERVER_ALREADY_EXISTS
Failure Definition: Indicates that the server being started encounters a server already running
in the system, or at least one of its components is present in the system.
Action: For RM/InfoExpress running on UNIX, this error occurs if the server invoked
previously is not terminated, or it is terminated improperly. If the server has been terminated
improperly, remove the related IPC (Inter Process Communications) objects (shared memory,
key starting with 0x49584D and semaphore, key starting with 0x495853, displayed using the
ipcs command) using the UNIX command ipcrm.
Error code 2: RMIX_API_ERR_OUT_OF_MEMORY
Failure Definition: Indicates that there is not enough memory available in the system for
RM/InfoExpress (server or server display programs) to continue.
Action: Bring down all the connected clients, bring down the server, and make more memory
available before starting the server again.
Error code 3: RMIX_API_ERR_TOO_MANY_USERS
Failure Definition: Indicates that too many server display programs are being invoked. The
limit is nine for UNIX and Windows.
Action: Close any unnecessary server display applications.
Error code 4: RMIX_API_ERR_NOT_AUTHORIZED
Failure Definition: Indicates that the application using the server API attempted either to
open the server database with a mode other than O_RDONLY, or it used an unauthorized
API. This message may also indicate that the server display executable is corrupted.
Action: In case of a corrupted server display executable, install RM/InfoExpress again.
Error code 5: RMIX_API_ERR_SERVER_NOT_PRESENT
Failure Definition: Indicates that either the application using the server API or the server
display application is being started without the server having been started.

Action: Start the server and then start the application.
Error code 6: RMIX_API_ERR_CLIENT_ID_NOT_FOUND
Failure Definition: Indicates a malfunction of either the server or the server display program.
Action: Bring down all the connected clients, terminate the server, and restart.
Error code 7: RMIX_API_ERR_TOO_MANY_CLIENTS
Failure Definition: Indicates that the server has run out of free slots for remote clients.
Action: Bring down unused client connections to release some slots on the server.
Alternatively, you can also perform one of the following:
• Edit the server configuration file, rmixsrvr.ini, to include the UseCount option. For
more information, see Common Server-Specific Configuration Options (on page 90).
• Bring down all the connected clients, terminate the server, and restart with the -k
command line option. For more information, see Chapter 2: Configuring and Running
the RM/InfoExpress Server (on page 27).
Error code 8: RMIX_API_ERR_TOO_MANY_FILES
Failure Definition: Indicates that the server has run out of the free slots for open files.
Action: Close inactive open files from the client applications. Alternatively, edit the server
configuration file, rmixsrvr.ini, to include the FileCount option. For more information, see
Common Server-Specific Configuration Options (on page 90).
Error code 9: RMIX_API_ERR_CLIENT_NOT_FOUND
Failure Definition: Indicates a server malfunction.

Error code 11: RMIX_API_ERR_FILE_NOT_FOUND
Error code 12: RMIX_API_ERR_SERVER_APPLICATION_MISMATCH
Failure Definition: Indicates that either the server display or the server API application that
is being started does not match the server running in the system.
Action: Use a matching server display. Also, make sure that the server display and the server
belong to same release, even though they support the same protocol.
Error code 13: RMIX_API_ERR_SERVER_DATABASE_NOT_OPEN

RM/InfoExpress-Generated Error Codes

Error codes 21 through 59 are common to the client, the server, and the server display.
Error code 21: RMIX_ERR_INVALID_FAP_MESSAGE
Failure Definition: Indicates an RM/InfoExpress system error.

Action: Contact Micro Focus Customer Care for assistance.
Error code 22: RMIX_ERR_FILE_HANDLE_NOT_FOUND

Error code 23: RMIX_ERR_OUT_OF_MEMORY
Failure Definition: Indicates that there is not enough memory available in the system for
RM/InfoExpress (client or server) to continue.
Action: If the associated error type is 15 (RM/InfoExpress Server Error), bring down all the
connected clients, bring the server down, and make more memory available before starting the
server again. If the associated error type is 16 (RM/InfoExpress Client Error), terminate the
client application and restart it after making more memory available on the client system.
Error code 24 RMIX_ERR_SESSION_REJECTED
Failure Definition: This error is reported by either the Windows client or the server. When
returned by the server, it indicates a problem with the network interface. When returned by
the Windows client, it indicates that the RM/COBOL runtime does not match the client.
Action: If returned by the server, contact Micro Focus Customer Care for assistance. If
returned by the client, use the version of the runtime that matches the Windows client.
Error code 26 RMIX_ERR_SIGNAL_CAUGHT

Error code 27 RMIX_ERR_FAP_MANIPULATION

Error code 28 RMIX_ERR_IPC_OBJECTS_REMOVED
Failure Definition: Indicates that the server or the server display discovered Inter Process
Communications (IPC) objects missing in the system. This error is specific to the server and
the server display for UNIX.

Action: It may be that the IPC objects have been removed accidentally. Remove the other
IPC objects and start the server and/or the server display again.
Error code 30 RMIX_ERR_INVALID_COMMAND

Error code 32 RMIX_ERR_TOO_MANY_CLIENTS
Failure Definition: The server reports this error when the number of clients exceeds the value
specified on the -k option (or the UseCount configuration file option) or the number of
licensed use counts, whichever is less.
Action: Restart the server with a larger value on the UseCount configuration file option, as
described in Common Server-Specific Configuration Options (on page 90), or use a server
licensed for more users.
Error code 33 RMIX_ERR_DEF_USER_NAME_NOT_FOUND
Failure Definition: The server, running at a security level of 0 to 2, reports this error when it
detects that the name specified on the DefaultServerUser configuration file option or the user
name rmserver is not a valid user on the server machine. This error may also occur if root is
specified as the default user name.
Action: Using system administration tools, add a new user with the name specified. If that
user already exists, check the etc/passwd file.
Error code 34 RMIX_ERR_SECURITY_INFO_NOT_FOUND
Failure Definition: The RM/InfoExpress server reports this error when it cannot find a match
for the server-user-name, client-machine-name, and server-machine-name triple passed by the
client in the server’s security parameter file, ixpwfile.
Action: Update ixpwfile by using the utility program ixsecure.cob on both the client and
the server machines to add an entry for the client-machine-name and the server-user-name
pair. For more information, see Chapter 6: File Security on the RM/InfoExpress UNIX Server
(on page 53) and Appendix E: RM/InfoExpress Security Parameter File Update Utility (on
page 97). For a Windows client, the client name is the Windows computer name. For a
UNIX client, this is the node name and is given by the uname command.
Error code 35 RMIX_ERR_USER_PASSWORD_PARAM_NOT_FOUND
Failure Definition: This error is normally reported by the RM/InfoExpress server running at
a security level of 3 or higher.
Error code 36 RMIX_ERR_SYSTEM_PASSWORD_MISMATCH
Failure Definition: The server, running at a security level of 3 or higher, reports this error
when it detects that the password string stored in the ixpwfile security parameter file on the

client machine and on the server machine, and the password stored in the UNIX system, do
not match.
Action: See that the password string entered interactively at the client terminal or stored in
ixpwfile on the client machine matches the password string stored in ixpwfile on the server
machine and the one stored in the UNIX system. To update the password entry in ixpwfile,
use the utility program ixsecure.cob. See Appendix E: RM/InfoExpress Security Parameter
File Update Utility (on page 97).
Error code 37 RMIX_ERR_SYSTEM_PASSWORD_NOT_FOUND
Failure Definition: The server, running at a security level of 3 or higher, reports this error
when it cannot locate the user password in the UNIX system security database.
Action: This error normally occurs on UNIX systems that maintain the security database in a
file different from the /etc/passwd file. This indicates that one or both of these files have
been corrupted. Contact your system administrator.
Error code 38 RMIX_ERR_RHOSTS_FILE_OPEN_ERROR
Failure Definition: The server reports this error when it cannot open the .rhosts file in the
user’s home directory.
Action: Seek your server administrator’s help in creating the .rhosts file with appropriate
entries in the user’s home directory on the server machine.
Error code 39 RMIX_ERR_RHOSTS_FILE_PERMISSIONS_INVALID
Failure Definition: The server reports this error when it finds the permissions of the .rhosts
file in the user’s home directory to be invalid.
Action: Set the permissions of the .rhosts file in the user’s home directory on the server
machine to be “-rw-r--r--” and make certain that the user is the owner of this file.
Error code 40 RMIX_ERR_ENTRY_NOT_FOUND_IN_RHOSTS_FILE
Failure Definition: The server reports this error when it fails to find a matching client name
entry (with the client-machine-name parameter passed by the client machine) in the .rhosts
file on the server machine.
Action: With the help of your server administrator, edit the .rhosts file in the user’s home
directory on the server machine and add a new entry containing the client-machine-name and
an optional server-user-name.
Error code 41 RMIX_ERR_NO_SESSION
Failure Definition: Both the server and the client may report this error. Although not fatal,
this error is still considered an RM/InfoExpress system error.

Error code 42 RMIX_ERR_SERVER_USER_NAME_PARAM_NOT_

FOUND
detects that the server-user-name parameter is absent in the information passed by the client
when connections are established.
Action: This error may occur when an old client tries to establish a connection with the new
server running at security level 2 or higher. This error may also occur when the new client
cannot provide the required information to the server due to some problem in processing the
security parameter file, ixpwfile (for example, the file is not present on the client machine).
Upgrade to a new version of the RM/InfoExpress client in order to use security features on the
server.
Error code 43 RMIX_ERR_CLIENT_MACH_NAME_PARAM_NOT_

FOUND
detects that the client-machine-name parameter is absent in the information passed by the
client when connections are established.
Action: This error may occur when an old client tries to establish a connection with the new
server running at security level 2 or higher. This error may also occur when the new client
cannot provide the required information to the server due to some problem in processing the
security parameter file, ixpwfile (for example, the file is not present on the client machine).
Upgrade to a new version of the RM/InfoExpress client in order to use security features on the
server.
Error code 44 RMIX_ERR_SERVER_SECURITY_INFO_FILE_ERROR
Failure Definition: This error occurs when the server fails to open the security parameter file,
ixpwfile, on the server machine.
Action: Make sure that a valid security parameter file, ixpwfile, is present on the server
machine. If this file does not exist, create it using the ixsecure.cob utility program (see
Appendix E).
Error code 45 RMIX_ERR_MALFORMED_MESSAGE
Failure Definition: Indicates an RM/InfoExpress system error. This error occurs when either
the client or the server fails to decompress the message received from the session partner.
Error code 46 RMIX_ERR_NO_MEMORY_FOR_COMPRESSION
Failure Definition: There was insufficient memory to compress or decompress the data.
Action: Set the IxCompress configuration file option to No to disable message compression,
as described in Common Configuration Options (on page 85). Message compression should
not be used for records of more than 64000 bytes.

RM/InfoExpress WinSock Error Codes
Error code 47 RMIX_ERR_TOO_MANY_FILES
Failure Definition: The client(s) have exceeded the total number of open files supported by
the server.
Action: Increase the value of the FileCount configuration file option and restart the server, as
discussed in Common Server-Specific Configuration Options (on page 90).
Error code 48 RMIX_ERR_SYSTEM_PASSWORD_FILE_OPEN_

ERROR
Failure Definition: This error occurs when an invalid /etc/passwd file (which may be
missing) or the server-user-name with which the client is trying to run is not present on the
server machine.
Action: Contact your system administrator.
Error code 49 RMIX_ERR_CLIENT_SECURITY_INFO_FILE_ERROR
Failure Definition: This error occurs when the client fails to open the security parameter file,
ixpwfile, on the client machine.
Action: Make sure that a valid security parameter file, ixpwfile, is present on the client
machine. If this file does not exist, create it using the ixsecure.cob utility program. See
Error codes 50 — 59
Failure Definition: Error codes 50 through 59 represent internal errors in the

RM/InfoExpress server program. Error code 54 may indicate an attempt to use an old client
with a new server in a mode other than compatibility mode.

Table 4 lists the possible error codes for permanent error type 21, which is described on
page 69. Codes in the 10000 range represent network or system errors. Codes in the 11000
range represent database errors.
Table 4: Error Codes Generated by Windows Sockets
Error Codes Generated by Windows Sockets

Error Windows Sockets Error
Code Description Equivalent UNIX Error Equivalent
10004 Interrupted system call WSAEINTR EINTR

10009 Bad file number WSAEBADF EBADF
10013 Permission denied WSAEACCES EACCES
10014 Bad address WSAEFAULT EFAULT
10022 Invalid argument WSAEINVAL ENOTSOCK


10024 Too many open files WSAEMFILE EMFILE
10035 Operation would block WSAEWOULDBLOCK EWOULDBLOCK
10036 Blocking operation in WSAEINPROGRESS EINPROGRESS
progress
10037 Operation already in WSAEALREADY EALREADY
progress
10038 Operation on non-socket WSAENOTSOCK ENOTSOCK
10039 Destination address WSAEDESTADDRREQ EDESTADDRREQ
required
10040 Message too long WSAEMSGSIZE EMSGSIZE
10041 Wrong protocol type WSAEPROTOTYPE EPROTOTYPE
10044 Socket type not supported WSAESOCKTNOSUPPORT ESOCKTNOSUPPORT
10045 Operation not supported WSAEOPNOTSUPP EOPNOTSUPP
10046 Protocol family not WSAEPFNOSUPPORT EPFNOSUPPORT
supported
10047 Address family not WSAEAFNOSUPPORT EAFNOSUPPORT
supported
10048 Address already in use WSAEADDRINUSE EADDRINUSE
10049 Cannot assign address WSAEADDRNOTAVAIL EADDRNOTAVAIL
10050 Network is down WSAENETDOWN ENETDOWN
10051 Network is unreachable WSAENETUNREACH ENETUNREACH
10052 Network reset connection WSAENETRESET ENETRESET
10053 Connection was aborted WSAECONNABORTED ECONNABORTED

10054 Peer reset connection WSAECONNRESET ECONNRESET
10055 No available buffer space WSAENOBUFS ENOBUFS
10056 Socket already connected WSAEISCONN EISCONN
10057 Socket not connected WSAENOTCONN ENOTCONN
10058 Socket was shut down WSAESHUTDOWN ESHUTDOWN
10059 Too many references WSAETOOMANYREFS ETOOMANYREFS
10060 Connection timed out WSAETIMEDOUT ETIMEDOUT
10061 Connection refused WSAECONNREFUSED ECONNREFUSED
10062 Symbolic link loop WSAELOOP ELOOP
10063 Pathname too long WSAENAMETOOLONG ENAMETOOLONG
10064 Host is down WSAEHOSTDOWN EHOSTDOWN
10065 Host is unreachable WSAEHOSTUNREACH EHOSTUNREACH
10066 Directory not empty WSAENOTEMPTY
10067 Process limit WSAEPROCLIM
10091 Network is unusable WSASYSNOTREADY
10092 Version not supported WSAVERNOTSUPPORTED

RM/InfoExpress Windows Sockets Interface Error Codes

10093 Startup not done WSANOTINITIALISED
11001 Host not found WSAHOST_NOT_FOUND HOST_NOT_FOUND
11002 Try again WSATRY_AGAIN TRY_AGAIN
11003 No recovery WSANO_RECOVERY NO_RECOVERY
11004 No data WSANO_DATA NO_DATA
RM/InfoExpress Windows Sockets Interface Error

Codes
Codes in the 12000 range, shown in Table 5, are generated by the Windows Sockets interface
portion of the RM/InfoExpress Windows client program or the Windows server program and
represent memory allocation failures or unexpected conditions.
These errors are considered RM/InfoExpress system errors. When these errors are detected,
contact Micro Focus Customer Care for assistance.
Table 5: Error Codes Generated by the RM/InfoExpress Windows Sockets Interface
Error Codes Generated by the RM/InfoExpress Windows Sockets Interface

Error Code Description
12001 Insufficient memory for connect.

12002 Internal socket number already in use.
12003 Unexpected event occurred during connect.
12004 Unexpected error condition from connect.
12005 Unexpected event occurred during initial receive.
12006 Received data length error (client/server not synchronized).
12009 Received data length inconsistent with FAP message length.
12010 Unexpected event occurred during secondary receive.
12011 Unexpected event occurred during send.
12012 Internal buffer length too small for status.
12013 Insufficient memory for status.
12014 Unknown error during asynchronous wait.
12015 Unknown error during event wait.
12016 Received data length error.
12017 Unknown error during asynchronous-wait.

RM/InfoExpress BSD Sockets Interface Error Codes
Error Codes Generated by the RM/InfoExpress Windows Sockets Interface


RM/InfoExpress BSD Sockets Interface Error Codes

Error codes 401 through 413 are generated by the BSD Sockets interface portion of the
RM/InfoExpress client and the server. These error codes are defined in Table 6.
These errors are considered RM/InfoExpress system errors. When these errors are detected,
contact Micro Focus Customer Care for assistance.
Table 6: Error Codes Generated by the RM/InfoExpress BSD Windows Sockets

Interface
Error Codes Generated by the RM/InfoExpress BSD Windows Sockets Interface

401 Insufficient for connect.

402 Socket already in use.
403 Out of memory.
409 Received data length inconsistent with FAP message length.
412 Internal buffer length too small for status.
501 BSD Sockets error HOST_NOT_FOUND.
502 BSD Sockets error TRY_AGAIN.
503 BSD Sockets error NO_RECOVERY.
504 BSD Sockets error NO_DATA.

Limits and Ranges
Appendix B: Limits and Ranges
Appendix B: Limits and Ranges
This appendix describes RM/InfoExpress limits and ranges.
Limits and Ranges

The following limitations apply to RM/InfoExpress:
1. It is not possible to run more than one RM/InfoExpress server program at a time on a
given machine.
2. No more than nine RM/InfoExpress UNIX and Windows server display (screen handler)
programs may be run at one time on a given machine.

Failure to Locate File or Path
Appendix C: Troubleshooting RM/InfoExpress
Appendix C: Troubleshooting
RM/InfoExpress
This appendix is designed to help if you run into any problems when using RM/InfoExpress.
Each section offers steps you can take to solve the problem.
Failure to Locate File or Path

Error messages that occur while accessing the file on the server machine, for example, “File
not found” or “Path not found”, generally indicate one of the following conditions:
1. The RM/InfoExpress UNIX server program is not running on a UNIX server machine. In
this case, load rmservertcp.
2. The complete filename (defined using the synonym or other means) does not correctly
point to the location on the server. Check your environment variables and synonyms.
3. In the case of a Windows client, the rmtcp32 and winsock DLLs are not in the
execution path.
4. For a Windows client, the runcobol configuration file contains an incorrect DLL name or
the DLL specified on the NAME option of the EXTERNAL-ACCESS-METHOD record
cannot be located.
5. Invoke the RM/InfoExpress server with the -c l option so that pathnames from Windows
clients will be converted to lowercase by the server.
6. While accessing files from a UNIX client, make certain that the machine name specified
in the pathname is the same as the one in the /etc/hosts file on the client machine. For
example, the machine name “HAL9000” in the pathname defined by
INXFL=//RS6000/rminfox/inxfl matches the name “HAL9000” in the /etc/hosts file
entry 111.22.333.44 hal9000 HAL9000.
RM/InfoExpress Client Entries Not Terminating

Certain situations on some versions of UNIX, when running RM/InfoExpress using the
TCP/IP protocol, can cause the server not to notice that a client has been terminated. This
occurs only if the client is terminated in a non-standard method, such as turning off the client
workstation or experiencing a system failure on the client workstation. In such instances, the

Removing IPC Objects After Server Failure
Appendix C: Troubleshooting RM/InfoExpress
RM/InfoExpress client is unable to inform the server that the client is terminating. Although
the operating system eventually notifies the RM/InfoExpress server that the connection has
been broken, it could take several hours on some implementations of UNIX before the
notification occurs.
One version of UNIX that exhibits this behavior is AIX running on the RS/6000. To reduce
the amount of time before the inactivity on a TCP/IP connection is interpreted as a lost
connection under AIX, use the following no command:
no -o tcp_keepidle=200 -o tcp_keepintvl=60
where,
-o is a network option.
Note On AIX 5.2, there is a defect that prevents a single no command from having two -
o options. In this case, you must use two no commands.
tcp_keepidle determines the number of half-seconds to wait after the last successful I/O
operation before attempting to determine whether a connection has been lost.
tcp_keepintvl determines the number of half-seconds to wait between requests for a
response from the possibly lost connection.
After ten requests with no response, the operating system reports a lost connection to the
server. The settings shown in this example will report a broken connection after 400 seconds
(100+30*10).
Note You must run the no commands each time the network is started since it does not
permanently change the default configuration values.
Removing IPC Objects After Server Failure

The recommended way to terminate the server is by using the command sequence (Terminate,
Server, Now, Yes) of the screen display (screen handler) program when no active client is
connected.
Using the kill command causes the RM/InfoExpress UNIX server to exit without removing
the IPC (Inter Process Communications) objects, such as shared memory segments and
semaphores. Consequently, when the server is started next time, it fails with server error code
1 (RMIX_API_ERR_SERVER_ALREADY_EXISTS).
In this situation, remove the IPC objects using the following UNIX commands:
ipcrm -m <shm_id> -s <sem_id>
where the <shm_id> and <sem_id> objects are obtained by using the UNIX command:
ipcs
Note that the key values for RM/InfoExpress IPC objects start with the value 0x49584D for
shared memory and 0x495853 for semaphores.

Configuration Files and Options
Appendix D: Configuring RM/InfoExpress
Appendix D: Configuring
RM/InfoExpress
RM/InfoExpress can be uniformly configured across all implementations of clients and

servers. To maintain compatibility with previous versions of RM/InfoExpress, environment
variables supported by previous versions can be used to override the settings of the
configuration file. On the server, all the command line options can be specified in the
configuration file.
This appendix describes the configuration files and their options.

Even though the names of the configuration files used by different implementations of
RM/InfoExpress are different, the format of all these files is identical. The configuration files
are as follows:
Use To set configuration parameters for
rmixclnt.ini RM/InfoExpress Windows and UNIX client programs.

rmixsrvr.ini Either the RM/InfoExpress UNIX or the Windows server program.
For Windows clients and Windows servers, the configuration file must be present in the
Windows directory (usually C:\WINDOWS). For UNIX clients and UNIX servers, the
configuration file must be present in the current directory or the directory pointed to by the
environment variable, IXCONFIG.
In a configuration file, any line beginning with a semi-colon (;) is treated as a comment and is
not processed.
The client and server configuration files are divided into sections, each of which consists of a
group of related options that you can use to customize your implementation of
RM/InfoExpress. Some configuration options are used only by the client, while others are
used only by the server. Some options are specific to the type of server. Still others are
common to both client and server. All configuration options are shown in the sample
configuration file that follows. See the more detailed descriptions of the configuration
options on page 85.
Note Option names are not case-sensitive.

Sample Configuration File
[Debug]
;###Common###
InfoxDebug=debug filename
[Options]
;###Common###
IxCompress=Yes|No
ReconnectEnable=Yes|No
;###Client-Specific###
KeepSession=Yes|No
PathPrefixExcluded=list
PathPrefixIncluded=list
ReconnectDelay=number
StartupLogPath=directory-path
;###Server-Specific, All Servers###

DotsBias=number
FileBufferPool=number
FileCount=number
FileProcessCount=number
MinimumBlockSize=number
RoundToNiceBlockSize=Yes|No
UseCount=number
ReconnectTimeout=number
LargeFileLockLimit=number
InxUseLargeLimit=Yes|No
RelUseLargeLimit=Yes|No
SeqUseLargeLimit=Yes|No
;###Server-Specific, UNIX Server Only###

ConvertFileName=NoConvert|UpperCase|LowerCase
;###Server-Specific, Window Server Only###

UseCurrentDirectory=Yes|No
UseSystemShares=Yes|No
[Security]
;###Common###
EncodeData=Yes|No
IxPwFile=pathname
AcceptPassword=Yes|No
;###Server-Specific, UNIX Server Only###

DefaultServerUser=server-user-name
ServerSecurityLevel=number

Common Configuration Options
[Sharing]
;###Server-Specific, Windows Server Only###
share-name=share-path
[Tcp]
;###Common###
MaxSendSize=number
[Winsock]
;###Common###
IgnoreHangupError=Yes|No (Windows only)
UseBlockingIO=Yes|No

The following configuration options, listed alphabetically, are common to both the client and
server components of RM/InfoExpress:
• EncodeData. The EncodeData option in the [Security] section is used to encode
messages to provide more security to the data transmitted on the network.
EncodeData=No is the default. When the value is set to Yes, the RM/InfoExpress
component (either the client or the server) negotiates the encoding algorithm of the
messages exchanged with its session counterpart. If both the session partners have the
value set to Yes, the messages are encoded before they are sent and unencoded
immediately after they are received. However, if any of the session partners have the
value set to No, the message encoding does not take place. Message encoding will not
take place if either of the session partners is using a release of RM/InfoExpress earlier
than version 2.1.
• IgnoreHangupError. The IgnoreHangupError option in the [Winsock] section is used
only by RM/InfoExpress on Windows. If the value is IgnoreHangupError=Yes, any error
returned by Windows Sockets functions, called while the Windows client is trying to
disconnect the session with the server, are ignored. Do not specify this option unless
instructed to do so by Micro Focus Customer Care.
IgnoreHangupError=No is the default value. If the value is set to No, a possibly serious
error, should one occur while disconnecting the session with the server, is returned to the
Close operation. This is normal behavior for any I/O operation.
• InfoxDebug. The InfoxDebug option in the [Debug] section causes the file whose
pathname is given by debug filename to be created and trace information written into it.
After the client RM/COBOL application is terminated, send this file to Micro Focus
Customer Care for further investigation. Use this option only when you are investigating
a problem with the assistance of Micro Focus Customer Care. Using this option under
normal conditions affects client operations negatively.
On the server, the InfoxDebug configuration option is equivalent to the -d command line
option, as described in the appropriate sections of Starting the RM/InfoExpress UNIX
Server Program (on page 27) and Starting and Stopping the RM/InfoExpress Windows
Server Program (on page 29). Note that the command line option overrides the
configuration option.

• IxCompress. The IxCompress option in the [Options] section is used to compress

messages transmitted on the network. Depending on the compressibility of the messages,
which may contain COBOL data records, this option may improve the performance on
the network. IxCompress=Yes is the default. When the value is set to Yes, the
RM/InfoExpress component (either the client or the server) negotiates the compressibility
of the messages exchanged with its session counterpart. If both the session partners have
the value set to Yes, the messages are compressed before they are sent and decompressed
immediately after they are received. However, if any of the session partners have the
value set to No, the message compression does not take place. Message compression will
not take place if either of the session partners is using a release of RM/InfoExpress earlier
than version 2.1.
• IxPwFile. The value of pathname specified on the IxPwFile option in the [Security]
section is used to locate the file containing the security parameters. If this option is
absent, RM/InfoExpress looks for the security parameter file, ixpwfile, in the current
directory. See Chapter 6: File Security on the RM/InfoExpress UNIX Server (on
page 53).
• MaxSendSize. The MaxSendSize option in the [Tcp] section may be specified for those
TCP/IP implementations that have a limitation. We recommend that you leave this value
unspecified unless you know that the TCP/IP in use has a limitation. Some UNIX
systems have a limit of 4096 bytes. Note that this value is not the same value as the size
of the maximum packet allowed on the network
The value specified by the MaxSendSize option is used to determine whether the
RM/InfoExpress client or server code must perform multiple send operations on a given
message. The underlying TCP stack implementation determines the maximum allowable
value for a single send operation. Multiple send operations may be required for some
large messages. The TCP stack will transmit the data in as many network packets as
required by the underlying network. Again, for large messages, multiple network packets
may be required.
If I/O errors occur on a file with a record size larger than about 4000 bytes while files
with smaller record sizes perform normally, try specifying MaxSendSize=4096. The
default value is system-dependent, but is currently 4096 or larger. The value cannot be
less than 512.
On the server, the MaxSendSize configuration option is equivalent to the -z command
line option, as described in the appropriate sections of Starting the RM/InfoExpress
UNIX Server Program (on page 27) and Starting and Stopping the RM/InfoExpress
Windows Server Program (on page 29). Note that the command line option overrides
the configuration option.
• ReconnectEnable. The ReconnectEnable option in the [Options] section determines
whether reconnection logic in the client or server is enabled or disabled. For the client,
the option determines whether the client will attempt to reconnect the session with the
server if the connection is broken. For the server, this option determines whether the
server will keep the file manager process and the current state of its open files intact
waiting for the client to reconnect and continue from where it left off when the
connection was broken.
Both the client and server sides of a connection must have reconnection enabled for the
attempt to succeed. If the value is set to No for the client and the server, then they both
behave identically to previous RM/InfoExpress releases; that is, the client reports an error
to the COBOL program and the server closes files and terminates the file manager
process running on behalf of the client. The default value is Yes for the client and No for
the server. These defaults allow reconnection to any given server to be enabled simply
by changing the rmixsrvr.ini file for that server and starting the server again.

Client-Specific Configuration Options
Beginning with version 8, a limited reconnection capability, which allows a connection

that becomes broken to be reconnected automatically, has been added to the
RM/InfoExpress client and server logic. The client and server continue normal operation
without the client run unit (COBOL program) ever being aware of the disconnection.
The server writes a log file, named RMRECONN.LOG, which is created in the directory
specified in the environment variable RM_RECONN_LOG_PATH, if defined. If this
environment variable is not defined, the log file is created in the TEMP directory on
Windows or in the current directory on UNIX. Although it is not recommended, you can
disable the log file by setting the RM_RECONN_LOG_PATH environment variable to a
non-existent directory name.
TCP/IP provides a capability, known as “keepalive” support, to determine automatically
whether an idle connection is still intact. When a connection has been idle for a certain
period of time, TCP/IP transmits keepalive packets to see whether they are
acknowledged, thus indicating an intact connection. After several retries—with each
attempt receiving no acknowledgement—TCP/IP informs RM/InfoExpress that the
connection is broken.
Having keepalive support enabled and keepalive packets being sent every short interval
helps the reconnection logic work in a reasonable manner. Unfortunately, systems
typically have keepalive support disabled or set to occur only after two hours of
inactivity. Micro Focus recommends enabling keepalive support, if necessary, and
setting the keepalive delay time to a cycle of two minutes or less. Since the method of
setting these system TCP/IP variables varies from system to system, consult your system
administration documentation. On UNIX, these TCP/IP parameters are normally part of
the kernel parameters that UNIX system administrators can set. On all versions of
Windows, these TCP/IP parameters are set in the Windows registry under the following
key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameter
In particular, it is the value name KeepAliveTime, the REG_DWORD value that

defaults to 7,200,000 milliseconds (two hours), which is the value that Micro Focus
recommends changing to 120,000 milliseconds (two minutes) or less. More information
is available by searching the Microsoft Support Knowledge Base for “keepalive
configuration.” RM/InfoExpress calls the setsockopt function to enable the
SO_KEEPALIVE socket option.

The following configuration options, listed alphabetically, are specific to RM/InfoExpress
clients:
• AcceptPassword. The AcceptPassword option in the [Security] section specifies
whether the client should always accept passwords interactively. The default value is No.
The server requires a password from the client when the server is running at security
level 3, 4, or 5. At level 5, the server forces the client to always accept the password
interactively, ignoring any password stored in the ixpwfile file on the client machine.
When AcceptPassword=No is set and the server is running at level 3 or 4, the client
obtains the password from the ixpwfile on the client machine and sends it to the server.
When AcceptPassword=Yes is set and the server is running at level 3 or 4, the client
accepts the password interactively (as it does for level 5).

The server administrator may wish to set AcceptPassword=Yes on unsecured client

machines where it is undesirable to store any passwords (even though they are encoded)
in the ixpwfile on that client machine.
• KeepSession. Located in the [Options] section. KeepSession=Yes is the default. If the
value is set to Yes, the client keeps the session with the server until the run unit
terminates, even if all files on that server are closed before that time. This option is
sometimes necessary when the client application opens and closes files rapidly, causing
sessions to be established and released in rapid succession. Some network
implementations cannot handle such frequent session creation, which can lead to errors
and program hangs. This option may also improve performance slightly by eliminating
the overhead of releasing and re-establishing a session between the Close of one remote
file and the Open of another remote file on the same server. The drawback of specifying
this option is that sessions may be kept with several servers for long periods of time when
they will never be used again, thereby consuming network resources. Errors may occur if
some network resources are exhausted.
If the value is KeepSession=No, the client releases the session with the server when the
last open file is closed. In addition, the UNIX client supports this option as an
environment variable (also called KEEPSESSION), which when set, overrides the current
setting.
• PathPrefixExcluded and PathPrefixIncluded. These two configuration options are
both used to allow an RM/InfoExpress client to exclude selected UNC-style pathnames
(beginning with \\ or //) from access via RM/InfoExpress. (Prior to version 8,
RM/InfoExpress always attempted access to all UNC-style pathnames.) The
PathPrefixExcluded option in the [Options] section determines which pathname prefixes
are not to be accessed via RM/InfoExpress. The PathPrefixIncluded option in the
[Options] section determines which pathname prefixes can be accessed via
RM/InfoExpress.
In each option, the list is a comma-separated list of pathname prefix strings. Embedded
spaces within each string are kept while leading and trailing spaces are ignored.
Matching is case-insensitive and slash (/) matches backslash (\). Thus, \\SRV1\TMP is
equivalent to //srv1/tmp. Only whole edgenames are matched, where edgename means
the text between two slashes or backslashes or end of string. Consequently, //srv
matches //srv/tmp/file.ext but does not match //srv1/tmp/file.ext. No wildcard characters
are allowed.
Consider the following to determine when and how to use these closely related options:
− If only PathPrefixExcluded is specified, matching pathnames are excluded and all
other pathnames are included.
− If only PathPrefixIncluded is specified, matching pathnames are included and all
other pathnames are excluded.
− If both PathPrefixExcluded and PathPrefixIncluded are specified, the longest
matching prefix string determines exclusion or inclusion, and pathnames matching
none of the prefix strings are included by default.
− If neither PathPrefixExcluded nor PathPrefixIncluded is specified, all pathnames are
included (which is the same behavior as prior versions of RM/InfoExpress).
Typically, you would specify either PathPrefixExcluded or PathPrefixIncluded based
upon which pathname prefix list is the shortest or most well defined to enumerate.
However, both options can be specified for more complicated exclusion and inclusion
schemes.
For example, specifying:

PathPrefixExcluded=//srv1,//srv2
PathPrefixIncluded=//srv2/data,//srv2/tmp
means that an RM/InfoExpress client will not attempt to access any files on server srv1
and will attempt to access only files whose pathnames begin with //srv2/data or
//srv2/tmp on server srv2. You might want this in a situation in which srv2 is a Windows
server where all RM/InfoExpress data files reside in directories data and tmp, but there
are also Windows printers that you want to access via pathnames //srv2/printer1,
//srv2/printer2, and so forth. Note, however, that if printer1 and printer2 are the only two
pathnames that you do not want to access via RM/InfoExpress on srv2, then specifying
only the following would achieve the same result:
PathPrefixExcluded=//srv1,//srv2/printer1,//srv2/printer2
Any other pathname on srv2, such as //srv2/data/file, would be included by default since
that pathname does not match any excluded path prefix.
• ReconnectDelay. The ReconnectDelay option in the [Options] section determines the
number of milliseconds the client will delay before attempting to reconnect to the server
after the client becomes aware that the connection has been broken. The default value is
100 (one tenth of a second).
• StartupLogPath. The StartupLogPath option in the [Options] section creates a file
whose directory and pathname are given by directory-path, and writes logging
information into the file. This client-side log file can be used to diagnose and
troubleshoot problems when initially starting up the connection of the RM/InfoExpress
client to the RM/InfoExpress server. This log file indicates errors that are encountered in
the pre-connection, connect, and first message sent and received operations during the
initial connection to the server. The log file also contains the client-side host name, the
client-side IP address (from gethostbyname), the server-side host name, the server side IP
address, and the result of the connect request.
To configure the location of this log file, RMCLIENT.LOG, specify the following
configuration parameter in the [Options] section of the rmixclnt.ini file:
StartupLogPath=c:\Micro Focus\Logs
Note The environment variable, RM_CLIENT_LOG_PATH, may also be used to

configure and specify the location of the RMCLIENT.LOG file. Setting the environment
variable takes precedence over setting the configuration parameter in the rmixclnt.ini file
(as described above).
• UseBlockingIO. The UseBlockingIO option in the [Winsock] section is provided to
improve the performance of the RM/InfoExpress Windows client. If the value is
UseBlockingIO=Yes, Windows Sockets functions are called in blocking mode; that is,
every function call will block until the request is complete. Using this value also ensures
that Windows Sockets Asynchronous functions and the PeekMessage function are never
called. Substantial performance improvements may occur, depending upon the type of
Windows Sockets implementation used. However, the operator will not be able to cancel
a Read operation waiting on a locked record. We suggest users experiment using their
own benchmark programs to determine whether specifying the value Yes results in better
performance for the specific TCP/IP implementation in use.
If the value is UseBlockingIO=No (the default value), Windows Sockets Asynchronous
functions and the PeekMessage function are used; that is, functions are called in non-
blocking mode. If any COBOL program using the Windows client executes a Read
operation that waits on a locked record and the operator requires the ability to cancel that
operation, the UseBlockingIO option must be set to No.

Common Server-Specific Configuration Options
Sample RM/InfoExpress Windows Client Configuration

File
The following is a sample Windows client configuration file (rmixclnt.ini).
[Debug]
;;;InfoxDebug=DBGFILE
[Security]
IxPwFile=d:\tmp\IXPWFILE
[Winsock]
UseBlockingIO=Yes

CAUTION It is imperative that on every RM/InfoExpress server and RM/COBOL runtime
system accessing any particular file from any machine, the values specified for the
FileProcessCount, LargeFileLockLimit, RelUseLargeLimit, and SeqUseLargeLimit keywords
in the RM/InfoExpress server configuration file must match the values specified in the
corresponding configuration option in the RM/COBOL runtime system.
The following configuration options, listed alphabetically, are common to both the
RM/InfoExpress UNIX server and the Windows server programs:
• DotsBias. The DotsBias option in the [Options] section is used to specify where an
ellipsis (…) appears in filenames that are too long to fit in the display field of the server
display program. The leftmost part of the filename appears to the left of the dots and the
rightmost part of the filename appears to the right of the dots (the middle of the filename
is replaced by the ellipsis.) The default value is zero, which causes the ellipsis to appear
in the middle of the field. Negative values move the ellipsis to the left and positive
values move the ellipsis to the right. Special value +9999 moves the ellipsis completely
out of the right side of the field, thus displaying the leftmost part of the filename
(truncated). This is equivalent to RM/InfoExpress version 2.0 behavior. Special value -
9999 moves the ellipsis completely out of the left side so that the rightmost part of the
filename is displayed (with no ellipsis). This option is cosmetic and has no effect on
server operation other than the display.
• FileBufferPool. The FileBufferPool option in the [Options] section is used to specify the
common buffer pool size on the server machine. The default value is zero, which causes
the default size for the common buffer pool. Normally, you should not need to specify a
value. This option corresponds to the BUFFER-POOL-SIZE keyword in the RUN-
FILES-ATTR configuration record specified for runcobol, as described in Chapter 10:
Configuration, of the RM/COBOL User’s Guide.
The FileBufferPool configuration option is equivalent to the -p command line option,
as described in the appropriate sections of Starting the RM/InfoExpress UNIX Server
Program (on page 27) and Starting and Stopping the RM/InfoExpress Windows Server
Program (on page 29). Note that the command line option overrides the configuration
option.
• FileCount. The FileCount option in the [Options] section may be used to specify the
number of files the server can have open simultaneously. The default value is ten times

the UseCount. FileCount may need to be increased when every client application has
more than ten files on the server open simultaneously. Reducing FileCount will reduce
the server’s shared and local memory requirements.
• FileProcessCount. The FileProcessCount option in the [Options] section determines the
maximum number of run units that can have a file open at the same time. It applies to all
file organizations. For record and file locks to perform correctly, all RM/InfoExpress
servers and RM/COBOL runtime systems opening a file must use the same file process
count. The maximum value for this keyword is 16384; the minimum value is 8. The
default value is 1024. This option corresponds to the FILE-PROCESS-COUNT keyword
in the RUN-FILES-ATTR configuration record specified for runcobol, as described in
Chapter 10: Configuration, of the RM/COBOL User’s Guide.
• InxUseLargeLimit. The InxUseLargeLimit option in the [Options] section determines
which value to use for the lock limit when creating a version 4 indexed file. If the value
is set to No (the default), the lock limit placed into the KIB is 2 GB for indexed files
created by the RM/InfoExpress server. If the value is set to Yes, the lock limit placed
into the KIB is the value of the LargeFileLockLimit option for indexed files created by
the RM/InfoExpress server. Note that existing version 4 indexed files always use the
lock limit stored in their KIB. This option corresponds to the USE-LARGE-FILE-
LOCK-LIMIT keyword in the RUN-INDEX-FILES configuration record specified for
runcobol, as described in Chapter 10: Configuration, of the RM/COBOL User’s Guide.
• LargeFileLockLimit. The LargeFileLockLimit option in the [Options] section
determines the limit for the location to apply locks to a file that will be accessed as a
large file. For record and file locks to perform correctly, all RM/InfoExpress servers and
RM/COBOL runtime systems opening a particular file must use the same lock limit for
that file. The lock limit also limits the actual amount of data that can be stored in a file.
This limit will be used when a new indexed file is created provided the file version of the
file is 3 or greater. Otherwise, this limit has no effect on indexed files. The value
assigned to this keyword is specified in gigabytes (GB). The maximum value is
1048576, which equates to 1 petabyte (250). The minimum value is 1. The default value
is 64. The lock limit for a normal file is 2 GB. This option corresponds to the LARGE-
FILE-LOCK-LIMIT keyword in the RUN-FILES-ATTR configuration record specified
for runcobol, as described in Chapter 10: Configuration, of the RM/COBOL User’s
Guide.
• MinimumBlockSize. The MinimumBlockSize option in the [Options] section
determines the minimum disk block size for the indexed files created by the
RM/InfoExpress server, represented as a decimal number. The maximum value for this
keyword is 4096; the minimum value is 256. The default value is 1024. This option
corresponds to the MINIMUM-BLOCK-SIZE keyword in the RUN-INDEX-FILES
configuration record specified for runcobol, as described in Chapter 10: Configuration,
of the RM/COBOL User’s Guide.
• ReconnectTimeout. The ReconnectTimeout option in the [Options] section determines
the number of minutes the server will keep the file manager process serving the client
intact waiting for the client to reconnect to it. In particular, all file and record locks
remain in place while the client is disconnected and will prevent access by other run
units. The default value is 180 (three hours).
• RelUseLargeLimit. The RelUseLargeLimit option in the [Options] section determines
which value to use for the limit when applying locks to a relative file. If the value is set
to No (the default), the lock limit for relative files is 2 GB. If the value is set to Yes, the
value of the LargeFileLockLimit option is used. For record and file locks to perform
correctly, all run units RM/InfoExpress servers and RM/COBOL runtime systems
opening a file must use the same lock limit for that file. This option corresponds to the
USE-LARGE-FILE-LOCK-LIMIT keyword in the RUN-REL-FILES configuration

UNIX Server-Specific Configuration Options
record specified for runcobol, as described in Chapter 10: Configuration, of the

RM/COBOL User’s Guide.
• RoundToNiceBlockSize. The RoundToNiceBlockSize option in the [Options] section
determines whether the block size computed for the indexed files created by the
RM/InfoExpress server is forced to be a multiple of 512 (under Windows) or the value of
BUFSIZ, taken from the C include file <stdio.h> (under UNIX). The default value for
this keyword is Yes. This option corresponds to the ROUND-TO-NICE-BLOCK-SIZE
keyword in the RUN-INDEX-FILES configuration record specified for runcobol, as
described in Chapter 10: Configuration, of the RM/COBOL User’s Guide.
• SeqUseLargeLimit. The SeqUseLargeLimit option in the [Options] section determines
which value to use for the limit when applying locks to a sequential file. If the value is
set to No (the default), the lock limit for sequential files is 2 GB. If the value is set to
Yes, the value of the LargeFileLockLimit option is used. For record and file locks to
perform correctly, all RM/InfoExpress servers and RM/COBOL runtime systems opening
a file must use the same lock limit for that file. This option corresponds to the USE-
LARGE-FILE-LOCK-LIMIT keyword in the RUN-SEQ-FILES configuration record
specified for runcobol, as described in Chapter 10: Configuration, of the RM/COBOL
User’s Guide.
• UseCount. The UseCount option in the [Options] section may be used to specify the
number of clients that the server can serve simultaneously. This number must not be
greater than the server’s licensed client count. A reduced value on the UseCount option
will reduce the server’s shared and local memory requirements. The number of clients
will default to the server’s licensed client count unless the client count is “unlimited.” In
that case, it will default to 50.
The UseCount configuration option is equivalent to the -k command line option, as
described in the appropriate sections of Starting the RM/InfoExpress UNIX Server
option.
UNIX Server-Specific Configuration Options

The following configuration options, listed alphabetically, are specific to the RM/InfoExpress
UNIX server:
• ConvertFileName. The ConvertFileName option, which is located in the [Options]
section and can have three values, is used to process the filename before the file is
opened on the server’s native operating system. When ConvertFileName=NoConvert
(the default value), no filename mapping is performed. ConvertFileName=UpperCase
indicates that the entire filename is mapped to uppercase before the Open request is
attempted. ConvertFileName=LowerCase indicates that the entire filename is mapped to
lowercase before the Open request is attempted.
The ConvertFileName configuration option is equivalent to the -c command line option,
as described in the appropriate sections of Starting the RM/InfoExpress UNIX Server
option.
• DefaultServerUser. The DefaultServerUser option in the [Security] section specifies the
user name (at security levels 0 or 1) to run on the server when the security validation
fails. Normally, the default server user will be allowed to access files that do not require

Windows Server-Specific Configuration Options
high levels of security. The default server user must be a valid user on the server. The
default is DefaultServerUser=rmserver.
• ServerSecurityLevel. The ServerSecurityLevel option in the [Security] section specifies
the security level number at which the UNIX server is to run (for more information, see
Chapter 6: File Security on the RM/InfoExpress UNIX Server on page 53). Valid values
range from 0 through 5. If this option is not specified, the server runs in compatibility
mode, that is, the behavior is equivalent to an RM/InfoExpress version 2.0 server.
Sample RM/InfoExpress UNIX Server Configuration File

The following is a sample UNIX server configuration file (rmixsrvr.ini).
[Debug]
[Security]
IxPwFile=/usr/foo/ixpwfile
DefaultServerUser=foo

The following configuration options are specific to the RM/InfoExpress Windows server:
• share-name. The share-name option in the [Sharing] section defines a share name and
equates it with a pathname (share-path). On Windows, the edgename following the
server machine name is a share name; for example, \\server-name\share-name\rest-of-
path-to-file. All share names and paths are case-insensitive.
The server generates pathnames as follows:
1. Searches for the specified share name.
2. If found, substitutes the share-path for the name; if not found, searches for a null
share name.
3. If found, prepends the share-path to the filename; if not found, checks the
UseCurrentDirectory configuration flag.
4. If “Yes”, prepends the current working directory path to the filename; if “No”,
returns a “35” error.
The generated pathname is then given to the RM/COBOL File Manager.
For example, if the [Sharing] section on host serverW contains
[Sharing]
cdrive=c:\tmp
AcctPayable=d:\acctpayable\data
=e:\guest\data
then the client path \\serverW\cdrive\file.dat causes the server to access
c:\tmp\file.dat

Similarly,
\\serverW\cdrive\red\\white\blue c:\tmp\red\white\blue
\\serverW\acctpayable\master.inx d:\acctpayable\data\master.inx
\\serverW\file1 e:\guest\data\file1
\\serverW\xyzzy\tmp\junk.x e:\guest\data\xyzzy\tmp\junk.x
\\serverW\cdrive e:\guest\data\cdrive
If the null share name line (=e:\guest\data) did not exist and the server was started
in c:\bin, then:
\\serverW\file1 c:\bin\file1
\\serverW\xyzzy\tmp\junk.x c:\bin\xyzzy\tmp\junk.x
\\serverW\cdrive c:\bin\cdrive
The server’s current working directory is the default path for the null share name
provided the UseCurrentDirectory option is set to Yes.
If there is no [Sharing] section and if UseCurrentDirectory=No and
UseSystemShares=No are both set, then every open returns a 35 error.
The path associated with a share name is intended to start with a drive letter and to
specify a valid directory so that the resulting final pathname is an absolute pathname on
the server machine.
• UseCurrentDirectory. The UseCurrentDirectory option in the [Options] section
determines whether or not the server’s current directory pathname is prepended to the
filename when the edgename following the server name does not match any valid share
name. UseCurrentDirectory=Yes is the default.
• UseSystemShares. The UseSystemShares option in the [Options] section determines
whether or not the Windows server system share names are used. UseSystemShares=Yes
is the default. A Windows server system share name is defined in the Shared As portion
of the Sharing tab of the disk or directory folder Properties. Note that RM/InfoExpress
server ignores the Access Type and Passwords portions of the Sharing tab. If
UseSystemShares=No is specified, only the share names defined in the rmixsrvr.ini file
[Sharing] section are used.
Sample RM/InfoExpress Windows Server Configuration

File
The following is a sample Windows server configuration file (rmixsrvr.ini).
[Debug]
[Sharing]
cdrive=c:\
ShareTemp=d:\tmp\shared\files

[Options]
UseCurrentDirectory=Yes
UseSystemShares=Yes

Using the Utility
Appendix E: RM/InfoExpress
Security Parameter File Update
Utility
This appendix describes how to use the ixsecure.cob program to update the ixpwfile
parameter file with security-related information that is used by the server to authenticate the
clients. Note that ixpwfile must exist when the RM/InfoExpress server is run at security
levels greater than level 2. The implementation of file security in RM/InfoExpress is detailed
in Chapter 6: File Security on the RM/InfoExpress UNIX Server (on page 53).
The RM/COBOL object program, ixsecure.cob, is included with the RM/InfoExpress media
to enable users to build the security parameter file, ixpwfile. The RM/COBOL runtime
system (runcobol) is needed to run this object program.
A separate parameter file (ixpwfile) is required for each of the client machines and one for the
server machine. The parameter file for the client machine may have several entries, each
giving information about this client and one of the servers with which this client
communicates. Similarly, the parameter file for the server machine may have several entries,
each giving information about this server and one of the clients that may connect to the server.
Using the Utility

To run the security parameter file update utility, use the following command:
runcobol ixsecure
If the security parameter file, ixpwfile, is not in the current directory or has a different name,
set the IXPWFILE environment variable to the current pathname of the file.
The RM/InfoExpress Security Parameter File Update utility Main screen, illustrated in
Figure 15, is displayed.

Adding a New Entry
Figure 15: Security Parameter File Update Utility Main Screen
To choose an option on this screen, move the cursor with the arrow keys to a particular option
and press Enter. Alternatively, you can type the option number or the first letter of the option
description (it is not necessary to press Enter afterwards). To exit the utility program, choose
option 5.
Note If RM/COBOL finds an error while performing the requested operation, a message with
the appropriate RM/COBOL runtime error is displayed on the last line of the screen, and the
utility waits for acknowledgment.
When the ixpwfile is empty (such as the first time this utility is run on a machine), a warning
message is displayed and the file is created.
Adding a New Entry

To add a new entry, choose option 1 on the Main screen. The RM/InfoExpress Security
Parameter File Update utility Add Entry screen, illustrated in Figure 16, is displayed.
Figure 16: Add Entry Screen
Type the requested information and press Enter on the last line to complete the entry. If you
want to cancel the input at any time, press Esc. The utility displays the RM/InfoExpress
Security Parameter File Update utility Main screen, illustrated in Figure 15 on page 98.
Otherwise, the entry will be added to the file.
The SERVER USER NAME is case-sensitive.

Modifying an Existing Entry
The SERVER USER NAME and CLIENT MACHINE NAME are not case-sensitive; that is,
they will be displayed as entered but will be mapped to uppercase for use by RM/InfoExpress.
Note If you are creating a security parameter file for an RM/InfoExpress server, the password
field on the Add Entry screen should be left blank (simply press Enter in this field). The
password in an entry for the server security parameter file is always ignored.
Modifying an Existing Entry

To modify an existing entry, choose option 2 on the Main screen. The RM/InfoExpress
Security Parameter File Update utility Modify Entry screen, illustrated in Figure 17, is
displayed.
Figure 17: Modify Entry Screen
Using the arrow keys, choose the entry you wish to modify. Update the information on the
screen and press Enter on the last line to complete the entry. If you want to cancel the input at
any time, press Esc. The utility displays the RM/InfoExpress Security Parameter File Update
utility Main screen, illustrated in Figure 15 on page 98. Otherwise, the current entry in the
file will be replaced by this information.
Deleting an Existing Entry

To delete an existing entry, choose option 3 on the Main screen. The RM/InfoExpress
Security Parameter File Update utility Delete Entry screen, illustrated in Figure 18, is
displayed.

Listing All Entries
Figure 18: Delete Entry Screen
Using the arrow keys, choose the entry you wish to delete and press Enter. If you want to
cancel the input at any time, press Esc. The utility displays the RM/InfoExpress Security
Parameter File Update utility Main screen, illustrated in Figure 15 on page 98. Otherwise, the
current entry in the file will be deleted.
After successful deletion, the following message is displayed for confirmation:
Confirm deletion (Y/N)
Type Y to confirm deletion. (To abandon the deletion, type N.) The following message is
displayed to confirm the successful deletion of the entry from the file:
Record deleted successfully. Press any key. . .
Listing All Entries

To list all entries in the file, choose option 4 on the Main screen. The RM/InfoExpress
Security Parameter File Update utility List Entries screen, illustrated in Figure 19, is displayed
showing the following information.
Figure 19: List Entries Screen
Press any key to return to the RM/InfoExpress Security Parameter File Update utility Main
screen, illustrated in Figure 15 on page 98. If the file contains more entries than can be

Listing All Entries
displayed on one screen, additional screens will be displayed when a key is pressed. When all
entries have been displayed, pressing a key will return to the Main screen.
Note The password information is not displayed.

Changes to Relativity Configuration for 32-Bit Windows Clients
Appendix F: Using RM/InfoExpress with Relativity
Appendix F: Using
RM/InfoExpress with Relativity
RM/InfoExpress can be used with Relativity for RM/COBOL to access the catalog and/or
files stored on a server running the RM/InfoExpress server program. This appendix provides
instructions for 32-bit RM/InfoExpress Windows clients.
Note Some earlier versions of Relativity are called Relational DataBridge.
Changes to Relativity Configuration for 32-Bit

Windows Clients
The 32-bit RM/InfoExpress Windows client software (rmtcp32.dll) is installed with
Relativity. Note that the RM/InfoExpress Windows client software is not supplied with the
RM/InfoExpress server software or versions of Relativity prior to 2.5. It is distributed with
the RM/COBOL for Windows runtime or development system or, alternatively, it can be
downloaded from the Micro Focus web site (supportline.microfocus.com). Contact Micro
Focus Customer Care for more information.
The configuration procedures begin in the section Configure Relativity to Use
RM/InfoExpress (on page 104). These instructions assume the following:
• You have the RM/InfoExpress server main program and server display program installed
and running on your server machine. For more information, see the installation
instructions in Chapter 1: Installation and Verification (on page 7).
• You have the complete Microsoft TCP/IP software package installed and configured in
the Networking option on the Control Panel. (See also Chapter 1 of this manual.)
• You are running Windows clients.
Create a Configuration File

Create a file, called rmixclnt.ini, in the main Windows directory to set configuration
parameters for RM/InfoExpress client programs. Include the following entry:
[Winsock]
UseBlockingIO=Yes

This entry prevents a 10055 system error: “No available buffer space”. This configuration
parameter is discussed in Client-Specific Configuration Options (on page 87).
Configure Relativity to Use RM/InfoExpress

There are two aspects to configuring the Relativity ODBC data source setup: configuring
Relativity to use RM/InfoExpress and specifying the location of the Relativity catalog on the
server.
Note All setup options can be configured from the Windows client workstation using the
ODBC Data Source Administrator that is distributed with Relativity.
To configure Relativity to use RM/InfoExpress:
1. On the Windows client workstation, open the Control Panel.
2. To access the ODBC Data Source Administrator from the Control Panel, double-click
Administrative Tools.
3. On the Administrative Tools page, double-click Data Sources (ODBC).
4. In the ODBC Data Source Administrator dialog box, select the User DSN tab and then
click Add.
5. In the Create Data Source dialog box, double-click Relativity (*.rcg) as the driver type.
6. In the Relativity dialog box, select the RM/COBOL option in the File Manager tab and
then select the RM/InfoExpress tab to display the RM/InfoExpress page.
7. In the RM File Manager options area, select the Enable RM/InfoExpress check box,
which enables access to RM/InfoExpress.
The option for “Allow File Creation” is selected by default.
8. Next, click the Display Initial Message Box option to verify correct operation.
This action is useful when first configuring Relativity to use RM/InfoExpress. A
message box will be displayed when RM/InfoExpress is first called. If the message box
is not displayed, it indicates that any problems are not network related, but are caused by
the software installation. Similarly, if there is a problem but the message box is
displayed, the problem is related to the network.
Note After installation is verified, you may return to the RM/InfoExpress tab using the
32-bit ODBC Administrator, as described in Step 3, and clear the Display Initial Message
Box option.
9. In the Relativity dialog box, select the DSN tab.
This tab has entries for the data source name and description, as well as buttons to select
or create a Relativity catalog.
Continue by specifying the location of the Relativity catalog on the server:

1. In the Data Source Name box on the DSN tab, enter the name needed for the data source
(what users will see from their ODBC-enabled application, such as Microsoft Access or
Excel).
2. Click the Select Catalog button. The Select Catalog for Data Source dialog box is
displayed.
3. In the Select Catalog for Data Source dialog box, select the Use RM/InfoExpress only
check box.

4. In the File name box, enter the complete pathname.

You must specify the name in the following format:
\\RMInfoExpressServer\PathToFile
where RMInfoExpressServer must match the TCP/IP host name for the server machine on
this client (for example, \\HOSTNAME\test.rcg). The following example specifies
a Relativity catalog called shirt3.rcg in the directory /usr/relsamples on the server
unixware21:
\\unixware21\usr\relsamples\shirt3.rcg
5. After you enter a valid RM/InfoExpress server and filename, click Open. The Relativity
catalog name will be validated and returned to the Relativity dialog box as the name of
the Relativity catalog for the data source. This information is displayed in the Catalog
Name area.
6. In the Relativity dialog box, click OK to complete creation of the Relativity data source.

Version 12 Enhancements
Appendix G: Summary of Enhancements
Appendix G: Summary of
Enhancements
This appendix provides a summary of the new features and changes in the various releases of
RM/InfoExpress. It also tells you where to look for more information about them.
The enhancements and changes for the most recent release described by this document are
listed first. The information in this appendix is historical and was accurate at the time written
for the specific version being described. Various features may have changed in later releases,
and, possibly, some features may have been removed.
Note The RM/InfoExpress version number refers to the RM/InfoExpress server;
RM/InfoExpress client(s) do not have version numbers.
The following summarizes the major new enhancements in RM/InfoExpress version 12:
• The RM/InfoExpress server File Manager has been updated to RM/COBOL version 12
compatibility.
• Client-side logging is a new capability to diagnose initial connection problems from the
RM/InfoExpress client to the RM/InfoExpress server. The RMCLIENT.LOG file logs
errors that are encountered in the pre-connection, connect, and the first message sent and
received operations. In addition, this new log file contains the following information for
each connection:
− the client-side host name
− the client-side IP address (from gethostbyname)
− the server-side host name
− the server-side IP address
− the result of the connect request
For more information, see the StartupLogPath configuration parameter in Client-Specific

Configuration Options (on page 87) of Appendix D: Configuring RM/InfoExpress.

compatibility.
• Support for Microsoft Windows Vista was added.
compatibility.
compatibility. (For further information, see “Version 9 Enhancements” in Appendix L:
Summary of Enhancements, of the RM/COBOL User’s Guide.)
• The RM/InfoExpress server display main screen now shows the server uptime (in days)
at the end of the date and time line. It can also now display 999,999,999,999 (one
trillion—U.S.—minus one) total messages after which the count wraps back to zero. See
Server Display Commands (on page 42).
• The Windows server (rmsrvtcp.exe) now uses WinSock 2. In particular, this allows a
much larger connection queue (WinSock 1 had a maximum backlog of 5), which should
avoid error 10061.
• The Windows server installation creates a Windows Firewall Exception, if applicable,
for the RM/InfoExpress TCP port number 21069. If you change the port number
(which is not recommended), you must change both the services file and the Windows
Firewall configuration.
This section summarizes the major enhancements available in version 8 of RM/InfoExpress.
Support for Large Files

Because the RM/InfoExpress server contains the RM/COBOL file management system, the
RM/InfoExpress server includes the same support for large files as that offered by the
RM/COBOL runtime system (runcobol).

When running under operating systems that support files larger than 2 GB (gigabytes), the
RM/COBOL runtime system allows RM/COBOL files to grow past limits imposed in
previous versions. This support is provided by the LARGE-FILE-LOCK-LIMIT keyword of
the RUN-FILES-ATTR configuration record. In order to use this new limit on relative or
sequential files, you must use the USE-LARGE-FILE-LOCK-LIMIT keyword in a RUN-
REL-FILES or RUN-SEQ-FILES configuration record. In RM/InfoExpress, the server
configuration file (rmixsrvr.ini) contains keywords that correspond to those in the
RM/COBOL runtime system and that provide the same support. For record and file locks to
perform correctly, all RM/InfoExpress servers and RM/COBOL runtime systems opening a
file must use the same lock limit for that file.
On the Windows 9x class of operating systems, files up to 4 gigabytes (GB) are supported.
The Windows NT class of operating systems supports multiple terabyte files on the NT file
system. Only files on FAT32 (file system format supported for Windows 9x-class operating
systems) or NTFS (file system format supported on Windows NT-class operating systems)
may be larger than 2 GB.
For more information, see Appendix D: Configuring RM/InfoExpress (on page 83) of this
manual and Chapter 10: Configuration, of the RM/COBOL User’s Guide. In order to use this
new limit on indexed files, you must use an indexed file version level of 3 (see the “Very
Large File Support” topic in Chapter 8: RM/COBOL Features, of the RM/COBOL User’s
Guide for more information). Additional information about UNIX and Windows systems that
support large files also can be found in the “Using Large Files” topic in Chapter 2:
Installation and System Considerations for UNIX and in Chapter 3: Installation and System
Considerations for Microsoft Windows, respectively, of the RM/COBOL User's Guide.
Atomic I/O Support for File Version Level 4

In RM/InfoExpress, as in RM/COBOL, file version level 4 indexed files optionally support
the new “atomic I/O” capability, which provides a means for users to avoid almost all 98
errors caused by failures that occur while a file is open. Files created with atomic I/O will
almost never need recovery. If a crash occurs during a COBOL I/O operation, the file will be
automatically and quickly recovered the next time the file is opened or a write operation is
performed. The ENABLE-ATOMIC-IO keyword has been added to the RUN-INDEX-FILES
configuration record to determine whether indexed files created by the runtime system use
atomic I/O.
The default indexed file version for new files has been changed from 2 to 4 to automatically
provide the higher level of reliability to new files. The DEFAULT-FILE-VERSION-
NUMBER keyword of the RUN-INDEX-FILES configuration record may be used to specify
a different value.
Version 4 indexed files may, like version 3 files, grow to a larger size than version 0 or 2
files. However, unlike version 3 files, version 4 files may be either large or regular sized
files, depending on the new USE-LARGE-FILE-LOCK-LIMIT keyword of the RUN-
INDEX-FILE configuration record. This new keyword determines whether the LARGE-
FILE-LOCK-LIMIT or the FILE-LOCK-LIMIT keyword of the RUN-FILES-ATTR
configuration record is used to determine the largest address that can be locked in the file.
This, in turn, determines how large the file can be.
Limited Automatic Session Reconnection

Beginning with version 8, a limited reconnection capability, which allows a connection that
becomes broken to be reconnected automatically, has been added to the RM/InfoExpress
client and server logic. The client and server continue normal operation without the client run

Version 2.1 Enhancements
unit (COBOL program) ever being aware of the disconnection. To enable this capability, you
must set ReconnectEnable=Yes in the [Options] section of the rmixsrvr.ini server
configuration file, as explained in Appendix D: Configuring RM/InfoExpress (on page 83).
Client Path Prefix Inclusion and Exclusion

A new feature has been added in version 8 to allow the RM/InfoExpress client to exclude
selected UNC-style pathnames (beginning with \\ or //) from access via RM/InfoExpress.
Prior versions of RM/InfoExpress always attempted access to all UNC-style pathnames. In
the rmixclnt.ini configuration file in the [Options] section, you can specify
PathPrefixIncluded=list and PathPrefixExcluded=list. For more information, see Appendix D
(on page 83).

This section summarizes the major enhancements available in version 2.1 of RM/InfoExpress.
RM/InfoExpress Server Now Supported on Windows NT

Version 4.0
A version of the RM/InfoExpress server software now runs on the Windows NT Server
(version 4.0).
File Security on the RM/InfoExpress UNIX Server

The RM/InfoExpress UNIX server now provides enhanced file security. The level of security
is specified at the time the server is invoked. The server performs various validations on the
authenticity of the client(s) before granting access to a file. For more information, see
Chapter 6: File Security on the RM/InfoExpress UNIX Server (on page 53).
New Utility to Update RM/InfoExpress Parameter File

To make the RM/InfoExpress server screens display similar information about all types of
clients, all new clients now provide client-specific information (such as client-machine-name
and user-name of the client on the server, as described in Chapter 6) to the server from a
security parameter file. This parameter file, default name ixpwfile, is created using a utility
program, ixsecure.cob. For more information about how to use this utility, refer to Appendix
E: RM/InfoExpress Security Parameter File Update Utility (on page 97).
Improved Server Screens

Additional information has been added to the server screens to identify the clients. For
example, the Error Log screen now displays the name of the file on which the error occurred.

Optional Message Compression

This version of RM/InfoExpress optionally compresses messages before transmitting them on
the network. Depending on the compressibility of the messages, which include the records
from RM/COBOL data files, compression may improve the performance of RM/InfoExpress
over WANs and heavily loaded LANs.
Optional Message Encoding

This version of RM/InfoExpress optionally encodes messages before transmitting them on the
network to provide more security for the COBOL data.
Initialization File Support

All implementations of RM/InfoExpress now allow configuration information to be stored in
a file that is in an .INI format. For more information, see Appendix D: Configuring
RM/InfoExpress (on page 83).
-m Server Option Obsolete

The RM/InfoExpress server now automatically expands the message buffer size (previously
set using the -m option on the server command line) as required by each session. The user
should no longer receive the error RMIX_ERR_OUT_OF_MEMORY when transmitting
records larger than 5000 bytes.
Use Count Check by the Server

The RM/InfoExpress server now limits the number of client connections to the value specified
by the UseCount configuration option or the licensed use count, whichever is less. For more
information, see the UseCount configuration option (on page 92).
New File Count Option

The RM/InfoExpress server can now be configured for any number of simultaneously open
files, independent of the licensed use count. For more information, see the FileCount
configuration option (on page 90).
New Option to Handle the Display of Long Filenames

The RM/InfoExpress screen handler (server display) program can now be configured to
display more reasonably a filename that is too long to fit in the display field of the screen
handler. For more information, see the DotsBias configuration option as described in
Appendix D (on page 83).

Version 2.0.2 Enhancements
Version 2.0.2 Enhancements

This section summarizes the major enhancements available in version 2.0.2 of
RM/InfoExpress.
New Server Option Enables the RM/plusDB Interface

The -b option has been added in order to enable RM/InfoExpress to communicate with
RM/plusDB. Use the -b option when invoking the RM/InfoExpress server with the
RM/plusDB product if every filename is to be checked for an RM/plusDB table name by the
server before opening the RM/COBOL data file.
Note Beginning with version 8 of RM/InfoExpress, Micro Focus no longer develops or
supports RM/plusDB. This option is maintained for backward compatibility only and should
be ignored. Do not specify this option unless you have used RM/plusDB in your application.

This section summarizes the major enhancements available in version 2.0 of RM/InfoExpress.
RM/InfoExpress UNIX Server Filename Case-Sensitivity

For the RM/InfoExpress UNIX server, the -c option allows you to specify whether to map the
filename on an Open request to uppercase, lowercase, or leave it unaltered (the default). For
more information, see Chapter 2: Configuring and Running the RM/InfoExpress Server (on
page 27).
RM/InfoExpress UNIX Server Configuration Option

For the RM/InfoExpress UNIX server, the -c 1 configuration option must be specified if the
pathnames are to be converted to lowercase (as in the previous version). The default is no
conversion. For more information, see Chapter 2 (on page 27).
RM/InfoExpress UNIX Server Runs as a Daemon

This version of the RM/InfoExpress UNIX server runs unattended in the background and no
longer requires an additional terminal. The server uses data structures built-in shared
memory. The server modifies the data structures using a well-defined administrative API
(Application Programming Interface) to preserve the integrity of the server data structures.
RM/InfoExpress Screen Handler Program

The screen handler (server display) portion of RM/InfoExpress has been removed from the
server program and is now a separate application. The screen handler application shares the

data structures present in shared memory along with the server daemon. The screen handler
accesses the data structures using a well-defined administrative API.
The screen handler program is improved to read an entire screen of information in a single
operation, thus providing more consistency to the data it displays.
Under UNIX, the screen handler can be invoked more than once on the system, making it
possible for multiple users to view the server statistics simultaneously. The screen handler
application can be run from any terminal on the UNIX system.
The command sequence, Terminate Display, now terminates the screen handler program
without affecting the server or any clients.
The following sections describe two additional modifications to the screen handler program.
Changes in the Default Behavior

The default behavior of the screen handler (server display) program allows only the
termination of the screen handler program itself. This prevents you from accidentally
stopping the server or a specific client. To terminate the server or a particular client, you must
specify the -t option (as described in Chapter 2: Configuring and Running the
RM/InfoExpress Server on page 27) when you start the screen handler program.
New Screens
The Error Information screen has been replaced by two new screens.
The Open Log screen displays information about the most recent 24 open operations
performed by the server. The Error Log screen displays information about the most recent 24
errors, including the complete error code and location of the error. For more information, see
Chapter 5: RM/InfoExpress Server Operations (on page 41).
More COBOL Information Added to Existing Screens

More COBOL-related information has been added to existing screens. The Client Files
Information screen now displays the organization, open mode, and the access mode of each
file currently opened by the client. A new field, System name, has been added to the Client
Information screen. This field displays the type of operating system on which the client is
running. See Chapter 5 (on page 41) for further details.
Improved Error Handling

Error handling has been improved in this version of RM/InfoExpress. Additional
information, such as the location of the occurrence, is also now maintained.
KEEPSESSION Configuration Option

The default value for the KEEPSESSION configuration option has changed from NO to YES.
For more information, see Appendix D: Configuring RM/InfoExpress (on page 83).

Index
Compiler options (RM/COBOL), hyphens, used with

3
Configuration 83, See also Configuration file options;
Command line options, server
Index
client 83, 85, 87
files, samples of 84, 90, 93, 94
server 83, 85, 90, 92, 93
with RM/COBOL 83, 108
Configuration file options 83
client 87
AcceptPassword 87
KeepSession 88
PathPrefixExcluded 88
PathPrefixIncluded 88
ReconnectDelay 89
StartLogPath 89
A UseBlockingIO 89
AcceptPassword configuration option 87 client and server 85
AIX operating system 14 EncodeData 85
IgnoreHangupError 85
InfoxDebug 28, 31, 85
B IxCompress 86
Block size 91 IxPwFile 58, 86
Bold type, use of as a document convention 3 MaxSendSize 29, 32, 86
Browsers 10–14 ReconnectEnable 86
BSD Sockets software, error messages 68, 78 server 27, 90, 92, 93
Buffer pool size 28, 32, 90 ConvertFileName 28, 92
BUFFER-POOL-SIZE keyword, RUN-FILES-ATTR DefaultServerUser 55, 57, 64, 92
configuration record 90 DotsBias 47, 48, 90
FileBufferPool 29, 32, 90
FileCount 90
C FileProcessCount 91
-c command line option, server 28, 92 InxUseLargeLimit 91
Case-sensitivity, configuration options 28, 83, 112 LargeFileLockLimit 91
Character-based terminals 41 MinimumBlockSize 91
Client program 8 ReconnectTimeout 91
accessing 33, 37 RelUseLargeLimit 91
configuration file options 83, 85, 87 RoundToNiceBlockSize 92
executing RM/COBOL programs with 36, 39 SeqUseLargeLimit 92
installation 18 ServerSecurityLevel 54, 57, 64, 93
pointing to network data files 33–36, 37–39 share-name 93
setting up TCP/IP package 18 UseCount 28, 32, 92
system requirements 7–8 UseCurrentDirectory 94
terminating communication to 29, 32, 49, 81 UseSystemShares 94
verification, installation 19–25, 19–25 Configuration files
Clients, validating 53 client (rmixclnt.ini) 58–64, 83
Command line options, server 27, 28, 31 server (rmixsrvr.ini) 58–64, 83
buffer pool size (-p) 28, 32, 90 Configuration records, RM/COBOL
debug (-d) 28, 31, 85 EXTERNAL-ACCESS-METHOD 33, 37
display program (-t) 29, 30, 32, 49 RUN-FILES-ATTR 90, 91, 109
mapping filenames (-c) 28, 92 RUN-REL-FILES 109
maximum amount of data handled by TCP send RUN-SEQ-FILES 109
function (-z) 29, 32, 86 Console interface 41
maximum number of clients open (-k) 28, 32, 92 Conventions and symbols used in this manual 3
Communication, client and server machines 21, 24 ConvertFileName configuration option 28, 92
Compatibility mode 54, 57, 93 Customer Care 4

Index
D FileCount configuration option 90

FileProcessCount configuration option 91
-d command line option, server 28, 31, 85 FILE-PROCESS-COUNT keyword, RUN-FILES-
Data-names, RM/COBOL programs 35, 39 ATTR configuration record 91
Debugging 28, 31, 85 Files
DefaultServerUser configuration option 55, 57, 64, client program
92 librminfox.so, UNIX 8, 19, 24, 37
Directory search sequence, synonyms 34, 38 rmtcp32.dll, Windows 8, 18, 33
DNS See Domain Name Service configuration
Documentation overview 1 rmixclnt.ini 83, 90
Domain Name Service 9, 18 rmixsrvr.ini 27, 83, 93, 94
DOS environment variables 34 sample of 84
DotsBias configuration option 47, 48, 90 hosts 9, 18, 23
Downloading, from Web 10–14 rhosts 53, 56, 59
server display program
E rmdisptcp, UNIX 8, 27
rmdistcp.exe, Windows 8
Ellipsis in filenames 90
server program
EncodeData configuration option 85
rmservertcp, UNIX 8, 27
Encoding messages 85
rmsrvtcp.exe, Windows 8
Enhancements to RM/InfoExpress services 9, 18, 23
version 10 108
version 11 108
version 12 107 H
version 2.0 112 hosts file 9, 18, 23
version 2.0.2 112 HP-UX operating system 14
version 2.1 110 Hyphen (-), using with optional, RM/COBOL
version 8 108 compilation and runtime options 3
version 9 108
Environment variables
DOS 34 I
IXCONFIG 58, 83 IBM AIX operating system 14
IXPWFILE 58 IgnoreHangupError configuration option 85
IXPWFILE 97 Indexed files 91, 109
KEEPSESSION 88 InfoxDebug configuration option 28, 31, 85
PATH 24 infoxdmo, verification program 23, 24
RM_CLIENT_LOG_PATH 89 Installation
RM_RECONN_LOG_PATH 87 client program 8, 18
RUNPATH 24, 35, 38 server display program 8, 10, 13
troubleshooting 81 server program 8, 10, 13
Error messages 67–78 setting up TCP/IP package for
Explicit pathnames 35, 38 RM/InfoExpress clients 18
EXTERNAL-ACCESS-METHOD configuration RM/InfoExpress servers 9
record 33, 37 system considerations 13, See also Configuration
records
F system requirements 7–8
verification 19–25
Failure to locate file or path 81 Intel UNIX System V Release 4 operating system 14
File access, network 33, 37 Intel x86 operating system 15
File lock limit 91, 92, 109 InxUseLargeLimit configuration option 91
File security 8, 53, 97, See also Security, on UNIX IPC objects, removing after server failure 51, 82
server Italic type, use of as a document convention 3
File security parameter file update utility IxCompress configuration option 86
(ixsecure.cob) 8, 54, 97 IXCONFIG environment variable 58, 83
File version level, in indexed files 91, 109 ixpwfile (security parameter file) 54, 56, 58, 97
FileBufferPool configuration option 29, 32, 90 IxPwFile configuration option 58, 86

Index
IXPWFILE environment variable 58, 97 PATH environment variable 24

ixsecure.cob, file security parameter file update Pathnames 22, 81
utility 8, 54, 97 case-sensitivity 28
ixverify, Windows client verification program 21 explicit 35, 38
specifying 33–36, 37–39
K UNC-style 88, 110
PathPrefixExcluded configuration option 88
-k command line option, server 28, 32, 92 PathPrefixIncluded configuration option 88
Keepalive support, TCP 87 PDF format 1
KeepSession configuration option 88 Performance, network 86
KEEPSESSION environment variable 88 Ports, user 9, 18
Key combinations, document convention for 3
Keyboard interface, server display program 41
R
kill command, UNIX 51, 82
ReconnectDelay configuration option 89
L ReconnectEnable configuration option 86
Reconnecting server and client 86, 89
Large file support 91, 92, 108 ReconnectTimeout configuration option 91
LargeFileLockLimit configuration option 91 Related publications 2
LARGE-FILE-LOCK-LIMIT keyword, RUN- Relativity, using with 103
FILES-ATTR configuration record 91, 109 RelUseLargeLimit configuration option 91
liant.lic (license certificate file) See License file rhosts file 53, 56, 59
librminfox.so, client program, UNIX 8, 19, 24, 37 RM/COBOL
License file 10, 12, 13, 14 client program 8, 18
use count 92 compilation options, hyphens, used with 3
Limits and ranges 79 configuration file options 83, 108
Linux operating system 14 list support modules loaded by the RM/COBOL
Local area networks (LANs) 1 runtime option (V) 24
Log file, initial client connection to server 89 runtime options, hyphens, used with 3
using with RM/InfoExpress 33, 37
M RM/InfoExpress
client program 8
MaxSendSize configuration option 29, 32, 86 accessing 33, 37
Messages configuration file options 83, 85, 87
compression 86 executing RM/COBOL programs with 36, 39
encoding 85 installation 18
error 67–78 pointing to network data files 33–36, 37–39
large 86 setting up TCP/IP package 18
MinimumBlockSize configuration option 91 system requirements 7–8
terminating communication to 29, 32, 49, 81
N verification, installation 19–25
configuring with RM/COBOL 83, 108
Network enhancements, summary of 107
accessing clients 33, 37 error messages 67–78
compressing messages 86 installation 10, 13, 18
data files, pointing to 33–36, 37–39 limits and ranges 79
security 58, See also Security, on UNIX server messages 67–78
Relativity, using with 103
O RM/COBOL, using with 33, 37
security, on UNIX server 53, 86, 92, 93, 97, See
Organization of this manual 1 also Security, on UNIX server
server display program 8, 10, 13
P command line option 29, 30, 32, 49
commands
-p command line option, server 28, 32, 90 Clients 44
Passwords, client 87 Error Log 48

Index
Files 45 S
Main 44
Open Log 47 SCO OpenServer 5 operating system 15
Terminate 49 SCO OpenServer 6 operating system 15
Client 50 Screen handler program See Server display program
Display 50 Security, on UNIX server 53
Server 50 .rhosts file 53, 56, 59
keyboard functions 41 client validation 57
main screen 42 clients, non-UNIX 57
screen format, illustrated 42 compatibility mode 54, 57, 93
starting 27, 29 configuration file options 54, 55, 57, 58, 64
terminating 29, 32, 49 default server user 55, 57, 64, 92
server program 8 file security 53, 97
command line options 27, 28, 31 security levels 54, 57, 58, 64, 93
configuration 27 security parameter file (ixpwfile) 54, 56, 58, 86, 97
configuration file options 83, 85, 90, 92, 93 setting up network 58
default server user 55, 57 Send operations, maximum allowed 29, 32, 86
installation 10 SeqUseLargeLimit configuration option 92
security, on UNIX 53, 86, 92, 93, 97, See also Server configuration file (rmixsrvr.ini) 27
Security, on UNIX server Server display program 8, 10, 13
setting up TCP/IP package 9 command line option 29, 30, 32
starting 27, 29 commands
automatically 31
Clients 44
System account 20, 30
Error Log 48
system requirements 7–8
Files 45
terminating 29, 30, 32, 49
Main 44
verification, installation 19–25
Open Log 47
version number, significance of 107
Terminate 49
system requirements, installation 7–8
Client 50
terminating 49 Display 50
troubleshooting 81 Server 50
verification, installation 19 keyboard functions 41
RM_CLIENT_LOG_PATH environment variable 89 main screen 42
RM_RECONN_LOG_PATH environment variable screen format, illustrated 42
87 starting 27, 29
RMCLIENT.LOG 89 terminating 29, 32, 49, 50
rmdisptcp, server display program, UNIX 8 Server program 8
rmdistcp.exe, server display program, Windows 8 command line options 27, 28, 31
rmixclnt.ini, client configuration file 58–64, 83, 90, configuration file options 83, 85, 90, 92, 93
See also Configuration file options installation 10, 13
rmixsrvr.ini, server configuration file 27, 58–64, 83, security, on UNIX 53, 86, 92, 93, 97
93, 94, See also Configuration file options .rhosts file 53, 56, 59
rmservertcp, server program, UNIX 8 client validation 57
rmsrvtcp.exe, server program, Windows 8 clients, non-UNIX 57
rmtcp32.dll, client program, Windows 8, 18, 33 compatibility mode 54, 57
RoundToNiceBlockSize configuration option 92 configuration file options 54, 55, 57, 58, 64
RUN-FILES-ATTR configuration record 109 default server user 55, 57, 64
BUFFER-POOL-SIZE keyword 90 file security 53
FILE-PROCESS-COUNT keyword 91 security levels 54, 57, 58, 64
LARGE-FILE-LOCK-LIMIT keyword 91, 109 security parameter file (ixpwfile) 54, 56, 58
RUNPATH environment variable 24, 35, 38 server display program 10, 13
RUN-REL-FILES configuration record, USE- setting up TCP/IP package 9
LARGE-FILE-LOCK-LIMIT keyword 91, 109 starting 19, 20, 27, 29
RUN-SEQ-FILES configuration record, USE- automatically 31
LARGE-FILE-LOCK-LIMIT keyword 92, 109 System account 20, 30
Runtime options (RM/COBOL), hyphens, used with system requirements 7–8
3 terminating 29, 32, 49

Index
verification, installation 19–25 installation 13

version number, significance of 107 security 53
ServerSecurityLevel configuration option 54, 57, 64, server display program 41
93 starting 27
services file 9, 18, 23 verification, installation 19–25
share-name configuration option 93 UnixWare operating system 15
Starting UseBlockingIO configuration option 89
server display program 27, 29 UseCount configuration option 28, 32, 92
server program 27, 29 UseCurrentDirectory configuration option 94
automatically 31 USE-LARGE-FILE-LOCK-LIMIT keyword
on a specific account 31 RUN-REL-FILES configuration record 91, 109
StartupLogPath configuration option 89 RUN-SEQ-FILES configuration record 92, 109
Sun Solaris SPARC operating system 15 UseSystemShares configuration option 94
Support services, technical 4
Symbols and conventions used in this manual 3 V
Synonyms, directory search sequence 34, 38
System account 20, 30, 31 V Runtime Command option, RM/COBOL 24
System requirements, installation 7–8 Validating clients 53
Verification
UNIX client 24
T
UNIX client and server communciation 24
-t command line option, server display 29, 30, 32, 49 UNIX server 20
TCP/IP communication protocol 7, 9, 18, 19 Windows client 21
keepalive support 87 Windows client and server communication 21
send function 29, 32, 86 Windows server 19
TCP/IP package, setting up for Version number, RM/InfoExpress client 107
RM/InfoExpress clients 18 Version number, RM/InfoExpress server 107
RM/InfoExpress servers 9
Terminating 29, 32 W
client communications 49, 50
client entries, troubleshooting 81 Web browser 10–14
server 49, 50 Wide area networks (WANs) 1
server display 49, 50 Windows client 8, See also Client program;
Transmission Control Protocol/Internet Protocol See RM/InfoExpress
TCP/IP communication protocol accessing 33
Troubleshooting configuration file options 83, 85, 87
client entries not terminating 81 installation 18
failure to locate file or path 81 system requirements 7–8
removing IPC objects after server failure 51, 82 verification, installation 19–25
Windows console 41
Windows operating systems 8
U
Windows server 8, See also Server program;
UNC-style pathnames 88, 110 RM/InfoExpress
UNIX client 8, See also Client program; command line options 31, 32
RM/InfoExpress configuration file options 83, 85, 90, 93
accessing 37 installation 10
configuration file options 83, 85, 87 server display program 10, 41
installation 18 starting 29
system requirements 7–8 automatically 31
verification, installation 19–25 System account 20, 30
UNIX server 8, See also Server program; terminating 30
RM/InfoExpress verification, installation 19–25
command line options 28, 29 Windows service See Windows Service Control
configuration file options 83, 85, 90, 92 Manager (SCM)
file security parameter file update utility Windows Service Control Manager (SCM) 11, 12,
(ixsecure.cob) 8, 54, 97 19, 29, 30, 31

Index
Windows Sockets software 18, 21

blocking mode 89
error messages 68, 75, 77
IgnoreHangupError configuration option 85
Z
-z command line option, server 29, 32, 86

0RMC InfoExpress UG

Uploaded by

Copyright:

Available Formats

0RMC InfoExpress UG

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

0RMC InfoExpress UG

Uploaded by

Copyright:

Available Formats

Micro Focus

RM/InfoExpress User’s Guide

© Copyright 2017-2020 Micro Focus or one of its affiliates.

Revised 2020-05-06 for version 12.17

Chapter 1: Installation and Verification ................................................ 7

Chapter 2: Configuring and Running the RM/InfoExpress Server ... 27

Chapter 3: Using RM/InfoExpress with RM/COBOL for Windows

Chapter 4: Using RM/InfoExpress with RM/COBOL for UNIX

Chapter 5: RM/InfoExpress Server Operations .................................. 41

ii RM/InfoExpress User's Guide

Appendix B: Limits and Ranges .......................................................... 79

Appendix C: Troubleshooting RM/InfoExpress ................................. 81

Appendix D: Configuring RM/InfoExpress ......................................... 83

RM/InfoExpress User's Guide iii

Appendix F: Using RM/InfoExpress with Relativity ......................... 103

Appendix G: Summary of Enhancements ........................................ 107

Index ..................................................................................................... 115

iv RM/InfoExpress User's Guide

RM/InfoExpress User's Guide v

About Your Documentation

RM/InfoExpress User's Guide 1

Chapter 3—Using RM/InfoExpress with RM/COBOL for Windows Programs describes

Contact the appropriate vendor for other publications:

2 RM/InfoExpress User's Guide

Conventions and Symbols

runcobol name [options]

RM/InfoExpress User's Guide 3

4 RM/InfoExpress User's Guide

RM/InfoExpress User's Guide 5

Chapter 1: Installation and

RM/InfoExpress Server Program

RM/InfoExpress User's Guide 7

RM/InfoExpress consists of two server programs:

RM/InfoExpress Client Program

Setup and Installation

8 RM/InfoExpress User's Guide

Setting Up the TCP/IP Package for RM/InfoExpress Servers on

RM/InfoExpress User's Guide 9

Installing RM/InfoExpress Server on Windows

Electronic Software Delivery Installation for Windows

10 RM/InfoExpress User's Guide

• If the license certificate for RM/InfoExpress server software being installed is

Note The RM/InfoExpress server is installed and run as a Windows service.

RM/InfoExpress User's Guide 11

where, d is the drive letter of the CD-ROM drive. Click OK.

Note The RM/InfoExpress server is installed and run as a Windows service.

12 RM/InfoExpress User's Guide

Installing RM/InfoExpress Server on UNIX

Electronic Software Delivery Installation for UNIX

3. Execute the installation script using the following command:

Messages are displayed periodically indicating the status of the installation.

RM/InfoExpress User's Guide 13

Loading the License File

Mounting the Diskette as an MS-DOS File System

• Linux (kernel 2.6)

mount –t msdos /dev/fd0H1440 /mnt/floppy

c. Copy the license file to the /tmp directory:

14 RM/InfoExpress User's Guide

a. Insert the diskette into the diskette drive.

mount –f DOS,lower /dev/fd0 /floppy