RIS Installation Guide: For 32-Bit Applications

RIS Installation Guide
for 32-Bit Applications

August 1996
DNA1151A0
Version 5.4
Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract,
and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or
amendment of such warranties.
The information and the software discussed in this document are subject to change without notice and should not be
considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any
error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance
with the terms of this license.
No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by
Intergraph or its affiliated companies.
Trademarks
InterAct, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DIALOG, InterServe, and TD1
are trademarks of Intergraph Corporation. All other brands and product names are trademarks of their respective
owners.
Copyright
1996 Intergraph Corporation
All Rights Reserved
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license
agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected
by copyright and trade secret law and may not be provided or otherwise made available without proper
authorization.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of
The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and
(2) of Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable.
Unpublished rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
Table of Contents iii
Table of Contents
__________________________________________________________________________________________________________________________________________________
iv Table of Contents
Table of Contents v
Table of Contents
__________________________________________________________________________________________________________________________________________________
1.
Before You Begin ..................................................................................................
1-3
2.
Architecture and Configuration Overview ..........................................................
2-3
2.1
2.2
2-3
2-7
RIS Architecture ..........................................................................................

Environment Overview ................................................................................
2.2.1
2.2.2
2.2.3
Schema Definition and Database Connection .................................

Integrated Data Dictionary ..............................................................
Networking .......................................................................................
2 - 11
2 - 11
2 - 11
The RIS Products .........................................................................................
2 - 12
2.3.1
2.3.2
2.3.3
2.3.4
RIS Client .........................................................................................

RIS Development Platform ..............................................................
RIS Utilities ......................................................................................
RIS Data and Net Servers ...............................................................
2 - 12
2 - 13
2 - 14
2 - 14
Interoperability and Upgrading ...........................................................................
3-3
2.3
3.
3.1
3.2
3.3
3.4
3.5
3.6
4.
5.
Overview of Interoperability .......................................................................

Straightforward Upgrades ...........................................................................
Potential Problems .......................................................................................
Multiple Versions of RIS on One System ....................................................
The RIS Upgrade Utility (risupgrd) ............................................................
Configure RIS Version Utility .....................................................................
3-3
3-5
3 - 13
3 - 18
3 - 19
3 - 22
System Requirements ...........................................................................................
4-3
4.1
4.2
Hardware Needed ........................................................................................

Software Needed ..........................................................................................
4-3
4-3
Installing RIS .......................................................................................................
5-3
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5-3
5-4
5-5
5-6
5-7
5-7
5-9
Starting Setup ..............................................................................................

Personalizing Your Intergraph Software ....................................................
Selecting the Product Destination Path ......................................................
Selecting the Installation Type for RISDP .................................................
Creating Configuration Files .......................................................................
Installing Applications in Batch Mode ........................................................
RIS Orphan Processes .................................................................................
vi Table of Contents
5.7.1
5.7.2
Orphan Process Symptoms ..............................................................

Changing the Wait Time ..................................................................
5-9
5 - 10
6.
RIS License List Utility ........................................................................................
6-3
7.
RISINFDS/RISINFNS Registry Utility ...............................................................
7-3
8.
Configuring SNA Server for RIS DB2 Data Server ............................................
8-3
8.1
8.2
8.3
8.4
Related Documentation ...............................................................................

Installing RIS ...............................................................................................
Installing SNA Server ..................................................................................
Configuring SNA Server ..............................................................................
8-3
8-3
8-4
8-4
8.4.1
8.4.2
The Server ........................................................................................

The Connection .................................................................................
8-5
8-5
8.4.2.1
Restarting SNA Server ......................................................
8-7
Creating Logical Units (LUs) ......................................................................
8-8
8.5
8.5.1
8.5.2
8.5.3
8.5.4
The Local LU ....................................................................................

The Remote LU .................................................................................
Partnering LUs .................................................................................
Checking LU Status .........................................................................
8-8
8-9
8 - 10
8 - 11
The Mode ......................................................................................................

Creating Schemas ........................................................................................
Troubleshooting ...........................................................................................
8 - 12
8 - 13
8 - 14
8.8.1
System Logs ......................................................................................
8 - 15
Removing RIS Products ........................................................................................
9-3
10.
Differences Between RIS for UNIX and RIS for 32-Bit Applications ...............
10 - 3
11.
Running the RIS Executables ............................................................................
11 - 3
8.6
8.7
8.8
9.
Appendix A:
A.1
A.2
A.3
Redistribution of RIS Runtime and RIS Utilities ..............................
A-3
Directory Structure ............................................................................................

Setup Files ..........................................................................................................
Installing the RIS Shared Component ..............................................................
A-3
A-3
A-5
Appendix B:
B.1
On-line Documentation .......................................................................
B-3
Using On-line Help ............................................................................................
B-3
B.1.1
B-3
Parts of the Help Window ......................................................................
Table of Contents vii
Glossary .......................................................................................................................
GL - 3
Index ............................................................................................................................
IN - 3
viii Table of Contents
Before You Begin 1 - 1
Before You Begin
__________________________________________________________________________________________________________________________________________________
1-2
Before You Begin
1.
__________________________________________________________________________________________________________________________________________________
Before You Begin

This document describes how to install the following RIS products in a 32-bit operating
system environment:
RIS Shared Component (as a part of RISDP or a RIS data server and as a
part of a non_RIS product)
RIS Development Platform
RIS Oracle Data Server
RIS Oracle Net Server
RIS Microsoft SQL Data Server
RIS Sybase SQL Data Server
RIS DB2 Data Server
RIS Informix Data Server
RIS Informix NET/STAR Data Server
Two icon-driven utilities now let you convert existing RIS 4.3 applications to be
compatible with the RIS 05.** shared component and utilities. For more
information on upgrading RIS to maintain version interoperability, refer to the
section RIS Interoperability and Upgrading for Windows NT in the RIS SQL
Users Guide for 32-Bit Applications.
Document Prerequisites
This document assumes that you are familiar with the Windows NT operating environment.
Related Documentation
DNA1116
DNA1003
DNA1117
DNA1009
DNA1190
DNA1161
RIS SQL Users Guide for 32-Bit Applications

RIS SQL Commands Quick Reference
RIS Utilities Guide for 32-Bit Applications
RIS Programmers Quick Reference
RIS Programmers Guide for 32-Bit Applications
RIS Installation Guide for DB2
1-4
Before You Begin
Document Conventions
Filenames and directory paths appear in italic typeface. However, the italic typeface is
also used for emphasis of new words or important phrases. For example:
c:\windows
Command names, menu names, tools, system prompts and messages, and keys may
appear in boldface type. For example:
File menu
OR
Press Enter
The word mouse refers to the 2-button or 3-button mouse.
The word select means to select a command by pressing the left mouse button over a
menu command or by pressing the Alt key and the underlined character
simultaneously.
The word choose means to choose a button or icon by pressing the left mouse button
over a Toolbar button, or application icon.
The word reset means to terminate a command initiated with the mouse. Reset by
pressing the right mouse button.
The word identify means to define an area or place graphic elements in a graphics file.
For PCs, identify with the left mouse button.
The phrase key in generally means to enter data into a field on a dialog box. To
advance to the next field, use the Tab key.
Do not use the Enter key to advance to the next field. This key is mostly
used as the default key to accept a dialog box instead of pressing the OK
button.
System key-ins, keywords, and programming code segments, appear in monospaced
type. For example:
main ( )
OR
commit
In actual usage, keywords can be in either upper or lowercase.
Words that appear in angle brackets, < >, are identifiers or names that you must
supply, or dynamic information that can change for each error message. For example:
ERROR: Error opening the file <filename>
Phrases in square brackets, [ ], are optional phrases.
Curly braces contain several options (used in conjunction with a logical OR symbol ( | ))
or phrases that can be repeated (used in conjunction with [, ...]). A comma followed by a
series of three periods in square brackets ([, ...]) indicates that the last phrase contained
within curly braces ({}), or the last item, can be repeated numerous times (separated by
commas).
For example: { <column> <data type> } [, ...] means that numerous column names and
associated data types can be specified (separated by commas).
The logical or symbol ( | ) separates phrases or keywords within curly braces ({}) that
can be used alone but not together.
For example: { user | database } means that either the user keyword or the
database keyword can be specified, but not both.
This symbol notes important information.
This symbol cautions about operations that can cause limited damage.
This symbol warns about operations that can cause severe damage.
1-6
w.
Before You Begin
Architecture and Configuration Overview 2 - 1
Architecture and Configuration Overview
__________________________________________________________________________________________________________________________________________________
2-2
2.
__________________________________________________________________________________________________________________________________________________

The Intergraph Relational Interface System (RIS) is a generic interface to relational
database management systems (RDBMSs). RIS offers simultaneous connections to RDBMSs
from many venders on dissimilar hardware platforms using numerous protocols. RIS makes
an entire network of databases available as if there were a single, local database.
The RIS products provide the following features:
Real-time read and write access to data.
Access to many popular relational database management systems on a variety of
hardware platforms.
Transparent network connections to remote database systems.
A single, consistent interface that lets you do the following:
Develop software applications independent of the type of database system.
Run your software applications, without modification, with any database system,
hardware platform, and network that RIS supports.
A set of utilities that make data access more convenient.
Design flexibility to allow for the addition of new database connections, network
connections, and database features as they become available.
2.1 RIS Architecture

The following figure illustrates how the RIS pieces fit into the connection between an
application and a database.
Since the application and RIS client usually run on the same system, they use shared
memory for fast interprocess communication. When the database is local, the client and
server run on the same machine and also use shared memory to minimize the communication
overhead.
2-4
When the database is remote, the server normally runs on the same machine as the database
system. Net servers do not run on the same system as the database. The CPU load is
distributed between the client and the server machines and, in most cases, with a choice of
network protocols.
If desired, the RIS client can run remotely. RIS client must run remotely for the
configuration of DOS and Windows 3.1 applications.
The implementation of the IBM connection is a variation of the general configuration with an
additional piece called the RIS DB2 Transaction Processor running on IBM. The mainframe
configuration varies with the communication link between the InterServe and the IBM. One
configuration is an SNA/LU6.2 connection (over SDLC or Token Ring) into CICS, illustrated
in the following two configurations.
For RIS connections to database systems running on platforms not supported directly by RIS
(NCR, Pyramid, Sequent, and so forth), the network products of the RDBMS vendors can be
used within the framework of RIS.
2-6
In the DOS and Windows 3.1 environments, only the RIS library linked with the application
is on the Intel system to minimize resource usage on that system. The client process always
runs on a workstation or server, and it connects to the RIS server as in the other
configurations.
2.2 Environment Overview

