Guia Oficial N°09. Vel30IA

Velocis
Installation and Administration Guide

20-7201-1001
Trademarks
Centura, the Centura logo, Centura net.db, Centura Web Developer, Gupta, the Gupta
logo, Gupta Powered, the Gupta Powered logo, Fast Facts, Object Nationalizer, Quest,
QuickObjects, SQL/API, SQLBase, SQLBase Exchange, SQLConsole, SQLGateway,
SQLHost, SQLNetwork, SQLRouter, SQLTalk, and Team Object Manager, RDM, ROM,
and Velocis are trademarks of Centura Software Corporation and may be registered in the
United States of America and/or other countries. SQLWindows is a registered trademark
and TeamWindows, ReportWindows and EditWindows are trademarks exclusively used
and licensed by Centura Software Corporation.
Adobe is a trademark of Adobe Systems, Incorporated.
IBM, OS/2, NetBIOS, and AIX are registered trademarks of International Business
Machines Corporation.
UNIX is a registered trademark licensed exclusively by The Open Group.
SCO UNIX is a trademark of Santa Cruz Operation, Incorporated.
Microsoft is a registered trademark, and DOS, Windows, Windows NT, and Windows 95
are trademarks, of Microsoft Corporation.
Java and Solaris are trademarks of Sun Microsystems, Incorporated.
Microsoft, Internet Explorer, Internet Information Server, DOS, Win 32, Windows,
Windows NT, Windows 95 and Visual Basic are either registered trademarks or
trademarks of Microsoft Corporation in the United States of America and/or other
countries.
Novell is a registered trademark, and NetWare is a trademark, of Novell Incorporated.
All other product or service names mentioned herein are trademarks or registered
trademarks of their respective owners.
Copyright
Copyright  1999 by Centura Software Corporation. All rights reserved.
Velocis 3.0 Installation and Administration Guide
20-7301-1002
November 1999
Contents
Chapter 1 Introduction
1.1 Velocis Documentation................................................................................................ 1-1
1.1.1 About This Manual................................................................................................. 1-1
1.1.2 Related Velocis Documents ................................................................................... 1-2
1.1.3 Document Conventions ......................................................................................... 1-2
1.2 Other Helpful Resources ............................................................................................. 1-3
Chapter 2 About the Velocis Environment

2.1 Transport Protocols Supported by Velocis................................................................ 2-1
2.2 Standalone Velocis Platforms...................................................................................... 2-2
2.2.1 Windows 95/98 and Windows NT 4.0.............................................................. 2-2
2.3 Velocis Server Platforms.............................................................................................. 2-3
2.3.1 Configuring Server Transports .......................................................................... 2-3
2.3.2 Windows 95/98 Server Platform ....................................................................... 2-4
2.3.2.1 Windows 95/98 Platform Requirements ................................................. 2-4
2.3.2.2 TCP/IP Transport for Windows 95/98 .................................................... 2-5
2.3.2.3 Local Transport for Windows 95/98 ........................................................ 2-5
2.3.3 Windows NT 4.0 Server Platform ...................................................................... 2-5
2.3.3.1 Windows NT 4.0/2000 Platform Requirements...................................... 2-5
2.3.3.2 NT Named Pipes Transport....................................................................... 2-6
2.3.3.3 TCP/IP Transport for Windows NT 4.0/2000 ........................................ 2-6
2.3.3.4 Local Transport for Windows NT 4.0/2000............................................. 2-6
2.3.4 UNIX Server Platforms ....................................................................................... 2-6
2.3.4.1 UNIX Platform Requirements ................................................................... 2-6
2.3.4.2 TCP/IP Transport for UNIX...................................................................... 2-7
2.3.4.3 UNIX Domain Transport for UNIX .......................................................... 2-7
2.3.4.4 Local Transport for UNIX .......................................................................... 2-7
2.4 Velocis Client Platforms .............................................................................................. 2-8
2.4.1 Configuring Client Transports ........................................................................... 2-8
2.4.1.1 Defining Aliases .......................................................................................... 2-9
2.4.1.2 Defining Global Transport Parameters .................................................. 2-11
2.4.2 Windows 95/98 Client Platform ...................................................................... 2-12
2.4.2.1 Windows 95/98 Platform Requirements ............................................... 2-12
2.4.2.2 Named Pipes Transport for Windows 95/98 ........................................ 2-12
2.4.2.3 TCP/IP Transport for Windows 95/98 .................................................. 2-12
2.4.2.4 Local Transport for Windows 95/98 ...................................................... 2-12
2.4.3 Windows NT 4.0/2000 Client Platform .......................................................... 2-13
2.4.3.1 Windows NT 4.0/2000 Platform Requirements.................................... 2-13
Contents i
2.4.3.2 Named Pipes Transport for Windows NT 4.0/2000............................. 2-13
2.4.3.3 TCP/IP Transport for Windows NT 4.0/2000 ...................................... 2-13
2.4.3.4 Local Transport for Windows NT 4.0/2000........................................... 2-13
2.4.4 UNIX Client Platform........................................................................................ 2-13
2.4.4.1 UNIX Platform Requirements ................................................................. 2-13
2.4.4.2 TCP/IP Transport for UNIX.................................................................... 2-14
2.4.4.3 Local Transport for UNIX ........................................................................ 2-14
2.4.4.4 UNIX Domain Sockets Transport for UNIX .......................................... 2-14
Chapter 3 Installing Velocis Server Software

3.1 Overview of the Velocis Installation and Setup Process ......................................... 3-1
3.2 Installing the Server Software on Windows.............................................................. 3-2
3.2.1 Preparing for Installation .................................................................................... 3-2
Additional Preparations for a Windows NT 4.0/2000 Platform ............................ 3-2
3.2.2 Installing the Server Software ............................................................................ 3-2
3.2.2.1 The Velocis Setup Program........................................................................ 3-2
3.2.2.2 Running the Setup Program ...................................................................... 3-3
3.2.2.3 Entering Setup Information and Options ................................................ 3-4
3.2.3 Checking the Directory Structure ...................................................................... 3-5
Checking Windows Directories .................................................................................. 3-5
3.2.4 Configuring the Server Environment................................................................ 3-6
Configuring the Windows Environment................................................................... 3-6
3.3 Installing the Server Software on UNIX and UNIX-like Operating Systems .... 3-7
3.3.2 Installing the Server Software ............................................................................ 3-8
3.3.3 Checking the Directory Structure ...................................................................... 3-8
3.3.4 Configuring a UNIX Server Environment ........................................................ 3-9
Chapter 4 Installing Velocis Client Software

4.1 Installing the Client Software on Windows .............................................................. 4-1
Additional Preparations for a Windows NT 4.0/2000 Platform ............................ 4-1
4.1.2 Installing the Client Software ............................................................................. 4-2
4.1.2.1 The Velocis Setup Program........................................................................ 4-2
4.1.2.2 Running the Setup Program ...................................................................... 4-2
4.1.2.3 Entering Setup Information and Options ................................................ 4-3
4.1.3 Configuring the Client Environment ................................................................ 4-5
Configuring the Windows Client Environment ....................................................... 4-5
4.2 Installing the Client Software on UNIX and UNIX-like Operating Systems ........ 4-5
4.2.2 Installing the Client Software ............................................................................. 4-6
4.2.3 Configuring a UNIX Client Environment......................................................... 4-7
ii Centura Velocis Installation/Administration Guide

Chapter 5 Running Velocis
5.1 Server Startup Procedures........................................................................................... 5-1
5.1.1 Starting the Server on Windows 95/98 ............................................................. 5-1
5.1.1.1 Starting the Server Manually..................................................................... 5-2
5.1.1.2 Starting the Server as a Service ................................................................. 5-3
5.1.2 Starting the Server on Windows NT 4.0/2000 ................................................. 5-3
5.1.2.1 Starting the Server Manually..................................................................... 5-3
5.1.2.2 Starting from the Service Control Manager............................................. 5-4
5.1.3 Starting the Server on UNIX............................................................................... 5-5
5.2 System Administration Utilities ................................................................................. 5-5
5.2.1 The Velocis Administrator Utility ..................................................................... 5-6
5.2.1.1 Opening Velocis Administrator ................................................................ 5-6
5.2.1.2 Logging Into a Server ................................................................................. 5-7
5.2.1.3 Managing Your System with Velocis Administrator ............................. 5-8
5.2.1.4 Logging Out of a Server ............................................................................. 5-9
5.2.1.5 Closing Velocis Administrator .................................................................. 5-9
5.2.2 The rdsadm Utility............................................................................................... 5-9
5.2.2.1 Opening rdsadm and Logging Into a Server........................................... 5-9
5.2.2.2 Managing a Database System with rdsadm .......................................... 5-10
5.2.3 The vping Utility................................................................................................ 5-11
5.3 Testing Procedures ..................................................................................................... 5-11
5.4 Server Shutdown Procedures ................................................................................... 5-13
5.4.1 Shutting Down a Server Using Velocis Administrator ................................. 5-13
5.4.2 Shutting Down a Server Using the rdsadm Utility ....................................... 5-13
5.4.3 Shutting Down a Server on Windows 95/98 or NT 4.0/2000 ...................... 5-14
5.4.3.1 Shutting Down Manually......................................................................... 5-14
5.4.3.2 Shutting Down from the Service Control Manager (Windows NT
4.0/2000 Only) ............................................................................................................ 5-14
5.4.4 Shutting Down a Server on UNIX ................................................................... 5-14
Chapter 6 Server Configuration

6.1 Adjusting Server Parameters ...................................................................................... 6-2
6.1.1 Optimizing Server Parameter Values................................................................ 6-2
6.1.1.1 General Suggestions ................................................................................... 6-2
6.1.1.2 Using Velocis Administrator to Change a Parameter Value ................. 6-2
6.1.1.3 Using rdsadm to Change a Parameter Value .......................................... 6-4
6.1.1.4 Recommended Changes to Parameter Values ........................................ 6-5
6.1.2 Licensing the Velocis Server............................................................................... 6-7
6.1.2.1 Using Velocis Administrator to License the Velocis Server .................. 6-7
6.1.2.2 Using rdsadm to Upgrade the Licensed Number of Users ................... 6-8
6.2 Copying System Catalogs............................................................................................ 6-9
6.3 Configuring and Managing Database Devices ......................................................... 6-9
Contents iii
6.3.1 Registering a Database Device ......................................................................... 6-10
6.3.1.1 Using Velocis Administrator to Register a Database Device .............. 6-11
6.3.1.2 Using rdsadm to Register a Database Device........................................ 6-12
6.3.2 Changing a Database Device ............................................................................ 6-13
6.3.2.1 Using Velocis Administrator to Change a Database Device ............... 6-13
6.3.2.2 Using rdsadm to Change a Database Device ........................................ 6-13
6.3.3 Deleting a Database Device .............................................................................. 6-14
6.3.3.1 Using Velocis Administrator to Delete a Database Device.................. 6-14
6.3.3.2 Using rdsadm to Delete a Database Device........................................... 6-15
6.4 Configuring and Managing Databases .................................................................... 6-15
6.4.1 Registering a Database ...................................................................................... 6-15
6.4.1.1 Using Velocis Administrator to Register a Database ........................... 6-16
6.4.1.2 Using rdsadm to Register a Database..................................................... 6-18
6.4.2 Initializing a Database ....................................................................................... 6-19
6.4.2.1 Using Velocis Administrator to Initialize a Database .......................... 6-19
6.4.2.2 Using rdsadm to Initialize a Database.................................................... 6-19
6.4.3 Changing a Database ......................................................................................... 6-19
6.4.3.1 Using Velocis Administrator to Change the Location of a Database . 6-20
6.4.3.2 Using Velocis Administrator to Change Global Database Access...... 6-20
6.4.4 Deleting a Database Definition......................................................................... 6-20
6.5 Configuring and Managing Database Users........................................................... 6-21
6.5.1 Controlling User Permissions........................................................................... 6-21
6.5.1.1 Access Levels ............................................................................................. 6-21
6.5.1.2 Permissions ................................................................................................ 6-22
6.5.1.3 Preloaded Examples ................................................................................. 6-23
6.5.1.4 Case in Database User Accounts............................................................. 6-23
6.5.2 Managing User Accounts.................................................................................. 6-23
6.5.2.1 Registering a Database User .................................................................... 6-24
6.5.2.2 Modifying a User Account....................................................................... 6-26
6.5.2.3 Deleting a User Account .......................................................................... 6-27
6.5.3 Managing Database Access .............................................................................. 6-27
6.5.3.1 Setting Up Database Access and Permissions ....................................... 6-27
6.5.3.2 Changing a User’s Database Permissions .............................................. 6-28
6.5.3.3 Removing Database Access ..................................................................... 6-29
6.5.4 Setting Up Velocis SQL Database Access Privileges ..................................... 6-29
6.5.4.1 Using rsql to Set Up Access Privileges to a Velocis SQL Database .... 6-30
6.5.4.2 Using the grant Statement to Assign Database Access Privileges ...... 6-31
6.5.4.3 Using the grant Statement to Assign Command Privileges ................ 6-31
6.5.5 Revoking Velocis SQL Database Access Privileges ....................................... 6-31
6.5.5.1 Using rsql to Delete Access Privileges ................................................... 6-32
6.5.5.2 Using the revoke Statement to Delete Database Access Privileges .... 6-32
6.5.5.3 Using the revoke Statement to Delete Command Privileges .............. 6-33
6.5.6 Setting Up a Permanent Administrator Account........................................... 6-33
iv Centura Velocis Installation/Administration Guide

6.6 Configuring and Managing Server Extension Modules........................................ 6-34
6.6.1 Installing an Extension Module ....................................................................... 6-34
6.6.2 Updating an Extension Module ....................................................................... 6-35
6.6.3 Deleting an Extension Module ......................................................................... 6-35
Chapter 7 Velocis Maintenance

7.1 Checking for Database Corruption ............................................................................ 7-1
7.2 Backing Up the Server ................................................................................................. 7-1
7.2.1 Selecting Files to Back Up ................................................................................... 7-2
7.2.2 Using Velocis Administrator to Back Up the Server ....................................... 7-2
7.2.3 Using rdsadm to Back Up the Server ................................................................ 7-3
7.3 Recovering the Server .................................................................................................. 7-3
7.3.1 Restoring Database Files ..................................................................................... 7-4
7.3.2 Performing Roll Forward Recovery................................................................... 7-4
7.4 Troubleshooting and Corrective Maintenance ......................................................... 7-5
7.4.1 Responding to Server Messages......................................................................... 7-5
7.4.1.1 Handling Informational Text Messages ................................................... 7-6
7.4.1.2 Handling Diagnostic Error Messages....................................................... 7-6
7.4.2 Diagnosing Problems........................................................................................... 7-6
7.4.3 Correcting Velocis Faults .................................................................................. 7-10
7.4.3.1 Verifying that the Utility Can Run (Windows 95/98,
Windows NT 4.0/2000) ............................................................................... 7-10
7.4.3.2 Correcting an ODBC Data Source Connect Error ................................. 7-10
7.4.3.3 Verifying the System Catalog Path ......................................................... 7-10
7.4.3.4 Correcting a UNIX Dynamic Library Path Variable............................. 7-11
7.4.3.5 Preparing an Extension Module for Loading ........................................ 7-12
7.4.3.6 Preparing a UDP for Loading.................................................................. 7-12
7.4.3.7 Preparing a UDF for Registration ........................................................... 7-12
7.4.3.8 Checking Client-Server Communications ............................................. 7-12
7.4.3.9 Changing Access for a Windows NT 4.0/2000 Service........................ 7-13
7.4.3.10 Setting Up a Database Device.................................................................. 7-13
Contents v
Appendix A velocis.ini File Parameters
A.1 Velocis Server Parameters ..........................................................................................A-1
A.2 Changing a velocis.ini File Parameter.......................................................................A-1
A.3 [Server] Section Parameters .......................................................................................A-2
A.4 [Engine] Section Parameters ......................................................................................A-3
A.5 [SQL] Section Parameters ...........................................................................................A-8
A.6 [Environment] Section Parameters............................................................................A-9
A.7 BLOB Data Logging .................................................................................................. A-10
Appendix B connect.ini File Parameters

B.1 Velocis Transport Protocol Parameters .....................................................................B-1
B.2 Changing a connect.ini File Parameter ......................................................................B-1
B.2 Section types..................................................................................................................B-1
B.2.1 Aliases ...................................................................................................................B-2
vi Centura Velocis Installation/Administration Guide

Tables
Table 1-1. Document Notational Conventions .................................................................... 1-2
Table 2-1. Supported Transport Protocols ........................................................................... 2-2
Table 2-2. Velocis Server Platform Section Reference ........................................................ 2-3
Table 2-3. Velocis Client Platform Section Reference......................................................... 2-8
Table 3-1. Server Setup Information..................................................................................... 3-4
Table 3-1. Server Setup Information (continued) ................................................................. 3-5
Table 3-2. Directories for a Windows Server....................................................................... 3-6
Table 3-3. Directories for a UNIX Server ............................................................................. 3-9
Table 3-4. Executing the rdshome Server Script on Different Shells.............................. 3-10
Table 4-1. Client Setup Information for Windows.............................................................. 4-3
Table 4-1. Client Setup Information for Windows (continued) .......................................... 4-4
Table 4-2. Execution of the rdshome Client Script on Different Shells ............................ 4-7
Table 5-1. Service Control Manager Startup Options......................................................... 5-4
Table 6-1. Configuration Order Section Reference ............................................................. 6-1
Table 6-2. Update VELOCIS.INI File Dialog Box Elements .............................................. 6-3
Table 6-3. Recommended Optimizations............................................................................. 6-5
Table 6-4. Velocis Database Devices ..................................................................................... 6-9
Table 6-5. Server Object Section Reference ........................................................................ 6-14
Table 6-6. User Permissions Configuration Section Reference ....................................... 6-21
Table 6-7. Database Permission Types ............................................................................... 6-22
Table 6-8. Access Permissions ............................................................................................. 6-22
Table 6-9. Initial Velocis Users ............................................................................................ 6-23
Table 7-1. Fault Isolation for Velocis .................................................................................... 7-7
Table 7-1. Fault Isolation for Velocis (continued) ................................................................. 7-8
Table 7-1. Fault Isolation for Velocis (continued) ................................................................. 7-9
Table A-1. velocis.ini File Parameter Reference.................................................................A-1
Table A-2. [Server] Section Parameters...............................................................................A-2
Table A-3. [Engine] Section Parameters..............................................................................A-3
Table A-4. [SQL] Section Parameters ..................................................................................A-8
Table A-5. [Environment] Section Parameters ................................................................. A-10
Table A-6. LogBlob Configuration Settings...................................................................... A-10
Table B-1. Alias Parameters ...................................................................................................B-2
Table B-2. Configuration Section Parameters......................................................................B-3
Contents vii
Figures
Figure 5-1. Velocis Administrator at Startup....................................................................... 5-7
Figure 5-2. Velocis Administrator Toolbar Buttons............................................................ 5-9
Figure 5-3. rdsadm Opening Menu .................................................................................... 5-10
Figure 6-1. Update VELOCIS.INI File Dialog Box.............................................................. 6-3
Figure 6-2. Database Devices View..................................................................................... 6-11
Figure 6-3. Databases View.................................................................................................. 6-16
Figure 6-4. Install Database Dialog Box ............................................................................. 6-17
Figure 6-5. Accounts View................................................................................................... 6-24
Figure 6-6. New User Accounts Dialog Box ...................................................................... 6-25
Figure 6-7. New Database Access Dialog Box................................................................... 6-28
Figure 6-8. Extensions View ................................................................................................ 6-34
viii Centura Velocis Installation/Administration Guide

Chapter 1
Introduction
The Velocis Installation/Administration Guide provides information and instructions about
installing and configuring your Velocis Database Server client-server database
management system. It is intended for system administrators and also provides
information about managing and maintaining a Velocis database system.
1.1 Velocis Documentation

Velocis documentation is a four-manual set and includes this Installation/Administration
Guide, the Velocis User’s Guide, Velocis Reference Manual and the Language Guide.
1.1.1 About This Manual

The Installation/Administration Guide is organized as described below. Related Velocis
documents are discussed in section 1.1.2.
Chapter 2 provides detailed information about the various Velocis platforms for both
standalone and networked configurations.
Since Velocis is a client-server system, you must install the server software on the server
platform and the client software on each workstation that will connect to the server.
Chapter 3 provides instructions for installing Velocis server software, and Chapter 4
provides instructions for installing Velocis client software. Chapter 5 provides
instructions for running a Velocis database system, including procedures for starting and
stopping a server, testing the hardware and software in your system, logging into and out
of a server, and using the Velocis system administration utilities.
When you have installed and tested Velocis on your system, you must configure the
system for your users. Chapter 6 provides instructions for configuring your Velocis
database system, which includes adjusting the server software’s parameters to obtain the
best performance for your system, registering your database devices with the server,
registering the databases with the server, setting up user accounts for your users, and
registering any extension modules with the server.
Chapter 7 provides information about managing and maintaining your Velocis database
system, including instructions for backing up your server, recovering the server after a
failure, checking for database corruption, monitoring server use, and resolving system
problems. Appendix A provides information about the parameters of the velocis.ini file.
Introduction 1-1
Finally, Appendix B provides the directory structure of the files on the Velocis installation
disk.
Before attempting to install the Velocis software, be sure to read Chapter 2. We also
recommend that you read the first three chapters of the Velocis Database Server User’s
Guide for a descriptive overview of Velocis.
1.1.2 Related Velocis Documents

Velocis User’s Guide provides a detailed description of Velocis and in-depth instructions
for the application developer.
Velocis Reference Manual provides developer-level details of Velocis utilities, application
programming interface (API) functions, complex data types, and return codes.
Velocis Language Guide provides language specifics for the Database Definition Language
(DDL), which is used with the Velocis Core API. Additionally the manual furnishes a
complete statement and function reference for Velocis SQL.
Note: The trademarked name of this product is Velocis Database Server. However, for
ease of reference within the manuals, the simpler form of Velocis is used.
Velocis system components are furnished on a CD. The CD includes a readme.txt file
that contains the release notes for your particular operating environment. Be sure to read
this file carefully. It provides detailed information about:
• Recent changes to the system that are not documented in the current manuals.
• Issues specific to your particular operating system or compiler.
1.1.3 Document Conventions

Table 1-1 describes the notational conventions used in this guide.
Table 1-1. Document Notational Conventions
Convention Description
Bold Text Indicates the names of functions, commands, data
structures, statements, databases, utilities, files, etc.
Note that the case distinctions used in the names are
not significant for all operating systems.
Italic Text Represents the names of variables, such as parameters
and command options. Additionally, the Velocis
documents use italics for the names of books.
1-2 Centura Velocis Installation/Administration Guide

Table 1-1. Document Notational Conventions (continued)
Courier Text Indicates a programming example or a command line
entry. Programming examples in this book are
enclosed in boxes.
Brackets ([ ]) Indicate optional fields or parameters in command
lines and syntax statements.
Bar Symbol (|) Separates alternative selections. You should enter one
of the items separated by the bar.
Ellipsis (...) Indicates that you can repeat the preceding item. Both
horizontal and vertical ellipses are used in
programming examples to indicate code that has been
omitted.
Arrow Symbols (< >) Indicate information that you must supply. For
example, <filename>.h represents a header file that
you name. Arrow symbols are also used in text to set
off keyboard key names.
1.2 Other Helpful Resources

Centura offers various options for additional information on Velocis.
• Centura Books Online
The Centura Velocis document set is available online. This document collection
lets you perform full-text indexed searches across the product document set,
navigate the table of contents using the expandable/collapsible browser, or print
any chapter. Access the collection by going to the CD, navigating to the Book Set
folder, and opening the PDF file listed in that directory.
• Worldwide Web
The Centura Worldwide Web home page is located at http://www.centurasoft.com.
The Centura web server provides access to a wealth of information about Centura
products and services.
Introduction 1-3
Chapter 2
About the Velocis Environment
This chapter describes environment and network details for the different platforms
supported by the Velocis Database Server. Section 2.1 provides basic information about
each of the network transports that Velocis can use. Section 2.2 describes the platforms
that support standalone versions of Velocis. Section 2.3 provides detailed operating
system and network transport information about each platform that can host a Velocis
server. Section 2.4 gives similar operating system and network transport details about the
client platforms that can host Velocis.
Note: The underlying architectures of the Velocis platforms do not support running more
than one copy of Velocis (either server or standalone Velocis configurations) at the same
time on the same system catalog or database files. However, the environments can
support more than one server, provided that each has a unique name and interacts with
separate system catalog and database files.
We suggest that you read the particular information in this chapter that concerns the
platforms on which you want to install and administer Velocis. Then proceed to Chapter
3 for standalone Velocis or Velocis server installation instructions, including procedures
for post-installation environment configuration. Chapter 4 presents the same type of
information, but for Velocis client platforms.
2.1 Transport Protocols Supported by Velocis