The following figures show the environments supported by RIS. A figure is provided for each
key piece (application/development platform, client, and data servers) in a configuration as
well as some special case connections for IBM and others. A client can connect to several
databases and database systems in various environments simultaneously.
2-8
2 - 10
RDBMS Versions
The following RDBMS versions are compatible with RIS 5 on the operating systems shown.
See the section Changes to This Version of RIS in the RIS SQL Users Guide for
32-Bit Applications for more information about the changes between RIS
Version 4 and RIS Version 5.
2.2.1 Schema Definition and Database Connection

For RIS, a schema is a named set of tables and views within a specific database or database
system. The meaning of the term database varies widely from vendor to vendor. RIS
schemas are identified by a schema name and (optionally) a schema password.
The schema definition is the one element of RIS that is database-specific. After being
defined, a schema may be used by an application without any knowledge of the brand or
location of the schemas database system.
2.2.2 Integrated Data Dictionary

RIS has its own integrated data dictionary, a set of tables and views created to provide
information about a schemas tables, columns, and views. The data dictionary provides basic
information in a form consistent across the different brands of databases; applications query
the RIS dictionary tables instead of RDBMS-specific dictionary tables. A RIS dictionary can
be exclusive to one schema or shared by multiple schemas.
2.2.3 Networking
RIS includes networking capabilities that let applications store data on different network
nodes or to isolate all data on one central node. This capability is especially useful in a
network environment where numerous workstation applications need to share data. In this
configuration, only one copy of the RDBMS is needed for the server node.
2 - 12
Network connections vary, depending on the hardware platform. Among the protocols
currently supported by RIS are SNA/LU6.2.
The server products are network independent. There is no need to obtain different server
products to support different protocols. As long as the platform has the appropriate network
products installed, a single server will handle multiple network protocols. Refer to the
configuration figures in the section Environment Overview.
In some cases, there are different programs within a RIS product for different networks, but
they are still part of a single product. For the DB2 connection, the client-to-server connection
can be any of the usual supported protocols (TCP/IP), but the link to the transaction
processor on the IBM currently uses only SNA/LU6.2.
2.3 The RIS Products

The RIS software consists of four components: the RIS Client and Runtime package
(RISCLI), the RIS Development Platform (RISDP), the RIS Utilities (RISUTL), and the
data/net servers. The RIS Client and Runtime package is needed to run RIS-based
applications. The RIS Development Platform is needed only by developers creating RISbased applications. The RIS Utilities are optional RIS tools.
2.3.1 RIS Client

RIS is based upon a client/server architecture. The client requests information from the
server. The server then retrieves the information from the database and returns it to the
client.
The RIS Client and Runtime package contains the RIS Client executable and runtime
support files that are needed for all workstations or servers that are acting as clients to a RIS
data server machine. The features provided by the RIS Client and Runtime package are
documented in the RIS SQL Users Guide for 32-Bit Applications.
2.3.2 RIS Development Platform

The RIS Development Platform (RISDP) contains an Embedded SQL preprocessor for the C
programming language along with the libraries, include files, and sample programs
necessary for the development of RIS-based applications.
The RIS Development Platform functions and features let you:
Provide the same interface that Intergraph uses to build database-independent
applications.
Embed SQL statements into the C language for source code.
Provide a single interface to multiple brands of relational databases.
Provide the remote access built into RIS.
Support numerous network protocols.
Eliminate expensive network products.
The RIS interface is based on the American National Standards Institute (ANSI) Structured
Query Language (SQL) standard and is therefore compatible with all RDBMSs that are
compatible with the standard.
2 - 14
2.3.3 RIS Utilities

The RIS Utilities contains several RIS utilities that let users perform tasks such as schema
management, adhoc queries, and bulk loading of data. The RIS Utilities product includes the
following:
risunlod and rislod Utilities
The risunlod utility copies data definition statements and data from one or more RIS
schemas into one or more text files. The rislod utility can then use these text files to
recreate and restore the information into the schemas. This capability is useful for
archiving or transferring schema definitions and large amounts of data from one
database to another. However, these programs are not meant to replace the database
vendor backup utilities and should not be used for backup or archiving purposes.
Other RIS utilities include:
risbatch (RIS command-line program)
risclnsr (RIS clean server)
risdcode (RIS decode)
risdtype (RIS data types)
risplbck (RIS playback)
risrecrd (RIS record)
rliclist (RIS license list utility)
2.3.4 RIS Data and Net Servers

The RIS Data servers enable client applications to communicate with the relational
databases. The data servers must be installed on the system where the relational database
is located.
The RIS net servers enable client applications to communicate through the network with
databases located on remote systems. They support the TCP/IP communications protocol.
Interoperability and Upgrading 3 - 1
Interoperability and Upgrading
__________________________________________________________________________________________________________________________________________________
3-2
3.
__________________________________________________________________________________________________________________________________________________

3.1 Overview of Interoperability
A significant part of the interoperability between versions of RIS is that new back-end
processes support older front-end pieces, maintaining the same level of functionality. The
following figure illustrates support of different versions between the different pieces of RIS.
(There are some special exceptions.)
The Shared Component refers to the combined RIS Client and RIS Utilities
products.
The figures in this section refer to applications. Note that the RIS Utilities are
applications. Note also that intermediate and remote systems assume a 32-bit
operating system.
Some of this will be illustrated in the discussion of upgrading.

The overall message is that you can upgrade your database systems, RIS Data Servers, and
the RIS Shared Component, and still run your older applications.
3-4
To use ORACLE 7, SYBASE System 10 or System 11, you must use a RIS 5
Client and Data Server.
If both versions of RIS are installed on the same system, the application (or RIS
Client) always uses the version that most closely matches its own.
To use the new features of RIS 5, your application must be built with RIS 5.
Schema files cannot be mixed. A RIS 4.3 schema file can be upgraded to RIS 5
format, but cannot be used as is by a RIS 5 client. Similarly, a RIS 4.3 client
cannot read a RIS 5 schema file.
Data Servers and schemas of different versions cannot be mixed. A 4.3 Data
Server cannot work with a 5 schema, and a 5 Data Server cannot work with a
4.3 schema.
3.2
__________________________________________________________________________________________________________________________________________________
Straightforward Upgrades
Upgrading from RIS version 4.3 to RIS version 5 can be a simple, straightforward process.
However, because of the multiple components of RIS, the distributed nature of RIS, and the
interoperability capability that is now available, the number of possibilities in the
configuration of RIS is quite large.
To make things as easy as possible, this document explains the upgrade of one or two simple
configurations and progresses from there to some of the more complex options.
Upgrading from RIS 4.3 to RIS 5 does not interfere with the operation of your
applications, even though the applications were built and designed for RIS 4.3.
The following pieces are involved in an upgrade:

1.
RIS Shared Component (RIS Client and Utilities)
2.
RIS Data Server (RISORADS/RISORANS/etc.)
3.
RIS schema file
4.
RIS schema itself (the RIS dictionary tables in the RDBMS)

Data Servers for 5 support 4.3 Clients, but not the other way around.
Scenario: A single system with a local database

Objective: Straightforward upgrade of RIS
3-6
Perform the following steps:

1.
Log in as administrator.
2.
Remove the RIS 4.3 Data Server.
3.
Install the RIS 5 Data Server product.
4.
Click on Configure RIS Version icon to configure RIS for interoperability with RIS V5
Shared Component. See the section Configure RIS Utility for details.
5.
Click on the Upgrade RIS icon to upgrade the schema file and all known schemas. See
the section on The RIS Upgrade Utility for details.
The RIS V4 local Data Server can only be accessed through a remote RIS V4
Client.
If other workstations are accessing this system using RIS, it is important that
you continue reading. This configuration requires additional consideration.
The RIS Upgrade utility can only be executed on a system having a local RIS
client and a local schema file. The RIS upgrade utility is delivered with the RIS
V5 shared component.
Scenario: Workstation to remote server (local client, local schema file, remote
server)

1.
Log in the remote system as administrator.
2.
Remove the RIS 4.3 Data Server.
3.
Install the new RIS V5 Data Server product.
4.
Using the RIS V4.3 Utilities on the local system, locate the RIS V5 Client on the remote
machine.
5.
If multiple RIS shared components are present, click on Configure RIS Version icon to
configure RIS for interoperability with RIS V5 Shared Component. See the section
Configure RIS Utility for details.
6.
the section on The RIS Upgrade Utility for details.
3-8
The RIS V4 schemas file has to be upgraded to V5 to be used by a RIS V5 client. This
upgrade can be done by copying the schemas file over to the machine which has the V5
Shared Component and clicking on the Upgrade RIS icon.
The scenario changes from local client, local schema file, and remote server to remote
client, remote schema file, and remote server.
If other workstations are accessing the remote system using RIS, it is important
that you continue reading. This configuration requires additional consideration.
Scenario: Workstation to remote server (remote client, remote schema file, remote
server)
This is a minor variation of the previous upgrade.

1.
Log in to the remote system as administrator.
2.
Remove the RIS 4.3 Data Server product.
3.
4.
Click on the Configure RIS Version icon to configure RIS for interoperability with RIS
V5 Shared Component. See the section Configure RIS Version Utility for details.
5.
the section The RIS Upgrade Utility for details on running this utility.
3 - 10
Scenario: Workstation to intermediate system to remote server (remote client,

remote schema file, remote server)
This is another minor variation of the previous upgrade, showing the fully distributed
environment.

1.
Log in to the remote system as administrator.
2.
Remove the RIS 4.3 Data Server product.
3.
4.
Log in to the intermediate system as administrator.
5.
Install the RIS 5 Development Platform (RISDP) or 5 Data Server.
6.
Click on the Configure RIS Version icon to configure RIS for interoperability with RIS
V5 Shared Component. See the section Configure RIS Version Utility for details.
7.
the section The RIS Upgrade Utility for details on running this utility.
3 - 12
3.3
__________________________________________________________________________________________________________________________________________________
Potential Problems
There are a few problem areas that can occur in an environment that has some systems
upgraded and others not upgraded.
1.
A V4.3 schema file and a V5 schema file are not compatible.
2.
Unknown error codes are returned.
3.
A V4.3 Data Server cannot connect to an upgraded schema.
4.
A V5 Data Server cannot create a V5 schema where a V4.3 schema already exists, and
it cannot connect to V4.3 schema.
Scenario: Incompatible schema files