Velocis implements the multi-protocol network communication processor (MNCP) to
facilitate communication between a client process and the server. MNCP allows multiple
transport protocols to be used concurrently by the client process and by the server.
A server can maintain concurrent open sessions with different client processes that use
different transport protocols. Conversely, a client process can open sessions to more than
one Velocis server using different transports. For example, a server can communicate
with remote clients using the more expensive Transmission Control Protocol/Internet
Protocol (TCP/IP) transports, while using the lightweight local transport to communicate
with the clients running on the same machine.
Table 2-1 shows which transport protocols are supported by the Velocis MNCP on
particular server and client platforms. Locate the cell showing the intersection of your
server and client platforms, and make sure that the network transport that you intend to
use is listed. Then read the appropriate transport-specific sections for the server platform
(section 2.3) and the client platform (section 2.4) for details, before you install Velocis.
About the Velocis Environment 2-1

Table 2-1. Supported Transport Protocols
Server Windows 95/98 Windows NT 4.0 Windows NT 2000 UNIX
Client
Windows 95/98 TCP/IP TCP/IP TCP/IP TCP/IP
Local transport* Named Pipes Named Pipes
Windows NT 4.0 TCP/IP TCP/IP TCP/IP TCP/IP

Named Pipes Named Pipes
Local transport*
Windows NT 2000 TCP/IP TCP/IP TCP/IP TCP/IP

Named Pipes Named Pipes
Local transport*
UNIX TCP/IP TCP/IP TCP/IP TCP/IP
UNIX domain sockets
Local NCP**
* Does not use network services.

** Only available on some UNIX platforms.
The local transport does not use network services; it provides a lightweight
communication facility for use in standalone Velocis installations. This special transport
is marked in Table 2-1 with an asterisk and is described in section 2.2.
2.2 Standalone Velocis Platforms

The term standalone refers to a Velocis client/server configuration where the client and
server processes run in the same memory space. This architecture uses lightweight
transport mechanisms that do not use network services.
2.2.1 Windows 95/98 and Windows NT 4.0

Standalone Velocis (32-bit) on Windows 95/98 and Windows NT 4.0 uses a lightweight
local transport protocol. To implement this transport, the NCP module uses memory-
mapped files. The hardware platforms require at least 12 MB of memory. Velocis
requires at least 5 MB of free disk space in addition to the disk space required by the
Velocis databases.
The local transport allows client applications to run as separate processes on the same
Windows 95/98/NT 4.0 and 2000 machine as the Velocis server without connection to a
network. Note that the local transport does not support name services. The client
process can only connect to the Velocis server by specifying the server name explicitly.

More than one server can run on the same machine as long as each server has a unique
name and uses a separate system catalog.
When using ODBC clients, use the ODBC administrator utility to configure Velocis data
sources. The utility provides configuration options that allow you to name the server and
to specify how Velocis is to interpret database names. The default server name is the
same as the data source name. However, a given server can be used with different data
sources. You can add as many data source names and servers as you like.
Most ODBC applications operate best with Velocis when database names are interpreted
as owners. However, earlier versions of Velocis only return database names as qualifiers.
This has caused problems with some ODBC tools (for example, Microsoft Access).
2.3 Velocis Server Platforms

This section provides details, including network transport information, about each of the
operating system platforms on which a Velocis server can run. For information about a
particular network transport, refer to the section of this chapter shown in Table 2-2 below.
Table 2-2. Velocis Server Platform Section Reference
Operating System Platform Network Transport Section

Windows 95/98 All 2.3.2.1
Windows 95/98 TCP/IP 2.3.2.2
Windows 95/98 Local 2.3.2.3
Windows NT 4.0/2000 All 2.3.3.1
Windows NT 4.0/2000 Named Pipes 2.3.3.2
Windows NT 4.0/2000 TCP/IP 2.3.3.3
Windows NT 4.0/2000 Local 2.3.3.4
UNIX All 2.3.5.1
UNIX TCP/IP 2.3.5.2
UNIX UNIX domain sockets (UD) 2.3.5.3
UNIX (Solaris, UnixWare only) Local 2.3.5.4
2.3.1 Configuring Server Transports

The velocis.ini file contains a separate section for each transport supported on the
platform. If any configuration parameters are missing, the default values are used.
The following sections can be defined:

[TCP Configuration] All servers
[Named Pipes Configuration] Windows NT servers only
[Local Configuration] Windows 95/98/NT/2000 & some UNIX platforms
[UD Configuration] UNIX
The following parameters are used to configure different transports in the velocis.ini file:
Enabled=yes_no
Indicates whether or not the particular transport will be turned on. The value of this
parameter can be yes (the default) or no. Thus, if the configuration section is missing
from the velocis.ini file for a transport, it is enabled. If the transport is turned off,
any attempt to connect to this server from the client applications using this particular
transport will fail. This effectively disables all aliases defined in any connect.ini file
on the client machines that are bound to this server and the transport.
Port=number
Specifies the TCP/IP port number to which the server is bound. You can use this
parameter for configuring the [TCP Configuration] section.
PacketSize=size
Defines the packet size the server uses with the specific protocol. The default packet
size is 4096. This setting can be used for the [TCP Configuration] and [UD
Configuration] sections.
Required=yes_no
Indicates whether this transport must initialize and start correctly for the server to
continue. If the transport cannot initialize and this flag is yes, the server will shut
down. If the transport cannot initialize and this flag is no, the server will continue to
initialize if at least one transport has been initialized correctly. The default for all
transports is yes.
Temp=path
Specifies the path for temporary files used in connections for the UD transport and
for the local transport. This parameter is only available on UNIX. The default path is
/tmp.
2.3.2 Windows 95/98 Server Platform
2.3.2.1 Windows 95/98 Platform Requirements

A Windows 95/98 platform can host a Velocis server. Supported network transports on
Windows 95/98 are TCP/IP and local transport. The server machine requires at least 12
MB of memory. Velocis needs at least 5 MB of free disk space in addition to the disk
space required by the Velocis databases.

2.3.2.2 TCP/IP Transport for Windows 95/98
To use this transport, you must identify a particular port number to which the server will
be bound for TCP/IP connections with the remote clients. This number must be specified
in the [TCP Configuration] section of the velocis.ini file. To support earlier Velocis
versions, Velocis will do a lookup in the services file if the port is not specified in the
velocis.ini file. The services file is located in the Windows 95/98 root directory.
2.3.2.3 Local Transport for Windows 95/98

The local transport is a lightweight communication mechanism, based on shared memory,
that does not use network services. Of all transports supported by Velocis, it has the
lowest overhead and is the natural choice for connections from local clients. It is the only
transport available in the standalone version of Velocis for Windows 95/98. See section
2.2.1.
2.3.3 Windows NT 4.0 Server Platform
2.3.3.1 Windows NT 4.0/2000 Platform Requirements

To run a Velocis server on Windows NT 4.0/2000 requires at least 16 MB of memory.
Velocis requires at least 5 MB of free disk space in addition to the disk space required by
the Velocis databases. Available network transports include the following: Named
Pipes, TCP/IP, and local transport. For compilers supported on Windows NT 4.0/2000,
see Chapter 13 of the Velocis User’s Guide.
On Windows NT 4.0/2000, you can run Velocis either from a command prompt window
or through the Service Control Manager. If you use a command prompt, the server name
is not included with the network transport name services. During post-installation
environment configuration, you must set the CATPATH environment variable to point to
the system catalog files.
If you want to use the Service Control Manager, Windows NT 4.0/2000 allows Velocis to
register itself as a service that is started and stopped by the manager. Thus Velocis can
run even when no user is logged in.
Important: With the Service Control Manager, you must register Velocis as a service
either during the Velocis server setup process or by using the instrds utility as instructed
in Chapter 3. This utility places the CATPATH variable in the Windows NT 4.0/2000
Registry for you, and sets the variable to point to the system catalog files. Velocis also
stores other pieces of configuration information in the Registry, including the name by
which the Velocis server is known in the NT domain (limited to eight characters). For
more information on Windows NT 4.0/2000 servers and domain controllers, see your
Windows NT 4.0/2000 system administration manuals.

2.3.3.2 NT Named Pipes Transport
A Velocis server running on a Windows NT 4.0/2000 platform can use NT Named Pipes
as a network transport.
Each Named Pipe is composed of the host-computer node name and the Velocis server
name. For example, if the Windows NT 4.0/2000 Named Pipes node name of the host
computer is "ntas" and the Velocis server name is "velocis", the Named Pipe is
\\ntas\pipe\velocis.
There is nothing special to do on Windows NT 4.0 to support name services.
2.3.3.3 TCP/IP Transport for Windows NT 4.0/2000

To use this transport, you have to identify a particular port number to which the server
will be bound for TCP/IP connections with the remote clients. This number must be
specified in the [TCP Configuration] section of the velocis.ini file. To support earlier
Velocis versions, Velocis will do a lookup in the services file if the port is not specified in
the velocis.ini file. For Windows NT 4.0, the services file is located in the
%WINDIR%\system32\drivers\etc directory.
2.3.3.4 Local Transport for Windows NT 4.0/2000

The local transport is available along with the network transports. It is used by the clients
running locally on the server machine. Of all transports supported by Velocis, local
transport has the lowest overhead and is the natural choice for connections from local
clients.
2.3.4 UNIX Server Platforms
2.3.4.1 UNIX Platform Requirements

You can run a Velocis server on the several UNIX platforms, including AIX 4.3, HP-UX
11, Intel Solaris 2.6 or higher, BSDI 4.1, Linux 6.0 kernel 2.222.9a, and UNIXWare 7
platforms. The network transports supported on these platforms are TCP/IP and UNIX
Domain Transport. For compilers supported on UNIX, see Chapter 13 of the Velocis
User’s Guide.
The default Velocis configuration is usually compatible with normal resource allocations
on most UNIX platforms. However, the requirements of other applications, minimal
configurations, and a large number of concurrent sessions can make normal resource
allocations inadequate.
Under these circumstances, Velocis might attempt to use more system resources than
your current UNIX configuration allows. In particular, the file handles and sockets
needed by Velocis vary according to limits specified in the Velocis system catalog. As a

general rule, an operating system with a large number of concurrent sessions should have
one socket available per session (or two, if client applications are running on the server
machine in a standalone configuration).
It is also possible that Velocis, or Velocis in combination with other applications, will
consume more shared memory IPC resources than are configured for your platform.
UNIX typically controls the limits for these resources by the kernel configuration. Some
limits are controlled explicitly, while others are determined by a controlling parameter
such as MaxUsersOn.
To change these limits on some older UNIX systems, you might need to recompile the
UNIX kernel after changing a configuration file. On other systems it is possible to just
change the kernel configuration file and then reboot. Refer to your UNIX system
administration manuals for specific information on the names of the relevant parameters,
how they are calculated, and how to make changes to them.
2.3.4.2 TCP/IP Transport for UNIX

To use this transport, you must identify a particular port number to which the server will
be bound for TCP/IP connections with the remote clients. This number must be specified
in the [TCP Configuration] section of the velocis.ini file. To support previous Velocis
customers, Velocis will do a lookup in the services file if the port is not specified in the
velocis.ini file. For UNIX, the services file is located in the /etc directory.
Note: If needed for setting up the Port parameter, you can use the rpcinfo utility to print
a list of active ports.
2.3.4.3 UNIX Domain Transport for UNIX

The UNIX Domain transport uses sockets similar to TCP/IP, but is limited to
communication within a single machine. Therefore, this transport is not practical to use
across a network.
There is no port to set up. Instead, a temporary file is used to initiate communication.
The TMP parameter in the [UD Configuration] section of the velocis.ini file specifies
where this temporary file will be generated.
2.3.4.4 Local Transport for UNIX

This transport is available on only some platforms (currently Intel Solaris) because those
platforms use kernel threads. The local transport uses a shared memory buffer for
communicating. This buffer, unlike Windows NT, must have a physical file associated
with it. The location of this file is controlled by the Temp parameter in the [Local
Configuration] section of the velocis.ini file.

2.4 Velocis Client Platforms
This section contains information about each of the client platforms that can run Velocis,
including network transports. For information about a particular network transport, refer
to the section of this chapter shown in Table 2-3 below.
Table 2-3. Velocis Client Platform Section Reference
Operating System Platform Network Transport Section

Windows 95/98 All 2.4.2.1
Windows 95/98 Named Pipes 2.4.2.2
Windows 95/98 TCP/IP 2.4.2.3
Windows 95/98 Local 2.4.2.4
Windows NT 4.0/2000 All 2.4.3.1
Windows NT 4.0/2000 Named Pipes 2.4.3.2
Windows NT 4.0/2000 TCP/IP 2.4.3.3
Windows NT 4.0/2000 Local 2.4.3.4
UNIX All 2.4.5.1
UNIX TCP/IP 2.4.5.2
UNIX (Intel Solaris, UnixWare 7) Local 2.4.5.3
UNIX UNIX Domain 2.4.5.4
2.4.1 Configuring Client Transports

To open a session with the server, the client program must issue the login command.
Required login parameters include connection name, user name, and password. The
connection name can be simply a server name or an alias defined in the connect.ini file.
If this file is present, it is used first to determine connection information. To find the
connect.ini file, locations are searched in the order below.
1. The directory specified by the CONNPATH environment variable.
2. The system directory (WINDIR for Windows 95/98 or Windows NT 4.0/2000 or /etc
for UNIX).
3. The directory from which the client was executed.
If the file does not exist, or if the alias is not found in the connect.ini file, Velocis uses the
connection name as the name of the server and attempts to connect using the available
transports in the following order (assuming that each protocol is available and enabled).

For Windows 95/98 or Windows NT 4.0/2000
1. Local
2. TCP/IP
3. Named Pipes
For UNIX
1. Local
2. UNIX Domain
3. TCP/IP
2.4.1.1 Defining Aliases

An alias defines a connection to a specific server using a specific transport protocol or
protocols. An alias can be defined in the connect.ini file using the following format:
[aliasname1]
Param1=<value1>
...
ParamN=<valueN>
The following parameters are used to define aliases bound to different transport
protocols:
Protocol=name
Specifies a name for the protocol. An alias section must contain this parameter. The
protocol value can be a comma-separated list of protocols that are declared in the
same order in which attempted connections are made with the protocols. Valid
values for this parameter are TCP, Named Pipes, UNIX DOMAIN, and Local.
Name=server_name
Specifies a string that represents the name of the running Velocis server. This
parameter is recommended for all aliases except those bound to TCP/IP. Instead, the
TCP/IP-bound aliases should use the combination of Host and Port to locate the
server process. For protocols other than TCP/IP, if a Name parameter is not specified,
the alias name is used as the server name.
Encryption=mode_number
Specifies the encryption mode to use for the connection. This parameter defines
secure connection. If this parameter is missing, a mode of 0 (no encryption) is used.
Note: Instead of offering encryption capabilities, Velocis supplies hooks that the
application developer can use to be certain all messages sent across the connection are
secure. In this case, the number given in the Encryption parameter in the connect.ini file
is passed to the encryption shared library. This allows different connections to use
different modes of encryption.

Host=address
Specifies the host address. This parameter is recommended for aliases using the
TCP/IP transport protocol. The address can be a name that will be looked up in the
hosts file, or it can be an IP address in the format XXX.XXX.XXX.XXX. If no Host
parameter is specified for TCP/IP, the alias name is used to search in the hosts file.
Port=number
Specifies the port number used by the server when using TCP/IP. It must be a valid
port used by a Velocis server on the host computer, with the TCP/IP address as
defined by the Host parameter. If the Host parameter is specified as an IP address,
this parameter is required. If the Host parameter is specified as a name or is not
present, the Port parameter is optional. In this case, the name used to search for the
IP address in the hosts file is also used to search in the services file for a port number.
Node=name
Specifies the node name of the computer hosting the Velocis server and is used in the
construction of the Named Pipe’s name. This parameter is used for aliases using the
Named Pipes transport. If a Node parameter is specified, a connection attempt is
made with that node and the specified server name. If no Node is specified, the
behavior of the connection attempt is determined by the value of the NamedServices
parameter in the [Named Pipe Configuration] section of the velocis.ini file. See
manual section 2.4.1.2 for details. If Named Services is on, the connection attempt
will query the network, looking for a server of the specified name. If Named Services
is off, an attempt is made to connect to a server of the specified name on the local
machine. The Node parameter can be set to "." (period) to force the connection to go
only to the local machine.
Temp=path
Specifies the directory path for temporary files. This parameter is used on UNIX for
the UNIX Domain and local transports. It should be the same as the Temp parameter
on the server side, so the client can find the server’s connection files.
The following example shows how different aliases can be defined in the connect.ini file.
[unixtestserver]
Protocol=TCP
Host=solaris.raima.com
Port=1251
Encryption=0
[misserver]
Protocol=Named Pipes
Name=MIS
Node=ACCOUNTING
Encryption=1
[localserver]
Protocol=Local
Name=RDS

The following example shows a definition of an alias that causes the client NCP to
connect to a second server if the first attempt fails. This is useful if you want to connect to
a local server. If a local server is not available, the connection should go to a remote
server. The client will try to connect to a local server named "beta" that has its temporary
files located at /centura/beta/tmp. If that attempt fails, the client will try to connect to a
server located at 198.206.247.123 using port 5001.
[unixbetaserver]
Protocol=UD,TCP
Host=198.206.247.123
Port=5001
Name=beta
Temp=/centura/beta/tmp
2.4.1.2 Defining Global Transport Parameters

For each transport available on the client machine, you can specify a number of global
parameters that apply to all the aliases using this particular transport. To define transport
parameters, a transport specific section must be added to the connect.ini file similar to
the one in the velocis.ini file. The following sections can be defined:
[Configuration] Defines parameters for all transports
[TCP Configuration]
[Named Pipe Configuration]
[Local Configuration]
[UD Configuration]
Use the following parameters to configure different transports in the connect.ini file.
Enabled=yes_no
Indicates whether or not the particular transport will be turned on. The value of the
parameter can be yes (the default) or no. Thus, if the configuration section is missing
from the connect.ini file for a transport, it is enabled. If the transport is turned off, all
the alias definitions for this transport are disabled.
PacketSize=size
Specifies the packet size used for the TCP/IP and UNIX Domain protocols. The
default packet size is 4096. It is recommended that the client side PacketSize
parameter match that of the server side.
NamedServices=on_off
Specifies whether name services is available, for the Named Pipes transport only.
The value can be on or off (the default). Turning Named Services on allows a client
to connect to a server of a known name but unknown location on the network. If this
option is enabled on large networks, the connection process can be very slow. This
parameter works on Windows NT 4.0/2000, but not on Windows 95/98.
Sessions=number
Specifies the maximum number of sessions allowed from one client application. It is

currently the only parameter for the [Configuration] section that specifies settings
global to all transports. The default number of sessions is 20. One session is
established for each s_login or SQLConnect call from every client task. Velocis
allocates its resources at startup based on this number. Too large a value causes
Velocis to waste memory, possibly preventing client applications from running. This
value is a per application variable, not a per client machine variable. If two client
applications are running on the same machine and the Sessions parameter is set to 4,
then each client has allocated resources for four connections, and together they can
have eight separate and simultaneous connections.
2.4.2 Windows 95/98 Client Platform
2.4.2.1 Windows 95/98 Platform Requirements

You can run Velocis clients on Windows 95/98. The client machine requires at least 12
MB of memory and about 5 MB of free disk space to hold client applications and
examples. Available network transports are Named Pipes, TCP/IP, and local transport.
For compilers supported on Windows 95/98, see Chapter 13 of the Velocis User’s Guide.
To access Velocis through ODBC on Windows 95/98, use the ODBC administrator utility
to configure Velocis data sources. The utility provides new configuration options that
allow you to name the server and specify how Velocis should interpret database names.
The default server name is the same as the data source name. However, a given server
can be used with different data sources. You can add as many data source names and
servers as you like.
Note that this causes problems with some ODBC tools (for example, Microsoft Access).
2.4.2.2 Named Pipes Transport for Windows 95/98

Velocis clients use this transport to connect to a Velocis server running on Windows NT
4.0. Named Pipes on Windows 95/98 cannot use Named Services.
2.4.2.3 TCP/IP Transport for Windows 95/98

A Velocis client can use this transport to connect to a Velocis server running Windows
NT 4.0, Windows 95/98, or any UNIX platform. We recommend that the client define
connection aliases in the connect.ini file. For compatibility with previous versions of
Velocis, the IP address and port number can be looked up in the hosts and services files.

2.4.2.4 Local Transport for Windows 95/98
Velocis clients running on the Windows 95/98 machine can connect to a locally running
Velocis server using the lightweight local transport. It is implemented using the shared
memory and does not require network services. This is the only transport available in
standalone Velocis for Windows 95/98.
2.4.3 Windows NT 4.0/2000 Client Platform
2.4.3.1 Windows NT 4.0/2000 Platform Requirements

You can run Velocis clients on Windows NT 4.0/2000. The transports supported by
Velocis on Windows NT 4.0/2000 include Named Pipes, TCP/IP, and local transport. For
compilers supported on Windows NT 4.0/2000, see Chapter 13 of the Velocis User’s Guide.
To access Velocis through ODBC on Windows NT 4.0/2000, use the ODBC administrator
utility to configure Velocis data sources. The utility provides new configuration options
that allow you to name the server and specify how Velocis should interpret database
names. The default server name is the same as the data source name. However, a given
server can be used with different data sources. You can add as many data source names
and servers as you like.
Note that this causes problems with some ODBC tools (for example, Microsoft Access).
2.4.3.2 Named Pipes Transport for Windows NT 4.0/2000

Using Named Pipes, a Velocis client can connect to a server running on Windows NT
4.0/2000 platforms only.
2.4.3.3 TCP/IP Transport for Windows NT 4.0/2000

A Velocis client can use this transport to connect to a Velocis server running Windows
NT 4.0/2000, Windows 95/98, or any UNIX platform. We recommend that the client
define connection aliases in the connect.ini file. For compatibility with previous versions
of Velocis, the IP address and port number can be looked up in the hosts and services
files.
2.4.3.4 Local Transport for Windows NT 4.0/2000

Velocis clients running locally on the server machine can connect to a server using the
lightweight local transport. It is implemented using shared memory and does not require
network services. This is the only transport available in standalone Velocis for Windows
NT 4.0/2000.

2.4.4 UNIX Client Platform
2.4.4.1 UNIX Platform Requirements

You can run Velocis client software on the several UNIX platforms, including AIX 4.3,
HP-UX 11, Intel Solaris, BSDI 4.1, Linux 6.0 kernel 2.222.9a, and UNIXWare 7 platforms.
The network transports supported on these platforms are TCP/IP, local transport and
UNIX Domain Transport. For compilers supported on UNIX, see Chapter 13 of the
Velocis User’s Guide.
Velocis may attempt to use more system resources than your UNIX configuration allows.
In particular, the file handles and sockets needed by Velocis vary according to system
catalog limits. Try to keep the catalog limits low, or configure your UNIX system to
handle resources requested by Velocis when catalog limits are set higher. To
accommodate a large number of logins, configure the system with one socket per login, or
two sockets if the client is running on the same computer as the server. For configuration
details, see Chapter 4.
2.4.4.2 TCP/IP Transport for UNIX

This is a natural transport for a Velocis UNIX client. The client can use it to connect to a
server running on any platform. When using this transport, we recommend that you
specify the Host and Port parameters in the alias definition in the connect.ini file. (See
section 2.4.1.1.) For compatibility with previous versions of Velocis, the IP address and
port number can be looked up in the hosts and services files.
2.4.4.3 Local Transport for UNIX