Although this can happen in a variety of configurations, the following scenario is one of the
most likely.
3 - 14
The incomplete upgrade ...
One option in this case is to use separate schema files. The drawback to this is that the
applications lose the advantages of a shared schema file.
Another option is to upgrade the other workstations to RIS 5 and click on the Configure RIS
Version icon. See the section Configure RIS Version Utility for details.
The quickest short-term option is to locate the client from the other workstations to the
upgraded one:
If the upgraded system switched to a new version 5 schema while upgrading the schemas,
you may inadvertently be using separate schema files without realizing it. This may cause
some confusion when one application creates a schema, but others do not see it.
3 - 16
Scenario: Unknown Error Numbers

When running a RIS 4.3 application and client against a RIS 5 Data Server, it is possible for
the Data Server to return error messages that are not known to RIS 4.3. This appears as
follows:
***************************************************************
*RIS Error: Error name not found for 0x8a94bd32 (0x8a94bd32)
*
*Message not found for 0x8a94bd32
***************************************************************
The error number varies, depending on the particular error. The error message can be
obtained by running the risdcode utility (version 5) on a system that has the RIS 5 client
installed.
Scenario: RIS 4.3 Data Server tries to connect to a RIS 5 schema (new or
upgraded)
or
RIS 4.3 Data Server tries to create a schema where a RIS 5 schema already exists
The RIS 4.3 Data Server returns the following error message if it tries to connect to a schema
that has been upgraded to RIS 5 or has been created through RIS 5:
***************************************************************
*RIS Error: RIS_E_INV_SCHUSR_INSERT
*
*Dictionary error: problem inserting into risschusr;
*Insert into ris_schusr values (...);
***************************************************************
The same error appears if the schema already exists.

Since the schema is a RIS 5 schema, a RIS 5 Data Server must be used. In most cases, this
can be solved immediately by removing the RIS 4.3 Data Server.
Scenario: RIS 5 Data Server tries to connect to a RIS 4.3 schema

or
RIS 5 Data Server tries to create a schema where a RIS 4.3 schema exists
A 5 Data Server trying to connect to a 4.3 schema usually occurs when a RIS 5 Data Server
is being used and the schema file has been upgraded to 5, but the schema itself has not been
upgraded. The error during connection is:
***************************************************************
*RIS Error: RIS_E_NO_SCHEMA_TABLES
*
*The dictionary tables for this schema do not exist (schema
was dropped).
***************************************************************
If you then try to create the schema, the following error appears:
***************************************************************
*RIS Error: RIS_E_INV_CREATE_XCOLUMNS
*
*Error occurred while trying to create ris_columns.
*Table already exists.
***************************************************************
The appropriate action is to run the RIS upgrade utility to upgrade the schema.
3 - 18
3.4
__________________________________________________________________________________________________________________________________________________
Multiple Versions of RIS on One System

To configure your operating system so that multiple versions of RISDP and a RIS Data
Server can coexist, a unique destination directory must be given for each RIS product.
The RIS Shared Components can coexist on a system even if multiple versions
of the Development Platform and Data Servers do not.
3.5
__________________________________________________________________________________________________________________________________________________
The RIS Upgrade Utility (risupgrd)

The upgrade utility is delivered with the RIS Shared Component and can be invoked by
clicking on the Upgrade RIS icon.
This utility has two purposes:
1.
Convert a schema file from RIS 4.3 format to RIS 5 format.

This can be done without destroying the original schema file.
2.
Convert schemas in the database from RIS 4.3 format to RIS 5 format.
The upgrade of the schemas in the database does not affect any customer
data or customer tables. This affects only the RIS dictionary tables that
make up a schema.
3 - 20
Step by Step: Straightforward Upgrade

Perform the following the steps:
1.
Make a copy of your old schemas and parms files:

copy \win32app\ingr\share\ris04.03\parms
\Program Files\Common Files\Intergraph\ris05.nn\parms
copy \win32app\ingr\share\ris04.03\schemas
\Program Files\Common Files\Intergraph\ris05.nn\schemas
where .nn = the version number of RIS.
2.
Click on the Upgrade RIS icon.
3.
When prompted, reply Y.
4.
The upgrade utility asks for the name of a new schema file. By default, this is the old
name with v5 added to the end.
The upgrade utility upgrades the schema file to version 5 format (unless it has already
been upgraded).
5.
The upgrade utility then goes through each schema in the schema file, asking if you
want to upgrade each one.
a.
Continue to press <Return> until it has upgraded all of the schemas.
b.
Information about the schemas is stored temporarily in files for use in the event of
database problems or a system crash.
c.
You are asked where to store the information. The current directory is acceptable.
The Upgrade Process

This is a brief explanation of what happens during an upgrade.
1.
A RIS 5 schema file is created from the RIS 4.3 schema file. This stores additional
information in the new schema file.
2.
The upgrading of the schema file is recorded in an upgrade status file: \Program
Files\Common Files\Intergraph\ris05.nn\risupg.inf
3.
A connection is made to the RIS 4.3 schema.
4.
Metadata about tables, columns, and views is retrieved from the RIS 4.3 dictionary and
stored in some files. You are prompted for a location to store these files. It does not
matter where they are stored. The files are used for recovery in the event of a system
crash or database problem.
5.
The RIS 4.3 schema is dropped. This does not affect any customer data; it just removes
the RIS 4.3 dictionary tables.
6.
The RIS 5 schema is created.
7.
Tables are included in the RIS 5 schema based on information stored in the files.
8.
Column information and privilege information is updated.
After each step, the progress of the upgrade is recorded in the risupg.inf status file.
What if something goes wrong?
Power failures, system crashes, running out of space in the database,... The upgrade utility
is designed to survive these situations.
At any point, you can re-run the upgrade utility. It automatically picks up where it left off.
If there is ever any confusion, the risupg.inf file shows what has been upgraded. This file can
be eliminated at any time, and the upgrade utility can be run again. Once the schema has
been upgraded through the point of dropping and creating the RIS 5 schema, the schema can
never again be used by a RIS 4.3 Data Server.
3 - 22
3.6
__________________________________________________________________________________________________________________________________________________
Configure RIS Version Utility

The Configure RIS Version Utility is delivered with the Shared Component and is designed
to help with upgrades to current versions of the shared components. The utility removes the
previous RIS Shared Component files, directories, registry entries, icons and program
groups. After running this utility, applications can interoperate with a recent Client and
Data Server.
Previous versions of RIS indicates V4.3 and earlier V5 versions.
The RIS V5 Data Server need not be a part of the configuration unless the
application needs to connect to a local RIS V5 Data Server.
Objective: Configure RIS for V5 interoperability.
1.
Invoke the Configure RIS Version Utility from the command line or click on the
Configure RIS Version icon.
2.
When the first message box appears, select Continue.
3.
A warning message is displayed stating that previous RIS Shared Component

directories and user-generated files will be deleted from the product directory.
To delete the previous RIS files and directories, select Delete. If Do Not Delete is
selected, the files and directories are not deleted.
4.
Provide a destination path and filename where the existing previous RIS schemas file
should be copied and select Continue. By default, the utility looks for a file named
schemas in the previous RIS Shared Component directory. If the previous versions of
RIS schemas file has a name other than schemas, the name and path should be entered
in the field labeled From. If the schemas file cannot be found, an error message is
displayed stating, Source file does not exist and the schemas file will not be copied to the
new V5 location.
5.
Provide a destination path and filename where the previous version of RIS parms file
should be copied and select Continue. By default, the utility looks for a file named
parms in the previous RIS Shared Component directory. If the previous RIS parms file
has a name other than parms, enter the name and path in the field labeled From. If
the parms file cannot be found, an error message is displayed stating, Source file does
not exist and the parms file will not be copied to the new version 5 location.
The Configure RIS Version utility removes the previous RIS Shared Component from
the product registry, deletes the icons, and allows previous applications to connect to
the V5 Client.
Previous RIS schema files are not compatible with V5 clients. Therefore,
previous schemas must be converted to V5 schemas with the RIS Upgrade
Utility. See the section The RIS Upgrade Utility for details.
3 - 24
System Requirements 4 - 1
System Requirements
__________________________________________________________________________________________________________________________________________________
4-2
System Requirements
System Requirements 4 - 3
4.
__________________________________________________________________________________________________________________________________________________
System Requirements
4.1 Hardware Needed
The following hardware is needed to run RIS products in the Windows NT environment:
A PC with the following minimum hardware:
386 processor
12 MB of RAM (16 MB recommended)
A hard disk drive with at least 15 MB of free disk space (for complete installation of all
products).
4.2 Software Needed

The following software is needed to run RIS products in a 32-bit operating system
environment:
Windows NT Operating System (Version 3.51 and 4.0)
OR
Windows 95 Operating System.
Microsoft Visual C++ 2.0, 2.1 or 2.2 Compiler (Development Platform only).
Microsoft SNA Server 2.1 or 2.11 (RIS DB2 Data Server only).
4-4
System Requirements
Installing RIS 5 - 1
Installing RIS
__________________________________________________________________________________________________________________________________________________
5-2
Installing RIS
5.
__________________________________________________________________________________________________________________________________________________
Installing RIS
Use the setup program to install software products on a PC system running a 32-bit
operating system.
You must have administrative privileges to run setup Also, if you install the
RIS product onto a clean system, you must reboot to initialize the system path
variable for the product. Otherwise, the system cannot see the executables and
returns an error when you attempt to use a RIS utility.
You can use setup to install an Intergraph product as follows:
1.
Insert the delivery medium and start setup.
2.
Record customer information in the software.
3.
Select the product destination path.
4.
Select the type of installation (compact, typical, or custom). This option applies only to
the RIS Development Platform installation.
The setup program copies product files to the system, then creates or modifies system
configuration files. If for some reason the installation fails, risdp.log or risds.log and
risrem.log are copied to $TEMP directory.
5.1 Starting Setup

Insert the delivery medium (floppy disk or CD/ROM) into the appropriate drive, and start
setup as follows:
1.
Select Run from the File menu in the File Manager window.
2.
Key in one of the following commands on the command line:

a:\setup
For a floppy disk.
drive:\setup
For a single-product CD/ROM, where drive is the

drive letter for the CD/ROM drive.
drive:\directory\setup
For a multiple-product CD/ROM or for a shared

network directory, where drive is the drive letter
for the CD/ROM drive or the drive letter for the
network drive, and directory is the pathname to
setup.
5-4
Installing RIS
\\server\share\directory\setup
3.
For a shared network directory, where server is

the server from which you are installing, share is
the share name, and directory is the pathname to
setup.
Choose the Continue button.

You first see the Welcome dialog box. Then, if an existing version is already on
your system, a prompt lets you continue or cancel installation. If you select
Continue, setup deletes the existing version and continues with the current
installation. Select Cancel Setup to quit.
5.2 Personalizing Your Intergraph Software

Intergraph requires you to enter customer information during installation. Intergraph
products use this information for the following purposes:
Recording customer information in the software.
Displaying when the product is started.
Displaying when users show information about the product.
Auditing product usage.
You are prompted for your customer information with a dialog box similar to the one shown
in the following figure:
Customer Information Dialog Box
Key in your username, your company name, and the product serial number, and click on
Continue.
The serial number is checked before installation continues; if the serial number
is incorrect, the product is not installed. Keep a record of your serial number in
case you need to reinstall the product.
Please take a few minutes to fill out and send in your registration card now.
5.3 Selecting the Product Destination Path

You are prompted for the destination path to use for product installation with a dialog box
similar to the one shown in the following figure:
Installation Destination Dialog Box

The following list shows the default installation locations for the products described in this
document:
RIS Development Platform: C:\Program Files\RISDP directory.
RIS Oracle Data Server: C:\Program Files\RISORADS directory.
RIS Oracle Net Server: C:\Program Files\RISORANS directory.
RIS Microsoft SQL Data Server: C:\Program Files\RISMSFDS directory.
RIS Sybase SQL Data Server: C:\Program Files\RISSYBDS directory.
RIS DB2 Data Server: C:\Program Files\RISDB2DS directory.
RIS Informix Data Server: C:\Program Files\RISINFDS directory.
5-6
Installing RIS
RIS Informix NET/STAR Data Server: C:\Program Files\RISINFNS directory.

RIS Shared Component: C:\Program Files\Common Files\Intergraph
If you key in a directory that already contains a version of the product you are
installing, warning messages display.
Also, if File Manager is active and the destination directory is expanded,
setup fails. To correct this problem, collapse the destination directory and
restart setup.
After the installation is properly configured, setup copies product files from the media to the
specified destination path.
5.4 Selecting the Installation Type for RISDP

After you enter your customer information, you are prompted to select the type of installation
with a dialog box similar to the one shown in the following figure:
Installation Options Dialog Box

In addition to displaying the installation options, this dialog box displays the amount of
additional disk space required for the selected installation. If the product you are installing
already resides on the system, this value may be 0 blocks, indicating that no additional disk
space is required for the installation.
Select from the following installation options:
Compact
Installs only the files and tools that you need to develop RIS SQL
applications.
Typical
Installs the minimum configuration and the files that you need to
develop loader/unloader and forms applications, sample files, and RIS
packaging files that you need to redeliver RIS.
Custom
Installs the minimum configuration and lets you select which parts of
the complete configuration to install.
Customized Installation Dialog Box
5.5 Creating Configuration Files

Once files are successfully copied, system configuration files such as the System Registry are
modified. New Program Manager groups are created, if necessary.
Customer information (such as username and company name) obtained at the beginning of
the installation is now recorded.
5.6 Installing Applications in Batch Mode

Intergraph has provided an /h: extension to the standard setup program that lets you install
products in batch mode.
This lets you create settings files to perform customized installations to large numbers of
machines. You can then use the setup /h: extension to install the products.
5-8
Installing RIS
The following shows a sample settings file.

[Standard]
DestPath=C:\Program Files\risdp
InstallType="typical"
[Registration]
name="Jane Smith"
organization="Intergraph Corporation"
serial="0014558200668"
[Options]
OptFiles1=no
OptFiles2=no
OptFiles3=no
RISPack=no
[SMS_Options]
Producer=Intergraph Corporation
ProductName=risdp
Version=05.04
PName=risdp
OurCaption=Intergraph RIS Development Platform
SetupModule=.\setup.exe
MIF=\risdp.mif
The settings file specifies the following information:

DestPath
Specifies the destination directory. This directory defaults to

C:\Program Files\RISDP for the RIS Development Platform;
C:\Program Files\RISORADS for the RIS Oracle Data Server;
C:\Program Files\RISORANS for the RIS Oracle Net Server;
C:\Program Files\RISMSFDS for the RIS MS SQL Data Server;
C:\Program Files\RISSYBDS for the RIS Sybase SQL Data Server;
C:\Program Files\RISDB2DS for the RIS DB2 Data Server;
C:\Program Files\RISINFDS for the RIS Informix Data Server; and
C:\Program Files\RISINFNS for the RIS Informix NET/STAR Data
Server.
InstallType
Specifies the type of installation. You can choose from compact, typical,
or custom. The default installation type for RISINFDS is typical.
name
The username to be recorded during installation.

You must change the default name value from Licensed to
Intergraph Corporation. Otherwise, you receive an
installation error.
organization
The company name to be recorded during installation.
serial
The serial number to be recorded during installation.
[Options]
This section is used only if the custom installation type is specified.

This section specifies the installation options to be used during
installation. Only if variables equate to yes are the files associated
with the key. The variables used in this section apply only to the risdp
product and include the following:
OptFiles1
Specifies the forms library and include files.
OptFiles2
Specifies the loader/unloader library and include files.
OptFiles3
Specifies samples.
RISPack
Specifies the shared component files and floppy delivery files.
To use the setup /h: command, key in the following, where filename specifies the complete
pathname to the settings file you created:
setup /h:filename
For example, the following command runs setup /h: using the SETTINGS.INI settings file:
setup /h:C:\SETTINGS.INI
5.7 RIS Orphan Processes

Several RIS applications have encountered an orphan process problem in previous versions of
RIS.
5.7.1 Orphan Process Symptoms

RIS Client and RIS Data Server processes continue to exist on the RIS client machine
when a user re-boots their RIS application machine while connected to the database
through RIS. This happens when a RIS application is connected to the RIS client
through TCP/IP. Because the RIS client process exists, all RIS server processes
connected to the RIS client process exist.
RIS Data Server processes continue to exist on the RIS server machine when a user reboots their RIS client machine while connected to the database through RIS. This
happens when the RIS client machine is connected to an RIS Data Server through
TCP/IP.
In the version of the RIS Client delivered with RISDP, orphan processes are no longer a
problem. Also, the RIS Data Server orphan process problem is fixed in the RIS Data Server
version 5.3.1 or higher products.
The default wait time for an orphan process is 2 hours. Thus, after the RIS application or
RIS client machine is re-booted, the orphan process waits for 2 hours before it goes away. The
wait time can be changed and the procedeure for this change is platform specific.
The side-effect of changing the wait time is that it affects all applications using the
TCP/IP KeepAlive feature. Do not set the KeepAlive wait time to less than 30
minutes.
5 - 10
Installing RIS
5.7.2 Changing the Wait Time

Instructions for changing the process wait time:
In the Registry Editor, add or modify the KeepAliveTime value for the Tcpip\Parameters
key. The entry for this TCP/IP parameter appears under the following Registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Edit the TcpipParameters Registry Key and Add/Modify the Value:

Value Name
Data Type
KeepAliveTime
REG_DWORD
String (Specify in Binary, Decimal, or Hex)

1 to 0xffffffff milliseconds (hex)
Suggested values:
7,200,000 (decimal) milliseconds - two hours (Default)
3,600,000 (decimal) milliseconds - 1 hour
1,800,000 (decimal) milliseconds - 30 minutes
Remember to restart your machine for these changes to take effect.
RIS License List Utility 6 - 1
RIS License List Utility
__________________________________________________________________________________________________________________________________________________
6-2
RIS License List Utility 6 - 3
6.
__________________________________________________________________________________________________________________________________________________

The RIS License List utility (rliclist) delivered with RIS Utilities Version 5 allows the system
administrator to monitor data server use by remote RIS users. This utility, often called the
monitor utility, also allows the administrator to monitor peak RIS license usage.
The license list utility must reside on the same system as the RIS data server.
To use the license list utility, type rliclist.exe at the system prompt.
The RIS Server License List Utility dialog box appears.
The utility queries the system for RIS data server usage. If no data server is active, no usage
message is displayed. License user limits and database connections are displayed only if
there is a current RIS data server user.
Click the Refresh button to repeat the query.
6-4
To monitor peak license usage, click the Peak Usage button. The RIS Data Server Peak
Usage dialog box appears.
This function allows the administrator to view the maximum number of connections that
have occurred since the log was started or cleared. Clearing the log file begins a new
monitoring period.
When the license user limit is exceeded, a note is posted in the rliclist display area.
Typically, this only happens during the initial 90-day grace period.
Use the Save As button to save the log information to a text file.
RISINFDS/RISINFNS Registry Utility
7-1
__________________________________________________________________________________________________________________________________________________
7-2
7-3
7.
__________________________________________________________________________________________________________________________________________________

The RISINFDS/RISINFNS Registry Utility delivered with the RIS Informix Data Server
(RISINFDS)/RIS Informix Net Server (RISINFNS) Version 5.4 allows you to define
INFORMIX Servers in the registry for RIS Informix Data Server and RIS Informix Net
Server.
The registry utility must be used on the same system as the RIS INFORMIX
Data/Net server.
To use the registry utility, choose the RISINFDS/RISINFNS Registry Utility icon. The RIS
Informix Data Server Registry Utility dialog box appears.
The utility queries the Registry system and lists all existing servers in the Informix Server
List. If no Informix servers exist, you are prompted to add a new server.
7-4
ADD
1.
Click the Add button.
2.
Enter the following information:

Informix Server - Name of the Informix server.
Host Name - Node name where the database resides.
Protocol Name - olsoctcp or onsoctcp for Informix OnLine or sesoctcp for
Informix Standard Engine.
Service Name - sqlexec for Informix Standard Engine or turbo for Informix
OnLine Engine.
3.
Click the OK button.
MODIFY
1.
Select an Informix server from the Informix Server List.
2.
Click Modify.
3.
Modify the values in the Host Name, Protocol Name, and Service Name fields.
4.
Click the OK button to save the changes in the Registry.
DELETE
1.
Select an Informix server from the Informix Server List, then click Delete.
2.
Click the OK button to delete the server from the Registry.
Registry Keys
The following keys are created in the Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\RISINFDS\05.04\Environment
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\RISINFDS\05.04\Remote_DBServers
The Registry utility stores the Informix servers information under the second key. After the
Informix Servers are defined successfully using this utility, RIS Informix Data/Net Server
can be used to create schemas.
In RISINFDS/RISINFNS Version 5.3, the registry keys were:
HKEY_LOCAL_MACHINE\SOFTWARE\INFORMIX\ENVIRONMENT
HKEY_LOCAL_MACHINE\SOFTWARE\INFORMIX\Remote_DBServers
7-5
The registry keys have changed for 5.4. If you have any Informix servers
defined under
HKEY_LOCAL_MACHINE\SOFTWARE\INFORMIX\Remote_DBServers
for RISINFDS/RISINFNS version 5.3, the setup program copies the existing
server information to
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\RISINFDS\05.04\Remote_DBServers
for the product to use.
8-1
Configuring SNA Server for RIS DB2 Data Server 8 - 1
Configuring SNA Server for RIS DB2 Data Server
__________________________________________________________________________________________________________________________________________________
8-2
8.
__________________________________________________________________________________________________________________________________________________

This chapter describes how to configure the SNA Server, which is a client-server product that
enables a personal computer (PC) to communicate with an IBM mainframe system that runs
the Systems Network Architecture (SNA) network. SNA Server can be used with the
appropriate Intergraph RIS data servers for Windows NT to communicate with DB2
databases. This chapter provides information to assist in configuring SNA Server for use
with RIS.
8.1 Related Documentation

Refer to the following Microsoft documents for information on installing and configuring SNA
Server.
Microsoft SNA Server Installation Guide
Microsoft SNA Server Administration Guide
Refer to the following Intergraph documents for information on installing and using other
necessary RIS components.
DNA1161
DNA1116
DNA1117
RIS Installation Guide for DB2

8.2 Installing RIS

To use RIS with DB2 databases, you must install the appropriate RIS data server and a RIS
transaction processor. The data server for DB2 database must be installed on a workstation
or server running Windows NT. See Installing RIS for instructions on installing RIS
products. The RIS transaction processor must be installed on an IBM mainframe. The
instructions for this process are given in the RIS Installation Guide for DB2. Installation on
an IBM Mainframe can be complex. If needed, contact an Intergraph Registered Consultant
for assistance.
8.3 Installing SNA Server

SNA Server has a client and a server component. The client can be installed on a
workstation running Windows NT, while the server portion must be installed on a machine
running the Windows NT Server operating system. The client machine must also have the
RIS data server installed. The server machine must have a physical network connection to
the IBM mainframe. The client and server portion of SNA Server can communicate using
any of several network protocols such as Named Pipes, Novell Netware, Banyan Vines, or
8-4
TCP/IP. It is possible to have multiple clients using the same server or multiple servers. For
a more complete description of possible SNA Server configurations and installation
instructions, see the Microsoft SNA Server Installation Guide.
8.4 Configuring SNA Server

After SNA Server is installed, it must be configured. The primary source of information for
configuring SNA Server is the Microsoft SNA Server Administration Guide.
For this discussion, use the SNA Server Administration Program to configure SNA Server.
Double click on the SNA Server Admin icon to start the configuration. Once it starts, the
following window appears.
RIS is written to use the Advanced Program-to-Program Communications interface (APPC).

APPC, in turn, depends on the LU6.2 protocol within SNA. You need this information to
determine how to configure SNA Server.
To configure SNA Server for use with RIS, you must create objects that represent the server,
the connection, and the logical units for the server and the database machine, as described in
the following.
8.4.1 The Server

There is only one server object that represents SNA Server and this object must be
configured first. To do so, open the Servers and Connections window and choose Properties
from the Services menu. You then see a dialog box like the following.
The server parameters that can be configured are Network Name and Control Point Name.
Supplying values for these parameters may not be necessary depending on how the database
machine is configured. For more information, see the Microsoft SNA Server Administration
Guide. You might need to ask the database machine system administrator for the correct
values.
8.4.2 The Connection

The next item to define is a connection. The connection defines how the SNA Server machine
talks to the mainframe. SNA Server supports many types of connections and of these RIS
can be used only with 802.2, which is the protocol for token ring connections.
To create a new connection, select the server in the Servers and Connections window. Then
choose New Connection from the Services menu. You then see the following dialog box.
Choose 802.2 and then click on OK. The next dialog box that appears is Connection
Properties.
8-6
The fields that must be set include Connection Name, Link Service, Remote End, Activation
and Allowed Directions. Notes about each are given below.
Connection Name:
This is a unique name for the connection.
Link Service:
The link service lets the connection access a particular

communications adapter card. Link services are installed by
using the setup program in the Microsoft SNA Server program
group, and with the SNA Server Admin utility. See the
Microsoft SNA Server Installation Guide for information on
installing link services.
Remote End:
This specifies if control is maintained by the remote system or is

shared. For the mainframe, select Host System.
Activation:
This specifies when the connection is started. Choose whichever

setting is appropriate for your site. If it is feasible, the simplest
method is to have connections started automatically by choosing
On Server Startup.
Allowed Directions:
This specifies if outgoing and incoming calls are allowed. Only

outgoing calls are needed for usage with RIS.
After you have completed the Connection Properties dialog, click on Setup. You then see the
following 802.2 Setup dialog.
The fields that must be set are Remote Network Address and Local Node ID. The Network
Name, Control Point Name, and Remote Node ID fields may not be necessary. Ask the
system administrator of the mainframe if these values are required.
Remote Network Address:
This is a 12-digit hexadecimal token ring address for the
mainframe.
Local Node ID:
This is an 8-digit hexadecimal number that identifies the local

system to the mainframe. Use the same Local Node ID for all
connections on a server. Contact the system administrator of the
mainframe to notify them of the Local Node ID used for your
system.
You can most likely use the default settings for Retry Timers and Advanced. If you have
problems making a connection, consult the Microsoft SNA documentation for information
concerning these parameters.
8.4.2.1 Restarting SNA Server

After you have completed the 802.2 setup, click on the OK button. You must restart SNA
Server for your configuration changes to take effect.
Before restarting the server, ensure that all SNA Server users log off to avoid
disrupting their work on the mainframe.
After all users are logged off, select the server entry in the Servers and Connections window.
Then, choose Stop Service from the Services menu. When you are prompted for confirmation,
click on Yes.
Once SNA Server is stopped, the server and all of its connections become inactive. To start it
again, choose Start Services from the Services Menu. Now the server and all connections are
shown as Active if you specified them to be started automatically. Otherwise, you must
manually start the connections. If a connection remains in the Pending state indefinitely,
then you have probably specified invalid information in the configuration. See the section
Troubleshooting for possible corrective actions.
8-8
8.5 Creating Logical Units (LUs)

The next step in the configuration process is to create the necessary LUs. Two LUs are
necessary: One is associated with the server, and the other associated with the connection.
The server LU is referred to as a local LU and the connection LU is a remote LU.
8.5.1 The Local LU

Because the RIS data server for DB2 is based on APPC, you must create a local LU for
APPC. To do this, select the server in the Server and Connections Window and then choose
Assign LUs from the Services menu. You then see the following dialog box.
Make sure APPC is selected and then click on the OK button. You then see an APPC LU
Properties dialog box like the one below.
First, make sure that the Independent button is selected. RIS only supports independent
LUs. Next, you must fill in the LU Alias, Network Name, and LU Name fields.
LU Alias:
This is the name of the LU. It must be unique among all of the LU
names for this server.
Network Name:
This is the name of the SNA network. Get this from the system
administrator of the mainframe. NETID value in the VTAM start
parameter list.
LU Name:
This is also the name of the LU. In most cases, it is identical to the
LU Alias. However, it can be different. The combination of Network
Name and LU Name must be unique for this server.
For now, clear the Enable Automatic Partnering box. After you have RIS working you can go
back and examine the documentation to see if you want to set this option.
Next, select the Member of Default Outgoing Local APPC LU Pool box. The RIS DB2 Server
on NT does not use the ris_lu field in the create schema statement. Instead, when you use a
schema, a local LU is automatically selected. There are two ways for a local LU to be chosen.
The first is to specify a default LU for a user. This is done in the Users and Groups window
of the SNA Server Admin Utility. The second, and simpler, method is to make the local LU
part of the default outgoing local APPC LU pool for the server.
The default values for the remaining fields, Implicit Incoming Remote LU and Timeout for
Starting Invokable TPs, are sufficient. Click on the OK button to complete the configuration
of the local LU.
8.5.2 The Remote LU

To create a remote LU, you must first select a connection from the Servers and Connections
window. Next, choose Assign LUs from the Services menu. You then see the same Insert LU
dialog box as you did when you created a local LU. Select APPC and click on OK. The New
APPC Remote LU Properties dialog then appears.
The fields that must be set are LU Alias, Network Name, and LU Name.
LU Alias:
This is the name used locally for the remote LU. It must be unique for
this connection and not match the name of a local LU. The LU Alias
can be the same as or different from the LU name.
8 - 10
Network Name:
This is the name of the SNA network. It is the same as the network
name for the local LU.
LU Name:
This is the name of the remote LU. The combination of Network

Name and LU Name must be unique for the connection and must not
match a local LU. Get this name from the system administrator for
the mainframe.
The Uninterpreted LU Name field, required for dependent LUs, can be filled in, but is not
required for RIS because RIS supports independent LUs only.
Next, make sure that the Supports Parallel Sessions box is marked, and the Enable
Automatic Partnering box is cleared. Parallel sessions are explained in the Modes section.
Automatic partnering is covered in the Local LU section.
The default values for Implicit Incoming Mode and Security are acceptable. Partners are
covered in the next section. Click on OK to complete the configuration.
8.5.3 Partnering LUs