Velocis clients on Intel Solaris should use this transport when running locally on the
server machine. Since this transport is implemented using a shared memory buffer and
does not require network services, it is very efficient.
2.4.4.4 UNIX Domain Sockets Transport for UNIX

As an alternative to the local transport, all UNIX Velocis clients can use UNIX domain
sockets to connect to a server that runs locally on the same UNIX server or workstation.
As local transport usually offers better performance than domain sockets, it is most
practical to use this transport on the platforms that do not support kernel threads.

Chapter 3
Installing Velocis Server Software
This chapter covers the installation and configuration of the server software for a Velocis
standalone or networked database system. It is divided into four sections. Section 3.1
provides an overview of the entire process of installing and setting up a Velocis system
and directs you to the chapters in this manual that deal with subsequent steps in that
process.
Section 3.2 provides information about installing and configuring a server on the
Windows 95/98, Windows NT 4.0, and Windows NT 2000 platforms (collectively referred
to as Windows platforms). Section 3.3 provides information about installing and
configuring a server on UNIX platforms.
3.1 Overview of the Velocis Installation and Setup Process

The process of installing and setting up a Velocis database system includes the following
steps:
• Installing the server software on the server computer and configuring the
computer’s operating environment for server operation. This step is covered in
this chapter.
If you install the standalone version of Velocis, the setup program installs both the
server and client software at the same time.
• Installing the client software on a client computer and configuring a client
computer’s operating environment for client operation. This step is covered in
Chapter 4.
If you install the standalone version of Velocis, you should skip this step.
• Starting the server, logging into it, and testing to make sure that the installation
was successful. This step is covered in Chapter 5.
• Configuring the server’s operating parameters and creating and registering the
components that make up your system, including database devices, databases, user
accounts, and extension modules. (A Velocis database device is not a physical disk
drive or device. It is a logical name for a directory in which Velocis stores files.)
This step is covered in Chapter 6.
If you have trouble installing or running Velocis, consult Chapter 7, "Velocis
Maintenance," which includes information about troubleshooting and diagnosing
problems.
Installing Velocis Server Software 3-1

3.2 Installing the Server Software on Windows
This section provides information about preparing for installation, installing the Velocis
server software as either a standalone or a networked server, and checking the directory
structure for all Velocis platforms except UNIX (i.e., Windows 95/98, Windows NT 4.0,
and Windows 2000).
3.2.1 Preparing for Installation

Before installing the Velocis server software as either a standalone or network server on a
Windows platform, you need the following:
• The Velocis installation CD-ROM.
• Familiarity with the platform on which you are installing the server software. For
information about a platform, see the appropriate section in Chapter 2.
If you are installing the server software on a Windows NT 4.0/2000, also read the
appropriate section below for more information.
Additional Preparations for a Windows NT 4.0/2000 Platform

Log into the workstation with administrator access. The Velocis installation for Windows
NT 4.0 requires changes in the Windows NT 4.0 Registry, for which you need
administrator-level privileges.
If you are installing the Velocis server software on a computer that already has a Velocis
server installed, you cannot install the new server in the same folder as the current server.
The setup program will display an Additional Installation Options dialog box that offers
you the choice of installing the new server in a different folder or letting the setup
program remove the current server and install the new one in its place. This dialog box
will appear after Step 7 of the setup procedure described in section 3.2.2.2.
3.2.2 Installing the Server Software

To install the Velocis server software, you run a setup program that asks you to supply
information and to choose where and how you want Velocis installed on your computer.
3.2.2.1 The Velocis Setup Program

The Velocis setup program consists of a series of screens containing instructions and
displaying boxes or option buttons for entering your responses.
Each screen also includes Next, Back, and Cancel buttons. To enter your response to a
screen and then go on to the next screen, click Next. To return to the previous screen,
click Back. To stop installing Velocis and exit the setup program, click Cancel.

3.2.2.2 Running the Setup Program
To run the setup program:

1. Insert the Velocis installation CD-ROM into the appropriate drive.
2. Open the Run dialog box and click Browse.
The Browse dialog box appears.
3. Use the Browse dialog box to display the folders on the installation CD-ROM. If you
need instructions for using the Browse dialog box, consult Windows Help.
• Locate and open the Server folder for the appropriate Windows platform.
Select the Setup.exe file and click Open.
or,
• If you are installing a standalone system, open the Standalone folder, select the
setup.exe file, and click Open.
The Browse dialog box closes and the path you selected appears in the Run dialog
box. (For example, the path could be D:\Velocis30\nt\server\Setup.exe for a
Windows NT 4.0/2000 server.)
4. Click OK.
The Velocis Database Server logo window appears, and then the Setup message box
opens to tell you that the InstallShield Wizard will guide you through the setup
process.
5. When the Welcome to Velocis screen appears, read the information on the screen. If
you want leave the setup program, click Cancel. To continue installing Velocis, click
Next.
The Software License Agreement appears.
6. Read the Software License Agreement. If you do not accept the terms of the
agreement, click No and quit the Velocis setup program. If you accept the terms of
the license agreement, click Yes.
The Choose Destination Location screen appears.
7. On the Choose Destination Location and succeeding screens, read the instructions,
make the appropriate response, and then click Next. Enter the requested
information on each screen until you reach the About to Install screen. For more
information about responding to these screens, see section 3.2.2.3.
Note: If you are installing a server on a Windows NT 4.0/2000 platform and a server
has already been installed on the computer, see section 3.2.1.1 for further
information.
8. The About to Install screen lists the information and choices you have entered on the
preceding screens. Review this list and, if you wish to change anything, click Back

until you reach the appropriate screen for entering the change. When you have
changed the information, click Next. Return to the About to Install screen.
9. When you are satisfied with the options listed on the About to Install screen, click
Next.
The setup program then copies the Velocis server software into the folder you
specified on the Choose Destination Location screen (see section 3.2.2.3).
You can stop the copying process, if necessary, by pressing the <F3> key.
10. When the Setup Complete screen appears, you can choose whether to have the setup
program restart your computer immediately or to do it yourself later. (Restarting
your computer makes the setup program’s change to your autoexec.bat file
effective.)
To exit the setup program, click Finish.
3.2.2.3 Entering Setup Information and Options

Table 3-1 provides information about responding to the setup program screens.
Table 3-1. Server Setup Information
Screen Request Response

Choose Destination Location
Destination Folder Unless you specify otherwise, the setup program
creates a folder named \Centura\Velocis Server
and installs the server software in that folder.
Browse If you want Velocis installed in a different folder,
click Browse to open the Choose Folder dialog box.
Choose Folder
Path Use the Drives and Directories lists to select the
drive and the directory where you want Velocis to
be installed. Then click OK.
Network If you want to install Velocis on an unlisted drive,
click Network to open the Map Network Drive
dialog box.
Map Network Drive If you want to install the server software on an
unlisted drive, you must specify a letter to identify
the drive and enter the path for the drive.
Drive Select a letter to identify this drive.
Path Use this format to specify the path:
\\<computername>\<foldername>

Table 3-1. Server Setup Information (continued)
Reconnect at logon Specifies whether to connect to this shared folder

every time you start Windows. Unless you use this
folder often, do not check this folder. This will
speed your Windows startup.
Compiler Options Click the compiler you will use with Velocis.
Microsoft Visual C++ 6.0 For information about compiler options, see
Borland C++ Builder 4.0 Chapter 13 of the Velocis User’s Guide.
Setup Type To choose the type of setup to install, select an
option.
Typical Installs the following components: program files,
example files, help files, catalog files, include files,
Microsoft library files, and the Server Toolkit.
Custom Clicking this option opens the Select Components
dialog box where you can choose which of the
following options to install: program files, example
files, include files, and library files.
Additional Installation Options To choose an additional option, click the option.
Run Velocis Server as a Service With Velocis installed as a service, the service starts
the server automatically when computer is booted.
Add path to Velocis DLLs to The default location is C:\Centura\Velocis\bin.
autoexec.bat (Registry on
Windows NT 4.0/2000)
3.2.3 Checking the Directory Structure

When the setup program is finished copying the Velocis server files to your computer,
check the directory structure to make sure that the installation is complete. The following
section describes the Velocis directories for Windows platforms.
Checking Windows Directories

Table 3-2 describes the folders and files in which the Velocis server software is installed
on the Windows 95/98, and Windows NT 4.0/2000 platforms.

Table 3-2. Directories for a Windows Server
Directory Description
\Centura\Velocis The home directory.
\Centura\Velocis\Bin The directory for the rdsdll server device. Contains the
Velocis server file (rds.exe) and the DLLs. Utility program
files are also found in here.
\Centura\Velocis\Catalog The directory for the catdev server device. Contains the
system catalog database files, catalog.* and syscat.*. Also
includes lockcat.fil, dbfix_t.dbd, dbimp_t.d01,
dbimp_t.dbd, dbimp_t.k01, the velocis.ini file, which
contains configuration information for Velocis, and the
change log indicator file (rdm.chi).
\Centura\Velocis\Examples Contains example databases and programs.
\Centura\Velocis\Include Contains header and import files.
\Centura\Velocis\Lib Contains Velocis library files.
\Centura\Velocis\Sqldb The directory for the sqldev server device. Contains the
preloaded example SQL databases sales and invntory.
\Centura\Velocis\Syslog The directory for the sysdev server device. Contains the
change log and checkpoint files.
3.2.4 Configuring the Server Environment

When you have installed the server software on its computer, you must adjust the
operating environment for the Velocis server to operate correctly. This section provides
information about configuring the server’s operating environment for all Velocis
platforms except UNIX (i.e., Windows 95/98, Windows NT 4.0, and Windows 2000).
Configuring the Windows Environment

Before you start the server, make sure that you have the following settings in your
environment:
• The PATH environment variable includes the directory with the Velocis program
files and DLLs (for example, C:\Centura\Velocis\Bin).
• The CATPATH environment variable is defined to point to the Velocis system
catalog directory (for example, C:\Centura\Velocis\Catalog).

3.3 Installing the Server Software on UNIX and
UNIX-like Operating Systems
This section describes how to install the Velocis server on UNIX and UNIX-like platforms.
Note that the server software tree includes both the client software and the server
software. Thus, it is possible to have a single Velocis software installation available to
clients via the network file system (NFS). This approach may be desirable for
administrative simplicity, but also has security implications and should be considered
carefully. In any case, the Velocis server should be installed on a disk that is local to the
system on which the server software runs. While the Velocis server and databases can
reside entirely on NFS volumes, the use of NFS volumes for the server software tree
(primarily because it includes the catalog and syslog devices) and any customer database
devices will severely degrade performance and may cause database consistency
problems.
Some of the installation steps or prerequisites, such as mounting the CD-ROM or the
optional creation of a new user, require root access to most or all systems. If you do not
have this level of access, seek assistance from your system administrator. Many of these
same steps require platform-specific system administration knowledge. If you are not
familiar with the required tasks, consult your system documentation or your system
administrator.

Before you begin installing the Velocis client on a supported UNIX operating system, be
sure to taake care of the following:
• Have on hand the Velocis installation CD-ROM.
• Be familiar with the platform on which you are installing the server software and
have the necessary protocols and network drivers installed. For more information,
see the appropriate section of Chapter 2, "About the Velocis Environment."
• Decide which account will own the Velocis server installation. This can be a local
or NIS account and can be an existing account such as "root" or a new one
dedicated to Velocis administration. (This decision usually depends on local
policies and conventions, as well as administrative and security considerations.)
• Create or clear the directory in which you want to install the Velocis server
software. Make sure that the directory is owned by the account selected as the
Velocis software owner, and that the permissions allow all users to read and
execute files with it (in most cases only the owner should have write permission).
• Read all the installation steps.

3.3.2 Installing the Server Software
To install the server software:
1. Mount the CD-ROM on the system on which you wish to install the Velocis server
software.
On some systems, this may be automatically done by inserting the CD-ROM in the
drive. On all other systems, it will be necessary use the mount command while
logged in as "root". Note that if the system does not have a CD-ROM drive, it is
possible to mount the CD-ROM on a system that does and mount the CD-ROM on
the client system via NFS.
2. Log into the system on which you wish to install the Velocis client software as the
user selected to be the Velocis software owner.
3. Locate the mount point for the CD-ROM on your system and the directory on the
CD-ROM that contains the installation archive for your UNIX platform. In this
directory, resides a file named <platform>.tar, where <platform> is an abbreviation
for the platform on which to install the server software.
4. Use the cd command to change to the directory that you have cleared to hold the
Velocis software tree.
5. Extract the archive as follows:
tar xvf <absolute path of selected *.tar file>
For example, if your CD-ROM mount point is /cdrom and your platform is Linux,
the command would be as follows:
tar xvf /cdrom/Linux/Server/Lnxt.tar
6. From the Velocis home directory, run the shell script named "install", by executing
the following on the command line:
sh ./install
This script sets file permissions and creates the Velocis environment script files,
rdshome.sh (for the Bourne and Korn shells) and rdshome.csh (for the C shell).
3.3.3 Checking the Directory Structure

When you have finished the installation process, check the directory structure to be
certain that the installation was done correctly. You should find the directories listed in
Table 3-3 below.

Table 3-3. Directories for a UNIX Server
Directory Description
$RDSHOME The root directory of the Velocis software installation tree.
$RDSHOME/bin Contains Velocis binaries (including utilities and the server,
rds) and shared libraries.
$RDSHOME/catalog The directory for the catdev server device. Contains the
system catalog database files, catalog.* and syscat.*. Also
includes the velocis.ini file, which specifies configuration
information for Velocis. After the server is started for the
first time, this directory will include the change log indicator
file (rdm.chi) and the backup indicator log file (rdm.bil).
$RDSHOME/examples Contains example source code and databases.
$RDSHOME/include Contains header files.
$RDSHOME/Setoolkt Contains the Server Extension Toolkit source files.
$RDSHOME/sqldb The directory for the sqldev server device. Contains the
preloaded example SQL databases, sales and invntory.
$RDSHOME/syslog The directory for the sysdev server device. Contains the
change log files and, after the server is started for the first
time, the checkpoint image file (rdm.chk).
Note: The Velocis server will also use an RDS.log file, which will be created in the
directory from which you launch the server. This file is used to store server informational
and error messages, which are also printed to the screen when Velocis is run directly
from a command line.
3.3.4 Configuring a UNIX Server Environment

Each account that might be used to run the Velocis server software needs several changes
made to its shell environment so that Velocis performs correctly. Four modifications are
required for users of the server software:
1. Define an RDSHOME environment variable whose value is the path to the Velocis
server software installation directory.
2. Define a CATPATH environment variable whose value is $RDSHOME/catalog.
3. Modify the directory search path to include the $RDSHOME/bin directory.
4. Modify the LIBPATH (for AIX 4.3), SHLIB_PATH (for HP-UX 11), or
LD_LIBRARY_PATH (for the rest of the UNIX platforms) environment variable to

include $RDSHOME/bin so that the dynamic linker can locate the Velocis shared
libraries.
There are three basic ways an appropriate user configuration can be initialized:
• Each time a user wants to use Velocis, he can execute the appropriate rdshome script
(created as part of installation step 6), as shown in Table 3-4.
Table 3-4. Executing the rdshome Server Script on Different Shells
Shell Command
Bourne or Korn shell . ./rdshome.sh
C shell source ./rdshome.csh
• Add commands functionally equivalent to those in the appropriate rdshome script

to the user shell configuration file (.profile for the Bourne and Korn shells and .cshrc
for the C shell).
• Modify the user shell configuration file so that it executes the appropriate rdshome
script.

Chapter 4
Installing Velocis Client Software
This chapter covers the installation and configuration of the client software for a Velocis
database system. Section 4.1 provides information about installing and configuring the
client software on the Windows 95/98, Windows NT 4.0, and Windows 2000 platforms.
Section 4.2 covers the installation and configuration of Velocis client software on a UNIX
platform.
For an overview of the entire process of installing and setting up a Velocis system, see
section 3.1 of Chapter 3, "Installing Velocis Server Software." If you have trouble
installing or running Velocis, consult Chapter 7, "Velocis Maintenance," which includes
information about troubleshooting and diagnosing problems.
4.1 Installing the Client Software on Windows

This section provides information about preparing for installation, installing the client
software, and configuring the environment on the Windows 95/98, Windows NT 4.0, and
Windows 2000 client platforms.

Before installing the Velocis client software on a Windows platform, you need the
following:
• The Velocis installation CD-ROM.
• The necessary protocols and network drivers loaded on the workstation. For more
information, see the appropriate section of Chapter 2, "About the Velocis
Environment."
• Familiarity with the platform on which you are installing the server software. For
information about a platform, see the appropriate section in Chapter 2.
Additional Preparations for a Windows NT 4.0/2000 Platform

Log into the computer with administrator access. The Velocis installation for Windows
NT 4.0 requires changes to some items in the Windows NT 4.0/2000 Registry, for which
you need administrator-level privileges.
Installing Velocis Client Software 4-1

4.1.2 Installing the Client Software
To install the Velocis client software, you run a setup program that asks you to supply
information and to choose where and how you want Velocis installed on your computer.
4.1.2.1 The Velocis Setup Program

The Velocis setup program consists of a series of screens containing instructions and
displaying boxes or option buttons for entering your responses.
Each screen also includes Next, Back, and Cancel buttons. To enter your response to a
screen and then go on to the next screen, click Next. To return to the previous screen,
click Back. To stop installing Velocis and exit the setup program, click Cancel.
4.1.2.2 Running the Setup Program
To run the setup program:

1. Insert the Velocis installation CD-ROM into the drive.
2. Open the Run dialog box and click Browse.
The Browse dialog box appears.
3. Use the Browse dialog box to display the folders on the installation CD-ROM. If you
need instructions for using the Browse dialog box, consult Windows Help.
Locate and open the Client folder for the appropriate Windows platform. Select the
Setup.exe file and click Open.
The Browse dialog box closes and the path you selected appears in the Run dialog
box. (For example, the path could be D:\Velocis30\nt\client\Setup.exe, for a
Windows NT 4.0/2000 server.)
4. Click OK.
The Velocis logo window appears, and then the Setup message box opens to tell you
that the InstallShield Wizard will guide you through the setup process.
5. When the Welcome to Velocis screen appears, read the screen. If you want to leave
the setup program, click Cancel. To continue installing Velocis, click Next.
The Software License Agreement appears.
6. Read the Software License Agreement. If you do not accept the terms of the
agreement, click No and quit the Velocis setup program. If you accept the terms of
the license agreement, click Yes.
The Choose Destination Location screen appears.
7. On the Choose Destination Location and successive screens, read the instructions,
enter your response in the appropriate box, and then click Next.
Enter the requested information on each screen until you reach the About to Install
screen. For more information about responding to these screens, see section 4.1.2.3.

8. The About to Install screen lists the information and choices you have entered on the
preceding screens. Review this list and, if you wish to change anything, click Back
until you reach the appropriate screen for entering the change. When you have
changed the information, return to the About to Install screen.
9. When you are satisfied with the options listed on the About to Install screen, click
Next.
The setup program then copies the Velocis client software into the folder you
specified on the Choose Destination Location screen (see section 4.1.2.3).
You can stop the copying process, if necessary, by pressing the <F3> key.
10. When the Setup Complete screen appears, you can choose whether to have the setup
program restart your computer immediately or to do it yourself later. (Restarting
your computer makes the setup program’s change to your autoexec.bat file
effective.)
To exit the setup program, click Finish.
4.1.2.3 Entering Setup Information and Options

Table 4-1 provides information about responding to the setup program screens.
Table 4-1. Client Setup Information for Windows
Choose Destination Location

Destination Folder Unless you specify otherwise, the setup program
creates a folder named Centura\Velocis Client and
installs the client software in that folder.
Browse If you want Velocis installed in a different folder,
click Browse to open the Choose Folder dialog box.
Choose Folder
Path Use the Drives and Directories lists to select the
drive and the directory where you want Velocis to
be installed. Then click OK.
Network To install Velocis on an unlisted drive, click
Network to open the Map Network Drive dialog
box.
Map Network Drive To install the server software on an unlisted drive,
you must specify a letter to identify the drive and
enter the path for the drive.
Drive Select a letter to identify this drive.

Table 4-1. Client Setup Information for Windows (continued)

Path Use this format to specify the path:
\\<computername>\<foldername>
Reconnect at logon Specifies whether to connect to this shared folder
every time you start Windows. Unless you use this
folder often, do not check this folder. This will
speed your Windows startup.
Compiler Options Click the compiler you will use with Velocis.
Microsoft Visual C++ 6.0 For information about compiler options, see
Borland C++ Builder 4.0 Chapter 13 of the Velocis User’s Guide.
Setup Type To choose the type of install, click the option.
Typical Installs the following components: program files,
example files, help files, catalog files, include files,
and library files.
Custom Clicking this option opens the Select Components
dialog box where you can choose which of the
following options to install, program files, example
files, include files, and library files.
Additional Installation Options To choose an additional option, click the option.
Install ODBC Automatically installs the Velocis ODBC driver so
you can use the ODBC DM.
Add path to Velocis DLLs to Adds the Centura\Velocis\Bin directory path
autoexec.bat (Registry on (where the DLL files are stored) to the PATH
Windows NT 4.0/2000) environment variable in your autoexec.bat file
(registry on Windows NT 4.0/2000). We highly
recommend that you select this option.
Enter Information Displays the name of the server that will be
registered in the 32 bit ODBC driver manager. The
default is Velocis.
Select Program Folder Allows you to decide where to display the program
icons for Velocis client.
Program Folders You can select a folder from the list in the Existing
Folders box, or, if you type the name of a new
folder, the Install Wizard will create it for you.
Existing Folders You can select Velocis Client or another folder from
the list in this box.

4.1.3 Configuring the Client Environment
The configuration information in this section may apply to a client workstation running in
a Windows 95/98, Windows NT 4.0, or Windows 2000 operating environment.
Configuring the Windows Client Environment

If you chose not to modify the PATH variable during installation, you need to manually
adjust PATH to include the path to the Velocis program files and DLLs before you can
run Velocis client programs. For the default installation directory, the path is
C:\Centura\Velocis Client\Bin.
4.2 Installing the Client Software on UNIX and

UNIX-like Operating Systems
This section describes how to install the Velocis client software on UNIX and UNIX-like
platforms for client systems without network file system (NFS) access to the server
installation directory. In addition to the option of NFS mounting the server installation
directory, it is possible to install just the client software tree on an NFS that is mounted on
all of the client systems. This approach significantly reduces the work required to install
and maintain the client software for a group of clients. To do this, follow the instructions
in sections 4.2.1 and 4.2.2 once for installation on the file server, instead of once per client
system. If you are choosing to share the server installation directory, you should still
read and follow the instructions in section 4.2.3.
Some of the installation steps or prerequisites (such as mounting the CD-ROM or creating
a new user), require root access to most or all systems. If you do not have this level of
access, seek assistance from a system administrator. Many of these steps require
platform-specific system administration knowledge. If you are not familiar with the
required tasks, consult your system documentation or your system administrator.

Before you begin installing the Velocis client on a supported UNIX operating system, be
certain you have taken care of the following:
• Have on hand the Velocis installation CD-ROM.
• Be familiar with the platform on which you are installing the client software and
have the necessary protocols and network drivers installed. For more information,
see the appropriate section of Chapter 2, "About the Velocis Environment."
• Decide what account will own the Velocis client installation. This can be a local or
NIS account, and can be an existing account such as "root" or a new one dedicated

to Velocis administration. (This decision usually depends on local policies and
conventions, as well as administrative and security considerations.)
• Create or clear the directory in which you want to install the Velocis client
software. Make sure that it is owned by the account selected as the Velocis
software owner and that the permissions allow all users to read and execute files
with it. (In most cases, only the owner should have write permission.)
• Read all the installation steps.
4.2.2 Installing the Client Software