Now that you have created a local and a remote LU, the only configuration task remaining is
partnering the LUs. Partnering LUs tells SNA that the local and remote LUs can
communicate. In addition, the mode used in the partnership defines how the LUs
communicate.
You can set up the partnership by going through the properties dialog for either the local or
remote LU. The LUs you have configured are listed on the right side of the Servers and
Connections window. If the server is selected, you then see the local LUs. If a connection is
selected, you then see its remote LUs.
To bring up an LU properties dialog box, double click on the local or remote LU. In the
properties dialog, click on the Partners dialog. You then see the following dialog.
You must add a new partnership. To do this, click on the Add button to display a dialog
similar to the following.
To complete this dialog, select the partner LU and a mode. Pick the local or remote LU that
you configured depending on whichever is not shown on the Local LU line in the dialog. The
mode used for RIS is usually IGRLU62P. Check with the system administrator of the
mainframe to verify if this is the correct mode name. Now, select the IGRLU62P mode, or
other mode name as appropriate, and click on OK. If the required mode does not exist, click
on Cancel and then click on the Modes button in the LU properties dialog. This allows you to
define the mode. This is explained in The Mode section.
8.5.4 Checking LU Status

Once the LUs are partnered, you must restart SNA Server for your changes to take effect.
This procedure is described in the Restarting SNA Server section. After you have restarted
SNA Server, check the status of the LUs to see if they are working. Do this by opening the
LU properties dialog for the local LU. The local LU is displayed in the Servers and
Connections window when the server is selected. Double click on the local LU name to
activate the LU properties dialog. Then, click on the Status button. This brings up the
following LU status dialog.
This dialog shows the status for the local LU and all partners. Note that every LU pair you
created appears twice; once with the mode you specified, and again with the mode
SNASVCMG. This second entry is automatically created by SNA Server. The SNASVCMG
mode is a special internal mode used to start up connections. If the LUs have been specified
correctly, you will see at least one session running for each of the entries with the
SNASVCMG mode. If some of your connections are not working, see the Troubleshooting
section for help.
8 - 12
If your connections are working, then the SNA Server configuration is complete. See the
section Creating Schemas to continue with the SNA Server configuration. Note that when
you make connections through RIS, you must use the sessions listed in the LU status dialog
box.
8.6 The Mode
This dialog displays the properties for the existing modes and can be used to add, change,
and delete modes. Typically RIS installations use the IGRLU62P mode. Also, if you use the
alter schema modify DB2 password statement, then you may need the IGRLU62Q mode.
First, you must key in the name (IGRLU62P, for example) in the mode name field. This
enables the add button so that you can create a new mode. For the remainder of the fields,
except Parallel Session Limit and Enable Automatic Partnering, use the default values.
However, check with the mainframe system administrator to be sure.
Default Values for Mode Properties
Minimum Contention Winner Limit
Partner Min Contention Winner Limit
Automatic Activation Limit
High Priority Mode
Pacing Send Count
Pacing Receive Count
Max Send RU Size
Max Receive RU Size
0
0
0
Selected
4
4
1024
1024
For Enable Automatic Partnering, make sure the box is cleared. If you wish to enable this
later you must modify the LUs and the modes appropriately. This is described in the
Microsoft SNA Server Administration Guide.
The parallel session limit determines how many programs can use a pair of LUs at the same
time. If this limit is exceeded, then a transaction within RIS may be blocked until a
transaction in another process is committed. You must coordinate with the system
administrator of the mainframe to determine an appropriate limit.
After you have filled in all of the fields, click on the Add button. Click on the Close button to
dismiss the dialog box.
8.7 Creating Schemas

After you configure SNA Server, you must create a schema to determine if everything is
working. The easiest way to create a schema is by using the RIS Schema Manager. For
information on the schema manager and the create schema statement for DB2, see the RIS
Utilities Users Guide and the RIS SQL Users Guide. The figure below shows the Create
Schema form for DB2.
Notice the LU6.2-specific fields that are located in the lower right corner. These fields are
described following:
RIS LU Name
Corresponds to the local LU name. Schema manager requires

this field to be specified, but it is not actually used by the DB2
server for Windows NT. On Windows NT, the DB2 server is
dependent on the local LU being the default outgoing LU for
the user or the server in general.
Host LU
Name
Corresponds to the remote LU. This name must exactly

match the remote LU name you specified during the
configuration of SNA Server.
LU62 Mode
Name
Specifies the mode to be used for communication between the

LUs. This must match the mode that you defined during the
partnering of the LUs. Typically the IGRLU62P is used for
RIS.
8 - 14
Host
Program
Name
Specifies the name of the RIS Transaction Processor running

on the mainframe. Typically the transaction processor is
named RISX.
Once you have successfully created a schema, the DB2 connection is ready for use by RIS
based applications.
8.8 Troubleshooting
Several layers of software are used to communicate between RIS on Windows NT and a DB2
database. This, unfortunately, provides many places where problems can arise. If you have
a problem making a connection for the first time, verify that each of the layers are working
individually from the lowest to the highest.
Also, all parameters specified in the configuration of SNA Server must match those of the
mainframe. The mainframe is the controlling entity. If SNA Server parameters do not
match with those for the mainframe, the connection attempt is rejected.
The following steps offer troubleshooting tips:
1.
Network adapter and cables.

First of all, make sure that the hardware is in place, including the network board and
the token ring cable. It is usually necessary to run some sort of low level configuration
utility as well. Check the documentation that was provided with the token ring card for
details. Also check to see if there is a diagnostic utility to determine if the board is
working correctly.
2.
SNA Server software.

The SNA Server software is installed via setup. If SNA Server seems to be broken, the
installation may have been corrupted. In this case, remove and reinstall SNA Server.
Be sure to record all configuration information first; the configuration must be
recreated after you reinstall SNA Server. To remove SNA Server, select the Remove
option in the SNA Server Setup Utility. Do not attempt to remove the SNA Server files
directly.
Now, rerun the SNA Server setup and recreate your configuration using the SNA
Server Admin utility. Note that during the installation of SNA Server you must
reinstall the link service that SNA Server uses to communicate with the token ring
card.
If SNA server still does not appear to operate correctly, consult the Microsoft SNA
Server documentation for other possible actions.
3.
Server definition.
Make sure that the Network Name and Control Point Name are correct, if they are
needed. If they are not needed, make sure that these fields are empty.
4.
Connection definition.
For a connection, make sure that the Remote End, Remote Network Address, and Local
Node ID fields are correct. Also, check the Remote Node Name parameters if they are
needed. If they are not needed, make sure that the Remote Node Name fields are
empty.
If any of the Connection parameters are wrong, the Connection hangs when you try to
activate it. If this occurs and you cannot determine what is wrong, try checking the
system logs. The procedure for doing this is described in the next section.
5.
LU and Mode definition.

The most likely problem with LUs and Modes are mismatches in the names between
SNA Server and the mainframe. It is also possible that permissions have not been set
up correctly on the mainframe. Check the system logs for information on LU and Mode
problems.
6.
RIS Software
Make sure that you have all of the necessary pieces of compatible RIS software, the
database management system, and the operating system. If all else fails, try removing
and reinstalling the RIS software. Use the RIS remove utility instead of directly
deleting files. Note that schema definitions and other parameter settings can be lost if
RIS is removed.
7.
Schema definition.
A schema definition contains several items. Make sure that the user names,
passwords, database name, and network parameters are correct. Also verify with the
system administrator that you have the necessary privileges to access the database.
8.
Application software.
If you are having problems using RIS through an application, determine if the problem
is application-specific or a general RIS problem. Try connecting to the database
through the RIS Schema Manager or Interactive utility. If you can successfully execute
statements through the RIS utilities, then the problem is probably application-specific.
8.8.1 System Logs

Three log files exist to help diagnose problems related to SNA Server and RIS. These places
are the SNA Server client, the SNA Server server, and the mainframe.
Both the client and server portions of SNA Server can be made to record informational and
error messages in the Windows NT system log. To enable logging, select Logs from the
Options menu.
8 - 16
The log levels vary from Disabled to Detailed. If you are unsure of which option to take,
choose Detailed and click on OK. You must now restart SNA Server to make sure that the
new logging level takes effect.
When you finish examining the problem, reset the log level to Disabled or Significant,
otherwise the log file fills up quickly. You must then restart SNA Server again for the new
log level to take effect.
To view the log file on the client or server, you must use the Event Viewer on the appropriate
machine. The Event Viewer can be found in the Administrative Tools program group. Once
in the Event View, choose Application from the Log menu. You then see a list of application
events for SNA Server and possibly other applications.
Double click on any event line for detailed information. Note that the lines shown are just a
snapshot. To see the most current events choose Refresh from the View Menu. If the log file
becomes full, you can clear out all of the entries by choosing Clear All Events from the Log
menu.
The mainframe also logs events related to the network and the database management
system. Often, these logs are more informative because the error actually occurred on the
mainframe. Have the system administrator check these logs first if you are having problems.
Removing RIS Products 9 - 1
Removing RIS Products
__________________________________________________________________________________________________________________________________________________
9-2
Removing RIS Products 9 - 3
9.
__________________________________________________________________________________________________________________________________________________

This section assumes that the RIS Development Platform and associated data servers are
installed in the default directories, and that the RIS Shared Component (runtime) is
installed in the c:\Program files\Common files\Intergraph\ris<major.minor> directory.
To remove any RIS product, double-click on the Remove icon in the appropriate program
group.
If another application is using the RIS shared component, then Remove only
removes the specified product, such as the RIS Development Platform.
The remove executable is removed during the next system reboot. Users are prompted to
reboot now or wait.
9-4
Differences Between RIS for UNIX and RIS for 32-Bit Applications 10 - 1
Differences Between RIS for UNIX and RIS for 32Bit Applications
__________________________________________________________________________________________________________________________________________________
10 - 2
Differences Between RIS for UNIX and RIS for 32-Bit Applications
Differences Between RIS for UNIX and RIS for 32-Bit Applications 10 - 3
10.
__________________________________________________________________________________________________________________________________________________
Differences Between RIS for UNIX and RIS for 32Bit Applications
Every effort has been taken to make the RIS products operate the same way on each
operating system. However, because of the nature of the 32-bit operating systems and the
resources available in this environment, a few differences do exist. Note the following
differences:
The RIS client and utilities, known as the Shared Component, are delivered with all
RIS products.
The Cleanup utility is not available in the 32-bit environment.
The Help facility is not the standard Intergraph Help facility. You must use Windows
Help to view the on-line documentation. For more information, see the On-line
Documentation in Windows NT.
Several additional functions are available with Version 5 of the RIS Development
Platform. For more information, see the RIS Programmers Guide for 32-Bit
Applications.
10 - 4
Differences Between RIS for UNIX and RIS for 32-Bit Applications
Running the RIS Executables 11 - 1
Running the RIS Executables
__________________________________________________________________________________________________________________________________________________
11 - 2
Running the RIS Executables 11 - 3
11.
__________________________________________________________________________________________________________________________________________________

By default, the RIS executables are located in the following directories:
c:\Program Files\risdp\bin (development platform)
c:\Program Files\Common Files\Intergraph\ris<major.minor>\bin (shared component)
In the previous directory path, major and minor version numbers are
determined as follows: In the product release number 05.01, the major number
is 05, and the minor number is 01.
You can also start the RIS utilities from the Program Manager. For more information about
the RIS executables, refer to the RIS Utilities Guide for 32-Bit Applications and the RIS
Programmers Guide for 32-Bit Applications.
11 - 4
Appendix A: Redistribution of RIS Runtime and RIS Utilities A - 1
Appendix A
__________________________________________________________________________________________________________________________________________________
Redistribution of RIS Runtime and RIS Utilities
A-2
Appendix A: Redistribution of RIS Runtime and RIS Utilities
Appendix A
__________________________________________________________________________________________________________________________________________________
Redistribution of RIS Runtime and RIS Utilities

Redistribution rights and limitations are described in the product license agreement for the
RIS Development Platform.
When you develop an application with the RIS Development Platform, the application can
run only on systems that have the RIS Shared Component; therefore, you must redistribute
the RIS Shared Component with your application.
The following sections describe integrating the RIS Shared Component delivery into your
delivery procedure.
A.1 Directory Structure

The RIS Shared Component is delivered as part of the RIS Development Platform to the
c:\Program Files\risdp\shared directory. This directory includes files to be delivered to the
user system, and other setup and packaging files as described in the following section.
A.2 Setup Files

Use the following setup files to build the setup media for your application:
rissetup.lyt This file is the Microsoft Setup layout file for the RIS Shared Component
files. Append your applications .lyt file to this file.
Use the combined .lyt file to create a .inf file with the dsklayt2 utility (which is part of
the SETUPSDK product). Your setup program uses the .inf file to download the
necessary files to the end-users system.
rissetup.lib The functions in this library install the RIS Shared Component on the
end-users system. You must link your setup program with this library, and call the
following functions (in order):
a.
ReadInfFile();
Call this function once before calling any other setup functions for the RIS Shared
Component.
A-4
b.
SetupRIS();
This function determines the version of the RIS Shared Component that is already
installed, if any. You must use the value returned by this function as input to the
RegEdtRIS function.
Status
Returns
______________
0
1
2
c.
Existing version is newer than your version. RIS

shared component is not loaded.
Existing version is older, or the same date as your
version. RIS Shared Component is loaded.
Existing version not found. RIS Shared Component is
loaded.
CopyFilesInCopyList();
This function downloads your application files and the RIS Shared Component
files (if necessary).
d.
RegEdtRIS(int action, char *listEntry);

This function edits the registry for RIS and adds the RIStcpsrService into
Services.
Keyword/Identifier
__________________
Description
___________
action
listEntry
Return value from the SetupRIS function.

String that identifies the name and version of your
application. For example: MYAPP\\01.00.00.00
risrem.lib The functions in this library remove the RIS Shared Component from the
system. Link your application remove program with this library. To remove the RIS
Shared Component in case of an error, link your setup program with this library.
a.
RegRemoveRIS(HINSTANCE remInstance, char *listEntry);

Keyword/Identifier
__________________
Description
___________
remInstance
listEntry
Removal process instance for the application.

Entry in the RefList field for the application.
This function removes your applications entry from the RefList field in the RIS
Shared Component registry key.
Status
Returns
______________
0
1
RefList field is not empty.

RefList field is empty.
b.
RemoveRIS(HINSTANCE remInstance, int flag);

This function removes the RIS Shared Component services, files, and registry
entries.
Keyword/Identifier
__________________
Description
___________
remInstance
flag
Removal process instance for the application.

Return value from the RegRemoveRIS function.
readme1.txt This uncompressed README file contains the RIS product name and
version.
The primary purpose of this file is to keep track of the RIS Shared Component version,
but you can add information from the RIS README file if it would be useful to the
end-user.
manifes1.txt This uncompressed ASCII file lists the files that are delivered with the
RIS Shared Component. You must integrate this file into the manifest file for your
application.
A.3 Installing the RIS Shared Component

The installation procedure does the following:
1.
Installs the required files on the users file system (after first checking to make sure
that the version being installed is the same or newer than any existing version) and if
an older version is found, it is removed.
2.
Adds information to the registry.
3.
Installs the RIS TCP service, and starts it. This service lets remote applications and/or
clients connect to other servers on the system.
4.
Creates a RIS program group, which contains various help and executable utilities.
Location on File System

RIS Shared Component is installed to the location specified in the registry entry:
Program Files\Common Files\Intergraph\RIS\<Major.Minor>
The installation procedure examines the system PATH variable to see if it contains the
\Program Files\Common Files\Intergraph directory. If the PATH does not contain this
directory, the installation procedure appends \Program Files\Common Files\Intergraph to
the system PATH.
A-6
Registry Information
The RIS Shared Component puts information into the System Registry to indicate its
presence on the system. The component installation procedure creates the key
HKEY_LOCAL_MACHINE\Software\Intergraph\RIS\<Major.Minor>
and adds the following values:

Description
InstallDate
PathName
SoftwareType
IDNumber
RelDate
Version
RefList
The RefList entry facilitates removal of the shared component. All products that use the RIS
Shared Component must add themselves to this reference list (with the RegEdtRIS function)
during installation, and must remove themselves from the list (with the RemoveRIS function)
during removal.
Any product that wants to remove a shared component can do so only if the reference list for
the shared component is empty. The RefList consists of a semicolon-separated list of
products that use the shared component. The referencing product string has the format
<product_name>\<product_version> where this information is the same as the name\version
portion of the registry key for the product.
Appendix B: On-line Documentation B - 1
Appendix B
__________________________________________________________________________________________________________________________________________________
On-line Documentation
B-2
Appendix B: On-line Documentation
Appendix B
__________________________________________________________________________________________________________________________________________________
On-line Documentation
The following on-line documents are available:
RIS Programmers Guide for 32-Bit Applications
To display the document, select the icon from Program Manager.
B.1
Using On-line Help
On-line Help is an on-line reference tool accessible at any time the application is in use. The
on-line Help contains a description for each command and tool and step-by-step procedures
for common tasks. For example, if you need to perform a certain task, search and display the
topic. You can move or resize your application and Help windows so that they are next to
each other. This lets you follow the procedures without having to search for the pages in the
documentation.
B-4
B.1.1
Parts of the Help Window
To view the on-line Help, select Contents from the Help menu. To get more specific
information, select one of the major topics or perform a search on a specific topic.
Use
To
Contents
Display a listing of the table of contents for

the on-line Help file.
Search
Locate information about a certain topic that

you enter in the Search box.
Back
Take you back to the previous Help topics you

have already viewed.
History
Display a sequential list of every Help topic

you have viewed during your current Windows
session.
Find
Display a dialog box used to retrieve partial or

full text strings in the help file. Use the
Hints button for information on constructing
your search query.
<<
View the previous topic in a series of related

topics. The button is dimmed when you reach
the first topic in the series.
>>
View the next topic in a series of related

topics. The button is dimmed when you reach
the last topic in the series.
If the graphics in the on-line Help appear distorted, check your graphics driver.
If you are using an Intergraph TD1 machine, the S3 1024x768 256 color (Large
Font) distorts the graphics slightly. Changing to the (Small Font) version
corrects the display. If you are using other drivers, check with your PC manual
for information about available graphics drivers.
B-6
Glossary GL - 1
Glossary
__________________________________________________________________________________________________________________________________________________
GL - 2
Glossary
Glossary GL - 3
Glossary
__________________________________________________________________________________________________________________________________________________
802.2
The IEEE standard that defines the token ring network

protocol.
access
Perform actions necessary to use software.
APPC
Advanced program-to-program communication in System

Network Architecture.
application
System of programs or utilities designed to accomplish

specific tasks as requested by the user.
ASCII
American Standard Code for Information Interchange

character set.
General-purpose, structured programming language

developed at Bell Labs in the early 1970s.
char
Data type that stores one character.
character
Alphabetic letter, digit, punctuation, or symbol.
choose
To activate buttons, fields, and so forth on dialog boxes.
client
Portion of a client/server-based application that requests

services.
collapse
Changing a form or window from the normal display to a

small icon representing the collapsed form or window.
column
Vertical arrangement of figures or words.
command
Software that interacts with the user, obtaining user input

and then acting in a specified way based on that input. Each
icon on the menu accesses a command, although there could
also be additional commands accessed only by key-in.
command line
Alphanumeric key-ins used to invoke an executable directly

from the operating system environment.
connection
An association established between two functional units for

conveying information.
data type
Classification of a data item as an integer, letter, or real

number.
GL - 4
Glossary
database
Collection of comprehensive informational files having

predetermined structure and organization that can then be
communicated, interpreted, or processed by a specific
program.
default
Predetermined value of a parameter or option that is

automatically supplied by the system or program whenever a
value is not specified by the user.
development platform
Base or foundation of software on which application programs

can be built.
dialog box
A box that requests information about a particular task you

are performing.
dimmed
A button or command that is displayed in light gray instead of

black. When a button or command is dimmed, it is disabled
and nonselectable.
disk
Round flat plate coated with a magnetic substance on which

data is stored.
enter
To enter data from a mouse or from a keyboard.
error message
Description of an error found in a program.
executable
Program that has been written in, or translated into, a

machine language that is ready for execution by the
computer.
field
Any of the data grouped together in a record (also known as

an attribute or column). Also, an area for text entry on a
dialog.
file
Collection of logical records stored as a unit.
filename
User-defined name given to an interactively created file. The

name should be relevant to the contents of the file.
flag
A variable that can be set to indicate the presence or absence

of a certain condition.
floppy disk
Flexible magnetic sheet used to store information.
function
Small segment of code written to complete a portion of a

larger task.
graphic
Any symbol or method of visual communication that is not

text.
Glossary GL - 5
group
A collection of icons that represent documents and

applications within the Program Manager.
Help
See on-line Help.
Help window
Form in which the Help topics are displayed by the Help

process.
icon
Symbol that graphically identifies a command, application, or

document.
identify
To indicate your selection on a form or graphics by placing a

data point on the item.
int
Data type which stores a range of integer values.
interface
Shared boundary through which the user and software

communicate.
keyword
Word defined to have special meaning in a programming,