To install the client software:
1. Mount the CD-ROM on the system on which you wish to install the Velocis client
software. On some systems, this may be automatically done by inserting the
CD-ROM in the drive. On all other systems, it will be necessary to use the mount
command while logged in as "root". If the system does not have a CD-ROM drive, it
is possible to mount the CD-ROM on a system that does and mount the CD-ROM on
the client system via NFS.
2. Log into the system on which you wish to install the Velocis client software as the
user selected to be the Velocis software owner.
3. Locate the mount point for the CD-ROM on your system and the directory on the
CD-ROM that contains the installation archive for your UNIX platform. In this
directory, resides a file named <platform>cli.tar, where <platform> is an
abbreviation for the platform on which to install the client software.
4. Use the cd command to change to the directory that you have cleared to hold the
Velocis client software tree.
5. Extract the archive as follows:
tar xvf <absolute path of selected *cli.tar file>
For example, if your CD-ROM mount point is /cdrom and your platform is Intel
Linux 6.0 kernel 2.222.9, the command would be
tar xvf /cdrom/Linux/Client/Lnxtcli.tar
6. From the Velocis home directory, run the shell script named "install", by executing
the following on the command line:
sh ./install
This script sets file permissions and creates the Velocis environment script files,
rdshome.sh (for the Bourne and Korn shells) and rdshome.csh (for the C shell).

4.2.3 Configuring a UNIX Client Environment
Each account that uses the Velocis client software requires several changes made to its
shell environment so that Velocis works efficiently. Three modifications are required for
users of the client software:
1. Define an RDSHOME environment variable whose value is the path to the Velocis
client software installation directory.
2. Modify the directory search path to include the $RDSHOME/bin directory.
3. Modify the LIBPATH (for AIX 4.3), SHLIB_PATH (for HP-UX 11), or
LD_LIBRARY_PATH (for the rest of the UNIX platforms) environment variable to
include $RDSHOME/bin, so that the dynamic linker can locate the Velocis shared
libraries.
There are three basic ways an appropriate user configuration can be initialized:
• Each time a user wants to use Velocis, he can execute the appropriate rdshome
script (created as part of installation step 6, in section 4.2.2) as shown in Table 4-2.
Table 4-2. Execution of the rdshome Client Script on Different Shells
Shell Command
Bourne or Korn shell . ./rdshome.sh
C shell source ./rdshome.csh
• Add commands functionally equivalent to those in the appropriate rdshome script

to the user shell configuration file (.profile for the Bourne and Korn shells and
.cshrc for the C shell).
• Modify the user shell configuration file so that it executes the correct rdshome
script.

Chapter 5
Running Velocis
After you install the Velocis software on your server and client computers, you should
start your Velocis server, log into the server, and test to make sure that Velocis has been
properly installed.
This chapter contains information about starting, stopping, and testing a Velocis server.
Section 5.1 provides instructions for starting a server on each of the platforms on which a
Velocis server can run. Section 5.2 provides information about the major utilities that a
system administrator uses to configure and manage a Velocis database system. Section
5.3 provides instructions for testing your installation, and section 5.4 provides
instructions for shutting down a Velocis server.
Once you are sure that the Velocis software is functioning correctly, you must set up your
Velocis database system by configuring the database devices, databases, user accounts,
and extension modules that make up a Velocis database system. For information about
using the Velocis utilities to configure and to manage a Velocis database system, see
Chapters 6 and 7.
5.1 Server Startup Procedures

Startup of the Velocis server on any platform loads all necessary program files, initializes
the server by reading the system catalog, registers the server with the network, and then
begins operation. A normal startup loads all files, including an SQL support module.
However, for most platforms, you have the option of disabling the Velocis SQL module.
5.1.1 Starting the Server on Windows 95/98

There are three ways to start the Velocis server on a Windows 95/98 platform. If, when
you installed the server software, you selected the Run Velocis Server as Service option,
the server automatically starts when you start the server computer. For more
information, see section 5.1.1.2.
You also can start a server manually. For instructions on starting a server manually, see
section 5.1.1.1.
However, if you did not install the server as a service, the easiest way to start the server is
by using the shortcut icon created by the Velocis setup program.
To start a server using the shortcut icon:

1. From the Start menu, select Programs.
Running Velocis 5-1

2. From the Programs menu, select Velocis Database Server.
3. From the Velocis Database Server menu, click the Velocis Database Server icon.
A DOS window opens, displaying the startup routine for the server, including a list
of the transports on which the server is listening. When the server display indicates
"Ready" near the bottom of the screen, the server is operable and the startup
procedure is finished. During operation, the server displays messages reflecting
logins, logouts, and other server events.
5.1.1.1 Starting the Server Manually
To manually start the server from Windows 95/98:

1. Open a DOS window.
2. At the command prompt, type the following command:
rds [-d [-pn | -ph| -pi]] [<server name>]
If you do not specify a name when starting the server, Velocis uses "Velocis" as the
default server name.
The -d option instructs the server to run in background mode (the daemon mode).
The -p options set the priority of the background process, normal (-pn), high (-ph) or
idle (-pi). Normal priority is the default setting. This option takes effect only if -d is
specified.
Note: If the -d option is specified, the server remains running in the background after the
current Windows 95/98 user logs out.
The server displays its startup routine in the DOS window, including a list of the
transports on which the server is listening. When the server display indicates "Ready"
near the bottom of the screen, the server is operable and the startup procedure is finished.
During operation, the server displays messages reflecting logins, logouts, and other
server events.
If the -d option is specified, a copy of the server is launched in the background. The
original does not exit until the copy is fully initialized and is listening on the configured
transports. When the program returns to the DOS prompt, the background server is
completely up and running.
Proceed to section 5.2 to learn about accessing the Velocis Administrator and rdsadm
utilities, which are the primary tools for configuring and managing a Velocis database
system.
If your server display does not indicate "Ready," the server has failed to enter the Ready
state and is not operable. For diagnosis and suggested solutions, see Chapter 7, "Velocis
Maintenance."

5.1.1.2 Starting the Server as a Service
If you configured the server as a Windows 95/98 service during the installation or by
using the instrds command, the server starts automatically every time you reboot the
computer. When started as a service, the server runs in the background without a server
console (this is equivalent to manual startup using the -d option, described in section
5.1.1.1). Because Windows 95/98 does not provide a Service Control Manager, you can
stop the service only by using the rdsadm utility (menu item "Shutdown server") or by
calling the s_shutdown function in a program. Once stopped, the server can be manually
restarted in the background mode using the -d option. If you configured the service
using instrds, you can un-register the server as a service by using the instrds remove
command.
5.1.2 Starting the Server on Windows NT 4.0/2000

You can start the Velocis server for Windows NT 4.0/2000 in three ways. You can run the
server from the Windows NT 4.0/2000 prompt, as a manually started application. Or,
you can run it as a Windows NT 4.0/2000 service under the control of the Service Control
Manager.
However, the easiest way to start the server is by using the shortcut icon created by the
Velocis setup program.
To start a server using the shortcut icon:

1. From the Start menu, select Programs.
2. From the Programs menu, select Velocis Database Server.
3. From the Velocis Database Server menu, click the Velocis Database Server icon.
A DOS window opens, displaying the startup routine for the server, including a list
of the transports on which the server is listening. When the server display indicates
"Ready" near the bottom of the screen, the server is operable and the startup
procedure is finished. During operation, the server displays messages reflecting
logins, logouts, and other server events.
5.1.2.1 Starting the Server Manually
To manually start a server on the Windows NT 4.0 platform:

1. Open a DOS window.
rds [<server name>]
Running Velocis 5-3

The server displays its startup routine in the DOS window, including the list of transports
on which the server is listening. When the server display indicates "Ready" near the
bottom of the screen, the server is operable and the startup procedure is finished. During
operation, the server displays messages reflecting logins, logouts, and other server
events.
If your server display does not indicate "Ready," the server has failed to enter the Ready
Maintenance."
5.1.2.2 Starting from the Service Control Manager

When you run Velocis on a Windows NT 4.0/2000 platform, you can use the Service
Control Manager to specify how you want the server to start. The available startup
options are shown in Table 5-1 below.
Table 5-1. Service Control Manager Startup Options
Option Description
Automatic The server starts automatically when the server computer boots.
Manual The user starts the server.
Disabled No startup is available.
To start a server as a Windows NT 4.0/2000 server:

1. In the Windows NT 4.0/2000 Control Panel, click the Services icon.
The Services dialog box appears.
2. In the Services dialog box, select the Velocis Server entry (the name of the server
appears in parentheses).
3. Click Startup.
The Service Startup Options dialog box appears.
4. Select a startup option and click Close.
The Service Startup Options dialog box disappears.
5. To start Velocis, click Start.
If you need to pause or to stop the server during startup, click Pause or Stop. After
the server has started, Velocis generates an RDS.log file and places it in the same
directory from which you are running the server.
6. When you have finished using the Services Control Manager, click Close.

5.1.3 Starting the Server on UNIX
On the UNIX platform, Velocis starts the default server when you enter the startup
command, "rds". If you want to start a different server, you can specify the name of the
server following the startup command.
If you like, you can change the default server by changing the ServerName parameter in
the velocis.ini file. For information about changing a velocis.ini file parameter, see
Chapter 6, section 6.1.1.2.
To start the server from the UNIX platform:

At the UNIX command prompt, type the following command:
rds [-d] [<server name>]
The optional -d switch starts the server as a daemon.
The server displays its startup routine, including the list of transports on which the server
is listening. When the server display indicates "Ready" near the bottom of the screen, the
server is operable and the startup procedure is finished. During operation, the server
displays messages reflecting logins, logouts, and other server events.
If the -d option is specified, a copy of the server is launched in the background. The
original does not exit until the copy is fully initialized and is listening on the configured
transports. When the program returns to the shell prompt, the background server is
completely up and running. In daemon mode, the server has no console. Therefore, the
server events are only registered in RDS.log, which is created in the current working
directory when RDS is started.
Proceed to section 5.2 to learn about accessing the Velocis Administrator and rdsadm
utilities, which are the primary tools for configuring and managing a Velocis database
system.
If your server display does not indicate "Ready", the server has failed to enter the Ready
Maintenance."
5.2 System Administration Utilities

This section contains introductory information about Velocis utility programs that are
particularly useful to system administrators.
Section 5.2.1 provides information about Velocis Administrator (also called admin),
which is available on the Windows 95/98 and Windows NT 4.0/2000 platforms. Velocis
Running Velocis 5-5

Administrator provides an easy-to-use graphical interface for performing the following
tasks:
• Configuring the parameters of the velocis.ini file
• Creating and managing database devices
• Registering and managing databases
• Creating user accounts and controlling access to databases
• Configuring and managing server extension modules
• Backing up a server
• Shutting down a server
Section 5.2.2 provides information about the rdsadm utility program, which provides a
character-based interface for performing most of the same tasks as Velocis Administrator.
The rdsadm utility program is available on all platforms.
Section 5.2.3 describes the vping utility program, which allows you to test the connection
between a client and a server.
All Velocis utility programs are installed in the Centura\Velocis Server\Bin directory.
Technical details of the utility programs described in this section, as well as dbcheck, are
provided in Chapter 2 of the Velocis Reference Manual.
5.2.1 The Velocis Administrator Utility

If you are using a Windows 95/98, Windows NT 4.0/2000 platform, you can use the
Velocis Administrator utility. Velocis Administrator recognizes the privilege level of the
user. If you are not an administrative user, the utility does not permit you to perform the
more privileged functions. They are grayed out in the menus.
5.2.1.1 Opening Velocis Administrator

Before you open Velocis Administrator, you should start and log into the server (for
instructions on starting a server, see section 5.1). Note that you can open Velocis
Administrator without logging into the server, but you will not be able to see all of the
views and dialog boxes.
Use either of the following procedures to open Velocis Administrator.
To open Velocis Administrator:

In the Velocis program group, double-click the admin icon.
or
In the Centura\Velocis Client\Bin directory, double-click the admin.exe file.

When the Velocis Administrator window opens, it contains the Velocis Servers window.
It displays the parameters of the aliases defined in the connect.ini file.
Figure 5-1. Velocis Administrator at Startup
The opening Velocis Administrator window displays a menu bar and a toolbar at the top
of the window. Until you have logged into a server, only the Login to Server button (at
the left end of the toolbar) and the Help button (at the right end) are active. (For more
information about the toolbar, see section 5.2.1.3.) To activate the toolbar buttons and to
gain access to all the Velocis Administrator views and dialog boxes, you must log into a
server.
5.2.1.2 Logging Into a Server

After you have started a server and opened the Velocis Administrator window, you can
log into the server.
To log into a server:

1. From the Server menu, click Login. (You also can click the Login to Server button at
the left end of the toolbar.)
The Login to Server dialog box appears.
Running Velocis 5-7

2. In the Server box, you can type the name (or the alias) of the server or select it from
the drop down list.
3. In the User Name box, type your user name (or admin, the default name).
(Velocis provides a default user account named "admin" that has administrator level
privileges. To set up an account for yourself and to delete the admin account, use
the procedures in Chapter 6, section 6.5.)
4. In the Password box, type your password (or type secret, the password for the
default user account, admin).
5. Click OK.
The dialog box closes. After a short pause, a window for this server opens,
displaying the Databases view. To change to a different view, see section 5.2.1.3.
If your network contains more than one Velocis server, you can use Velocis
Administrator to log into another server. Use the procedure above, entering the name of
a different server in the Login to Server dialog box.
5.2.1.3 Managing Your System with Velocis Administrator

You can manage the user accounts, databases, database devices, and extension modules
on any server in your system with Velocis Administrator. You also can use Velocis
Administrator to see which users are logged into a server. You perform each of these
administrative functions by using a different view of Velocis Administrator.
Velocis Administrator provides the following views:
• Accounts view. Use this view to create user accounts, to specify a user’s access
level and permissions, and to grant user access to a database.
• Databases view. Use this view to register a database with a server, initialize a
database, and manage a database.
• Devices view. Use this view to create, register, and manage a database device. (A
Velocis database device is not a physical disk drive or device. It is a logical name
for a file directory in which Velocis stores files.)
• Extensions view. Use this view to create and manage extension modules.
• Logged-in Users view. Use this view to see which users are logged into a server.
You can access each of these views by clicking it on the View menu or by clicking its
button on the Velocis Administrator toolbar. The buttons on the toolbar are identified in
Figure 5-2.

Figure 5-2. Velocis Administrator Toolbar Buttons
If you want to look at more than one view at the same time, you can open a new window
(using the Window menu) and then display another view in the second window.
5.2.1.4 Logging Out of a Server

You also can use Velocis Administrator to log out of a server and to shut a server down.
To log out of a server:

From the Server menu, click Logout.
The server window closes. Unless you are still logged into another server, all the
toolbar buttons except the Server and Help buttons become inactive.
5.2.1.5 Closing Velocis Administrator

When you finish working in Velocis Administrator, you can minimize its window until
you are ready to use it again, or you can close Velocis Administrator.
To close Velocis Administrator:

From the Server menu, click Exit.
The Velocis Administrator window disappears.
5.2.2 The rdsadm Utility

The rdsadm utility is a character-based, system administration program that runs on any
Velocis platform. It provides most of the same functions as Velocis Administrator, but
can be used in a non-Windows environment.
5.2.2.1 Opening rdsadm and Logging Into a Server

Before you open rdsadm, make sure that the server that you want to log into is running.
Running Velocis 5-9

To open rdsadm and log into a server:
1. In a DOS window, at the command prompt, type the following command and press
<Enter>:
rdsadm
2. At the Enter Centura Server name prompt, type the connection name and press
<Enter>.
The connection name is the server name or alias defined in the connect.ini file. See
Chapter 2, section 2.4.1.1 for information on defining aliases.
3. At the Enter your userid prompt, type the name of your user account and press
<Enter>.
(If you are logging into a server for the first time, after installing the software, the
default userid is "admin".)
4. At the Enter your password prompt, type your password and press <Enter>.
(If you are logging into a server for the first time, and used the default userid
"admin," the default password is "secret".)
After a brief pause, Velocis displays the message, "Successful login," and the opening
menu, shown in Figure 5-3.
1. User
2. Device
3. Database
4. Configuration
5. Show
6. Extension Modules
7. Hot Backup
8. Shutdown Server
9. Exit
Enter selection (1-9):
Figure 5-3. rdsadm Opening Menu

Note: You can define the global login parameters via the environment variable,
RDSLOGIN. The variable should be a string with the connection name, user name, and
password each separated by a semicolon, for example, "rdslocal;admin;secret". Each
Velocis utility that logs into a server checks this variable before prompting for the login
parameters.
5.2.2.2 Managing a Database System with rdsadm

You can use rdsadm to manage the user accounts, database devices, databases, and
extension modules on any server in your system. You also can use rdsadm to back up a
database and to shut down a server.

The rdsadm user interface includes prompts that ask you to supply information and a
series of menus, similar to the opening menu.
To select an option from an rdsadm menu:

1. At the Enter selection prompt, type the number of the option and press <Enter>.
The utility displays a new menu for the option you selected.
2 To select an option from the new menu, repeat this procedure.
3. If rdsadm asks you to supply information, such as the name of a server, type the
information at the prompt and press <Enter>.
Instructions for using rdsadm to configure your database system are provided in Chapter
6, "Server Configuration."
To close rdsadm:
At the Enter selection prompt, type the number of the Exit option (9) and press
<Enter>.
5.2.3 The vping Utility

The vping utility is used to test a Velocis network connection. The program "pings" the
network connection at specified times to determine whether physical and logical
connections are active and whether message recipients are online. Run this utility from
the command line, using the commands described in Chapter 2 of the Velocis Reference
Manual.
5.3 Testing Procedures

You can use the vping utility to test whether the client software you installed can
successfully connect with the server software. Before using the following procedure to
test the software, check that your hardware has been properly set up and is started.
To use vping to test a client-server connection:

1. Make sure that no other software is interfering with Velocis. It is best not to run any
non-Velocis software on either the server or the client machines.
2. Start the server as described in section 5.1.
3. On the client computer, modify the connect.ini file to make sure that aliases are
defined for each transport the installed server supports. A template version of the
connect.ini file is installed in the \Bin subdirectory.
4. At the client machine command prompt, enter the following command:
vping
Running Velocis 5-11

5. The vping utility starts and displays a detailed list of the aliases defined in the
connect.ini file. It also lists all the transports supported on the client platform and
their configuration status (enabled or disabled). For example, if you have installed a
Windows NT 4.0 Velocis client and modified the connect.ini file for your network,
calling vping might display the following list:
Transports
==========
TCP/IP: Enabled, Packet Size: 4096
Local: Enabled
Named Pipes: Enabled, Named Services: Disabled
Available Aliases
=================
tcpserver (Encryption: off):
1. Protocol: TCP/IP
Host: 195.211.252.12, Port: 2000
localserver (Encryption: off):
1. Protocol: Local
Server: RDS
npserver (Encryption: off):
1. Protocol: Named Pipes
Name: RDS, Node: backbone
all (Encryption: 2):
1. Protocol: Local
Name: RDS
2. Protocol: Named Pipes
Name: RDS, Node: backbone
3. Protocol: TCP/IP
Host: 195.211.252.12, Port: 2000
6. Call vping using different aliases. This will test your connectivity to the newly
installed Velocis server using different transports.
7. The vping utility tests the physical and logical connections between the client and
the server. If everything is working properly, you should see a response similar to
the following example.
[1] 18029 sent 18029 received
If vping finds that a connection is not operable, it displays the message, "Error:
NCP_RC_SERVER unavailable," with suggestions for corrective action.

5.4 Server Shutdown Procedures
5.4.1 Shutting Down a Server Using Velocis Administrator

On Windows platforms, you can use the Velocis Administrator utility to shut down the
server remotely. You must have an administrative account with the server you are going
to shut down.
To shut down a server:

1. Using the procedure in section 5.2.1.2, log into the server you want to shut down.
2. From the Server menu, click Shutdown.
The server starts the shutdown process.
Note: If your account does not have the administrative rights on the server, Shutdown is
disabled (displayed in gray) on the server menu.
5.4.2 Shutting Down a Server Using the rdsadm Utility

You can use the rdsadm utility to shut down a server on all the client platforms. You
must have an administrative account with the server you are going to shut down.
To shut down a server:

rdsadm [-L <login string>]
2. At the Enter Centura Server name prompt, type the connection name and press
<Enter>.
The connection name is the server name or an alias defined in the connect.ini file.
See Chapter 2, section 2.4.1.1, for information on defining aliases.
3. At the Enter your userid prompt, type the name of an administrator account and
press <Enter>.
4. At the Enter your password prompt, type your administrator password and press
<Enter>.
5. At the Enter selection prompt, type 8 (for Shutdown server) and press <Enter>.
The server starts the shutdown process.
Note: If your account does not have the administrative rights on the server, an error
message is displayed.

5.4.3 Shutting Down a Server on Windows 95/98 or NT 4.0/2000
Section 5.4.3.1 provides instructions for shutting down a server manually on a Windows
95/98 or Windows NT 4.0/2000 platform, and section 5.4.3.2 provides instructions for
shutting down a server from the Service Control Manager.
5.4.3.1 Shutting Down Manually
To shut down a server manually on Windows 95/98 or Windows NT 4.0/2000:

1. Try to ensure that all database clients are logged out.
2. In the active server window, press <Ctrl+C>.
Velocis performs an immediate controlled shutdown, in which it aborts any
uncommitted transactions, closes all databases, and logs out all clients. After a short
pause, Velocis displays the message, "Successful Server Shutdown."
Any clients that are active at shutdown will receive an error message the next time the
application calls the server.
5.4.3.2 Shutting Down from the Service Control Manager (Windows NT 4.0/2000
Only)
To shut down a server from the Service Control Manager:

1. From the Windows NT 4.0/2000 Control Panel, click Services.
The Services dialog box appears.
2. Select the Velocis Server entry (the name of the server appears in parentheses).
3. Click Stop.
4. Click Close.
5.4.4 Shutting Down a Server on UNIX

Two UNIX signals will trigger the controlled shutdown of the server, interrupt (SIGINT)
and terminate (SIGTERM).
To shut down a server on UNIX:

1. Be sure that all database clients are logged out.
2. Generate one of the two signals to trigger shutdown.
You can use <Ctrl+C> (or <Del> key on some UNIX platforms) from the Velocis
session to generate an interrupt signal (SIGINT).
Alternatively, you can use the kill command from the other terminal to generate
either UNIX signal. To generate SIGINT, enter the following command:
kill -SIGINT <rds_pid>

To generate SIGTERM, enter this command:
kill <rds_pid>
The <rds_pid> parameter represents the ID of the Velocis server process.

Velocis makes an immediate controlled shutdown, in which it aborts any
uncommitted transactions, closes all databases, and logs out all clients. After a short
pause, Velocis displays the message, "Successful Server Shutdown."
Note: If the server was started as a daemon, you can only use the kill command to shut
down. Using rdsadm to shut down (described in section 5.4.2) works both with the
daemon and the regular server process.
Any clients active at shutdown receive an error message the next time the application
calls the server.

Chapter 6
Server Configuration
After you have installed the Velocis Database Server on your system, started your
servers, logged in, and tested the hardware and software, you are ready to configure your
Velocis system for operation.
This chapter provides instructions for configuring your Velocis database system. Section
6.1 provides instructions for changing the default values of Velocis server parameters in
order to improve the performance of your system. It also provides instructions for
increasing the number of users on your system from the default value of eight users.
Section 6.2 provides information about copying your system catalogs.
Sections 6.3-6.6 provide instructions for configuring the database objects that make up
your system, including database devices, databases, user accounts, and extension
modules. To configure a server object, you must register it by defining it, adding it to the
system catalog, and making any necessary support files available. To make server
parameter changes as described in section 6.1, you will need to restart the server, but for
all other changes the server will not need to be restarted.
You should perform all the configuration procedures described in this chapter before you
allow any clients to log in. Configuration tasks should be performed in the order shown
in Table 6-1 below.
Table 6-1. Configuration Order Section Reference
Configuration Task Section

Adjust the values for your server parameters to obtain the best 6.1
performance for your system.
Licensing the Velocis server. 6.1.2
Make a copy of the system catalog. 6.2
Configure the database devices for your system. 6.3
Configure the databases for your system. 6.4
Configure the user accounts for your system. 6.5
Configure the extension modules for your system. 6.6
You can use the Velocis Administrator or rdsadm utilities, described in Chapter 5, section
5.2, to perform most of the configuration procedures provided in this chapter.
Alternatively, you can create an administrative application.
Server Configuration 6-1