command, or query language.
library
Collection of subroutines.
link
Combine one or more program segments, subroutines, or

library routine into a single executable program.
logical unit (LU)
A port through which a user gains access to the services of an

SNA network.
MB
Acronym for megabyte.
memory
Device that can store data.
menu
Means for storing and selecting commands: icon-based,

function key, or paper.
mode
Particular functioning arrangement or condition.
mouse
Hand-controlled input and command selection device. There

are several models; most common are the 2-button mouse, the
3-button mouse, and the 12-button mouse.
MS-DOS
Disk Operating System (the single user operating system on

PCs).
network
Interconnection of host computers and workstations that lets

them share data and control. The term network can mean the
devices that connect the system, or it can mean the connected
system.
GL - 6
Glossary
on-line
documentation
See on-line Help.
on-line Help
Set of on-line, context sensitive files, that provide information

to the user about the capabilities of an application.
operating system
System programs that control the overall operation of a

computer system.
partnering
An association between a local LU and a remote LU that

enables them to communicate.
path
Sequence of directories leading to a file or a sequence of

menus leading to a command.
pathname
Sequence of directories leading to a file. See also absolute

pathname and relative pathname.
place
To create and position an element or object.
Program Manager
The main window in Microsoft Windows, used to start

applications and open documents. It also organizes the
applications and documents into groups. Within these groups
reside icons that represent each application and document.
RAM
Acronym for Random Access Memory.
record
Grouping of logically related data which can be manipulated

as a single entity. One or more records make up a file or a
table. Also known as a row or tuple.
relational database
Organizes data in two-dimensional tables to define

relationships.
Relational Interface
System
Intergraph software system that provides a generic interface

for applications to access many popular relational database
management systems.
resize
To change the size and position of a form or window.
RIS
Acronym for Relational Interface System.
run
To execute a program or process.
runtime
Time at or during which a program or process is executed.
select
To activate a command. This can be done by the user or

software.
server
Computer, connected to a network, that provides services to

one or more devices on that network. A server can also refer
to a process that provides services to one or more client
(requester) processes locally or remotely.
Glossary GL - 7
SNA
Acronym for System Network Architecture, which is IBMs

proprietary networking protocol.
SQL
Acronym for Structured Query Language.
string
Sequence of characters.
system
Collection of information and processes designed to interact to

complete a task.
table
Collection of data for quick reference, stored in sequential

locations in memory or printed as an array of rows and
columns of data items of the same type.
token ring
A network protocol in which a token is passed among network

nodes. The node that holds the token can transmit, at which
time the token is passed to the next node to transmit data.
type
Type of data that a programming variable can contain.
UNIX
General purpose operating system developed at Bell

Laboratories in the late 60s and early 70s.
value
Numeric or character data.
variable
Quantity that can assume any one of a set of values.
version
The number associated with the specific release of a product.
view
Concept described by the ANSI SQL Standard, used to

combine tables or restrict access to columns in a table. A view
looks and acts like a table, but does not actually store data.
window
Independent rectangular area which displays applications or

documents and that can be moved, resized, reshaped,
minimized, or maximized.
Windows NT
General purpose 32-bit operating system developed at

Microsoft Corporation.
GL - 8
Glossary
Index IN - 1
Index
__________________________________________________________________________________________________________________________________________________
IN - 2
Index
Index IN - 3
Index
__________________________________________________________________________________________________________________________________________________
A
American national standards institute 2-13
ANSI 2-13
architecture 2-3
B
batch mode installation 5-7
C
changing wait time 5-10
checking LU status 8-11
choose 1-4
client 2-12
configuration files
creating 5-7
Configuration Overview 2-3
configuring SNA server 8-4
RIS DB2 data server 8-3
connection 8-5
connection, database 2-11
CopyFilesInCopyList A-4
creating configuration files 5-7
creating logical units 8-8
creating schemas 8-13
custom installation dialog 5-7
customer information dialog 5-4
D
data dictionary 2-11
data servers 2-14
database connection 2-11
databases supported 2-11
DB2 data server 8-3
defining schemas 2-11
destination path 5-5
development platform 2-7, 2-13
dictionary, data 2-11
differences between RIS for UNIX and RIS
for 32-bit applications 10-3
document conventions 1-4
document prerequisites 1-3
dsklayt2 A-3
E
environment overview 2-7
H
hard drive requirements 4-3
hardware 4-3
Help
using on-line B-3
I
identify 1-4
installation, custom 5-7
installation destination dialog 5-5
installation options dialog 5-6
installation type
selecting 5-6
installing applications in batch mode 5-7
installing RIS 5-3, 8-3
installing SNA server 8-4
installing the RIS shared component A-5
interoperability 3-3
introduction 2-3
K
key in 1-4
L
license list utility 6-3
local LU 8-8
LU
checking status 8-11
creating 8-8
local 8-8
partnering 8-10
remote 8-9
M
manifes1.txt A-5
memory requirements 4-3
Microsoft SNA Server 2.1 or 2.11 4-3
Microsoft Visual C++ 2.0, 2.1 or 2.2
Compiler 4-3
mode 8-12
IN - 4
Index
monitor utility 6-3

mouse 1-4
N
net servers 2-14
networking 2-11
O
on-line Help B-3
orphan process
wait time change 5-10
orphan processes 5-9
symptoms 5-9
P
partnering LUs 8-10
parts of the Help window B-3
PATH A-6
path
destination 5-5
personalizing software 5-4
process wait time 5-10
processor requirements 4-3
product overview 2-3
product overviews 2-12
R
RAM requirements 4-3
RDBMS 2-3
ReadInfFile A-3
readme1.txt A-5
redistribution of RIS runtime and RIS
utilities A-3
RegEdtRIS A-4
registry utility 7-3
RegRemoveRIS A-5
related documentation 1-3
relational database management system
2-3
relational interface system 2-3
remote LU 8-9
RemoveRIS A-5
removing RIS products 9-3
requirements
hardware 4-3
software 4-3
system 4-3
reset 1-4
restarting SNA serer 8-7
RIS
client 2-7, 2-12
RIS (continued)
compatibility 2-13
data/net servers 2-14
definition 2-3
development platform 2-7, 2-13
Development Platform
capabilities 2-13
embedded SQL 2-13
installing 5-3
introduction to 2-3
runtime 2-12
servers 2-14
shared component directory structure
A-3
supported platforms 2-13
utilities 2-7, 2-14
RIS executables
running 11-3
RIS for UNIX and RIS for 32-bit
applications, differences 10-3
RIS installation 8-3
RIS Installation Guide for DB2 1-3, 8-3
RIS products 2-12
removing 9-3
RIS Programmers Guide for 32-Bit
Applications 1-3
RIS Programmers Quick Reference 1-3
RIS SQL Commands Quick Reference 1-3
RIS SQL Users Guide for 32-Bit
Applications 1-3, 8-3
1-3, 8-3
RISDP
selecting the installation type 5-6
risrem.lib A-4
rissetup.lib A-3
rissetup.lyt A-3
rliclist 6-3
running the RIS executables 11-3
S
schema definition 2-11
schemas 2-11
select 1-4
selecting the installation type for RISDP
5-6
selecting the product destination path 5-5
server 8-5
setup
starting 5-3
Index IN - 5
setup files A-3

SetupRIS A-4
SETUPSDK A-3
shared component A-3
shared component location A-6
shared component registry information A-7
SNA server
configuration 8-4
installation 8-4
restarting 8-7
software, personalizing 5-4
SQL
definition 2-13
starting setup 5-3
storage requirements 4-3
structured query language 2-13
supported databases 2-11
system logs 8-15
T
troubleshooting 8-14
U
upgrading 3-3
using on-line Help B-3
utilities 2-7, 2-14
license list 6-3
monitor 6-3
registry 7-3
rliclist 6-3
V
viewing on-line Help B-3
visual C++ compiler
compiler, visual C++ 4-3
W
wait time 5-10
Windows 95 4-3
Windows NT 4-3
IN - 6
Index

RIS Installation Guide: For 32-Bit Applications

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RIS Installation Guide: For 32-Bit Applications

Hochgeladen von

Copyright:

Verfügbare Formate

RIS Installation Guide

for 32-Bit Applications

Warranties and Liabilities

Table of Contents iii

Before You Begin ..................................................................................................

Architecture and Configuration Overview ..........................................................

RIS Architecture ..........................................................................................

Schema Definition and Database Connection .................................

The RIS Products .........................................................................................

RIS Client .........................................................................................

Interoperability and Upgrading ...........................................................................

Overview of Interoperability .......................................................................

System Requirements ...........................................................................................

Hardware Needed ........................................................................................

Installing RIS .......................................................................................................

Starting Setup ..............................................................................................

Orphan Process Symptoms ..............................................................

RIS License List Utility ........................................................................................

RISINFDS/RISINFNS Registry Utility ...............................................................

Configuring SNA Server for RIS DB2 Data Server ............................................

Related Documentation ...............................................................................

The Server ........................................................................................

Restarting SNA Server ......................................................

Creating Logical Units (LUs) ......................................................................

The Local LU ....................................................................................

The Mode ......................................................................................................

System Logs ......................................................................................

Removing RIS Products ........................................................................................

Running the RIS Executables ............................................................................

Redistribution of RIS Runtime and RIS Utilities ..............................

Directory Structure ............................................................................................

On-line Documentation .......................................................................

Using On-line Help ............................................................................................

Parts of the Help Window ......................................................................

Table of Contents vii

viii Table of Contents

Before You Begin 1 - 1

Before You Begin

Before You Begin

Before You Begin 1 - 3

Before You Begin

RIS SQL Users Guide for 32-Bit Applications

Before You Begin

Before You Begin 1 - 5

Before You Begin

Architecture and Configuration Overview 2 - 1

Architecture and Configuration Overview

Architecture and Configuration Overview

Architecture and Configuration Overview 2 - 3

Architecture and Configuration Overview

2.1 RIS Architecture

Architecture and Configuration Overview

Architecture and Configuration Overview 2 - 5

Architecture and Configuration Overview

Architecture and Configuration Overview 2 - 7

2.2 Environment Overview

Architecture and Configuration Overview

Architecture and Configuration Overview 2 - 9

Architecture and Configuration Overview

Architecture and Configuration Overview 2 - 11

2.2.1 Schema Definition and Database Connection

2.2.2 Integrated Data Dictionary

Architecture and Configuration Overview