6.1 Adjusting Server Parameters
Many of the parameters and environment variables for your system’s servers are defined
in the velocis.ini file (in the Centura\Velocis Server\Catalog directory). Most of the
parameters in this file are platform independent. For a description of these parameters,
see Appendix A, "velocis.ini File Parameters." Platform-dependent parameters are
described in the appropriate section of the Velocis readme.txt file.
6.1.1 Optimizing Server Parameter Values

When you install Velocis, the server parameters in the velocis.ini file are defined by
default values. You can improve the performance of your database system by changing
those default values to reflect the combination of servers and database objects in your
particular system. This section tells you how to maximize the performance of your
Velocis system by customizing the values of those server parameters.
6.1.1.1 General Suggestions

The following suggestions may help you to achieve a more efficient configuration:
• If your system has multiple disk drives and controllers, spread out the system files
to maximize input and output concurrency. For example, if you have two drives,
you can place all data and key files on one drive and place the change log and
checkpoint image files on the second drive.
• Look at the operating system configuration. Optimize the file system, system
buffers, and priorities for database server operation.
• Consider using static records. If you have record types that might be filled once
and then remain unchanged, using static records can improve the performance of
your system.
6.1.1.2 Using Velocis Administrator to Change a Parameter Value

If you run Velocis on a Windows 95/98, Windows NT 4.0, or Windows NT 2000 platform,
Velocis Administrator provides the most convenient way to change the value of a
parameter. You also can use the rdsadm utility on the operating system command line to
change a parameter value.
When you use Velocis Administrator to change parameter values, you use the Update
VELOCIS.INI File dialog box to make changes in the velocis.ini file or the Update
CONNECT.INI File dialog box to make changes in the connect.ini file. Follow the
procedures described in section 5.2.1 to open Velocis Administrator and to log into the
server you want to configure. When you have logged into the server, use the following
procedure to open the Update VELOCIS.INI File dialog box.

To open the Update VELOCIS.INI File dialog box:
On the Server menu, select Configuration and then on the submenu, select Server.
The following dialog box appears.
Figure 6-1. Update VELOCIS.INI File Dialog Box
Table 6-2 describes the parts of the Update VELOCIS.INI File dialog box. Note that the
dialog box refers to parameters as entries.
Table 6-2. Update VELOCIS.INI File Dialog Box Elements
Dialog Box Element Description

Sections list Lists the names of the sections in the velocis.ini file.
Entries list Lists the parameters contained in the section you selected in the
Sections list.
Section box Displays the name of the selected section.
Entry box Displays the name of the selected parameter.
Value box Displays the value of the selected parameter.
To display the value for a parameter:

1. In the Sections list, click the appropriate section of the file.
The parameters for that section appear in the Entries list.

2. In the Entries list, click the appropriate parameter of the file.
The value for that entry appears in the Value box.
The following procedure explains how to use this dialog box to change the value for a
server parameter. You can use this procedure to make any of the parameter changes
recommended in section 6.1.1.4.
To change the value of a parameter:

1. Open the Update VELOCIS.INI File dialog box.
2. In the Sections list, click SERVER.
3. In the Entries list, click the parameter you want to change.
The choices you clicked appear in the Section and Entry boxes below the list boxes.
The current value for the parameter appears in the Value box.
4. In the Value box, type the value you want for this parameter.
5. Click Update.
To open the Update CONNECT.INI File dialog box:

On the Server menu, select Configuration and then on the submenu, select Client.
The Update CONNECT.INI File dialog box appears.
Use this dialog box to change the value of a parameter in the connect.ini file.
6.1.1.3 Using rdsadm to Change a Parameter Value

If you do not run Velocis on a Windows platform, you can use the rdsadm utility to
change the value of a parameter. Follow the procedures described in section 5.2.2 to open
rdsadm and to log into the server you want to configure.
To use rdsadm to change a parameter:

1. At the Enter Selection prompt, type: 4
(for Configuration) and then press <Enter>.
The utility displays a list of the sections in the velocis.ini file.
2. At the Enter Section to modify prompt, type: server
and then press <Enter>.
The utility displays a list of the parameters in the Server section of the velocis.ini
file. (Case is not significant in entering the section name.)
3. At the Enter parameter to modify prompt, type the name of the parameter you want
to change and then press <Enter>.
The utility displays the current value for that parameter.
4. At the Enter new value prompt, type the new value and then press <Enter>.
The utility displays the message, "Configuration record has been updated."

6.1.1.4 Recommended Changes to Parameter Values
Depending upon the details of your particular database system, it may be advantageous
for you to change the values for some of your server parameters. Table 6-3 lists some
parameters you may want to change and discusses when we recommend changing them.
For a description of all the parameters in the velocis.ini file, see Appendix A.
Table 6-3. Recommended Optimizations
Parameter Value Considerations

Archiving 1 Setting this parameter to 1 enables the server to
preserve change logs so they can be archived to
another medium for later deletion. If files are left
indefinitely, they consume a great deal of disk space,
so we recommend that you archive and delete them
on a regular basis.
AsyncTransactions 1 Setting this parameter to 1, for delayed transactions,
enhances server performance. However, delayed
transactions can be lost if the server crashes.
CheckPointThreshold Varies Decreasing the value of this parameter increases the
number and frequency of checkpoints.
FileCommit 0 If you are working with databases that can be easily
restored if a crash occurs, setting the FileCommit
parameter to 0 to disable the file sync operation can
improve performance significantly. However, it can
also sacrifice recoverability.
The default is 1, which instructs Velocis to perform a
file sync operation at each checkpoint on each
database file.
FileExtendSize Varies Consider setting this parameter to a value that is
larger than the platform-dependent default. A larger
value generally results in better performance because
of the operating system overhead associated with
each file extend operation.

Table 6-3. Recommended Optimizations (continued)

GrowChangeLogMsgs 0 Setting this parameter to 0 creates a buffer pool
for change log writes. Using a buffer pool reduces
the number of memory allocations and increases
performance. However, increasing performance in
this way consumes additional memory.
MaxCachePages Varies The size of the server cache should balance a server’s
memory needs with the amount of memory required
for your Velocis databases. Keep in mind that many
operating systems support virtual memory and avoid
making the server "go virtual."
MaxChangeLogSize Varies Be sure that the value for this parameter is large
enough. If it is too small, the server will perform a
change log cycle too frequently.
MaxCheckPointSize Varies This parameter determines how often the server
performs checkpoints. Setting the value higher
decreases the frequency of checkpoints, but increases
the size and duration of each checkpoint. A high
value means that recovery may take longer because
there is more to recover.
If the value is too low, the server performs
checkpoints too often. The optimal size depends
upon the applications a server supports and the input
and output performance of the server machine.
Avoid setting this parameter below 150 K.
MinFreeDiskSpace Varies This parameter should be set to allow the server to
complete any impending disk writes with no risk
of running out of space during a shutdown or
checkpoint. Use caution on operating systems that
expand a page file for each additional task.
Note that the free disk space threshold is server-
wide. If any device falls below the threshold, all
databases on the server are automatically placed
in a read-only mode.

Table 6-3. Recommended Optimizations (continued)

WordsPerStackFrame Varies The default (5000) is sufficient for most normal
operations. If client applications are using deeply
nested functionality, you should consider increasing
the value of this parameter. If you are not using SQL,
you can decrease the value to 1000.
6.1.2 Licensing the Velocis Server

When you receive your Velocis server, it initially supports eight simultaneous users, but
will work for only a 60-day trial. Licensing the server removes the 60 day limit and if the
license supports more users, it will automatically upgrade the server to the new number
of users. However, if the number of users is upgraded, you must additionally update the
MaxUsersOn parameter in the velocis.ini file. Your license may be for unlimited users,
but if the maximum users you expect on the system simultaneously is, for example, 500,
you can save resources by setting the MaxUsersOn value to 500.
Instructions for activating your license are included with your shipment of Velocis. The
instructions also contain the serial number and password for your license. To activate
your license and increase the maximum number of concurrent users (MaxUsersOn),
follow those instructions.
6.1.2.1 Using Velocis Administrator to License the Velocis Server

Open the Update VELOCIS.INI File dialog box using the procedure described in section
6.1.1.2 and display the parameters for the Engine section of the file. Unless it has been
added to the file since you installed the server software, there will not be an entry for
MaxUsersLicensed; you must add that parameter to the file.
To update the entry for MaxUsersLicensed and to enter an activation key:

1. In the Sections list, click ENGINE.
2. In the Entry box, type: MaxUsersLicensed.
3. In the Value box, type the new license limit.
4. Click Update.
The Update Max Users popup box appears.
5. In the Update Max Users popup box, enter the serial number and password,
following the instructions on the licensing information sheet.
6. To enter your update, click OK.

Next, you must change the value for the maximum number of concurrent users.
To change the maximum number of concurrent users:

1. In the Entries list, click MaxUsersOn. The current number of users appears in the
Value box.
2. In the Value box, type the expected number of maximum users for your upgraded
system. (The number should be more than eight.)
3. Click Update.
4. Click Exit.
5. Using the procedure described in section 5.6, shut down the server.
6. Using the procedure described in section 5.1, start the server.
Note: You must shut down and restart the server because Velocis allocates resources for
each client during startup.
6.1.2.2 Using rdsadm to Upgrade the Licensed Number of Users

Follow the procedures described in section 5.2.2, to open rdsadm and to log into the
server you want to configure.
To use rdsadm to upgrade the licensed number of users:

(for Configuration) and then press <Enter>.
The utility displays a list of the sections in the velocis.ini file.
2. At the Enter Section to modify prompt, type: engine
and then press <Enter>. (Case is not significant when entering the section name.)
The utility displays a list of the parameters in the Server section of the velocis.ini
file.
3. At the Enter parameter to modify prompt, type: MaxUsersLicensed
and then press <Enter>. (Case is significant when entering a parameter name.)
The utility displays the current value for that parameter.
4. At the Enter new maximum number of licensed users prompt, type the new license
limit and then press <Enter>.
5. When prompted for the serial number, type the serial number and then press
<Enter>.
6. When prompted for your password, type it, and then press <Enter>.
The utility displays the message, "Configuration record has been updated."
(for Shutdown Server) and then press <Enter>.

The utility briefly displays the message, "Server successfully shut down," and then
closes the rdsadm window.
8. Using the procedure described in section 5.1, start the server.
Note: You must shut down and restart the server because Velocis allocates resources for
each client during startup.
6.2 Copying System Catalogs

It is a good idea to maintain a separate copy of the installed catalog and syscat databases,
as you might need to restore them to their installed state. Simply copy the catalog.* and
syscat.* files from the \Centura\Velocis Server\Catalog directory into another directory
(for example, \Centura\Velocis Server\Catalog\initial). If you need to restore the
catalogs at a later time, you can do so by copying the files back to the original directory.
We recommend that you create a script of commands for Velocis Administrator or the
rdsadm utility, so that you can start with an empty catalog (as it exists just after
installation), and recreate server objects. For SQL databases, you will also want to keep a
batch file that reruns the sddlp utility for Velocis SQL.ddl files.
Caution: Back up the system catalog files occasionally. Remember that they change
when you register server objects, etc.
6.3 Configuring and Managing Database Devices

Velocis user, database, and extension module server objects use database devices to locate
most of the Velocis system files (described in Chapter 2 of the Velocis User’s Guide).
Essentially a database device is a logical name for a file directory contained on a physical
disk drive or device.
(Velocis does not use database devices to locate the system catalog files, the country table
file, and the change log indicator files. These are located using the CATPATH
environment variable.)
A database device can have any name you like. A database device name represents a
fully qualified directory path or a relative path. If the name represents a relative path, the
path is relative to the Velocis catalog as specified in the CATPATH environment variable,
and must begin with ".\" or "..\" (the current or parent directory, relative to the directory
specified by CATPATH). If a specified path name is not fully qualified or does not begin
with ".", the server looks for that name relative to its current working directory.
Predefined database devices are all specified using relative path names.
At installation, Velocis uses the database devices shown in Table 6-4 below.

Table 6-4. Velocis Database Devices
Database Device Path

catdev \Centura\Velocis Server\Catalog
emsamp \Centura\Velocis Server\Examples\em
rdsdll \Centura\Velocis Server\Bin
samples \Centura\Velocis Server\Examples\tims
sqldev \Centura\Velocis Server\Sqldb
sqlsamp \Centura\Velocis Server\Examples\emsql
sysdev \Centura\Velocis Server\Syslog
Important: To locate a Velocis file, you must specify its associated database device.
Therefore, you must register a database device before attempting to register any other
server object that uses it. Each database device definition must have a unique path. No
two database devices should point to the same physical directory, even if the paths are
different (for example, one fully qualified and one relative).
Database file names do not need to be unique, except that within one database device,
unique physical file names are required. The number of database devices you define
depends upon your particular needs. The minimum is one database device, for which all
system files are located in the same directory.
Velocis places no restrictions regarding the location of system files, as long as the server
can transparently access the files. Generally, it is best for organizational purposes to
locate related files together. For example, you also can use one database device to locate
all data and key files for one database. You can also locate individual files with different
database devices. You may be able to improve the performance of your Velocis system
by placing files in different database devices, to take advantage of the concurrency of
multiple disk drives.
Note: You cannot place the Velocis \Catalog and \Syslog directories on a CD-ROM
device.
6.3.1 Registering a Database Device

When you register a database device, you specify the name and the path for the database
device. You also specify whether the database device is a Read Only device. (Read Only
designation for a database device is not the same as the Read permission status granted to
a database user.)

Specifying that a database device is Read Only prevents Velocis from checking the device
for minimum free disk space. This is necessary when you define a CD-ROM drive as a
database device because otherwise, when Velocis routinely attempts to check the
CD-ROM drive, it would cause the server with which the drive was registered to go into
Read Only mode.
6.3.1.1 Using Velocis Administrator to Register a Database Device

To register a database device, you use the Database Devices view in the Velocis
Administrator window. Follow the procedures described in section 5.2.1, to open Velocis
Administrator and to log into the server you want to configure. When you have logged
into the server, use the following procedure to display the Database Devices view.
To display the Database Devices view:

From the View menu, click Devices. (You also can display the Database Devices
view by clicking the Devices button on the toolbar.)
Figure 6-2. Database Devices View
To register a database device:

1. From the Database Devices view, click New.

The New Device dialog box appears.
2. In the Name box, type the name of the database device.
A database device name can be any alphanumeric string up to nine characters long.
Case is significant. Choose a name that reflects the types of files this database device
represents. Since you might later change the path associated with the database
device, do not use a name that is related to the path.
3. In the Path box, type the database device path.
A database device path must be a legal physical path, up to 500 characters long.
Optionally, you can specify a physical device name (such as d:\mis\customers) or
even a network drive. You can include a drive (or volume) specifier in the path.
4. If the device is read only (such as a CD-ROM drive), click the Read Only check box.
5. Click OK.
Note: If any directories in the path to the database device do not yet exist, you must
create them before you enter the path. Velocis Administrator rejects any attempt to use a
directory that does not exist.
Caution: Be careful about mapping a database device to a network drive. Using such a
drive can leave the server vulnerable to network problems (but no database corruption) if
the network connection to system files goes down. Additionally, using a network drive
for a database device can compromise system security because network drives can be
publicly accessed. A final reason for not using a network drive is that some network file
systems do not support write-through capabilities, which Velocis needs to guarantee
recovery in case of a system crash.
6.3.1.2 Using rdsadm to Register a Database Device

Follow the procedures described in section 5.2.2 to open rdsadm and to log into the
To use rdsadm to register a database device:

(for Device) and then press <Enter>.
A new menu appears.
(for Add Device) and then press <Enter>.
3. At the Enter Device Name prompt, type the name of the database device you want
to register and then press <Enter>.
4. At the Enter device path prompt, type the path to the database device and then press
<Enter>.

Begin the path with a < character if you are registering a CD-ROM or read-only
device.
Note: If any directories in the path to the database device do not yet exist, you must
create them before you enter the path. Velocis Administrator rejects any attempt to use a
directory that does not exist.
Caution: Be careful about mapping a database device to a network drive. Using such a
drive can leave the server vulnerable to network problems (but no database corruption) if
the network connection to system files goes down. Additionally, using a network drive
for a database device can compromise system security because network drives can be
publicly accessed. A final reason for not using a network drive is that some network file
systems do not support write-through capabilities, which Velocis needs to guarantee
recovery in case of a system crash.
6.3.2 Changing a Database Device

By changing the location of a database device, you are relocating any file that references
it. Unless the database device has been designated read-only, Velocis moves associated
files to the new location. The next time a client opens a system file, Velocis will examine
the system catalog to determine which files are connected to the associated database
device.
6.3.2.1 Using Velocis Administrator to Change a Database Device

Using the procedure described in section 6.3.1.1, display the Database Devices view.
To change the location of a database device:

1. Select the name of the database device you want to change and click Edit.
The Update Device dialog box appears. The database device you selected is
displayed in the Name box.
2. In the Path box, type the new path.
3. If the database device is read only, click the Read Only check box.
4. Click OK.
Note: If you modify an existing database device with Velocis Administrator and associate
it with a physical path that does not exist on the server, you must manually create the
path. Velocis Administrator rejects an attempt to use a directory that does not exist.
6.3.2.2 Using rdsadm to Change a Database Device

Follow the procedures described in section 5.2.2 to open rdsadm and to log into the

To use rdsadm to change a database device:
A new menu appears.
(for Change Device) and then press <Enter>.
to change and then press <Enter>.
(To see a list of the database devices currently registered with the server, type: ?
and then press <Enter>.)
The utility displays the device name and the current device path.
4. At the Enter device path prompt, type the new path to the database device and then
press <Enter>.
Begin the path with a < character if you are registering a CD-ROM or read-only
device.
6.3.3 Deleting a Database Device

The only time you can delete a database device from the catalog is when no other
definitions are associated with it. Therefore, to delete a database device you must first
delete the associated server objects or associate those server objects with other database
devices. For information about deleting or reassigning server objects, see the section
listed under "Information" in Table 6-5 below.
Table 6-5. Server Object Section Reference
Objects Associated with a Database Device Section

Databases 6.4
Users 6.5
Database access lists 6.5.3
Extension modules 6.6
6.3.3.1 Using Velocis Administrator to Delete a Database Device

Using the procedure described in section 6.3.1.1, display the Database Devices view.
To delete a database device:

1. Select the name of the database device you want to delete and click Delete.

The Velocis Administrator message box appears with the following message: "This
will remove the device from the server. Are you sure?"
2. Click OK.
6.3.3.2 Using rdsadm to Delete a Database Device

Follow the procedures described in sections 5.2.2 and 5.3 to open rdsadm and to log into
the server you want to configure.
To use rdsadm to delete a database device:

A new menu appears.
(for Delete Device) and then press <Enter>.
to delete and then press <Enter>.
(To see a list of the database devices currently registered with the server, type: ?
and then press <Enter>.)
6.4 Configuring and Managing Databases

This section provides information about setting up and managing the databases in your
Velocis database system. Before users can access a database, you must register it in the
system catalog and create its files on the server.
Each database has only one owner. As the system administrator, you are the initial
owner of each database. If desired, you can define a new owner for a database. Then
only that owner and you can modify the database access list, which is the list of users
who can access the database.
Before you begin registering databases on a server, make sure that you have registered all
the database devices on which you want to locate database files. See section 6.3 for
instructions.
6.4.1 Registering a Database

For a Core application, you need to register databases and set up security as described in
this section. For a Velocis SQL application, however, databases are created and registered
when the sddlp utility compiles the database schema. All you have to do to a Velocis
SQL database after schema compilation is to set up the users, as described in section 6.5.

Velocis Administrator provides the most convenient way to configure and manage
databases. However, you also can use the rdsadm utility or the operating system
command line.
6.4.1.1 Using Velocis Administrator to Register a Database

To use Velocis Administrator to register a database, you display the Databases view in
Velocis Administrator window. Follow the procedures described in section 5.2.1 to open
Velocis Administrator and to log into the server you want to configure. When you have
logged into the server, use the following procedure to display the Databases view.
To display the Databases view:

From the View menu, click Databases. (You also can display the Databases view by
clicking the Databases button on the toolbar.)
Figure 6-3. Databases View
The Databases view window contains four separate areas, each displaying a list and one
or more command buttons. When configuring and managing databases, you use the
command buttons in the Databases area of the window.

When you select a database in the Databases list, the Files area lists the names of all the
files in the selected database. When changing the database device on which a file is
located, you use the Edit button in the Files area of the window.
When you select a file in the Files list, the Extension Files area displays the names of all
the extension files attached to that file. When adding, modifying, or checking an
extension file, you use the command buttons in the Extension Files area of the window.
The User Access area lists the names of all the users who currently have more than just
Read permission for the selected database. When authorizing or changing user access,
you use the command buttons in the User Access area of the window.
To register a database:
1. In the Databases area, click New.
The Install Database dialog box appears.
Figure 6-4. Install Database Dialog Box
2. In the Name box, type the name of the database.

The name can be any alphanumeric string, up to 11 characters long. This name is not
case-sensitive.
3. In the Device list box, select the database device for this database.
The database device specifies the location of the database dictionary and the data
and key files.
4. If you want all database users to have access to this database, click the Global
Database check box.
If you do not set the database for global access, only specified users can access the
database. For instructions on designating specific database users, see section 6.5.
5. Click OK.
Notice that Velocis Administrator automatically extracts the names of the files in the
selected database from the database dictionary and displays them in the Files list of the
Databases view window. (These files are created when the client compiles a database
schema using the ddlproc or the sddlp utility, as described in Chapter 11 of the Velocis
User’s Guide.)

Note: Velocis Administrator provides two ways to manage user access to a database: the
Accounts view window and the User Access area of the Databases view window (Figure
6.3). You use the Accounts view to set up and manage all user accounts on a server. (For
information about setting up and managing user accounts, see section 6.5.) However,
when you are in the Databases view, the User Access area provides a quick way to
register a new user with a database or to modify a user’s access permissions, without
switching to the Accounts view.
To authorize user access to a database (from the Databases view window):

1. From the Databases list, select the name of the database you want the user to access.
The names of the files in that database appear in the Files list and the names of the
users who can access the database appear in the User Access list.
2. In the User Access area, click New.
The New User Access dialog box appears, displaying the name of the selected
database.
3. From the Account Name list box, select the user you want to access this database.
In order to be listed in the Account Name list, the user must have been registered
with the server as a user account. (See section 6.5 for instructions.)
4. If you want the user to have more than just Read permission for the database, click
the appropriate check boxes: Insert, Update, or Delete.
Note that Read access permission is automatically checked for any user granted
database access.
5. Click OK.
6.4.1.2 Using rdsadm to Register a Database

Follow the procedures described in sections 5.2.2 and 5.3 to open rdsadm and to log into
the server you want to configure.
To use rdsadm to register a database:

(for Database) and then press <Enter>.
A new menu appears.
(for Add Database) and then press <Enter>.
3. At the Enter Database Name prompt, type the name of the database you want to
register and then press <Enter>.
The name can be any alphanumeric string, up to 11 characters long. This name is not
case-sensitive.

4. At the Enter Access prompt, type either 0 for global access or 1 for restricted
access to the database and then press <Enter>.
5. At the Enter Device prompt, type the name of the database device where you want
Velocis to store the database dictionary, data files, and key files and then press
<Enter>.
6.4.2 Initializing a Database
6.4.2.1 Using Velocis Administrator to Initialize a Database

Use the procedure described in section 6.4.1.1 to display the Databases view.
To initialize a database:
1. In the Databases area, select the name of the database you want to initialize and click
Init.
will initialize all the data and key files. Are you sure?"
2. Click OK.
6.4.2.2 Using rdsadm to Initialize a Database

Follow the procedures described in section 5.2 to open rdsadm and to log into the server
you want to configure.
To use rdsadm to initialize a database:

(for Database) and then press <Enter>.
A new menu appears.
(for Initialize Database) and then press <Enter>.
3. At the Enter Database Name prompt, type the name of the database you want to
initialize and then press <Enter>.
The utility displays the message, "Database has been initialized."
6.4.3 Changing a Database

This section tells you how to change the database device on which a database is located
and how to set or clear global database access. Note that you can only change a database
that is not being used. If you try to change a database that is in use, you will receive a
warning that the database is open, and you will not be able to modify it while it is in use.

6.4.3.1 Using Velocis Administrator to Change the Location of a Database
To move a database to a different database device:

1. From the Databases list, select the name of the database you want to change.
2. Click Edit.
The Modify Database dialog box appears. The database you selected is displayed in
the Name box.
3. In the Device list box, select the name of the database device to which you want to
move the database.
4. Click OK.
Velocis changes the location of the database dictionary and the data and key files to
the database device you selected.
Note: If you are updating a database dictionary, you must first delete the existing
database definition (for information, see section 6.4.4) and then install the new database
dictionary according to instructions in section 6.4.1.
6.4.3.2 Using Velocis Administrator to Change Global Database Access

To change a global database access:

1. From the Databases list, select the name of the database you want to change.
2. Click Edit.
The Modify Database dialog box appears. The database you selected is displayed in
the Name box.
3. In the Global Database check box, click to set or to clear the box.
(If you deselect the Global attribute, you must indicate specific database users in the
User Access area of the Databases window.)
4. Click OK.
6.4.4 Deleting a Database Definition

Before you attempt to delete a database from your Velocis system, make sure that no one
is using the database. If you attempt to delete a database that is in use, Velocis will
display a message warning that you cannot complete the delete operation.
Using the procedure described in section 6.4.1.1, display the Databases view.

To delete a database definition:
1. From the Databases list, select the name of the database you want to delete.
2. Click Delete.
will remove the database from the server. Are you sure?"
3. Click OK.
6.5 Configuring and Managing Database Users

Security in a Velocis database system is maintained by controlling user permission to
perform two types of activities:
• Using the system’s databases to read, insert, update, and delete records
• Performing administrative functions such as registering users, controlling user
permissions, and granting access to databases
Configuring a Velocis system to control user permissions includes the tasks shown in
Table 6-6 below.
Table 6-6. User Permissions Configuration Section Reference
Configuration Task Section

Registering a new user with a server 6.5.2.1
Specifying a user’s level of access to the server’s databases 6.5.2.1
Granting database access and permissions to a user 6.5.3.1
Setting up a permanent administrator account 6.5.6
Most of these procedures can be performed by using the Velocis Administrator.

However, access to an SQL database requires additional procedures, which are covered
in sections 6.5.4 and 6.5.5.
6.5.1 Controlling User Permissions
6.5.1.1 Access Levels

Before a user can access a server and any of its databases, you must register the user with
the server as a user account. When you register a user as a new user account, you also
determine which of the following access levels is assigned to the user:
• Normal access level

• Administrator privilege level
A user’s access level determines what the user is permitted to do to a database. Normal
users have "read only" access to a database unless they are specifically granted
permission to perform other functions such as inserting, updating, or deleting records.
Normal users cannot perform system administration functions.
Users with administrator privilege level access can access all databases, perform all
database functions, and perform all system administration functions.
6.5.1.2 Permissions
Table 6-7 describes the database permissions available to users of Velocis databases:
Table 6-7. Database Permission Types
Permission Type Description

Insert Allows a user to create database records.
Update Allows a user to modify records.
Delete Allows a user to delete records.
Read Allows a user to query a database.
Table 6-8 summarizes the permissions available to normal users and to users with
administrator privilege level.
Table 6-8. Access Permissions
Administrative Function Insert Update Delete Read

Registering Users A A, N* A N**
Defining Databases A A A N
Registering Database Devices A A A N
Defining Extension Modules A A A N
Defining Database Access A A A N
Performing General Configuration -- A -- N
Accessing Databases N*** N*** N*** N***
Table Notes:
A Administrator only.
N Normal user.
* Normal user can update password only.
** Normal user can list the names of other users, but cannot list their passwords.
*** Normal user has access only to global databases or to non-global databases for which access is granted.

An organization’s system administrator is often the only user given the administrator
privilege level. However, Velocis allows you to assign administrator privilege to more
than one user and we recommend that you do so. Authorizing administrator privilege
for a backup person can enable you to keep your Velocis system running smoothly at all
times. On the other hand, since users with administrator privilege have the ability to
create additional users with the same access privileges, you should avoid proliferation of
privileged users.
6.5.1.3 Preloaded Examples

If you selected the examples option at server installation, Velocis created a system catalog
preloaded with several example databases and users. The users and their passwords are
shown in Table 6-9.
Table 6-9. Initial Velocis Users
User Name Password Privilege

admin secret Admin
guest guest Normal
wayne* Father Normal
* This name is used in documented examples and can be removed after you are familiar with Velocis.
It is a good idea to maintain a one-to-one correspondence between actual users and

account names. To provide maximum flexibility, register a user account for each person
who is going to log into the server. Users should use the supplied "wayne" and "guest"
accounts only until they are familiar with Velocis. Then you should delete these two
accounts.
6.5.1.4 Case in Database User Accounts

Case is significant in user names and passwords. For example, the user name "wayne" is
different from "Wayne".
6.5.2 Managing User Accounts

Providing the users of your Velocis database system with access to your databases is a
two-part process. The first step is to set up a user account for each user who will be using
a database. The second step is to provide your users with access to the databases they
will use.
The most convenient way to register user accounts and to authorize user access to
databases is to use Velocis Administrator. This section provides instructions for using
Velocis Administrator to register a user account; to modify an account by changing the

user’s password, home database device, or access level; and to delete a user account.
Section 6.5.3 provides instructions for using Velocis Administrator to manage user access
to your databases. You also can use the rdsadm utility to perform these tasks.
6.5.2.1 Registering a Database User

This section describes the procedure for registering a database user for access to both
Core and Velocis SQL applications. However, for a Velocis SQL user, this procedure only
enables select statements for a database with public access when the user connects to
Velocis for the first time. If the user needs to be able to issue other types of statements,
you also must set up data access and command privileges as described in section 6.5.4.
To use Velocis Administrator to register a database user, you display the Accounts view
in the Velocis Administrator window.
To display the Accounts view:

From the View menu, click Accounts. (You also can display the Accounts view by
clicking the Accounts button on the toolbar.) Figure 6-5 shows the Accounts view.
Figure 6-5. Accounts View

The Accounts view window contains two separate areas, each displaying a list and
several command buttons. When managing user accounts, you use the command buttons
in the User Accounts area of the window.
The User Accounts area lists the names of all users currently registered with the server.
Once you register a database user, the user’s name is listed in the User Accounts area.
When you select a user account name, the Database Access area lists all of the databases
that the selected user can access on this server. For information about managing
Database Access, see section 6.5.3.
To register a database user and set a user’s access level:

1. Using the procedure described above, display the Accounts view.
2. In the User Accounts area, click New.
The New User Account dialog box appears.
Figure 6-6. New User Accounts Dialog Box
3. In the Name box, type the name of the user you want to register.
A name can be any alphanumeric string, up to 14 characters long. User account
names are case-sensitive.
4. In the Password box, type a password for this user.
If this user will have administrator privileges, you must supply a password. If this is
a normal user, a password is optional. A password can be any alphanumeric string
up to seven characters long. Passwords are case-sensitive.
5. In the Home Device list box, select a home database device for this user.
Velocis will use this database device to locate databases that the client creates
through the database schema.
6. If you want this user to have administrator-privilege-level access, click the Admin
Privilege Level box. If you do not check this box, the user has normal access
privileges.
7. Click OK.

Note: Velocis SQL specifies user names as identifiers for use with the grant statement (as
described in section 6.5.4). If you are using the ANSI standard form of grant, you must
register user names with Velocis in uppercase form. Velocis SQL also provides a
nonstandard form of the grant statement that allows you to specify a user name as a
string.
Now that the user is registered with the server, you can authorize the user for access to
one or more databases, using the procedure described in section 6.5.3.
6.5.2.2 Modifying a User Account

A user with Administrator privilege level can use Velocis Administrator to change a
user’s password, home database device, or access level.
To change a user’s password:

1. From the User Accounts list, select the name of the user whose password you want
to change.
2. In the User Accounts area, click Edit.
The Modify User Account dialog box appears.
3. In the Password box, select the asterisks representing the current password. Type
the new password.
A password can be any alphanumeric string up to seven characters long. Passwords
are case-sensitive.
4. Click OK.
To change a user’s home database device:
1. From the User Accounts list, select the name of the user whose home database
device you want to change.
3. In the Home Device list box, select the new home database device.
4. Click OK.
To change a user’s access level:
1. From the User Accounts list, select the name of the user whose access level you want
to change.
3. In the Admin Privilege Level check box, click to set or to clear the box.
(If the box is not checked, the user has normal access privileges.)
4. Click OK.

6.5.2.3 Deleting a User Account
With the Accounts view displayed, use the following procedure to delete a user’s account
from a server.
To delete a user’s account:

1. From the User Accounts list, select the name of the user whose account you want to
delete.
2. In the User Accounts area, click Delete.
operation will delete the user account from the server. Are you sure?"
3. Click OK.
6.5.3 Managing Database Access

Once you have created a user account for a client, you must authorize the user to access
the necessary databases. This section provides instructions for using Velocis
Administrator to authorize user access to both Core and Velocis SQL applications.
However, for a Velocis SQL user, this procedure only enables select statements for a
database with public access when the user connects to Velocis for the first time. If the
user needs to be able to issue other types of statements, you must set up data access and
command privileges as described in section 6.5.4.
Note: Velocis provides an alternative method for authorizing user access to a database
that may be more convenient to use if you are adding a new database to an already
configured and operating Velocis server. That method allows you to access a dialog box
from the Databases view window and to select those users you want to have access to the
database from a list of the currently registered users. For information, see section 6.4.1.1.
6.5.3.1 Setting Up Database Access and Permissions

To use Velocis Administrator to authorize database access, you display the Accounts
view window. See section 6.5.2 for information about the Accounts view and for a screen
shot of the Accounts view window (Figure 6-5).
When you select the name of a user in the User Accounts area of the Accounts view
window, the Database Access area of the window lists all the databases that user
currently can access. To manage database access, you use the buttons in the Database
Access area.
Using the procedure described in section 6.5.2.1, display the Accounts view.

To authorize database access and set a user’s database permissions:
1. From the User Accounts list, select the name of the user you want to have database
access.
2. In the Database Access area, click New.
The New Database Access dialog box appears.
Figure 6-7. New Database Access Dialog Box
3. In the Database Name list box, select the name of the database you want the user to
access.
4. If you want the user to have more than just Read permission for the database, click
the appropriate check boxes: Insert, Update, or Delete.
(Note that Read access permission is automatically checked for any user granted
database access.)
5. Click OK.
6.5.3.2 Changing a User’s Database Permissions

With the Accounts view displayed, use the following procedure to change the
permissions a user has for a database.
To change a user’s database permissions:

1. From the User Accounts list, select the name of the user whose permissions you
want to change.
2. From the Database Access list, select the database for which you want to change
permission.
3. In the Database Access area, click Edit.
The Database Access dialog box appears.
4. In the check box for the permission you want to change, click to set or to clear the
permission.

You also can click the Set All check box to authorize the user to insert, update, and
delete database records or you can click the Clear All check box to remove all the
user’s permissions.
5. Click OK.
6.5.3.3 Removing Database Access

With the Accounts view displayed, use the following procedure to remove a user’s access
to a database.
To remove a user’s database access:

1. From the User Accounts list, select the name of the user whose access you want to
remove.
2. From the Database Access list, select the database for which you want to remove
access.
3. In the Database Access area, click Delete.
will remove the access record from the server. Are you sure?"
4. Click OK.
6.5.4 Setting Up Velocis SQL Database Access Privileges

Security and access permission for an SQL database is different than for a Core database.
A database for a Velocis SQL application is created and registered when the sddlp utility
compiles the database schema. Velocis SQL databases are marked as global in Velocis
Administrator and cannot be changed, even by a user with administrator privilege.
Therefore, you cannot use the Velocis Administrator utility to administer security for
such a database. The only way to control access rights to a Velocis SQL database is by
using the Velocis SQL grant and revoke statements.
Velocis provides two types of access privileges for a Velocis SQL database: database
access and command. Database access privileges set limits on database use and
operations. Command privileges specify the kinds of Velocis SQL statements available to
a user for database manipulation.
At creation, a Velocis SQL database is owned by the client running the sddlp utility.
Initially, only you and this owner have complete access privileges (both database access
and command) to the Velocis SQL database. For other users to be able to access the
database, either you or the owner must issue grant statements on each table in the
database for each user who is to have data access privileges. If you want all users to have
access to the database, you can use the grant statement to grant public access.

You also use the grant statement to set up command privileges for the database. When a
new Velocis SQL user is registered (using the procedure described in section 6.5.2.1),
Velocis only allows the user to issue select statements. For the user to be able to execute
other database access statements besides select (for example, insert or the commands for
running sddlp), you or the database owner must assign specific command privileges.
To manipulate a Velocis SQL database, a user must have both table and command
privileges. For example, Velocis does not allow a user without delete command
privileges to issue a delete statement, even if delete data access privileges have been
granted.
Velocis logs, in the syscat database, all Velocis SQL grant and revoke statements that it
executes. As the system administrator, you can track each statement based on the user
who issued it and the server object to which the grant or revoke statement pertains.
Caution: A user who issues a Velocis SQL statement for which access privileges have not
been granted receives an access rights violation error message (errACCESS) from Velocis.
See Chapter 18 of the Velocis Reference Manual for a description of this message.
6.5.4.1 Using rsql to Set Up Access Privileges to a Velocis SQL Database

Use the following process to set up access privileges for a particular Velocis SQL
database.
1. At the operating system command prompt, start the rsql utility.
2. Make the following query to display the security statements issued by all users.
select user_name, issued, txtln from sysseclog, systext
where sysseclog.log_addr = systext.log_addr;
3. To find all security statements issued on the database, use a query similar to the
following example, which is based on the sales sample database.
select syslookup.name, user_name, txtln
from syslookup, sysseclog, systext
where syslookup.lookup_addr = sysseclog.obj_addr
and sysseclog.log_addr = systext.log_addr
and syslookup.qual_name = "SALES"
4. For each user, use the grant statement to assign database access and command
privileges as required. For details, see sections 6.5.4.2 and 6.5.4.3.
5. Exit rsql by entering .q at the prompt.
If you issue a grant command while a user is logged into Velocis, the user will have to log
out and then log in again in order to use the new permissions.

6.5.4.2 Using the grant Statement to Assign Database Access Privileges
Database access privileges allow users to manipulate database tables, views, and
columns. You can assign these privileges by using the simple grant statement with the
privileges designated as described in Chapter 4 of the Velocis Language Guide. Note that
you can restrict access to the columns and rows of a table by granting access to certain
views instead of the base table itself.
In the example below, the system administrator or database owner is allowing all users
privileges to issue select statements to query invntory database tables. Only users
George and Martha have permissions to modify the database.
grant select on invntory.product to public;
grant select on invntory.outlet to public;
grant select on invntory.on_hand to public;
grant all on invntory.product to "George", "Martha";
grant all on invntory.outlet to "George", "Martha";
grant all privileges on invntory.on_hand to "George", "Martha";
The following example illustrates how you can use a view to restrict access to a portion of
a database table.
create view skk_customers as
select * from customer where sale_id = "SKK"
with check option;
grant all privileges on skk_customers to sidney;
6.5.4.3 Using the grant Statement to Assign Command Privileges

You can assign command privileges by using the grant statement with the all commands,
all commands but, or commands clause, as required. This form of the grant statement is
defined in Chapter 4 of the Velocis Language Guide.
The example below grants permission for all users to issue any statements except DDL
statements. It allows only the users George and Martha to create databases.
grant all commands but create database to public;
grant all commands to "George", "Martha";
The next example restricts the user Jack to issuing select, update, and create view
statements.
grant commands create view, update to Jack;
6.5.5 Revoking Velocis SQL Database Access Privileges

This section provides instructions for deleting access privileges for a particular Velocis
SQL database.

6.5.5.1 Using rsql to Delete Access Privileges
Use the following process to delete access privileges for a particular Velocis SQL
database.
1. At the operating system command prompt, start the rsql utility.
2. Make the following query to display the security statements issued by all users.
select user_name, issued, txtln from sysseclog, systext
where sysseclog.log_addr = systext.log_addr;
3. To find all security statements issued on the database, use a query similar to the
following example, which is based on the sales sample database.
select syslookup.name, user_name, txtln
from syslookup, sysseclog, systext
where syslookup.lookup_addr = sysseclog.obj_addr
and sysseclog.log_addr = systext.log_addr
and syslookup.qual_name = "SALES"
4. For each user whose privileges require deletion, use the revoke statement as
described in sections 6.5.5.2 and 6.5.5.3.
5. Exit rsql by entering .q at the prompt.
If you issue a revoke command while a user is logged into Velocis, ask the user to log out
and then log in again in order to apply the changed permissions.
6.5.5.2 Using the revoke Statement to Delete Database Access Privileges

You can revoke previously granted database access privileges by using the simple form of
the revoke statement specifying the privileges. For information about using the
statement, see Chapter 4 of the Velocis Language Guide.
In the example below, the system administrator or owner is revoking George’s access
privileges for several tables of the invntory database.
revoke insert, update, delete on product from "George";
revoke insert, update, delete on outlet from "George";
revoke insert, update, delete on on_hand from "George";
The next example shows an rsql script that automatically drops the home_sales view
when user Martha’s access privilege on the salesperson table is revoked.

.c 1 RDS Admin xyzzy
grant select on salesperson to "Martha";
.c 2 RDS Martha HipposAreHip
create view home_sales as select sale_name from salesperson where office
= "SEA";
select * from home_sales;
SALE_NAME
Flores, Bob
Porter, Greg
Stouffer, Bill
Blades, Chris
.d 2
.c 1
revoke select on salesperson from "Martha";
.c 2 RDS Martha HipposAreHip
select * from home_sales;
**** RSQL Error 14002: table not found: HOME_SALES
6.5.5.3 Using the revoke Statement to Delete Command Privileges

You can delete command privileges using the grant statement with the all commands, all
commands but, or commands clause, as described in Chapter 4 of the Velocis Language
Guide. Note that the revoke all commands but form of the statement identifies the
commands from the restricted list that the user can still use.
6.5.6 Setting Up a Permanent Administrator Account

Because the user name and password that Velocis supplies for initial use by system
administrators are published defaults, they pose a security risk to your Velocis database
system. Therefore, you must remove the admin user account from each server.
However, before you remove the "admin" account from a server, you should create a new
account for yourself that has administrator privilege level. Follow the procedure in
section 6.5.2.1 to register a new user account for yourself with administrator privilege
level.
Once you have registered a new account for yourself with administrator privileges, you
can delete the admin user account, using the procedure described in section 6.5.2.3. Do
not deploy your Velocis database system until you have created a new administrator
account and deleted the admin account.
You also will need to set up database access for your new account. Follow the procedure
in section 6.5.3.1 to authorize database access and to allow yourself full permissions for
each database on the server. You do not have to authorize access to the databases
immediately, since administrator privilege allows you to do that at any time.

6.6 Configuring and Managing Server Extension Modules
Velocis allows a developer to extend server functionality by creating server extension
modules, which are described in Chapters 9 and 10 of the Velocis User’s Guide. To make
an extension module available to a server, you must install it on the server.
This section provides instructions for using Velocis Administrator to install an extension
module, to update an extension module, and to delete an extension module. You also can
use the rdsadm utility to perform these tasks.
6.6.1 Installing an Extension Module

To use Velocis Administrator to install an extension module, you display the Extensions
view in the Velocis Administrator window.
To display the Extensions view:

From the View Menu, click Extensions. (You also can display the Extensions view
by clicking the Extensions button on the toolbar.)
Figure 6-8. Extensions View

To install a server extension module:
1. From the Extension Modules list, click New.
The Install Extension Module dialog box appears.
2. In the Name box, type the name of the extension module.
The name must be a legal filename, up to eight characters long, without a file
extension. Name the extension module after the file that contains it (for example,
arfcns is the name of an extension module contained in arfcns.dll and mailmod is an
extension module in mailmod.nlm).
3. In the Device list box, select the device where the extension module is stored.
4. Click OK.
6.6.2 Updating an Extension Module

Before you attempt to update an extension module, make sure that no one is using the
extension module. After you update the extension module file, its new contents will be
used when an application loads the extension module.
Using the procedure described in section 6.6.1, display the Extensions view.
To update an extension module:

1. From the Extension Modules list, select the name of the module you want to update.
2. Click Edit.
The Update Extension Module dialog box appears.
3. In the Device list box, select the device where the extension module is stored.
4. Click OK.
6.6.3 Deleting an Extension Module

Before you attempt to delete an extension module, make sure that no one is using the
extension module.
Using the procedure described in section 6.6.1, display the Extensions view.
To delete an extension module:

1. From the Extension Modules list, select the name of the module you want to delete.
2. Click Delete.
will remove the extension module from the server. Are you sure?"
3. Click OK.

Chapter 7
Velocis Maintenance
This chapter provides procedures to use in maintaining Velocis. Sections 7.1 through 7.3
present routine maintenance procedures, such as those for backup and recovery. Section
7.4 specifically addresses troubleshooting and corrective maintenance for Velocis.
7.1 Checking for Database Corruption

Before backing up a server database, it is a good idea to check the physical consistency of
all databases. This way you can be assured that it is safe to restore from a backup. If you
think that a database is corrupted, you must run the dbcheck utility to examine its
physical consistency.
To examine all databases, run dbcheck without any database name identified:
dbcheck -a
You may check a specific database at any time by listing it on the command line:
dbcheck -a database_name
The dbcheck utility places the server into hot backup mode so the database files will not
change during the consistency check.
7.2 Backing Up the Server

Velocis performs a "hot" online backup of files, implemented through the Windows-based
Velocis Administrator (admin) or the command-line rdsadm utility. As described in
Chapter 3 of the Velocis User’s Guide, hot backup mode sets all server databases so that
they can be backed up while they remain active and accessible to users. Then, with the
databases in hot backup mode, you can physically back up all files to appropriate media.
During normal operations, you should use hot online backup mode and periodically save
database files. To support roll-forward recovery, you also need to back up any inactive
change log files. Then, if a database recovery is necessary, you can restore the database
files, restore the inactive change logs, and then execute the roll forward recovery utility
(dbreplay) to roll changes into the restored database to bring it up to date.
Velocis Maintenance 7-1

7.2.1 Selecting Files to Back Up
All data, key, and BLOB files for every database stored on the server, including catalog
and syscat, need to be backed up after entering hot backup mode. The backup indicator
log file, rdm.bil (stored in the catalog directory), also needs to be backed up in order to
support a possible later roll-forward recovery. The s_showBackupFiles administrative
function can be used from an application program to return a list of the fully qualified file
names of all of the files requiring backup.
7.2.2 Using Velocis Administrator to Back Up the Server

1. Using Velocis Administrator, log into the server that you want to back up. See
instructions in Chapter 5.
Note: If you are already logged into more than one server, select the window for the
one that you want to back up.
2. From the Server menu, choose the Start Backup option. The server system log
displays the message "Hot backup mode started -- N bytes allocated", where N
varies in proportion to the number of files managed by your server.
3. Archive the server databases using the physical backup procedures that you
normally use. You might copy the database files to another directory or to another
database device. Alternatively, you might use tape or other media to archive the
database and change log files.
4. With the backup complete, access the Server menu again and select End Backup.
The server system log displays the message "Hot backup mode ended".
5. Select Flush Hot File from the Server menu at any time following the End Backup to
migrate all remaining hot database pages from the hot file to the database files. It is
not necessary to flush the hot file. Velocis migrates the hot pages to the database
files as they are referenced with little performance impact.
6. Exit to the main menu and click Exit to leave Velocis Administrator.
Caution: Since backup is manual, Velocis has no way of knowing whether you have
actually backed up every file. Therefore, you must take care to back up all files. If you
miss a file, subsequent roll forward recovery will fail.

7.2.3 Using rdsadm to Back Up the Server
1. Access rdsadm as described in Chapter 5.
2. At the main menu command prompt, select 7 (Hot Backup). The backup utility
menu is displayed, as shown below.
1. Begin Hot Backup Mode
2. End Hot Backup Mode
3. Flush Hot File
4. Exit
Enter selection (1-4):
3. Select 1 (Begin Hot Backup Mode). The server system log displays the message "Hot
backup mode started -- N bytes allocated", where N varies in proportion to the
number of files managed by your server.
4. Archive the server databases using the physical backup procedures that you
normally use. You might copy the database files to another directory or to another
database device. Alternatively, you might use tape or other media to archive the
database and change log files.
5. With the backup complete, end the hot backup mode by selecting 7 from the main
menu, and then 2 (End Hot Backup Mode). The server system log displays the
message "Hot backup mode ended".
6. Select 3 (Flush Hot File) from the Backup menu, at any time following the End Hot
Backup, to migrate all remaining hot database pages from the hot file to the database
files. It is not necessary to flush the hot file. Velocis migrates the hot pages to the
database files as they are referenced with little performance impact.
7. When you are ready to exit from rdsadm, select 9 (Exit) at the main menu command
prompt.
Caution: Since backup is manual, Velocis has no way of knowing whether you have
actually backed up every file. Therefore you must take care to back up all files. If you
miss a file, subsequent roll forward recovery will fail.
7.3 Recovering the Server

As described in Chapter 3 of the Velocis User’s Guide, Velocis provides automatic
transaction recovery when the server process aborts abnormally. Transaction recovery is
accomplished by using the transaction change log, checkpoint indicator, and checkpoint
image system files described in the Velocis User’s Guide. No administrative intervention is
required for transaction recovery beyond restarting the server.

Database recovery, as opposed to transaction recovery, is necessary when database files
have been damaged (due to media failures such as a disk crash), and does require
administrative intervention. The only protection against such failures is a full backup as
described above. Velocis requires you to backup and restore all database files within the
server’s domain.
Database recovery involves restoring all database files from a backup, then optionally
performing a roll forward recovery using the change logs that were created since the
backup was performed.
7.3.1 Restoring Database Files

Database recovery must be done when the Velocis server is not running. To restore a
server’s database files, first shut the server down, then copy all files from the backup to
their original locations.
Caution: If you choose not to perform a roll forward operation immediately after
restoring the server backup, you will not be able to perform roll forward recovery later
without complete restoring the backup again.
7.3.2 Performing Roll Forward Recovery

The backup restore and roll-forward utility, dbreplay, must be executed immediately
following a reload of previously backed up database files. It replays the changes
recorded in the change logs that were created since the backup was performed. The
dbreplay utility is invoked as follows.
dbreplay [-bcnqv] [-L "user[;pw]"] [-s "mm/dd/yy hh:mm:ss"] [logfile]
• The -b option hides the program startup banner.

• The -c option causes dbreplay to prompt for confirmation to reprocess each
transaction. If the -s option is also specified, the confirmation prompts occur only
for transactions that began on or after the specified timestamp. The replay stops at
the first transaction that is denied.
• The -n option suppresses transaction reprocessing, but scans the change log files
and reports progress as specified. This option is typically used with the -v option
to display a list of the transactions in the log files.
• The -q (quiet) option disables all user prompts. It cannot be specified with the -c
option. It is useful when dbreplay is executed as part of a batch process.
• The -v (verbose) option displays the timestamp, transaction ID string, and name of
issuing user for each transaction to be reprocessed.
• The -L option specifies the name and password of an administrator user. If this
option is omitted, dbreplay prompts the user for the login information.

• The -s option stops replay processing on the first transaction that is later than the
specified date/time string. All transactions that began before that time are
completed, and those that began after that time are not processed. If the -c option
is also specified, then when dbreplay reaches that point in the processing, it
prompts the user for confirmation for each transaction. The user can then choose
to continue or stop processing.
• The [logfile] argument must be specified only if both the checkpoint indicator file
(rdm.chi) and the backup indicator log file (rdm.bil) are missing from the catalog
directory. If specified, logfile is the name of the first change log file that was active
when the backup was taken.
The dbreplay utility reprocesses all committed transactions in the change log files that are
present in the syslog directory. The specific change log files to be reprocessed are
determined by dbreplay, based on information stored in the checkpoint indicator file
(rdm.chi) and the backup indicator log file (rdm.bil). The rdm.bil file is created when
hot backup mode is entered, and contains the name of the initial change log file that was
created after backup mode was entered. The rdm.bil file should be saved and restored
along with all other database files. The most recent change log file name is stored in the
rdm.chi file. If both of these files are present in the catalog directory, dbreplay extracts
them and reports the file names. You will have the opportunity to confirm that they are
correct before the replay proceeds.
If the rdm.chi file is not available, dbreplay locates all change log files contained in the
syslog directory that have cycle values greater than or equal to the change log file name
found in rdm.bil. If rdm.bil is not available, all of the change log files contained in the
syslog are selected (beginning with logfile, if specified on the command line).
The dbreplay utility validates the consistency of all database files before starting. It
makes sure that the database files are consistent with the change log files.
7.4 Troubleshooting and Corrective Maintenance
7.4.1 Responding to Server Messages

Velocis displays two types of messages on the server machine: informational text
messages and diagnostic error messages. Velocis timestamps both message types so that
you know the time when a message was displayed. An image of the console log is stored
in the RDS.log file, in the current directory for the server.

7.4.1.1 Handling Informational Text Messages
The server displays an informational text message for each of the following events:
• Use of miscellaneous startup options
• Client login and logout (optional)
• Disconnection of a client application (optional)
• Database recovery (upon server startup)
• A change log cycle
In general, you do not need to take any specific action in response to an informational text
message. However, you will find the information useful for diagnosing certain problems.
7.4.1.2 Handling Diagnostic Error Messages

The server contains several diagnostic traps to ensure system integrity. When an internal
consistency check fails, the server displays a diagnostic error message on the server
machine. The server then attempts a controlled shutdown, which consists of logging out
all clients (aborting transactions, freeing locks, and closing database files), closing all
system files, and performing an exit back to the operating system.
Note: For less severe errors, instead of making a controlled shutdown, the server
displays an error message.
When you see a diagnostic error message on the server console, you should note the
information displayed. You can then attempt to correct the error by using the diagnostic
guide and corrective procedures presented below.
7.4.2 Diagnosing Problems

Table 7-1 is a fault isolation chart that lists different problems that can occur during the
installation and operation of Velocis. For each problem, we suggest a solution and refer
you to a corrective procedure, provided either in section 7.4.3 of this chapter or in another
part of the book.

Table 7-1. Fault Isolation for Velocis
Symptom Diagnosis Solution

Startup Faults
The rsql or Velocis Diagnosis 1: The Velocis server Verify that the utility can
Administrator utility cannot is not yet running. run. See section 7.4.3.1.
connect to the server.
Velocis issues an ODBC error Although odbc.ini registry Correct the ODBC data
when attempting to connect to a settings contain a direct path to source connect error. See
data source. the Velocis ODBC driver, this section 7.4.3.2.
driver needs to load other
Velocis DLLs. Possibly they are
not listed for the PATH variable.
The server exits with a fatal Velocis cannot find the path to Verify the system catalog
error message that it failed to the system catalog in the path. See section 7.4.3.3.
open the system catalog, or the CATPATH variable.
message: "Unable to start
server".
The server does not indicate There is a server configuration Look for any messages in
"Ready" in its startup screen. problem, such as a parameter the RDS.log and correct the
setting for too many cache issue.
pages.
When you start Velocis, it exits The system catalog is empty. Reinstall the system catalog
with this fatal error message: as instructed in Chapter 3.
"Failed to find system
configuration record".
Installation Faults
The server indicates this Velocis does not recognize the Update the Velocis search
message: specified name. path. See section 7.4.3.4.
"The name specified is not
recognized as an internal or
external command, operable
program, or batch file".

Table 7-1. Fault Isolation for Velocis (continued)

UNIX Faults
For UNIX, the rds server The path variable has not been Correct the UNIX dynamic
program fails to execute. For set, has been set to the wrong library path variable. See
HP-UX 11, the operating system directory, or has not been section 7.4.3.4.
issues a message similar to this: exported.
"/rds/v131b35/dll/hpux//lib_
exif.so: can’t open file: errno=2".
The message for AIX 4.3 is
similar to that for HP-UX 11.
For the other UNIX platforms,
the message is like this:
"ld.so.1: rds: fatal: lib_exif.so:
can’t open file: errno=2".
After a number of clients have The UNIX system might not Check and increase the
logged in, the server exits with have enough sockets. socket limit. One socket is
this message: needed for each login, plus
"accept() failure, errno = 6". one for each client
connection running on the
same computer. You need
additional sockets for
additional programs.
Client Application Faults

An extension module fails to Velocis cannot locate the Prepare the extension
load. module, or the module cannot module for loading. See
find other modules that it section 7.4.3.5.
requires.
A UDP module fails to load. Velocis cannot locate the UDP Prepare the UDP for
module, or the module cannot loading. See section 7.4.3.6.
find other modules it requires.
Velocis cannot register The UDF module is not on the Prepare the UDF for
functions in a UDF (via the SQL specified database device, or the registration. See section
create function statement). module cannot find other 7.4.3.7.
modules that it needs.

Table 7-1. Fault Isolation for Velocis (continued)

Client-Server Communication Faults
General error code -2008 has The client and server cannot Check client-server
been issued by the vping, communicate. communications. See
Velocis Administrator, or section 7.4.3.8.
rdsadm utility.
When Velocis for Windows NT The drive has been mapped Change access for the
4.0 is running as a service, it from the network. service. See section 7.4.3.9.
cannot access a drive. It first
fails when a database device is
specified with a networked
drive.
When rdsadm, sddlp, or These DOS utilities do not Run the utility from a local
ddlproc attempts to copy over operate properly if a file being hard drive, or delete any
an existing file, the utility fails copied from the server to the old output files before
with a message similar to this: current directory already exists. running the utility.
"52 open|write error for file ’...’
". The existing file is not
modified.
Database Access Faults

The Velocis Administrator Diagnosis 1: The velocis.ini Properly set up the
utility cannot create a database MinFreeDiskSpace parameter database device. See
device. indicates too low a threshold for section 7.4.3.10.
database device. Velocis can
only start in read-only mode. It
cannot create the database
device or run Velocis
Administrator on databases.
Diagnosis 2: You have tried to Properly set up the
create two database devices, database device. See
represented in the same way section 7.4.3.10.
and pointing to the same path.
Running Velocis Administrator You have tried to create two Be sure the path specified
on a database fails. database devices, represented in for the .dbd file exactly
different ways and pointing to matches the path of the
the same path. specified database device.
A dbcheck utility error is raised The database is corrupted. Repair the database. See
during a database check. section 7.4.3.12.

7.4.3 Correcting Velocis Faults
7.4.3.1 Verifying that the Utility Can Run (Windows 95/98, Windows NT 4.0/2000)
1. Check whether the location of the Velocis DLLs is reflected in the PATH
environment variable.
2. Verify that CATPATH points to the Velocis catalog directory and PATH points to
the Velocis DLL and EXE files.
3. If you do change an environment variable, shut down Velocis and restart it as
described in Chapter 5.
7.4.3.2 Correcting an ODBC Data Source Connect Error

1. Verify the server connection. Some hints for doing this are provided in section
7.4.3.9.
2. Make sure that ODBC driver’s location is reflected in the PATH environment
variable.
3. If the error has occurred in a 32-bit ODBC application, run instodbc to set up the
data source.
instodbc dll_path server_name
Note: If you installed your Velocis DLLs to your Windows system directory during
setup, use that as your DLL path when running instodbc.
4. If you do change the environment variable, shut down Velocis and restart it as
7.4.3.3 Verifying the System Catalog Path

1. In the execution environment or shell, check the CATPATH environment variable to
make sure that it is set to the location of the system catalog (for example,
c:\Centura\Velocis Server\Catalog).
2. If necessary, set CATPATH properly so that Velocis can find the system catalog. If
the CATPATH variable is set correctly, the problem might be database corruption.
See the Database Access Faults section of Table 7-1.
3. If you do change the CATPATH variable, shut down Velocis and restart it as

7.4.3.4 Correcting a UNIX Dynamic Library Path Variable
Run the install batch file that is in the Velocis home directory with the following
command:
sh ./install
This creates two batch files called rdshome.csh (for the C shell) and rdshome.sh (for the
Bourne and related shells). If you are using the C shell, run the following command:
source ./rdshome.csh
If you are using the Bourne shell, run this command:

. ./rdshome.sh
If these do not set your environment correctly, you need to set your environment
manually as shown below.
1. If you are using the Bourne shell for AIX 4.3, locate the rdshome.sh script file and set
the LIBPATH variable as follows.
LIBPATH=/velocis/bin; export LIBPATH
If you are using the C shell for AIX 4.3, locate the rdshome.csh script file and set
LIBPATH.
setenv LIBPATH /velocis/bin
If you are using the Bourne shell for HP-UX 11, locate the rdshome.sh script file and
set the SHLIB_PATH variable.
SHLIB_PATH=/velocis/bin; export SHLIB_PATH
If you are using the C shell for HP-UX 11, locate the rdshome.csh script file and set
SHLIB_PATH.
setenv SHLIB_PATH /velocis/bin
If you are using the Bourne shell for UnixWare 7, Sparc Solaris, Intel Solaris, Linux,
or BSDI, locate the rdshome.sh script file and set the LD_LIBRARY_PATH variable.
LD_LIBRARY_PATH=/velocis/bin; export LD_LIBRARY_PATH
If you are using the C shell for UnixWare , Sparc Solaris, Intel Solaris, Linux, or
BSDI, locate the rdshome.csh script file and set LD_LIBRARY_PATH.
setenv LD_LIBRARY_PATH /velocis/bin
2. Shut down Velocis and restart it as described in Chapter 5.

7.4.3.5 Preparing an Extension Module for Loading
1. If Velocis cannot find an extension module, make sure that the module is registered
by the correct name in the system catalog. For Velocis Administrator, you can check
the module by selecting Extensions from the View menu. For rdsadm, you can
select Show from the main menu, and then choose Show Extension Modules.
2. Ensure that the extension module exists in the directory referenced by the associated
database device.
3. Ensure that the server environment includes paths to all modules to which the
extension module has been linked.
7.4.3.6 Preparing a UDP for Loading

1. If Velocis cannot find a UDP module, make sure that the module is registered by the
correct name in the system catalog. You can do this through rsql by issuing the
following command.
select * from sysproc;
2. Ensure that the UDP module exists in the directory referenced by the associated
database device.
3. Ensure that the server environment includes paths to all modules on which the UDP
module depends.
7.4.3.7 Preparing a UDF for Registration

1. Make sure that the UDF is registered by the correct name in the system catalog. If it
is registered, you can verify it by running rsql and issuing the following command.
select name, device from sysfunc;
The result set lists registered functions and the devices that contain the DLLs.
2. Ensure that the database device mentioned in the create function statement contains
the UDF.
3. Ensure that the server environment includes paths to all modules on which the UDF
module depends.
7.4.3.8 Checking Client-Server Communications

1. Ensure that the server is running properly by checking the server screen. If it
indicates "Ready" it is operational.
2. Verify that the client software was installed correctly. To do this, ensure that you do
not have any DLLs with a length of 0 bytes.
3. Make sure that you can connect to the server machine through your regular network
protocols. If you cannot connect, a network communications problem is indicated.

4. Make sure that any required patches and libraries have been installed on both client
and server platforms. See Chapter 2 for environment details for all platforms.
7.4.3.9 Changing Access for a Windows NT 4.0/2000 Service

To allow Velocis, while running as a Windows NT 4.0/2000 service, to access drives
mapped from the network, you must modify the NT registry and restart the operating
system.
1. Start the Registry Editor (regedt32 or regedit).
2. From the \HKEY_LOCAL_MACHINE subkey, go to the "Parameters" key in the
SYSTEM section of the editor. This key is found in the following hierarchy:
\CurrentControlSet
\Services
\LanmanServer
\Parameters
3. From the Edit menu, select Add Value.
4. For the Value Name field, enter: RestrictNullSessAccess
5. In the Data Type area, select REG_DWORD and click OK.
6. Access the DWORD Editor and enter 0 for Data. Click OK when finished.
7. Exit the Registry Editor.
8. Reboot Windows NT 4.0/2000.
7.4.3.10 Setting Up a Database Device

1. Use Velocis Administrator (Server menu) or rdsadm (Configuration) to access the
[Server] section of the velocis.ini file. Now lower the value of the MinFreeDiskSpace
parameter so that Velocis does not start in read-only mode. Alternatively, you can
free space on your disk by deleting files.
2. Review the database devices using the appropriate administrative utility for your
platform. Make sure you do not have the database device pointing to the same path
as another database device.
3. Make sure that the database device path actually exists on your machine.
4. Shut down Velocis and restart it as described in Chapter 5. Remember that most
new parameter settings do not take effect until you restart the server.
Note: You can change Velocis parameters after the server starts, but only before you
open a database.

Appendix A
velocis.ini File Parameters
A.1 Velocis Server Parameters

Velocis server parameters are contained in the velocis.ini file. The velocis.ini file has the
standard .ini format and is divided into the file sections shown in Table A-1.
Table A-1. velocis.ini File Parameter Reference
.ini Section Name Location

[Server] Described in A.3.
[Engine] Described in A.4.
[SQL] Described in A.5.
[Environment] Described in A.6.
[Extensions] Platform dependent. Not described in manual.
In addition, the velocis.ini file contains parameters for network transports. For
information about platform-specific parameters, see the readme.txt file.
Parameters are specified in the following format:
<parameter name>=<value>.
In a parameter name, case is not significant.
A.2 Changing a velocis.ini File Parameter

Changing the default values for some of your server parameters often can improve the
performance of a Velocis database system significantly. For instructions on how to
change a parameter, see Chapter 6, section 6.1.1.
You can change a parameter value at any time, even while the server is running. You do
not have to reboot or restart a server after you change a parameter value. However,
because many parameters relate to startup conditions, changes to their values do not take
effect until you restart the server.
velocis.ini File Parameters A-1

A.3 [Server] Section Parameters
The [Server] section of the velocis.ini file contains configuration parameters related to
starting up the server application. An application server could choose to use these same
values or get equivalent information elsewhere. Most of the parameters for this section of
the velocis.ini file are described in Table A-2.
Table A-2. [Server] Section Parameters
Parameter Description
CTRL_BREAK_EVENT If set to 1, specifies that the window running the server
is to give Velocis a shutdown signal if the Service
Control Manager issues a stop command. If this
Windows NT-specific parameter is set to 0, the server is
killed.
CTRL_C_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal upon entry of <Ctrl+C>
from the login window. If this Windows NT-specific
parameter is set to 0, the server is killed.
CTRL_CLOSE_EVENT If set to 1, specifies that the window running the server
is to give Velocis a shutdown signal when an application
is closed. If this Windows NT-specific parameter is set
to 0, the server is killed.
CTRL_LOGOFF_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal when the client logs out of
the server. If this Windows NT-specific parameter is set
to 0, the server is killed.
CTRL_SHUTDOWN_EVENT If set to 1, specifies that the window running the server
is to issue a shutdown signal upon server shutdown. If
this Windows NT-specific parameter is set to 0, the
server is killed.
NumRPCThreads Specifies the number of worker threads the RPC system
should start up when it is initialized. The default is 16.
This is indicates the maximum number of remote client
requests that can be handled simultaneously. Other
request will be queued until one of the threads finishes
its work and is available to work for another client.
A-2 Centura Velocis Installation/Administration Guide

Table A-2. [Server] Section Parameters (continued)
RemoteShutdown Specifies 1 (default) to enable remote shutdowns

through calls to the s_shutdown function. This
parameter specifies 0 if the function is disabled. Only an
administrator user can shut down the server, but for
added security, this can be set to 0 to indicate that the
server can only be shut down locally.
ServerName Specifies the default name of the server. The server uses
this name if another name is not specified on the server
command line at startup. Some platforms are case-
sensitive to this name.
WordsPerStackFrame Specifies the number of words per stack frame (default
5000). Each server thread is assigned a stack, defined in
words, determined by platform-specific integer size. For
example, when a platform uses a 32-bit integer, the
actual stack size is four times the value of this parameter.
A.4 [Engine] Section Parameters

The [Engine] section of the velocis.ini file contains configuration parameters reflecting
the runtime engine’s operational characteristics and sizes that are stored in the catalog
database. Most of the parameters for this section of the file are described in Table A-3.
Table A-3. [Engine] Section Parameters
Archiving Specifies 1 (default) if the server archives inactive
change log files, and 0 if it deletes the files when they are
cycled. If you want to perform roll forward recovery, set
this parameter to 1.
AsyncTransactions Specifies 0 (default) if the server commits transactions
immediately (before the d_trend or SQLCommit
function returns), and 1 if it delays them. Every
transaction commit requires at least one file write. The
default value of 0 forces the server to flush a transaction
end marker to the change log file, making transaction
changes permanent. A value of 1 places the transaction
in the internal change log buffer until the buffer
overflows, possibly committing dozens of transactions at
once with one file write.

Table A-3. [Engine] Section Parameters (continued)
AutoLoadModules Specifies a list of extension modules to be loaded by the

server at server startup. To add modules, add them to a
comma-separated list.
AutoLoadEnvelopeModules Specifies a list of extension modules to be loaded by the
server at server startup when the RPC subsystem is
loaded. By default, _erdm and _esql are loaded. If
_esql is not needed, it may be removed. To add
modules, add them to a comma-separated list.
ChangeLogBufSize Specifies the size, in bytes, of the change log buffer to
which Velocis logs database modifications for recovery
purposes. The default is 2MB. When the buffer is full,
Velocis flushes it to the change log file. The larger the
buffer, the fewer times Velocis must flush it. However,
since checkpoints and transaction commits and aborts
also require flushing of the change log, there is a point
beyond which a larger buffer size has little value.
ChangeLogDevice Specifies the name of the device in which the server
places change log files (.chg extension). The default
name is "sysdev".
ChangeLogSize Specifies the default size the change log will grow to
before attempting to cycle the log file. When it reaches
this size, the cycle function enters an “oportunistic”
mode where it will cycle the next time no transactions
are active. If the log file reaches double this size without
having cycled, the cycle function will try stopping new
transactions for a timeout period while it waits for
existing transactions to complete.
CheckPointDevice Specifies the name of the device in which the server
places the checkpoint image file (rdm.chk). The default
name is "sysdev".
CheckPointThreshold Specifies the percentage of cache pages modified when
the server generates a checkpoint (default 40 percent).
By default, 40 percent of 700 cache pages is 280 pages.
When 280 pages contain modified data, the server
generates a checkpoint. Either this parameter or
MaxCheckpointSize can trigger a checkpoint.

FileCommit Specifies 1 (default) if Velocis is to perform a file sync

operation when it completes each checkpoint operation
on each database file (on some platforms the operation
uses write-through or unbuffered writes). In a file sync
operation, Velocis makes sure that data has been written
to disk before proceeding in critical situations, such as
during a transaction commit. Setting this parameter to 0
disables the file sync operation.
FileCreateSize Database files are given this initial size when the
database is initialized. If no FileCreateSize is given, 512
bytes will be used. Larger values of FileCreateSize may
be used to increase the chances that disk blocks will be
allocated together.
FileExtendSize Specifies the number of bytes by which Velocis extends a
database file when the current file is full. The default is
platform-dependent.
FileHandleLimit Specifies the maximum number of file handles that the
Velocis server can open simultaneously (default
platform-dependent). The server selectively uses the
available file handles to perform input and output for
currently used files. When it needs to open additional
files, it closes less recently used files and reuses their
handles for the new files. The file handle limit does not
limit the number of files that the server can use.
FreeSpaceDiskCheckDelay When there is plenty of disk space, Velocis will only
periodically check the disk space rather than check it on
every file expansion. This value indicates the time to
wait between checks and is specified in seconds.
IOThreadPriority Specifies the priority of threads that will service the
change log, perform checkpoints, or read database
pages. Values are LOW, MEDIUM, or HIGH. On
Windows NT and Windows 95, this translates into a
SetThreadPriority call.

LogBlobs Specifies the method in which BLOB data is logged. The

available settings are listed below. If this parameter is
not specified, a value of 1 is used.
0 Default logging is off. Call d_bloblog to change.
1 Default logging is on. Call d_bloblog to change.
2 Never log BLOB data. Cannot be changed.
3 Always log BLOB data. Cannot be changed.
LogCheckpoints Set this to a non-zero value to cause the server to write a
notification to the server log that a checkpoint is
occurring.
MaxCachePages Specifies the maximum number of pages of database
cache (default 700). The cache stores frequently accessed
pages from data and key files. Memory requirements of
the cache depend on page sizes. The default page size is
1K, but the developer can specify this size as desired in
the database schema.
MaxChangeLogBlocks Should be set equal to MaxTrends. Default is 10.
MaxCheckPointSize Specifies the maximum size of the dynamically allocated
checkpoint buffer containing modified database pages to
be written to the database files during a checkpoint
operation (default 300,000 bytes). When the checkpoint
buffer reaches the specified size, a checkpoint occurs (if
not already generated by the CheckPointThreshold
criteria).
MaxTrends Specifies the maximum number of transaction commits
(d_trend calls) to be accumulated before forcing a flush
of the change log from memory to disk. By default, this
is one third of the sum of normal and priority threads
(NormalThreads+PriorityThreads)/3. This parameter only
affects transaction performance when transactions are
committed at a rate of several per second.
MaxTrendWait Specifies the number of milliseconds that will be spent
waiting for transaction commits before forcing a flush of
the change log from memory to disk. This parameter, or
MaxTrends, controls the frequency of change log
flushing.

MaxUsersOn Specifies the maximum number of clients who can log

into the server at once (default 8). The value of this
parameter must be less than or equal to the licensed limit
of logins. Even with an unlimited license, you should
still set this value to a reasonable limit (such as 120) to
limit resources that Velocis must allocate during server
startup.
MemoryLimit Specifies a limit, in bytes, on memory expansion capacity
(default -1). You can use this limit to prevent the server
from degrading or crashing when the size of the cache is
automatically expanded. The server only checks the
memory limit when it needs to expand the cache. If the
limit is reached, the server may suspend foreground
tasks until the checkpoint releases more cache pages.
MinFreeDiskSpace Specifies the minimum amount of free disk space
allowed by the server (default 5,120,000 bytes). During
server startup and file expansion, Velocis checks the disk
space available on the volume containing the file. If the
space is less than the amount specified by this
parameter, the server enters read-only mode.
NCPThreadPriority Specifies the priority of threads that will service the
Network Communications Processor (NCP). Values are
LOW, MEDIUM, or HIGH. On Windows 95 or
Windows NT, this translates into a SetThreadPriority
call.
SkipLoginLogout Specifies whether the system should log all login, logout,
and abort messages to the screen and log file (or log
function for an application server). A 1 (default)
indicates the system should log these messages.

A.5 [SQL] Section Parameters
The [SQL] section of the velocis.ini file includes parameters that control Velocis SQL
operation. Table A-4 describes those parameters.
You can override the system catalog parameters set in the syscat database by changing
those parameters in the [SQL] section of the velocis.ini file. (It is no longer necessary to
use an SQL update statement to change these parameters.) You can use either Velocis
Administrator or the rdsadm utility to change those parameters.
Table A-4. [SQL] Section Parameters
ColStats Specifies the state of column statistics. A value of 1 (default)
indicates that the SQL module maintains maximum and minimum
values for every column for use by the Velocis internal SQL
optimizer. A value of 0 turns off column statistics, saving server
memory.
CurrSymb Specifies the system currency symbol (default "$").
DateFormat Specifies the system date constant format (default 2, SQL standard):
1 MM-DD-YYYY
2 YYYY-MM-DD
3 DD-MM-YYYY
DateSep Specifies the system date separator character (default "-").
DecSymb Specifies the system decimal point symbol (default ".").
HisPrec Specifies the granularity of the update stats index file distribution
histogram. The default is 25 (meaning that counts are kept for each
25 percent increment). Finer granularity consumes more server
memory.
LockTime Specifies the wait time, in seconds, before a read lock times out
(default 30).
MaxDBs Specifies the size of the open database and open instance caches in
memory (default 16).
MaxEdges Specifies the size of the edge cache in memory (default 256).
MaxPrecision Specifies the maximum decimal precision (default 32).
MaxProcs Specifies the maximum number of UDPs that Velocis can cache
(default 24).
MaxScale Sets the maximum specifiable decimal scale (default 16).
MaxString Specifies the maximum length of a string literal (default 256).

Table A-4. [SQL] Section Parameters (continued)
MaxSubQVals Specifies the maximum number of correlated subquery result values

for Velocis to store (default 1024). If more rows are expected (or
returned), Velocis must evaluate the subquery for each outer row.
MaxTables Specifies the size of the table cache in memory (default 128).
MaxUDFs Specifies the maximum number of UDFs that Velocis can cache
(default 24).
MaxViews Specifies the number of views contained in the SQL view cache
(default 24).
MergeLimit Specifies the maximum number of tables for which views can be
merged (default 1).
OpenMode Specifies the default database open mode (default "s"). Possible
values are "s" and "x".
OptLimit Specifies the failure-to-improve iteration limit for the internal
Velocis SQL optimizer (default 1000).
OptYield Specifies the number of internal Velocis SQL optimizer iterations
allowed before the utility yields to the Velocis engine scheduler
(default 25).
SortLimit Specifies the number of result rows for which an external sort is of
little cost (default 0).
SortPgSz Specifies the size of the page in the SQL temporary sort database
(default 2048).
ThouSymb Specifies the system thousands separator symbol (default ",").
UseLogins Specifies the state of login and logout procedures. Possible values
are 1 for enabled (the default) and 0 for disabled.
Wildall Specifies the "match all like" pattern matching symbol (default "%",
ANSI standard).
Wildone Specifies the "match any like" pattern matching symbol (default "_",
ANSI standard).
A.6 [Environment] Section Parameters

The [Environment] section of the velocis.ini file contains server-side environment
variables that you set when you installed Velocis (Chapter 3) on your server. Table A-5
describes those parameters.

When Velocis internally queries the environment, it first searches for values in the
appropriate section of velocis.ini, and then in the environment for the particular
platform.
Table A-5. [Environment] Section Parameters
SQLDebug Turns on the level of SQL debug information. This is a bit map
which can be any combination of the following values:
1 Show compiled statements
2 Show expression tree
4 Show optimizer tables
8 Show execution plan
If this is non-zero, the debug output for each SQL statement is
written to a debug.xxx file, where xxx starts at 000 and increments
for each statement.
A.7 BLOB Data Logging

Logging of BLOB data is controlled through a Velocis configuration parameter named
LogBlobs and the d_bloblog function. The LogBlobs configuration parameter has four
values as described in the following table. The default value is 1.
Table A-6. LogBlob Configuration Settings
LogBlob Value Description

0 Default logging is off. Can be changed with d_bloblog call.
1 (default) Default logging is on. Can be changed with d_bloblog call.
2 Never log BLOB data. Cannot be changed with d_bloblog call.
3 Always log BLOB data. Cannot be changed with d_bloblog call.
The "default" options indicate the BLOB data logging option when d_bloblog is not
called. Note that all d_blob calls are logged. The logging option only indicates whether
the BLOB data itself is logged. Thus, the BLOB page allocations and BLOB structure
changes are always logged.

Appendix B
connect.ini File Parameters
B.1 Velocis Transport Protocol Parameters

Velocis transport protocol parameters are contained in the connect.ini file. The
connect.ini file has the standard .ini format. For information about platform-specific
parameters, see the readme.txt file.
Parameters are specified in the following format:
<parameter name>=<value>.
In a parameter name, case is not significant.
B.2 Changing a connect.ini File Parameter

You can change a parameter value at any time. However, because the client libraries
cache the information in the connect.ini file, changes to the parameter values do not take
effect until the client application is restarted.
B.3 Section types

The connect.ini file contains two sections: aliases and configuration. An alias organizes
all of the information about connecting to a particular server under a simple name. This
makes it simple to change where a server is located; simply change the information in the
alias section and no changes are needed to the source. Any number of aliases can be
defined. There can be one configuration section for each transport supported by the
client OS, and one generic configuration section.
B.3.1 Aliases
Each alias can have multiple parameters to describe how to find the server associated
with that alias. Table B-1 describes the alias parameters.
connect.ini File Parameters B-1

Table B-1. Alias Parameters
Parameter Transport Description

Protocol all Specifies which protocols to use when
connecting to the server. The value can be a
single protocol or a comma delimited list of
protocols, in which case protocols will be tried
in the order specified using the other parameters
in the alias section as necessary until connection
is made to a valid server. If a protocol is
disabled, that protocol will not be attempted. If
no value is specified, all the enabled protocols
are attempted.
Encryption all Specifies the encryption method to use for this
connection. No value or a value of zero means
no encryption.
Host TCP/IP Specifies the host on which to find the server. If
a name is specified, the name is used to look up
the host IP address via gethostbyname(). If an IP
address is specified in xxx.xxx.xxx.xxx format,
that address is used directly. If no value is
specified, the alias name is used to look up the
host IP address via gethostbyname(). A valid IP
address is necessary to connect via TCP/IP.
Port TCP/IP Specifies the port on which to connect to the
server. If no port is specified, the DefaultPort is
used if it exists. If no default exists, the port is
looked up via getservbyname(). A valid port is
needed to connect via TCP/IP.
Name Named Pipes, Specifies the specific server name to attempt to
Local, Unix connect to. If no name is specified, the alias
Domain Sockets name is used.
Node Named Pipes Specifies the node name on which the server
resides. If no node name is specified, the local
machine is checked. If the server is not local and
NamedServices is on, the network is searched for
a server of the specifed name.
B-2 Centura Velocis Installation/Administration Guide

Table B-1. Alias Parameters (continued)

Domain Named Pipes Specifies the particular domain to search if no
node is specified and NamedServices is on. If no
domain is specified, the entire local network is
searched.
Temp Local (Unix), Unix Specifies the same temporary directory that the
Domain Sockets server is using for the temporary files involved
in the Local and UNIX Domain Sockets
transports. If no value is specified, "/tm" is
used.
B.3.2 Configuration Sections

Each protocol can have a configuration section for parameters that are global to the
protocol. The section name for these would be [{protocol} Configuration] where
{protocol} could be TCP/IP, NP (Named Pipes), Local, or UD (UNIX Domain Sockets).
There is also a generic [Configuration] section. The only parameter in the generic
[Configuration] section is Sessions, which specifies the maximum number of sessions to
allocate per client application. This allows the client to allocate the minimum resources
necessary. The following table describes the {protocol} configuration sections.
Table B-2. Configuration Section Parameters

Enabled all Specifies whether the protocol should be used.
If disabled, the protocol gets skipped whenever
it is referenced by an alias. The default is 1.
DefaultPort TCP/IP Specifies a default port that may be used by all
aliases that do not specify a port.
PacketSize TCP/IP, Unix Specifies the chunk size of messages to send per
Domain Sockets packet. The default is 4096.
NamedServices Named Pipes Specifies whether to search the network for the
server if a node is not specified. This can be a
slot process and is not generally recommended.
The default is "off".
connect.ini File Parameters B-3

Index
faults 7-9
.cshrc file 4-7 client-server system 1-1
.profile file 4-7 communication problems See client-
A server communication
access faults. See database access faults configuration parameters A-1 to A-10
access levels 6-21 to 6-22 BLOB data logging A-10
access permissions 6-22 configuration process, overview 3-1
administrator account 6-33 configuring client environment
administrator privilege level 6-22, 6-26. on UNIX 4-7
See also normal privilege level on Windows 4-4 to 4-5
aliases configuring server environment
defining 2-9 on UNIX 3-9 to 3-10
parameters B-2 on Windows 3-6
autoexec.bat file 3-5, 4-4 connect.ini file 2-4, 2-8 to 2-12, 2-9, 5-10,
5-11, 5-12, 6-2, 6-4, 6-21, B-1 to B-3
B CONNPATH environment variable 2-8
backup 7-1 to 7-3 corruption of databases 7-1
Bourne shell 3-8, 3-10
D
C d_bloblog A-10
C shell 3-8, 3-10 daemon mode 5-2, 5-5
case 6-4, 6-8, 6-11, 6-23 database access 6-27 to 6-28
catalog 6-1, 6-2, 6-9, 6-10, 6-13, 6-14, changing user permissions
6-15, 6-21, 6-23 6-28 to 6-29
CATPATH 3-6, 3-9, 7-7, 7-10 global 6-17, 6-20
CATPATH variable 2-5 managing 6-27 to 6-28
cd command 4-6 removing 6-29
Centura setting up 6-27 to 6-28
Web home page 1-3 SQL databases. See SQL databases
client database access faults 7-9
installing, overview 3-1 database access lists 6-14
client application faults 7-8 database corruption
client software checking for 7-1
installing 4-1 to 4-7 database devices 6-9 to 6-15
installing on UNIX 4-5 to 4-7 changing 6-13 to 6-14
installing on Windows 4-1 to 4-5 configuring 6-9 to 6-15
installing on Windows NT 4-1 deleting 6-14 to 6-15
client-server communication managing 6-9 to 6-15
checking 7-12 registering 6-10 to 6-13
Centura Velocis Installation/Administration Guide Index-1

setting up 7-13 extensions view 5-8
database dictionary 6-17, 6-19, 6-20
G
database files
restoring 7-4 global transport parameters
databases 6-15 to 6-21. See also database defining 2-11
access grant statement 6-31
changing 6-19 I
configuring 6-15 to 6-21 insert permission 6-22
deleting database definitions installation
6-20 to 6-21 faults 7-7
initializing 6-19 process, overview 3-1
managing 6-15 to 6-21 instrds 5-3
registering 6-15 to 6-19 instrds utility 2-5
setting up 7-13
ddlproc utility 6-17 K
delete permission 6-22 Korn shell 3-8, 3-10
delete statement 6-30 L
devices. See database devices
LD_LIBRARY_PATH 7-11
devices view 5-8
LIBPATH 7-11
diagnosing problems 7-6 to 7-9
licensing 6-7
directory structure
changing 6-7 to 6-8
on UNIX 3-8 to 3-9
number of users 6-7. See also
on Windows 3-8 to 3-9
rdsadm; Velocis Administrator
dynamic library path
local transport for UNIX clients 2-14
correcting 7-11
local transport for UNIX servers 2-7
E local transport for Windows 95 clients
encryption 2-9 2-13
errACCESS message 6-30 local transport for Windows 95 servers
error message 2-5
access rights violation 6-30 LogBlobs parameter
active client at shutdown 5-14, 5-15 settings A-10
administrative rights 5-13 M
vping, sent by 5-12
MNCP 2-1
error messages 7-6
mount command 4-6
examples 6-23
Multi-Protocol Network
extension modules 6-34 to 6-35
Communication Processor 2-1
configuring 6-34 to 6-35
deleting 6-35 N
installing 6-34 to 6-35 Named Pipes 2-10, 2-12
managing 6-34 to 6-35 normal (user) privilege level 6-21. See
preparing 7-11 to 7-12 also administrator privilege level
updating 6-35 notational conventions, manual 1-2
Index-2 Centura Velocis Installation/Administration Guide

NT Named Pipes transport for registering a database 6-15 to 6-19
Windows 95 clients 2-12 registering a database device 6-12
shutting down server 5-13
O
rdshome.csh file 4-6, 4-7
objects 6-14 rdshome.sh file 4-6. 4-7
ODBC 2-3, 2-12, 2-13 read permission 6-22
ODBC data source connect error 7-10 readme.txt file 1-2
operating environment recovering a server 7-3 to 7-5
configuring, overview 3-1 registry 3-5
P Windows NT See Windows NT
parameter values Registry
changing 6-2 to 6-6. See also rdsadm; revoke statement 6-32 to 6-33
Velocis Administrator roll forward recovery 7-4 to 7-5
parameters 6-1 to 6-8 rpcinfo utility 2-7
server. See server parameters rsql utility 6-30, 6-32
PATH 7-7, 7-10 S
PATH environment variable 3-6, 4-4 sddlp utility 6-9, 6-15, 6-17, 6-29
PATH variable 4-5 select statements 6-24, 6-27, 6-30, 6-31
permissions 6-27 to 6-29. See also user server
accounts; database access. backing up 7-1 to 7-3
platforms. See Velocis, platforms installing, overview 3-1
supported logging in 5-7, 5-8, 5-9, 5-10
problems logging out 5-9
diagnosing. See diagnosing problems recovering 7-3 to 7-5
protocols. See Velocis, transport shutting down 5-14
protocols supported starting 5-1, 5-6
Q server extensions. See extension
query 6-22, 6-30, 6-31, 6-32 modules
server messages 7-5
R server parameters 6-2 to 6-7, A-1 to A-3
RDS.log file 3-9, 5-4 environmental section A-9 to A-10
rdsadm utility 5-3, 5-6, 5-9, 5-13. See also optimizing 6-2 to 6-7, A-1 to A-10,
Velocis administrtor B-1 to B-3
backing up server 7-2 to 7-3 server section A-3
changing a database device SQL section A-8
6-13 to 6-14 server problems. See diagnosing
changing licensed number of users problems
6-7 to 6-8 server section parameters A-2 to A-3
deleting a database device server software
6-14 to 6-15 installing 3-1 to 3-10
initializing a database 6-19 installing on UNIX 3-6
opening 5-9 installing on Windows 3-2 to 3-6

installing on Windows NT 3-2 to 3-6, U
server toolkit 3-5 UDF module problems 7-12
Service Control Manager 2-5, 5-3, 5-4, UNIX
5-14 client environment, configuring
services file 2-5, 2-6, 2-7, 2-10 4-5 to 4-7
setup options 4-3 client platform requirements 2-14
setup program dynamic library path variable
client software installation 4-2 to 4-4 See dynamic library path variable
server software installation 3-2 to 3-5 faults 7-8
SHLIBPATH 7-11 installing client software 4-5 to 4-7
Software License Agreement 3-3, 4-2 installing server software 3-6 to 3-10
SQL 6-7, 6-9, 6-15, 6-21, 6-24, 6-26, 6-27, server environment, configuring
6-29, 6-30, 6-31, 6-32, 6-33 3-9 to 3-10
SQL databases server platform requirements 2-6
access privileges 6-29 to 6-31 server, shutting down 5-14
revoking privileges 6-31 to 6-33 server, starting 5-5
SQL.ddl files 6-9 UNIX domain sockets
standalone platforms. See Velocis transport for UNIX clients 2-14
standalone platforms. transport for UNIX servers 2-7
standalone system update permission 6-22
installing software 3-1 user accounts 6-23 to 6-27
syscat 6-9, 6-30 creating 6-24 to 6-26
system administration utilities 5-5 deleting 6-27
system catalog path managing 6-23 to 6-27
verifying 7-10 modifying 6-26
system catalogs registering 6-24 to 6-26
copying 6-9
V
T Velocis
TCP/IP transport for UNIX clients 2-14 platforms supported 2-1 to 2-2
TCP/IP transport for UNIX servers 2-7 transport protocols supported
TCP/IP transport for Windows 95 2-1 to 2-2
clients 2-12 Velocis Administrator 5-2, 5-5 to 5-9,
TCP/IP transport for Windows 95 5-13. See also rdsadm
servers 2-5 backing up server 7-2
TCP/IP transport for Windows NT changing a database 6-19 to 6-20
clients 2-13 changing a database device
TCP/IP transport for Windows NT 6-13 to 6-14
servers 2-6 changing global access 6-20
transaction recovery 7-3 to 7-5 changing licensed number of users
troubleshooting 7-5 to 7-13 6-7 to 6-9
Index-4 Centura Velocis Installation/Administration Guide

changing parameter values 6-2 Windows 95 2-12 to 2-13
closing 5-9 Windows NT 2-13
deleting a database 6-20 Velocis environment 2-1 to 2-15
deleting a database device Velocis fault
6-14 to 6-15 correcting 7-9 to 7-13
deleting extension modules 6-35 Velocis server
granting global access 6-16 to 6-18 installing software 3-1 to 3-10
initializing a database 6-19 platforms
installing extension modules UNIX 2-6 to 2-7
6-34 to 6-35 Windows 95 2-4 to 2-5
opening 5-6 Windows NT 2-5 to 2-6
registering a database 6-15 to 6-19 Velocis standalone platforms 2-2 to 2-3
registering a database device 6-11 Velocis system
shutting down a server 5-13 configuring 6-1 to 6-35, A-1 to A-10,
toolbar 5-7 to 5-9 B-1 to B-3
updating extension modules 6-35 maintaining 7-1 to 7-13
Velocis client troubleshooting 7-1 to 7-13
installing software 4-1 to 4-7 velocis.ini file 2-3 to 2-7, 2-11, 3-6, 3-9,
platforms 5-5, 5-6, 6-2, 6-3, 6-4, 6-5, 6-7, 6-8, A-1
UNIX 2-14 to A-10, B-1
vping utility 5-6, 5-11, 5-12

Guia Oficial N°09. Vel30IA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guia Oficial N°09. Vel30IA

Uploaded by

Copyright:

Available Formats

Velocis

Installation and Administration Guide

Chapter 2 About the Velocis Environment

Chapter 3 Installing Velocis Server Software

Chapter 4 Installing Velocis Client Software

ii Centura Velocis Installation/Administration Guide

Chapter 6 Server Configuration

iv Centura Velocis Installation/Administration Guide

Chapter 7 Velocis Maintenance

Appendix B connect.ini File Parameters

vi Centura Velocis Installation/Administration Guide

viii Centura Velocis Installation/Administration Guide

1.1 Velocis Documentation

1.1.1 About This Manual

1.1.2 Related Velocis Documents

1.1.3 Document Conventions

Table 1-1. Document Notational Conventions

1-2 Centura Velocis Installation/Administration Guide

1.2 Other Helpful Resources

2.1 Transport Protocols Supported by Velocis

About the Velocis Environment 2-1

Windows NT 4.0 TCP/IP TCP/IP TCP/IP TCP/IP

Windows NT 2000 TCP/IP TCP/IP TCP/IP TCP/IP

* Does not use network services.

2.2 Standalone Velocis Platforms

2.2.1 Windows 95/98 and Windows NT 4.0

2-2 Centura Velocis Installation/Administration Guide

2.3 Velocis Server Platforms

Table 2-2. Velocis Server Platform Section Reference

Operating System Platform Network Transport Section

2.3.1 Configuring Server Transports

About the Velocis Environment 2-3

2.3.2 Windows 95/98 Server Platform

2.3.2.1 Windows 95/98 Platform Requirements

2-4 Centura Velocis Installation/Administration Guide

2.3.2.3 Local Transport for Windows 95/98

2.3.3 Windows NT 4.0 Server Platform

2.3.3.1 Windows NT 4.0/2000 Platform Requirements

About the Velocis Environment 2-5

2.3.3.3 TCP/IP Transport for Windows NT 4.0/2000

2.3.3.4 Local Transport for Windows NT 4.0/2000

2.3.4 UNIX Server Platforms

2.3.4.1 UNIX Platform Requirements

2-6 Centura Velocis Installation/Administration Guide

2.3.4.2 TCP/IP Transport for UNIX

2.3.4.3 UNIX Domain Transport for UNIX

2.3.4.4 Local Transport for UNIX

About the Velocis Environment 2-7

Table 2-3. Velocis Client Platform Section Reference

Operating System Platform Network Transport Section

2.4.1 Configuring Client Transports

2-8 Centura Velocis Installation/Administration Guide

2.4.1.1 Defining Aliases

About the Velocis Environment 2-9

2-10 Centura Velocis Installation/Administration Guide

2.4.1.2 Defining Global Transport Parameters

About the Velocis Environment 2-11

2.4.2 Windows 95/98 Client Platform

2.4.2.1 Windows 95/98 Platform Requirements

2.4.2.2 Named Pipes Transport for Windows 95/98

2.4.2.3 TCP/IP Transport for Windows 95/98

2-12 Centura Velocis Installation/Administration Guide

2.4.3 Windows NT 4.0/2000 Client Platform

2.4.3.1 Windows NT 4.0/2000 Platform Requirements