Pervasive PSQL v9 Service Pack 2

Transcription

Getting Started with Pervasive PSQL
Server Edition
Pervasive Software Inc.
12365 Riata Trace Parkway
Building B
Austin, TX 78727 USA
Telephone: 512 231 6000 or 800 287 4383
Fax: 512 231 6010
Email: [email protected]
Web: http://www.pervasive.com
disclaimer
PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND
DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS
IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS
OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC.
MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED,
REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION;
PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR
COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT
MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO
MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR
ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS.
trademarks
Btrieve, Client/Server in a Box, Pervasive, Pervasive Software, and the Pervasive Software
logo are registered trademarks of Pervasive Software Inc.
Built on Pervasive Software, DataExchange, MicroKernel Database Engine, MicroKernel Database
Architecture, Pervasive.SQL, Pervasive PSQL, Solution Network, Ultralight, and ZDBA are
trademarks of Pervasive Software Inc.
Microsoft, MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows Millennium,
Windows 2000, Windows XP, Win32, Win32s, and Visual Basic are registered trademarks of
Microsoft Corporation.
NetWare and Novell are registered trademarks of Novell, Inc.
NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are
trademarks of Novell, Inc.
Sun, Sun Microsystems, Java, all trademarks and logos that contain Sun, Solaris, or Java, are
trademarks or registered trademarks of Sun Microsystems.
All other company and product names are the trademarks or registered trademarks of their
respective companies.
© Copyright 2006 Pervasive Software Inc. All rights reserved. Reproduction, photocopying, or
transmittal of this publication, or portions of this publication, is prohibited without the express prior
written consent of the publisher.
This product includes software developed by Powerdog Industries. © Copyright 1994 Powerdog
Industries. All rights reserved.
This product includes software developed by KeyWorks Software. © Copyright 2002 KeyWorks
Software. All rights reserved.
This product includes software developed by DUNDAS SOFTWARE. © Copyright 1997-2000
DUNDAS SOFTWARE LTD., all rights reserved.
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/).
This product uses the free unixODBC Driver Manager as written by Peter Harvey
([email protected]), modified and extended by Nick Gorham ([email protected]), with
local modifications from Pervasive Software. Pervasive Software will donate their code changes to the
current maintainer of the unixODBC Driver Manager project, in accordance with the LGPL license
agreement of this project. The unixODBC Driver Danager home page is located at
www.unixodbc.org. For further information on this project, contact its current maintainer: Nick
Gorham ([email protected]).
A copy of the GNU Lesser General Public License (LGPL) is included on the distribution media for
this product. You may also view the LGPL at www.fsf.org/licensing/licenses/lgpl.html.
Getting Started with Pervasive PSQL v9 SP2 (Server edition)
May 2006
100-004289-004
Contents
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Who Should Read This Manual
Manual Organization . . . . . .
Getting Ready to Install .
Windows . . . . . . . . .
NetWare . . . . . . . . .
Linux . . . . . . . . . . .
After Installation . . . . .
Conventions . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xv
.
.
.
.
.
.
.
.
xvi
xvii
xvii
xvii
xviii
xviii
xix
xx
Getting Ready to Install
1
Welcome to Pervasive PSQL . . . . . . . . . . . . . . . . . . . . .
1-1
A Basic Introduction to Pervasive PSQL v9 Service Pack 2
About Pervasive PSQL . . . . . . . . . .
Competitive Advantages . . . . . .
Relational or Transactional Access
About the Server Engine . . . . . . . . .
Purpose . . . . . . . . . . . . . . .
Where to Install . . . . . . . . . .
Additional User Licenses . . . . .
Features . . . . . . . . . . . . . . .
2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Preparing to Install Pervasive PSQL . . . . . . . . . . . . . . . . .
1-2
1-2
1-3
1-4
1-4
1-4
1-4
1-4
2-1
Preparation Needed for Pervasive PSQL v9 Service Pack 2 Server Installation
Installation Overview . . . . . . . . . . . . . . . . . .
Major Components of the Product . . . . . . .
Installation Options . . . . . . . . . . . . . . .
Installing Over a Previous Version . . . . . . . .
Installation Checklist . . . . . . . . . . . . . . . . . .
Quick Checklist. . . . . . . . . . . . . . . . . .
Check the Hardware Requirements. . . . . . .
Check the Software Requirements . . . . . . .
Ensure Adequate Permissions . . . . . . . . . .
Verify Compatibility of Vendor Applications .
Schedule the Upgrade and Perform with Care.
Installing to a Cluster . . . . . . . . . . . . . .
Check for Special Configuration Issues . . . .
Read the README File . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-4
2-5
2-6
2-6
2-6
2-9
2-9
2-9
2-10
2-10
2-10
2-11
iii
Contents
3
Pervasive PSQL and Terminal Services . . . . . . . . . . . . . . .
3-1
How to Use Pervasive PSQL with Terminal Services
Overview . . . . . . . . . . . . . . . . . .
Supported Environments . . . . . .
Licensing . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . .
Windows 32-bit Server . . . . . . .
Configuration and Runtime. . . . . . . .
Remote Configuration with PCC .
Terminal Server as Network Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-2
3-3
3-4
3-4
3-5
3-5
3-5
Installing Pervasive PSQL Server for Windows . . . . . . . . . . .
4-1
Installing Components for Windows
4
Instructions for First-time Windows Server Installation
Before You Begin . . . . . . . . . . . . . . . . . . . . .
Platform Notes . . . . . . . . . . . . . . . . . .
Installation Tips . . . . . . . . . . . . . . . . . .
Installing Pervasive PSQL Server . . . . . . . . . . . .
What to do Next. . . . . . . . . . . . . . . . . .
Custom Installation Path . . . . . . . . . . . . . . . .
Common Questions After Installing Pervasive PSQL .
Where To Go From Here . . . . . . . . . . . . .
Uninstalling Pervasive PSQL Server . . . . . . . . . .
5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-2
4-2
4-4
4-12
4-13
4-16
4-16
4-17
Installing Pervasive PSQL Clients for Windows . . . . . . . . . . .
5-1
How to Install Pervasive PSQL Client Requester Software for Connecting to Servers
Before You Begin . . . . . . . . . . . . . . . . . . . .
Understanding Client Requesters . . . . . . . . . . .
Types of Windows Requesters . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . .
Installing the Pervasive PSQL Client Components .
Restarting Your Computer After Installation .
Custom Installation Path . . . . . . . . . . . . . . .
Where To Go From Here . . . . . . . . . . . . . . .
Installing DOS Requesters . . . . . . . . . . . . . . .
Available Requesters . . . . . . . . . . . . . .
Installation of the DOS Requesters . . . . . .
Alternate DOS Requesters . . . . . . . . . . .
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-3
5-3
5-4
5-4
5-6
5-13
5-14
5-16
5-17
5-17
5-18
5-18
Contents
6
Network Communication with Pervasive PSQL Server for Windows
6-1
Network Communications for a Windows-based Pervasive PSQL Server
Determining What Kind of Network You Have
Server Engine on Windows . . . . . . . .
Server Engine on NetWare . . . . . . . .
Server Engine on Linux . . . . . . . . . .
Network Communication Settings . . . . . . .
Setting Up TCP/IP Support . . . . . . . . . . .
Setting Up SPX Support . . . . . . . . . . . . .
Avoiding Unavailable Protocols . . . . . . . . .
7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Upgrading Your Pervasive PSQL Installation for Windows . . . . .
6-2
6-2
6-2
6-2
6-3
6-4
6-6
6-8
7-1
Instructions for Upgrading an Existing Pervasive PSQL Installation
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
Platform Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3
Migration of Existing Configuration Settings . . . . . . . . . . . . . . . . . . . .
7-3
Installing Over Existing Pervasive Products . . . . . . . . . . . . . . . . . . . . .
7-4
Accessing README file information . . . . . . . . . . . . . . . . . . . . . . . . .
7-4
Upgrading to Pervasive PSQL Server from Earlier Pervasive PSQL Versions or Btrieve 6.x 7-5
What to do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Custom Installation Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Common Questions After Installing Pervasive PSQL . . . . . . . . . . . . . . . . . . . 7-17
8
Application Configuration Scenarios . . . . . . . . . . . . . . . . .
8-1
Common Scenarios for Setting up Your Server
Support for Active Directory Service . . . . . . .
What Is Active Directory? . . . . . . . . . .
Installation of Active Directory . . . . . . .
Installation of Pervasive PSQL . . . . . . .
Pervasive Administrative Authority . . . .
Active Directory Tasks . . . . . . . . . . . .
Multiple Client Applications . . . . . . . . . . . .
Settings Affected by Multiple Applications.
Concurrent Local and Remote Applications . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-2
8-2
8-3
8-4
8-4
8-11
8-11
8-13
Installing Components for NetWare
9
Installing Pervasive PSQL Server for NetWare . . . . . . . . . . . .
9-1
Instructions for NetWare Server Installation or Patching
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Platform Notes for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-2
9-2
v
Contents
Installing Over Existing Pervasive Products. . .
Installation Tips . . . . . . . . . . . . . . . . . .
NetWare Security and Configuration Issues . .
Installing the Pervasive PSQL Server Components . .
If You Choose Custom Install . . . . . . . . . .
Custom Installation Path . . . . . . . . . . . . . . . .
Return to Steps for Complete Installation. . . .
Common Questions After Installing Pervasive PSQL .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-4
9-4
9-5
9-9
9-13
9-15
9-16
9-17
10 Network Settings for Server Engine on NetWare . . . . . . . . . .
10-1
How to Configure Network Settings for a NetWare-based Pervasive PSQL Server
Determining What Kind of Network You Have .
Server Engine on NetWare . . . . . . . . .
Mixed NetWare and Microsoft Network .
Default Settings. . . . . . . . . . . . . . . . . . .
Setting Up TCP/IP Support . . . . . . . . . . . .
Setting Up SPX Support . . . . . . . . . . . . . .
Disabling Certain Protocols . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10-2
10-2
10-2
10-3
10-5
10-7
10-8
11 Application Configuration on NetWare . . . . . . . . . . . . . . . .
11-1
Issues for Configuring Applications on the NetWare Platform
Local Applications on NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . .
NSS Volume Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-2
11-3
Installing Components for Linux
12 Installing Pervasive PSQL Server for Linux . . . . . . . . . . . . .
12-1
Instructions for First-time Installation of Pervasive PSQL v9 Service Pack 2 Server
Before You Begin . . . . . . . . . . . . . . . .
Samba Package Installation. . . . . . .
Platform Notes . . . . . . . . . . . . .
Installing Pervasive PSQL Server Using RPM
Installing Pervasive PSQL Server Using Tar .
After Installation . . . . . . . . . . . . . . . .
User Count License . . . . . . . . . . .
Accessing README File Information .
Configuration . . . . . . . . . . . . . .
Common Questions After Installation
Uninstalling the Server Engine . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 12-2
. 12-2
. 12-2
. 12-3
. 12-5
. 12-7
. 12-7
. 12-7
. 12-8
. 12-8
. 12-12
13 Installing Pervasive PSQL Client for Linux . . . . . . . . . . . . . .
13-1
Instructions for First-time Installation of Pervasive PSQL v9 Service Pack 2 Client for Linux
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
13-2
Contents
Hardware/Software Requirements . . . . . . . . . . .
Linux Client in Conjunction with Server Engine . . .
Installing the Pervasive PSQL Client Using RPM . . . . . .
Verifying an RPM Installation . . . . . . . . . . . . .
Installing the Client Using Tar . . . . . . . . . . . . . . . . .
After Installation . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Linux Client . . . . . . . . . . . . . .
Common Questions After Installing the Linux Client
Uninstalling the Pervasive PSQL Client . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 13-2
. 13-2
. 13-4
. 13-5
. 13-6
. 13-8
. 13-8
. 13-9
. 13-12
14 Installing PCC and Documentation on Linux. . . . . . . . . . . . .
14-1
First-time Installation of Pervasive PSQL PCC and Documentation on Linux
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pervasive PSQL Control Center. . . . . . . . . . . . . . . . . .
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Conditions for Installation . . . . . . . . . . . . . . .
Installing Pervasive PSQL Control Center Using RPM . . . . . . . .
RPM Installation Steps. . . . . . . . . . . . . . . . . . . . . . .
After Installation . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing README file information . . . . . . . . . . . . . . .
Installing Pervasive PSQL Control Center Using Tar . . . . . . . . .
Tar Installation Steps . . . . . . . . . . . . . . . . . . . . . . .
Installing Pervasive PSQL Documentation Using RPM . . . . . . . .
RPM Installation Steps. . . . . . . . . . . . . . . . . . . . . . .
After Installation . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Pervasive PSQL Documentation Using Tar . . . . . . . . .
Tar Installation Steps . . . . . . . . . . . . . . . . . . . . . . .
After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Documentation . . . . . . . . . . . . . . . .
Common Questions After Installing PCC and Documentation
Uninstalling Pervasive PSQL Control Center. . . . . . . . . . . . . .
Uninstalling Pervasive PSQL Documentation . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15 Upgrading Your Pervasive PSQL Installation for Linux . . . . . . .
14-2
14-2
14-2
14-3
14-4
14-4
14-4
14-5
14-6
14-6
14-7
14-8
14-8
14-8
14-9
14-10
14-10
14-11
14-12
14-12
14-14
14-15
14-16
15-1
How to Upgrade an Existing Installation of Pervasive PSQL on Linux
Before You Begin . . . . . . . . . . . . . . . . . . . . .
Samba Package Installation . . . . . . . . . . . .
Platform Notes . . . . . . . . . . . . . . . . . . .
Upgrading Pervasive PSQL Server Using RPM . . . . .
Upgrade Pervasive PSQL 9 . . . . . . . . . . . .
Upgrade Versions Older than Pervasive PSQL 9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15-2
15-2
15-2
15-3
15-3
15-4
vii
Contents
Installation Information . . . . . . . . . . . .
User Count License . . . . . . . . . . . . . . .
Accessing README file information . . . . .
Upgrading Pervasive PSQL Server Using Tar . . . .
Upgrade Pervasive PSQL 9 . . . . . . . . . . .
Upgrade Versions Prior to Pervasive PSQL 9 .
Upgrading Pervasive PSQL Client Using RPM . . .
Upgrading Pervasive PSQL Client Using Tar . . . .
After Upgrading . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . .
Common Questions After Upgrading . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15-4
15-5
15-5
15-6
15-6
15-7
15-9
15-9
15-10
15-11
15-11
15-12
15-14
15-14
15-14
16 Using Pervasive PSQL on Linux . . . . . . . . . . . . . . . . . . .
16-1
Working With the Installed Products
Finding What You Need. . . . . . . . . . . . . . .
Accessing the JavaHelp Documentation. . .
Man Pages . . . . . . . . . . . . . . . . . . .
Exclusions . . . . . . . . . . . . . . . . . . .
Pervasive PSQL Account Management on Linux .
After Installation Behavior . . . . . . . . . .
The User Environment . . . . . . . . . . . .
Using Utilities from Users Other than psql .
Configuration . . . . . . . . . . . . . . . . . . . .
Configuration File. . . . . . . . . . . . . . .
Authentication. . . . . . . . . . . . . . . . .
Supported Path Formats for Samba . . . . .
Client Information . . . . . . . . . . . . . . . . . .
Authentication to Remote Machines . . . .
Creating a Client DSN . . . . . . . . . . . .
Internationalization with the Client . . . . .
Setting Up Web-based Data Access . . . . . . . . .
ODBC Behavior . . . . . . . . . . . . . . . .
Configuring Web Server . . . . . . . . . . .
PHP. . . . . . . . . . . . . . . . . . . . . . .
Perl . . . . . . . . . . . . . . . . . . . . . . .
Using Perl and ODBC with Pervasive PSQL . . . .
Code Snippet for Perl and DBI . . . . . . . .
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
16-2
16-2
16-2
16-2
16-4
16-4
16-4
16-5
16-6
16-6
16-6
16-7
16-8
16-8
16-8
16-8
16-13
16-13
16-13
16-13
16-17
16-22
16-22
Contents
Working With Pervasive PSQL Clients
17 Connecting Clients to a Sample Database . . . . . . . . . . . . . .
17-1
How to Connect Clients to the Sample Database on a Pervasive PSQL Server Machine
Basics About Pervasive PSQL Engines and Clients .
Every Engine is Also a Client . . . . . . . . .
Clients. . . . . . . . . . . . . . . . . . . . . .
Connect a Client to a Pervasive PSQL Server . . . .
Use the Client to Obtain Data from the Server . . .
Become an Expert User . . . . . . . . . . . . . . . .
User’s Guide . . . . . . . . . . . . . . . . . .
Advanced Operations Guide . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18 Configuring Network Communications for Clients . . . . . . . . .
17-2
17-2
17-2
17-3
17-4
17-6
17-6
17-6
18-1
How to Configure Network Communications for Your Pervasive PSQL Clients
Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Configure the Pervasive Clients . . . . . . . . . . . . . .
Win32 Configuration Notes. . . . . . . . . . . . . . . . . .
Win16 Configuration Notes. . . . . . . . . . . . . . . . . .
Network Path Formats Supported by Pervasive Requesters . . . .
Universal Naming Convention (UNC) Path Formats. . . .
Drive-based Formats. . . . . . . . . . . . . . . . . . . . . .
NetWare Specific Formats. . . . . . . . . . . . . . . . . . .
Linux Path Formats . . . . . . . . . . . . . . . . . . . . . .
Using TCP/IP to Connect to a NetWare Server . . . . . . . . . .
Using SPX to Connect to a NetWare Server . . . . . . . . . . . .
Using TCP/IP to Connect to a Windows 32-bit Server . . . . . .
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using SPX to Connect to a Windows 32-bit Server . . . . . . . .
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Default Communication Ports. . . . . . . . . . . .
Services File . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetBIOS and the Pervasive PSQL Server Engine . . . . . . . . . .
Using TCP/IP to Connect to a Linux Server . . . . . . . . . . . .
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the DOS Requesters . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requesters Available . . . . . . . . . . . . . . . . . . . . . .
Supported Configurations. . . . . . . . . . . . . . . . . . .
Win16 and DOS Workstations . . . . . . . . . . . . . . . .
Running DOS applications on Windows 32-bit Platforms .
Running DOS applications on Windows 98/ME . . . . . .
Verifying the DOS Configuration. . . . . . . . . . . . . . .
DOS TCP/IP Technical Information . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18-2
18-4
18-4
18-4
18-5
18-5
18-6
18-6
18-8
18-9
18-11
18-12
18-12
18-15
18-15
18-17
18-17
18-19
18-20
18-20
18-23
18-23
18-23
18-24
18-25
18-25
18-28
18-35
18-35
ix
Contents
Configuring the Pervasive PSQL DOS Requester . . . . . . . . . . . . . . . . . .
18-39
After Installation
19 Troubleshooting After Installation . . . . . . . . . . . . . . . . . .
19-1
How to Proceed When You Encounter Errors During Installation
Troubleshooting Tools. . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Strategies . . . . . . . . . . . . . . . . . . .
Checklist for Problems . . . . . . . . . . . . . . . . . .
Troubleshoot the Problem . . . . . . . . . . . . . . . .
Configuration for Special Installation Situations . . . . . . .
Diagnosing Problems with Pervasive System Analyzer (PSA)
How to Start PSA . . . . . . . . . . . . . . . . . . . . .
Documentation for PSA . . . . . . . . . . . . . . . . .
SmartScout Replaced by PSA. . . . . . . . . . . . . . .
Verifying Database Engine is Running . . . . . . . . . . . . .
Windows . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetWare . . . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining File, Client, and Engine Version Number . . . . .
Determining Client and Engine Version . . . . . . . .
Determining a File Version . . . . . . . . . . . . . . . .
Issues After Uninstalling Pervasive PSQL on Windows . . . .
Engine and Client Version Conflicts . . . . . . . . . . . . . .
Disabling the Client Mismatch Warning Messages . . .
How to Get Additional Help . . . . . . . . . . . . . . . . . .
Thirty-Day Free Technical Support . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19-2
19-3
19-3
19-3
19-4
19-5
19-5
19-5
19-5
19-6
19-6
19-7
19-7
19-8
19-8
19-9
19-11
19-12
19-13
19-14
19-15
20 Pervasive PSQL Resources and Contacts . . . . . . . . . . . . . .
20-1
A Guide to Pervasive PSQL Customer Information Resources
Printed Documentation . . . . . . .
Developer Center. . . . . . . . . . .
Pervasive PSQL Knowledge Base . .
FTP Site . . . . . . . . . . . . . . . .
Online Documentation . . . . . . .
Pervasive Library . . . . . . .
Webinars . . . . . . . . . . . . . . .
Subscription Based E-mail Services .
DevTalk . . . . . . . . . . . . . . . .
Newsgroup . . . . . . . . . . . . . .
E-Mail Contacts . . . . . . . . . . .
Technical Support . . . . . . . . . .
x
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20-2
. 20-3
. 20-4
. 20-5
. 20-6
. 20-6
. 20-7
. 20-8
. 20-9
. 20-10
. 20-11
. 20-12
Figures
4-1
4-2
4-3
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-11
4-12
4-13
4-14
Pervasive Software’s Software License Agreement. . .
Applying the User Count License . . . . . . . . . . . .
Setup Type Dialog Box. . . . . . . . . . . . . . . . . .
Example Dialog Box for Programs that May Interfere
Installation Status Dialog Box. . . . . . . . . . . . . .
Transactional Engine Test . . . . . . . . . . . . . . . .
Transactional Engine Test Results from PSA . . . . .
Relational Engine Test . . . . . . . . . . . . . . . . . .
Relational Engine Test Results from PSA . . . . . . .
Product Registration Page . . . . . . . . . . . . . . . .
View Readme . . . . . . . . . . . . . . . . . . . . . . .
Example of Installation Choices . . . . . . . . . . . .
Location of Space Required Values . . . . . . . . . . .
Uninstall Remove Option . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-5
4-5
4-6
4-7
4-8
4-8
4-9
4-9
4-10
4-11
4-11
4-13
4-15
4-17
5-1
5-2
5-3
5-4
5-5
5-6
5-7
5-8
5-9
5-10
5-11
5-12
5-13
5-14
Setup Type Dialog Box. . . . . . . . . . . . . . . . . . .
Example Dialog Box for Programs that May Interfere .
Installation Status Dialog Box. . . . . . . . . . . . . . .
Network Communication Test . . . . . . . . . . . . . .
Network Transmission of Test Messages . . . . . . . . .
Successful Transmission of Test Messages . . . . . . . .
Transactional Engine Test . . . . . . . . . . . . . . . . .
Transactional Engine Test Results from PSA . . . . . .
Relational Engine Test . . . . . . . . . . . . . . . . . . .
Relational Engine Test Results from PSA . . . . . . . .
Product Registration Page . . . . . . . . . . . . . . . . .
View Readme . . . . . . . . . . . . . . . . . . . . . . . .
Example of Installation Choices (Client Components) .
Location of Space Required Values . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-6
5-7
5-8
5-9
5-9
5-9
5-10
5-10
5-11
5-11
5-12
5-13
5-14
5-15
7-1
7-2
7-3
7-4
7-5
7-6
7-7
7-8
7-9
7-10
Pervasive Software’s Software License Agreement. . .
Applying the User Count License . . . . . . . . . . . .
Setup Type Dialog Box. . . . . . . . . . . . . . . . . .
Example Dialog Box for Programs that May Interfere
Installation Status Dialog Box. . . . . . . . . . . . . .
Transactional Engine Test . . . . . . . . . . . . . . . .
Transactional Engine Test Results from PSA . . . . .
Relational Engine Test . . . . . . . . . . . . . . . . . .
Relational Engine Test Results from PSA . . . . . . .
Product Registration Page . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-6
7-6
7-7
7-8
7-9
7-9
7-10
7-10
7-11
7-12
.
.
.
.
.
.
.
.
.
.
xi
Figures
7-11
7-12
7-13
View Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Example of Installation Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Location of Space Required Values . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
9-1
9-2
9-3
9-4
9-5
9-6
9-7
9-8
9-9
9-10
Pervasive PSQL v9 Service Pack 2 Setup Reboot Required.
Mapping a Drive. . . . . . . . . . . . . . . . . . . . . . . .
Pervasive Software’s Software License Agreement . . . . .
Applying the User Count License . . . . . . . . . . . . . .
Location for System Components (NetWare Server) . . .
Location for Pervasive Files (NetWare Server) . . . . . . .
Setup Type Dialog Box . . . . . . . . . . . . . . . . . . . .
Installation Status Dialog Box (NetWare Server) . . . . . .
Example of Installation Choices (NetWare) . . . . . . . .
Location of Space Required Values . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9-5
. 9-9
. 9-10
. 9-10
. 9-11
. 9-12
. 9-12
. 9-13
. 9-15
. 9-16
17-1
17-2
17-3
17-4
17-5
17-6
Registering a New Engine. . . . . . . . . . . . . . . . . . . .
Choosing a Computer Name . . . . . . . . . . . . . . . . . .
Expanding the Databases List for a Machine . . . . . . . . .
Selecting the Department Table in DEMODATA . . . . . .
Displaying the Department Table in DEMODATA . . . . .
Refining Your Query - Department Table in DEMODATA .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 17-3
. 17-3
. 17-4
. 17-4
. 17-5
. 17-5
19-1
19-2
19-3
Displaying the Services Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Selecting the Btrieve Version button. . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Btrieve Version Info Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
xii
Tables
1-1
Comparison of Server and Workgroup Features . . . . . . . . . . . . . . . . . . 1-5
5-1
Configuration Setting Values not Migrated . . . . . . . . . . . . . . . . . . . . . 5-5
7-1
7-2
Configuration Setting Values not Migrated . . . . . . . . . . . . . . . . . . . . . 7-3
How to Proceed After Installing Server and Client Software . . . . . . . . . . . . 7-17
18-1
18-2
18-3
Supported UNC and Drive Path Formats . . . . . . . . . . . . . . . . . . . . . . 18-5
File name and Path formats for Novell Clients for NetWare . . . . . . . . . . . . 18-7
Supported DOS Requester Configurations. . . . . . . . . . . . . . . . . . . . . . 18-24
19-1
Pervasive Tools that Assist in Installation and Problem Determination . . . . . . 19-2
xiii
xiv
About This Manual
This manual contains information about installing the Pervasive
PSQL v9 Service Pack 2 database system. Pervasive PSQL v9 Service
Pack 2 is a complete database management system, providing the
best of both worlds. It combines a transactional interface designed
for high-performance data handling and improved programming
productivity with an embeddable and scalable relational interface.
This manual also contains information about common installation
issues, general network protocol information, and Pervasive PSQL
v9 Service Pack 2 components.
For information on using Pervasive PSQL utilities, see Pervasive
PSQL User's Guide. For information about configuring the Pervasive
PSQL v9 Service Pack 2 engine, see Advanced Operations Guide.
xv
About This Manual
Who Should Read This Manual
This manual provides information for users who install and run
Pervasive PSQL v9 Service Pack 2. This manual is also useful for
system administrators who are responsible for maintaining
databases on a network and for those who are using Pervasive PSQL
to develop server applications.
Pervasive Software would appreciate your comments and
suggestions about this manual. As a user of our documentation, you
are in a unique position to provide ideas that can have a direct
impact on future releases of this and other manuals. If you have
comments or suggestions for the product documentation, post your
request at http://www.pervasive.com/devtalk.
xvi
Manual Organization
This manual is arranged in the order of the main installation
sequence. You complete the installation by following the chapters in
order (skipping the chapters that do not apply to your server
platform). Getting Started With Pervasive PSQL is divided into the
following sections:
Getting Ready
to Install

Chapter 1—“Welcome to Pervasive PSQL”
This chapter provides a basic introduction to Pervasive PSQL v9
Service Pack 2.

Chapter 2—“Preparing to Install Pervasive PSQL”
This chapter discusses important preparations that you should
undertake before attempting to install Pervasive PSQL v9 Service
Pack 2.

Chapter 3—“Pervasive PSQL and Terminal Services”
This chapter describes how to use Pervasive PSQL with Terminal
Server Products.
Windows

Chapter 4—“Installing Pervasive PSQL Server for Windows”
This chapter describes how to install Pervasive PSQL Server for
the first time.

Chapter 5—“Installing Pervasive PSQL Clients for Windows”
This chapter describes how to install Pervasive PSQL Client for
the first time.

Chapter 6—“Network Communication with Pervasive PSQL
Server for Windows”
This chapter describes how to configure your network for use
with the Server engine on Windows.

Chapter 7—“Upgrading Your Pervasive PSQL Installation for
Windows”
This chapter describes how to upgrade a previous version of
Pervasive PSQL on Windows servers.

Chapter 8—“Application Configuration Scenarios”
xvii
About This Manual
This chapter describes different application configurations for
special scenarios.
NetWare

Chapter 9—“Installing Pervasive PSQL Server for NetWare”
This chapter describes how to install the Pervasive PSQL server
on NetWare.

Chapter 10—“Network Settings for Server Engine on NetWare”
This chapter describes how to configure your network for use
with the Server engine on NetWare.

Chapter 11—“Application Configuration on NetWare”
This chapter describes different application configurations for
special scenarios.
Linux

Chapter 12—“Installing Pervasive PSQL Server for Linux”
This chapter describes how to install the Pervasive PSQL Server
on Linux.

Chapter 13—“Installing Pervasive PSQL Client for Linux”
This chapter describes how to install the Pervasive PSQL Client
on Linux.

Chapter 14—“Installing PCC and Documentation on Linux”
This chapter describes how to install the Pervasive PSQL Control
Center (PCC) on Linux.

Chapter 15— “Upgrading Your Pervasive PSQL Installation for
Linux”
This chapter describes how to upgrade a previous version of
Pervasive PSQL on Linux.

Chapter 16—“Using Pervasive PSQL on Linux”
This chapter provides useful information after you install the
Pervasive PSQL products on Linux.
Client Requesters

Chapter 17—“Connecting Clients to a Sample Database”
This chapter describes how to connect to a server and display
data from a table in the sample database.
xviii

Chapter 18—“Configuring Network Communications for
Clients”
This chapter describes how to configure your clients network
settings for use with Server engines. It also offers
implementation notes for specific operating systems.
After
Installation

Chapter 19—“Troubleshooting After Installation”
This chapter provides information on Pervasive PSQL tools that
aid in diagnosing problems.

Chapter 20 —“Pervasive PSQL Resources and Contacts”
Should you not find the answer to your problem, this chapter
gives contact information for Pervasive PSQL support.
This manual also contains an index.
xix
About This Manual
Conventions
Unless otherwise noted, command syntax, code, and examples use
the following conventions:
xx
CASE
Commands and reserved words typically appear in uppercase
letters. Unless the manual states otherwise, you can enter
these items using uppercase, lowercase, or both. For
example, you can type MYPROG, myprog, or MYprog.
Bold
Words appearing in bold include the following: menu names,
dialog box names, commands, options, buttons, statements,
etc.
Monospaced
font
Monospaced font is reserved for words you enter, such as
command syntax.
[ ]
Square brackets enclose optional information, as in
[log_name]. If information is not enclosed in square brackets,
it is required.
|
A vertical bar indicates a choice of information to enter, as in
[file name | @file name].
< >
Angle brackets enclose multiple choices for a required item, as
in /D=<5|6|7>.
variable
Words appearing in italics are variables that you must replace
with appropriate values, as in file name.
...
An ellipsis following information indicates you can repeat the
information more than one time, as in [parameter ...].
::=
The symbol ::= means one item is defined in terms of another.
For example, a::=b means the item a is defined in terms of b.
G ETTING R EADY
TO I NSTALL
chapter
Welcome to Pervasive PSQL
1
A Basic Introduction to Pervasive PSQL v9 Service Pack 2
Thank you for purchasing Pervasive PSQL v9 Service Pack 2. We are
confident that you will find this release to be the very best high
performance, low maintenance database engine on the market.
This chapter contains the following topics:

“About Pervasive PSQL” on page 1-2
“About the Server Engine” on page 1-4
1-1
About Pervasive PSQL
Pervasive PSQL v9 Service Pack 2 is a reliable, low-maintenance,
high-performance database management system (DBMS).
Thousands of companies around the world license Pervasive PSQL
and distribute it as the underlying data storage program for their
data-intensive software products. These companies see no reason to
build their own DBMS or license from a competitor once they
experience the ease-of-use, reliability, and value offered by Pervasive
PSQL.
No matter whether you received Pervasive PSQL with another
product or purchased it yourself, this section explains a little about
the product and why it is right for you.
If you would like to read a detailed discussion of Pervasive PSQL
architecture and interfaces, please refer to Pervasive Products and
Services.
Competitive
Advantages
Pervasive PSQL provides a number of advantages over other
products available on the market. Here are just a few:

1-2
Lowest total cost of ownership. An independent study conducted
by Aberdeen Group concluded that no major database product
can match Pervasive PSQL’s low total cost of ownership. How do
we do it? See the next bullet.
No Database Administrator (DBA) required. You can look in the
newspaper any day of the week and see classified ads for Oracle,
Sybase, or SQL Server database administrators, with sky-high
salaries. Pervasive PSQL offers the unique Zero Database
Administrator, or Z-DBA™, architecture. Its easy-to-use tools,
bulletproof installation, and set-it-and-forget-it simplicity make
it the perfect workhorse for desktop, workgroup, and
departmental applications.
Scalable from the desktop to the Web. Pervasive PSQL is available
in two editions: the Ultra-light™ Workgroup database engine
supports single-user configurations up to small workgroup
configurations; and the Server engine comes with a 10-user
license and scales to hundreds of concurrent users, including
intranet and extranet applications. Upgrading to another
configuration requires no changes to the supported application,
just plug-and-play with the new database engine.
About Pervasive PSQL

Relational or
Transactional
Access
Cross-platform support. Unlike some competitors, Pervasive
PSQL does not confine you to a single platform. Pervasive PSQL
databases are binary-compatible and supported across
Microsoft Windows, Novell NetWare, and several Linux
distributions. No matter what operating system you currently
use or change to, Pervasive PSQL is there for you.
Big database features at a small price. Pervasive PSQL offers full
security, encryption, management and monitoring tools, and a
host of other features you would expect to see in more expensive
DBMS products.
Legendary stability and reliability. There’s no doubt why 70% of
the Windows desktop accounting market uses Pervasive PSQL as
the underlying database of choice. When you manage important
data, go for the database engine that won’t let you down.
Pervasive PSQL offers an architecture that is totally unique in the
database management market. Our product allows you to access the
exact same data through ODBC and OLE DB, supporting
applications like Microsoft ASP, Excel, and Access, or through the
lightning-fast transactional interface called Btrieve. ODBC allows
you to do complex reporting and data mining, while Btrieve
provides massive throughput when you need the ability to view,
update, or create millions of records a day.
Each application vendor chooses which interfaces are used. If you
want to know which access methods are used in your application,
contact your application vendor.
1-3
About the Server Engine
This section provides some basic information about the Pervasive
PSQL Server engine. For a detailed discussion of Pervasive PSQL
architecture, please refer to Pervasive Products and Services.
If you would like more information about what comes in your
product and what gets installed, please see Chapter 2, “Preparing to
Install Pervasive PSQL.”
Purpose
You have purchased the Pervasive PSQL Server engine. This database
engine is designed to support up to many hundreds of concurrent
network users when installed on the appropriate hardware. It is
capable of supporting web, corporate, departmental, and other
client/server or web-based applications where reliability and
performance are critical.
Where to Install The Server engine must be installed on the same computer where the
database files are located. The client portion of the software must be
installed on every computer that is expected to access the database.
In the case of web applications, the client must be installed on the
same computer as the web server. Multiple web server platforms
require a client on each platform.
Additional User If you receive Status Code 161 or other status codes indicating you
have exceeded your licensed user count, you may wish to buy
Licenses
additional user licenses. You can purchase additional licenses in
blocks of 10, 20, 50, 100, or more. You may purchase user count
upgrades from your application reseller or directly from Pervasive.
Features
1-4
All Pervasive database engines offer the same powerful feature set
and full-functioned support for programming interfaces. All engine
editions are plug-and-play compatible, requiring no application
changes to switch from one engine to another. Data files are binarycompatible across all supported platforms.
About the Server Engine
The chart below shows the major differences between the two
different editions of the product.
Table 1-1 Comparison of Server and Workgroup Features
Feature
Server
Workgroup
Supports Btrieve, ODBC, OLE DB, and ActiveX
interfaces
Full-featured relational support (online backup,
security, referential integrity, management tools,
and so on)
Binary compatible data files across all platforms
and engine editions
Easy plug-and-play upgrading, no application
changes required
Includes complete online documentation
Can access data on a file server where no
database engine is installed
Supports remote ODBC client connections
Requires a Workgroup engine on all computers
expected to access remote data
N/A
Engine runs on Windows
Engine runs on NetWare
Engine runs on Linux
Multi-user for small groups
Scales to hundreds of users
Extranet license available
1-5
1-6
chapter
Preparing to Install
Pervasive PSQL
2
Preparation Needed for Pervasive PSQL v9 Service Pack 2 Server Installation
Thank you for purchasing Pervasive PSQL v9 Service Pack 2. We
hope that you enjoy using this fast and reliable database product.

“Installation Overview” on page 2-2
“Installation Checklist” on page 2-6
2-1
Preparing to Install Pervasive PSQL
Installation Overview
This section provides an overview to the components that make up
Pervasive PSQL v9 Service Pack 2. Also included in this section is
information on the files included in the different types of
installation.
Major
The product consists of the following components:
Components of
the Product
Database Engine
Pervasive PSQL v9 Service Pack 2 consists of two database subengines:

MicroKernel Database Engine (MKDE), which provides Btrieve/
MicroKernel API support for Pervasive PSQL applications
SQL Relational Database Engine (SRDE), which provides
ODBC/SQL API support for Pervasive PSQL applications
Client
Requesters that allow you to access the server-based MicroKernel
from a DOS client, a Windows 98/ME client, or a Windows 32-bit
platform client.

The 16-bit requesters used in DOS clients are Btrieve requesters
only and will have no relational access.
Utilities
Pervasive PSQL v9 Service Pack 2 includes a suite of useful utilities
for every phase of database management from engine installation
and configuration to data maintenance. They include the following:

2-2
Pervasive System Analyzer (PSA)
Pervasive PSQL Control Center (PCC)

SQL Editor

Table Editor

Configuration properties for client and engines
Monitor
Function Executor
Maintenance

Rebuild
License Administrator
ODBC Administrator
Gateway Locator
Printed Documentation
If you received a boxed version of Pervasive PSQL v9 Service Pack 2,
your package contains a printed copy of Getting Started With
Pervasive PSQL (Server Edition) and the Status Codes and Messages
Quick Reference card. You can order a complete hardcopy set of the
manuals through the Pervasive Software Sales Team.
Online Documentation
The complete Pervasive PSQL v9 Service Pack 2 documentation set
is provided in JavaHelp format. This help also serves as the contextsensitive help for the Pervasive PSQL Control Center.
Documentation Titles
The following titles are included in the online library and are
available in hardcopy except where noted:

This book - Getting Started with Pervasive PSQL (Server Edition)
- helps you to get Pervasive PSQL v9 Service Pack 2 Server engine
running with installation, setup, and basic configuration
information based on your operating environment.
Getting Started with Pervasive PSQL (Workgroup Edition) - helps
you to get Pervasive PSQL v9 Service Pack 2 Workgroup engine
running with installation, setup, and basic configuration
information based on your operating environment. This title is
not available in hardcopy.
Pervasive Products and Services - provides an overview of
Pervasive Software products and services, including support
options and information regarding licensing and registration.
This manual also describes the database and product
architectures.
2-3

Installation
Options
Pervasive PSQL User's Guide - gives basic information on the
utilities provided with the Pervasive PSQL Control Center,
including several interactive wizards designed to help you
accomplish basic database tasks. This manual also contains
information on the Linux database engine and the utilities
available for that particular platform.
SQL Engine Reference - provides database programmers a
complete reference guide to the SQL relational database
language supported in Pervasive PSQL v9 Service Pack 2.
Advanced Operations Guide - details tasks typically performed by
Network or System Administrators, using various tools such as
the Rebuild, Maintenance, Monitor, and Function Executor
utilities.
Status Codes and Messages - lists the error and informational
codes and messages that can be received when using Pervasive
software.
On Windows operating systems and the NetWare operating system,
Pervasive PSQL v9 Service Pack 2 offers Complete and Custom
installation options. You can accept default installation parameters
by selecting the Complete install, or you can specify certain
installation parameters by selecting the Custom install option. The
following sections outline the major differences in these two
installation options. (On Linux distributions, each major
component has its own separate installation.)
Complete Setup Installation
The Complete installation, which is recommended for most first
time users, takes default actions for most operations performed
during the installation.
The Complete setup installs the following components:

2-4
Database engine (including ODBC interface)
All client requesters (Win32 and MS-DOS requesters)
Pervasive PSQL Control Center and other utilities

Transactional and Relational interfaces
Online documentation in JavaHelp format
Custom Setup Installation
Selecting Custom setup type allows you to specify the program folder
name and select the components to install.
During a Custom server installation, the following components are
optional:

Pervasive PSQL Control Center and JavaHelp documentation
Other Utilities (except minimum set)
Note Client installation programs for DOS, Windows, and Linux are
not part of the server installation. You must run a separate installation
program for Pervasive PSQL clients. See “Installing Pervasive PSQL
Clients for Windows” on page 5-1 for more information.
On Windows, the default installation location is C:\PVSW, assuming
the Windows system drive is C.
On NetWare, the default installation location is SYS:\SYSTEM.
On Linux, the default installation location is /usr/local/psql.
Installing Over
a Previous
Version
If you install the Pervasive PSQL Server product over a previous
version (update the server), be aware of the following:

An upgrade re-creates the system databases TEMPDB and
SYSTEMDB, and the sample database DEMODATA. The
upgrade removes all dictionary files and data files associated
with TEMPDB, SYSTEMDB, and DEMODATA, including ones
you may have added.
If the system database DEFAULTDB exists from a previous
installation, it is retained as is. An upgrade does not re-create
DEFAULTDB if it already exists.
This information applies to all platforms on which Pervasive PSQL
is supported.
2-5
Installation Checklist
This section provides you with a checklist to prepare you for
installation. Please use this checklist as a guide for a successful
installation.
Quick Checklist Each of the following bullet points is described in more detail in the
sections that follow.
R Your system hardware meets the minimum requirements (listed
later in this chapter) to install Pervasive PSQL v9 Service Pack 2
Server.
R Your operating system is supported by Pervasive PSQL v9
Service Pack 2 Server.
R You have full administrator-level rights on the machine where
you plan to install the product.
R Your application vendor supports the Pervasive PSQL v9 Service
Pack 2 engine.
R Schedule the upgrade appropriately and perform the installation
with care.
R Licenses for older versions of the product cannot be migrated
up.
R Read the README file for important, late-breaking warnings
and information.
R If you are installing a downloaded version of Pervasive PSQL, do
not place the install file in a location that is listed in the PATH
environment variables, as this can cause issues with file copying
during install. Place the setup files in a location such as the
Windows TEMP directory.
Check the
Hardware
Requirements
2-6
You must have the following to install Pervasive PSQL v9 Service
Pack 2:
Server – Windows
R Intel 486 processor or higher.
R At least 64 MB of free memory.
R At least 90 MB of free space in the installation location,
depending upon the installation options selected.
Server – NetWare
R At least 15 MB of free disk space for the server components.
Server – Linux
R Most Linux distributions with Kernel 2.4, Glibc 2.2, and RPM 4.
Note Due to recent trends in the rapid development of the Linux
operating environment, please refer to the Pervasive Software web site
for the latest information concerning the list of supported platforms.
R At least 25 MB of free space in the installation location.
Client – Windows
R At least 10 MB of free memory (more is recommended).
R Up to 30 MB of free space in the installation location, depending
upon the installation options selected.
2-7
R DOS only: DOS 5.0 or greater with 1MB hard disk space, 640 KB
RAM.
Client – Linux
R At least 10 MB of free memory (more is recommended).
R Up to 30 MB of free space in the installation location, depending
upon the installation options selected.
Pervasive PSQL Control Center (PCC) – Linux
R Java Runtime Environment (JRE) Standard Edition.
R Pervasive PSQL Server for Linux or Pervasive PSQL Client for
Linux
JavaHelp – Linux
R Java Runtime Environment (JRE) Standard Edition.
Network - Windows
R You must have a properly functioning network consisting of one
or more servers connected to one or more clients using network
cabling and hubs.
Network - NetWare
R You must have a properly functioning network to install
Pervasive PSQL v9 Service Pack 2. You need one or more servers
and one Windows client machine for each of those servers to
install Pervasive PSQL v9 Service Pack 2 remotely. NetWare can
only be installed from a client machine.
Network – Linux
R You must have a functioning network consisting of one or more
servers connected to one or more clients using network cabling
and hubs.
2-8
R TCP/IP protocol must be used and configured properly, because
other protocols (such as IPX/SPX) are not supported with
Linux.
Check the
Software
Requirements
Your operating system (and, optionally, version of Internet Explorer
for Windows platforms) must be supported by Pervasive PSQL v9
Service Pack 2. The README file for Pervasive PSQL v9 Service Pack
2 contains the list of supported operating systems and other software
requirements.
You can access the README file from the root directory on the
distribution media.
Support for Previously Released Pervasive PSQL Server
Engines
Pervasive recommends that you use client requesters that are the
same version as the database engine. If you choose, you may use a
client requester that is an older version than the database engine with
which it interacts. In some situations, depending on the type of SDK
access method used by your application, an older version requester
will not work with the database engine. Your application will be
unable to communicate with the database engine. For those
situations, you must use client requesters that are the same version as
the database engine. See also “Engine and Client Version Conflicts”
on page 19-12.
Client requesters that are a newer version than the database engine
may or may not function correctly. Pervasive does not guarantee that
newer versions of client requesters will function correctly with older
versions of the engine. Therefore, Pervasive recommends that you
avoid the use of newer version client requesters with an older engine.
Ensure
Adequate
Permissions
To install Pervasive PSQL v9 Service Pack 2 on a Windows 32-bit
server platform, you must have full administrator-level rights on the
machine where you will install Pervasive PSQL v9 Service Pack 2. For
information on granting administrative rights, please refer to
Pervasive PSQL User's Guide.
Verify
Compatibility of
Vendor
Applications
Contact your application vendor or review the documentation
provided by your vendor to ensure that they support the Pervasive
PSQL v9 Service Pack 2 engine version and mode that you want to
install.
2-9
Schedule the
Upgrade and
Perform with
Care
If installing the Pervasive PSQL v9 Service Pack 2 Server edition, the
installation and upgrade should be performed during a period of low
use.
As with any significant software installation, be sure to back up any
important files on the target hard drive, including data files, before
you begin the installation.
the database engine. See “Engine and Client Version Conflicts” on
page 19-12.
You should install the server first and immediately upgrade all the
client machines. That way, the client requesters are the same version
as the database engine.
Installing to a
Cluster
If you plan to install Pervasive PSQL to a clustered environment
using either Microsoft Cluster Service or NetWare Cluster Services,
please read the following in Advanced Operations Guide: “Server
High-Availability Support” on page 9-1.
Check for
Special
Configuration
Issues
Some default setting in Pervasive PSQL need to be adjusted if your
configuration includes certain qualities. For example, the default
settings need adjustment if you have:

Multiple network interface cards (NICs)
Files with Embedded Spaces
Please review “Configuration for Special Installation Situations” on
page 19-4 for these or other relevant issues, especially if you
encounter problems after installation.
2-10
Read the
README File
Pervasive Software strongly recommends that you read the
information contained in the README file, readme.htm. The
README file contains late-breaking product news that could not be
included as part of the JavaHelp documentation.
You can access the README file from the root directory on the
distribution media.
2-11
2-12
chapter
Pervasive PSQL and
Terminal Services
3
How to Use Pervasive PSQL with Terminal Services
This chapter explains how to use Pervasive PSQL with Microsoft
Terminal Server and Citrix MetaFrame. In general, you can use
Pervasive PSQL on machines with either product in almost the same
way as on a computer without remote access.
This chapter contains the following sections:

“Overview” on page 3-2
“Licensing” on page 3-3
“Installation” on page 3-4
“Configuration and Runtime” on page 3-5
3-1
Pervasive PSQL and Terminal Services
Overview
Microsoft Terminal Services is a multisession environment that
provides remote computers access to Windows-based programs
running on a server. Citrix MetaFrame extends Windows Terminal
Services with additional client and server functionality.
Only one instance of the database engine may run on any terminal
server platform. You cannot run separate copies of the database
engine within two or more terminal sessions.
Supported
Environments
3-2
Refer to the product README file for a list of environments
supported for Terminal Services.
Licensing
Licensing
Each terminal server client session counts as one user. Collectively,
all applications that access the database engine and run on the same
machine as the database engine also count as one user. You must
purchase sufficient user count licenses to cover the number of users
accessing each database engine. For example, if you have a 10-user
license, you may not have more than 10 users accessing the database
at once, whether they are connected through terminal sessions or
remote database connections.
You may not use a terminal server as a method of bypassing the user
count mechanism of the database engine.
3-3
Installation
To install Pervasive PSQL on a terminal server, you must be logged
into the terminal server as a user with system administrator rights.
Windows 32-bit Install Pervasive PSQL through Add New Programs. The operating
system automatically handles the changing of terminal server modes.
Server
3-4
Configuration and Runtime
Configuration and Runtime
This section provides information pertaining to configuration.
Remote
Configuration
with PCC
You cannot use PCC through a terminal session to configure a
remote database engine. You must use PCC at the terminal server
console or through a standard remote connection to configure the
database engine on the terminal server machine.
Terminal Server You may use your terminal server as your main network server and
database server. However, if you have high usage of the server as a file
as Network
server as well as many terminal sessions running at the same time,
Server
you may find the performance less than satisfactory.
Another concern is having all of your mission critical services on the
same machine. If it goes down, all of your services go down at once.
For these reasons, you may wish to consider distributing your
mission critical services on two or more computers.
3-5
3-6
I NSTALLING C OMPONENTS
W INDOWS
FOR
chapter
Installing Pervasive PSQL
Server for Windows
4
Instructions for First-time Windows Server Installation
This chapter contains procedures for installing and running
Pervasive PSQL v9 Service Pack 2. The chapter contains the
following sections:

“Before You Begin” on page 4-2
“Installing Pervasive PSQL Server” on page 4-4
“Custom Installation Path” on page 4-13
“Common Questions After Installing Pervasive PSQL” on page
4-16
“Uninstalling Pervasive PSQL Server” on page 4-17
4-1
Installing Pervasive PSQL Server for Windows
Before You Begin
This section contains information with which you need to be
familiar to successfully install Pervasive PSQL v9 Service Pack 2.
Before installing Pervasive PSQL v9 Service Pack 2, begin by
reviewing the following documents:

Platform Notes
This section contains installation information specific to the
Windows platform.

Installation
Tips
Chapter 2, “Preparing to Install Pervasive PSQL” - This chapter
provides important information, including system requirements
and platform specific notes, relevant to your operation.
README - This file is located on the distribution media and
contains late-breaking product news that could not be included
in the product documentation. The file is available in HTML
format.

To install Pervasive PSQL for Windows, you must have full
administrator-level rights on the machine where you will install
the product.
If you want your individual client machines to install the
requesters from the server, you must copy the requester
programs from the Pervasive PSQL installation media to folders
on the server and give the clients permission to access those
folders. Refer to the “Clients” folder on the installation media.
You can also install clients directly from the installation media.
When installing Pervasive PSQL v9 Service Pack 2 for the first
time on a system, Setup will check if all of the needed system files
meet the minimum requirements. In some cases, these files are
locked by the operating system and a reboot is required before
Setup can continue. A dialog box displays if a reboot is required.
Click the “Yes” option to restart the system then click OK. Setup
is then automatically restarted.
Caution You must reboot your system if you encounter the reboot
message. If you do not reboot your system, Setup will encounter
failures during engine and utilities configuration.
4-2
Before You Begin

If you have any trouble with the following installation, see
Chapter 19, “Troubleshooting After Installation.”
4-3
Installing Pervasive PSQL Server
You must install the Pervasive PSQL Server for Windows at the server
itself; you cannot install it remotely from a client machine.
Note If the installation fails before the program copies any files to the
target installation directory, the installation log file (psqlinst.log) can
be found in the Windows directory. This directory is often c:\windows
or c:\winnt.
³ To install Pervasive PSQL Server on a Windows
machine:
1
Launch the installation selection program from your Windows
machine.
a. Insert the Pervasive PSQL Server for Windows CD in the
CD-ROM drive of your Windows server.
b. If the installation does not start automatically, click Start
then Run, and type drive:\autorun\autorun where
drive is the drive letter of your CD-ROM device.
The installation selection dialog displays.
2
Click the button for the “Windows Server” installation.
The installation program begins its initial preparation. After the
preparation completes, the Welcome screen appears.
If a dialog appears advising you that a reboot is required, see
“Installation Tips” on page 4-2.
4-4
3
Click Next to proceed with the installation.
4
Read the Software License Agreement.
5
Click the “accept” option to enable the Next button.
Figure 4-1 Pervasive Software’s Software License Agreement
6
Click Next.
A dialog appears on which you specify a license key.
7
Type, or paste, a license key into the License field, or install the
default evaluation license.
Figure 4-2 Applying the User Count License
Your Pervasive PSQL v9 Service Pack 2 Server is set to the
number of users specified in the license key.
Note If you do not yet have a license key or it is not with you at the
moment, you can still continue with the installation by using an
evaluation license. Click Next to evaluate the product for a trial period
The trial version license is valid for 30 days, then expires.
You may run the License Administrator utility at a later time to view or
install a user count license key. The License Administrator utility is
documented in Pervasive PSQL User's Guide in the section “License
Administrator” on page 4-1.
4-5
8
Click the setup type desired: Complete or Custom (the default is
Complete).
Figure 4-3 Setup Type Dialog Box
The Complete installation, which is recommended for most
users, takes default actions for operations performed during the
installation. The Complete server installation installs the
following components to drive C:

Pervasive PSQL v9 Service Pack 2 engine (including ODBC
interface)
Client requesters (MS-DOS, Win32)
Pervasive PSQL Control Center
Utilities
Note Client installation images for Windows and Linux are not part of
the server installation. You must run a separate installation program
for Pervasive PSQL clients. See “Installing Pervasive PSQL Clients for
Windows” on page 5-1 for more information.
The Custom installation is typically for advanced users. It allows
you to specify the installation location, select the components to
install, and determine the space requirements for the
components.
9
Click Next, then continue based on your choice of Complete or
Custom:

4-6
If you choose a Complete install, continue with the next
step.

If you choose a Custom install, skip now to “Custom
Installation Path” on page 4-13. At the end of that section
you will return to this set of steps to continue the
installation.
At this point, if you want, you may click Back to change or review
any of the installation settings, or click Cancel to exit the
installation program. After you click Install, you may still exit
the installation, but you will be unable to change or review
settings.
10 Click Install.
If required, close any running applications that may interfere
with the Pervasive PSQL installation. A dialog box appears if
applications are running that can interfere with the installation
of Pervasive PSQL.
Figure 4-4 Example Dialog Box for Programs that May Interfere
Decide how to continue with the installation. Your choices are:
a. To exit all of the programs that may interfere, then click
Next.
b. Not to exit all of the programs that may interfere, then click
Ignore.
Note Next does not proceed with the installation unless you exit all
programs that will interfere.
If you wish to leave one or more programs running that may interfere,
you must click Ignore to continue. Unpredictable results may occur
during the Pervasive PSQL installation if you ignore programs that
may interfere.
If no running applications interfere with the Pervasive PSQL
installation, the installation process continues. A dialog box
appears that gives you a status.
4-7
Figure 4-5 Installation Status Dialog Box
Installation actions include, but are not limited to, the following:

Script operations
Component registration
File copying
Shortcut creation
System registry updates
Sample database creation
After the initial actions, the installation process launches the
Pervasive System Analyzer (PSA) Wizard. The PSA Wizard
allows you to test the transactional and relational interfaces.
These tests ensure that your database engine is working as
expected.
By default, the option for the transactional tests is selected.
Figure 4-6 Transactional Engine Test
11 Click Next to run the transactional tests and to see the results.
PSA performs a series of tasks to ensure that the transactional
engine is working properly.
4-8
PSA displays a check mark for each test that passes and an X for
each task that fails during the transaction engine test. A
summary report is also provided in the information window, as
shown in the following figure.
Figure 4-7 Transactional Engine Test Results from PSA
12 Once your transactional tests are successful, click Next to
proceed with the PSA Wizard.
PSA is now ready to ensure that the relational engine is working
properly.
Figure 4-8 Relational Engine Test
Note that the tests use your current machine name and the
sample demodata database. Use these values unless you
specifically wish to test a different database. To test a different
database, enter the Machine Name and Engine DSN for the
engine data you want to test.
13 Click Next to run the relational tests and to see the results.
4-9
each task that fails during the relational engine test. A summary
report is also provided in the information window, as shown in
the following figure.
Figure 4-9 Relational Engine Test Results from PSA
14 Once your relational engine tests are successful, click Next.
The final dialog of the PSA Wizard displays and provides a
summary of the tasks completed by the Wizard.
If you want to view the PSA log file, it is named by default
PSALog.txt and is located by default at <OSdrive>\Program
Files\Common Files\Pervasive Software Shared\PSA,
where <OSdrive> is the drive letter where your operating system
is installed.
15 Click Finish to complete the PSA Wizard.
The final dialog of the Installation Wizard displays along with a
registration page.
16 Register your product.
Pervasive Software recommends that you register your product
to receive news about future updates, and other timely
information. You can also register later using a web, e-mail, or
print-based registration form.
4-10
Figure 4-10 Product Registration Page
If you did not read the README file prior to installation as
described in “Before You Begin” on page 4-2, please do so now
from the registration page.
17 Click Readme on the registration page to read the README file.
Figure 4-11 View Readme
18 Close the Registration page (click the “X” in the upper right
corner).
19 Click Finish to complete the Installation Wizard.
If installed files could not be copied because they were locked in
memory, a reboot may be necessary at this point. Setup only
prompts for a reboot if a locked file or some other event was
detected that requires a reboot. Please reboot your system if
prompted to do so in order to ensure proper operation of your
Pervasive PSQL v9 Service Pack 2 product.
4-11
Note If you have any trouble with the installation, see Chapter 19,
“Troubleshooting After Installation.”
The installation program modifies the PATH and CLASSPATH
environment variables at the end of the installation process. These
settings control how your Windows operating system finds Pervasive
components. OnWindows 32-bit platforms, these environment
variables are stored in System information, which you access from the
Control Panel.
Thank you for choosing Pervasive PSQL.
What to do Next See “Common Questions After Installing Pervasive PSQL” on page
4-16.
4-12
Custom Installation Path
This section describes how to customize your installation of
Pervasive PSQL. This topic continues a discussion from step 9 on
page 4-6.
1
Click on a feature’s icon to display the installation choices.
For example, the following image shows the choices if you click
on the Windows Client icon.
Figure 4-12 Example of Installation Choices
2
Decide how you want to install each program feature and click
that choice
Installation Choice
Meaning
This feature will be installed
on local hard drive.
The feature’s components, and subfeatures if you
choose, are installed on the machine running the
installation program.
This feature, and all
subfeatures, will be installed
This feature will not be
available.
The feature’s components are excluded from the
installation.
You may exclude any of the following:

Pervasive PSQL Control Center, including the JavaHelp
documentation
Other Utilities (except for a minimum set)
4-13
A minimum set of utilities is installed as part of the Pervasive
PSQL Server Option. This set includes Function Executor,
Database Password Utility (pvdbpass), Network Password
Utility (pvnetpass), and the following command-line interface
(CLI) utilities: Maintenance, Rebuild, and License
Administrator.
If you exclude utilities, you will be unable to configure your
Pervasive PSQL Server product. The product is installed using all
default values. In addition to no configuration ability, other
restrictions apply. For example, no wizards will be available. We
recommend that you include the utilities unless you are certain
that you do not require the functionality provided by them.
The following utilities are not installed if you exclude them.

Pervasive PSQL Control Center (PCC)
Table Editor
SQL Editor
All wizards
Monitor, GUI Maintenance, and GUI Rebuild
GUI License Administrator
Client machines require the client requesters to access database
files on a Pervasive PSQL Server machine. You can install clients
from the CD media.
3
Optionally, change the location where the Pervasive PSQL Server
product and its features are installed.
The default installation location is C:\PVSW, assuming the
Windows system drive is C. To specify a different location for the
installation, click Change, specify a location, then click OK.
You may select only one installation location for the entire
product. The Change button is disabled for a feature if you
choose not to install that feature.
4
Optionally, click on a feature to check the amount of storage
space it requires.
The space required appears on the right:
4-14
Figure 4-13 Location of Space Required Values
5
Optionally, check the amount of storage space available on the
physical drives.
Click Space. The resulting dialog shows you by storage volume,
the total disk space, the available disk space, the space required
for the feature, and difference between the available space and
space required. Click OK after you finish checking storage
capacity.
6
Click Next.
A dialog appears that informs you the installation program is
ready to begin installing files. At this point, if you want, you may
click Back to change or review any of the installation settings, or
click Cancel to exit the installation program. After you click
Install, you may still exit the installation, but you will be unable
to change or review settings.
The Custom path rejoins the Complete installation path at this
point. Continue with Step 10 on page 4-7.
4-15
Common Questions After Installing Pervasive PSQL
This section contains information that you should read after
running the installation program. If you are having problems with
your installation, go to Chapter 19, “Troubleshooting After
Installation,” or get help online from our Knowledge Base website at
http://support.pervasive.com/eSupport.
How Do I Read the Online Documentation?
The documentation for Win32 platforms is in JavaHelp format. You
access the documentation from the Pervasive program on the Start
menu. Note that JavaHelp requires a Java Runtime Environment
(JRE), which is installed by default with the Pervasive PSQL Server
or Pervasive PSQL Client.
You can also view the documentation in the form of Adobe Acrobat
(PDF) files. These PDF files are available on the Pervasive PSQL
installation media in the “Books” directory.
A README file in the root directory of the distribution media lists
important last-minute information.
How Do I Verify or Update My User License?
The License Administrator utility is documented in Pervasive PSQL
User's Guide in the section “License Administrator” on page 4-1.
Please refer to that document for information on user licenses.
Where To Go
From Here
4-16
Continue with your Pervasive PSQL deployment by installing and
configuring the client requesters for the machines that will connect
to this server. Review Chapter 5, “Installing Pervasive PSQL Clients
for Windows.”
Uninstalling Pervasive PSQL Server
Uninstalling Pervasive PSQL Server
The uninstall program removes all Pervasive PSQL Server
components from your system that were added by the installation
program.
The uninstall program does not remove the following:

Databases that you create under the Pervasive PSQL Server
installation directory (which is C:\PVSW by default).
DSNs and database names associated with those databases.
Databases in locations other than the Pervasive PSQL Server
installation directory.
DSNs and database names associated with those databases.
The system databases TEMPDB, SYSTEMDB, and
DEFAULTDB, and sample database DEMODATA.
³ To uninstall Pervasive PSQL Server:
1
Access Add/Remove Programs from Control Panel on your
Windows operating system.
2
Click Pervasive PSQL Server in the list.
3
Click the button to remove a program. The button may be
labeled Add/Remove or Remove.
Depending on your operating system, the uninstall program
may begin the uninstall process when you click Remove. If so,
skip to Step 8; otherwise, continue with the next step.
4
Click Next.
5
Click the Remove option (if it is not already selected).
Figure 4-14 Uninstall Remove Option
6
Click Next.
4-17
A dialog appears that informs you the program is ready to begin
removing Pervasive PSQL Server. At this point, if you want, you
may click Back to change or review any of the settings, or click
Cancel to exit the uninstall program.
4-18
7
Click Remove to begin the uninstall process.
8
Click Finish when the uninstall program completes.
9
Reboot your system if prompted to do so.
chapter
Clients for Windows
5
How to Install Pervasive PSQL Client Requester Software for Connecting to Servers

“Understanding Client Requesters” on page 5-3
“Installing the Pervasive PSQL Client Components” on page 5-6
“Custom Installation Path” on page 5-14
“Where To Go From Here” on page 5-16
“Installing DOS Requesters” on page 5-17
5-1
Installing Pervasive PSQL Clients for Windows
Before You Begin
familiar to successfully install Pervasive PSQL. If you have not
already, review the following documents before installing Pervasive
PSQL client requesters:

5-2
in the product documentation.
Understanding Client Requesters
A workstation that needs to access database files is considered a client
to the machine running the Pervasive PSQL Server product. A piece
of software called a client requester, or requester for short, is required
to access database files from a Pervasive PSQL database server. Your
application’s Pervasive PSQL calls go through the requester, which
sends them to the Pervasive PSQL Server for processing and then
returns the reply to your application.
Refer to the README file provided with the product for a list of the
platforms on which Pervasive PSQL requesters are supported. The
requesters use the TCP, SPX or NetBIOS protocols to communicate
with the server MicroKernel, depending on the type of server you
have. Ensure that your workstation has the appropriate network
protocol software installed.
Note Clients using DOS operating systems will have only transactional
access to the data files. No relational access is available for this
platform.
Types of
Windows
Requesters
Pervasive PSQL includes the following types of requesters for
Windows:

DOS
Trace
WIN32
You do not load or unload the Requester explicitly (except for the
DOS requester); the system loads the Requester with the first
application call to Pervasive PSQL and unloads the Requester when
you exit your application.
DOS Requesters
This type of requester is used for applications that run under the
DOS operating system. You may install only the DOS requesters if
that is all you require. See“Installing DOS Requesters” on page 5-17.
5-3
Trace Requesters
Trace requesters are used for troubleshooting (tracing) client
problems at a low level. Generally, you will never need to perform
this type of tracing. The low-level tracing is intended for use by
trained support staff. Your product vendor or Pervasive Software
Support will direct you on how to conduct low-level client tracing,
which includes how to use the trace requesters.
Note that the tools provided with Pervasive Software solve most
troubleshooting issues. For example, you would run the network
connectivity tests in Pervasive System Analyzer to verify network
connectivity. Also at your disposal is the Pervasive Knowledge Base
(http://support.pervasive.com/eSupport), through which you may
search for information about particular client issues.
WIN32 Requesters
This type of requester is used for applications that run under a
Windows 32-bit operating system.
Installation
You have two choices for installing the requesters: install all three
types or install only the DOS requesters.
A single installation program installs all three types of requesters to
a client workstation. In addition, a set of Pervasive PSQL utilities is
installed and a set of Pervasive PSQL documentation. By default, the
requesters and most of the utilities are installed to C:\PVSW. You
may change the location during the installation process. The
documentation set, Pervasive System Analyzer (PSA), and some
common files are installed to Program Files\Common
Files\Pervasive Software Shared.
If you require only the DOS requesters. See“Installing DOS
Requesters” on page 5-17.
Configuration
The configuration of requesters is covered in Chapter 18,
“Configuring Network Communications for Clients.”
Existing Configuration Settings
If you have an existing installation of the Pervasive PSQL client
software on your computer, nearly all of the client configuration
values are automatically migrated to the client configuration during
5-4
the installation process. There are two exceptions that are not
migrated, shown in Table 5-1.
Table 5-1 Configuration Setting Values not Migrated
Configuration Setting
Client
Access
Use IDS
Server Address Table (SAT),
not available in Configuration
but stored in Windows
Registry
Value
Off. Because most customers do not use the
idshosts file, by default this setting is turned off to
improve performance. If you use the idshosts file,
you must turn this setting On. See “Use IDS” on
page 5-45 in Advanced Operations Guide.
The SAT keeps a record of the computers where
database servers have been detected or not
detected, to improve connection time. This
registry key is reset during the installation and will
be re-populated over time as you connect to the
servers in your environment.
5-5
Installing the Pervasive PSQL Client Components
³ To install the Pervasive PSQL v9 Service Pack 2 client
software:
1
machine.
c. Insert the Pervasive PSQL Server for Windows CD in the
d. If the installation does not start automatically, click Start
2
Click the button for the “Client” installation.
3
4
Complete).
following components to the local machine:

5-6
Transactional and relational interfaces
Client requesters (DOS, Trace, and Win32 requesters)
Utilities
components.
5
Custom:

step.
installation.
settings.
6
Click Install.
7
with the Pervasive PSQL installation.
A dialog box appears if applications are running that can
interfere with the installation of Pervasive PSQL.
Next.
Ignore.
5-7
may interfere.
Pervasive PSQL product.

Script operations
File copying
Shortcut creation
Pervasive System Analyzer (PSA) Wizard. The PSA Wizard can
also test network communications from the client machine to
the machine running Pervasive PSQL Server. The Wizard
initiates this test automatically.
8
5-8
Test the network communications from the client machine to
the machine running Pervasive PSQL Server.
For Target Machine, type the name or IP address of the machine
running Pervasive PSQL Server. For example, the following
example shows that the machine name is MachineA.
Figure 5-4 Network Communication Test
The communication test transmits a series of 75 test messages
between the two machines. Click Advanced Settings if you want
to change the number of messages transmitted or the type of
protocol used for the communication test.
9
Click Next.
Figure 5-5 Network Transmission of Test Messages
After all test messages are transmitted and received correctly, a
dialog confirms that all messages were successfully transmitted.
Figure 5-6 Successful Transmission of Test Messages
10 Click Next.
The PSA Wizard also allows you to test the transactional and
relational interfaces. These tests ensure that the database engine
on the machine running Pervasive PSQL Server is working as
expected.
5-9
11 Type the location of the Pervasive PSQL samples directory on
the machine running Pervasive PSQL Server.
By default, the directory is located on the server at
C:\PVSW\samples. Suppose, for example, that you have mapped
drive “P” to the machine running Pervasive PSQL Server. You
would specify the samples directory as shown in the figure
above.
5-10
properly.
If necessary for Machine Name, type the name of the machine
running Pervasive PSQL Server. Note that the test uses the
sample demodata database.
5-11
is installed.
registration page.
5-12
corner).
Restarting Your You should restart your Windows machine at the end of the
Computer After installation process if any of the following are true:
Installation

The installation program prompts you to reboot. This may be

due to installed files that could not be copied because they were
locked in memory.
You are using Windows 98 or Windows ME
Note The install program modifies the PATH and CLASSPATH
variables at the end of the installation process. These settings control
how Windows finds Pervasive components. On Windows 32-bit
platforms, environment variables are stored as part of System
information, which you access from the Control Panel.
5-13
Pervasive PSQL client components. This topic continues a
discussion from step 5 on page 5-7.
1
Decide if you want to exclude utilities.
A minimum set of utilities is installed as part of the Pervasive
PSQL client. This set includes the Password Utility and the
following command-line interface (CLI) utilities: Maintenance,
Rebuild, and License Administrator.
If you exclude the optional utilities, you will be unable to
configure your requester. The product is installed using all
recommended that you include the utilities unless you are
certain that you do not require the functionality provided by
them.

2
Pervasive PSQL Control Center (PCC) and JavaHelp
documentation
Table Editor and SQL Editor
All wizards
Figure 5-13 Example of Installation Choices (Client Components)
3
5-14
Click the desired installation choice.
4
If desired, change the location where the Pervasive PSQL
requester components are installed.
5
If desired, click on a feature to check the amount of storage space
it requires.
6
If desired, check the amount of storage space available on the
physical drives.
Click Space. The resulting dialog shows you by storage volume,
the total disk space, the available disk space, the space required
for the feature, and difference between the available space and
space required. Click OK after you finish checking storage
capacity.
7
Click Next.
5-15
Where To Go From Here
A proper configuration is essential to smooth operation of your
requester software. See Chapter 18, “Configuring Network
Communications for Clients” for detailed information on how to
configure Pervasive PSQL requesters.
If you need to install DOS requesters, please continue reading this
chapter. See “Installing DOS Requesters” on page 5-17.
5-16
Installing DOS Requesters
Pervasive PSQL v9 Service Pack 2 supports DOS Btrieve applications
in several different ways. This, however, depends on the current
configuration and environment of the workstation.
Available
Requesters
The following choices are available:

Win32 DOS Box support: Allows a DOS application to run in a
DOS box on a Windows NT or Windows 98 workstation. This
enables direct communication to the Windows 32-bit
workstation components rather than to the database engine.
This configuration can be used with either a local Pervasive
PSQL v9 Service Pack 2 Workgroup engine, or a remote
Pervasive PSQL v9 Service Pack 2 server engine. The TCP/IP or
SPX protocol supported for client/server access depends on the
configuration of the Windows 32-bit components.
DOS TCP/IP requester (BREQTCP): Allows a DOS application
to run in any Windows DOS box or on a DOS workstation, and
communicate to a remote Pervasive PSQL v9 Service Pack 2
server engine via the TCP/IP protocol.
DOS SPX requester (BREQUEST or BREQNT): Allows a DOS
application to run in any Windows DOS box or on a DOS
workstation, and communicate to a remote Pervasive PSQL v9
Service Pack 2 server engine via the SPX protocol.
There are different reasons for using these different options,
including:

Pervasive PSQL v9 Service Pack 2 Workgroup engine only
supports the Win32 DOS Box configuration.
DOS operating system requires the DOS TCP/IP or SPX
requesters when accessing a remote server engine.
A particular environment may have only one of the supported
protocols available.
Windows 98/ME and 32-bit Platforms
The preferred requester for Windows 98/ME and 32-bit platforms is
BTRBOX. You can use this Requester even for legacy DOS
applications.
5-17
Note Use the BREQUEST/BREQNT/BREQTCP Requesters ONLY if
you experience a problem with BTRBOX.
Win16 and DOS Workstations
The Requesters for non-Win32 boxes are:

BREQUEST
BREQNT
BREQTCP
If you experience problems with these requesters, see “Alternate DOS
Installation of
the DOS
Requesters
³ To install Pervasive PSQL v9 Service Pack 2 client
software on a DOS client:
Note Clients using the DOS operating system will have only
transactional access to the data files. No relational access is available for
this platform.
Installation of the DOS requesters is a matter of copying the files to
the desired directory on your hard drive.
1
Find the “Client” directory on the Pervasive PSQL installation
media.
2
Copy the contents of “DOS” directory to the desired directory
on your hard drive.
To configure your DOS requesters, go to “Using the DOS
Alternate DOS
Requesters
Functionality was added to BREQUEST.EXE, BREQNT.EXE and
BREQTCP.EXE starting in versions Pervasive.SQL 2000i (SP3) to
allow them to access newer Novell NetWare Client APIs to obtain
information about the user's rights to files being Opened or Created.
This reduced the time required to Open or Create a file by
approximately two seconds.
On some DOS machines, however, these improved executable files
do not function correctly and the following issues may result:
5-18

Status 20 (the Microkernel or Btrieve Router is inactive)
Status 91 (application encountered a server error)
Status 94 (application encountered a permission error)
EMM386 error #12 and EMM386 general protection faults
(GPF).
If you experience any of these issues using the standard DOS
requesters, there are two possible solutions:

Upgrade the Novell NetWare Client to those Novell shipped with
NetWare 5.0 or later.
Use the alternate DOS requesters.
Pervasive includes versions of the BREQ*.EXE executable files
that do not include the newer NetWare API calls. These
executable files are in the DOS\ALT directory on the Pervasive
PSQL installation media (under the “Clients” folder).
Replace the BREQ*.EXE files on your DOS requester with the
alternate files.
5-19
5-20
chapter
Network Communication with
Pervasive PSQL Server for Windows
6
Network Communications for a Windows-based Pervasive PSQL Server
This chapter identifies the network communication settings for your
database server engine and how to set protocol support for your
network.

“Determining What Kind of Network You Have” on page 6-2
“Network Communication Settings” on page 6-3
“Setting Up TCP/IP Support” on page 6-4
“Setting Up SPX Support” on page 6-6
“Avoiding Unavailable Protocols” on page 6-8
6-1
This section explains how to determine the network protocol that
you should use with the database engine. If you already know what
protocol or protocols are supported on your network, you can skip
this section.
Server Engine
on Windows
If your network is 100% Microsoft, and you have a database Server
engine, then your network probably uses TCP/IP. The Server engine
does not support NetBIOS.
You can run applications over SPX on Microsoft networks if the
applications use only the Pervasive PSQL transactional interface.
The use of ODBC applications over SPX requires a NetWare server
for name resolution. If you do not have a NetWare server on your
network, you may not use SPX for ODBC applications.
(Applications that use the relational interface.)
Server Engine
on NetWare
If you have a NetWare network, you must determine whether it is
running SPX, TCP/IP, or both. You can find out whether TCP/IP is
supported by checking to see if TCPIP.NLM is loaded on the server.
Server Engine
on Linux
Linux engines support only TCP/IP.
6-2
Network Communication Settings
Network Communication Settings
This section references server configuration settings that are related
to network communication. Configuration settings are properties of
the server engine. You specify configuration settings with PCC or a
command line utility. See “Changing Your Configuration” on page
4-1 in Advanced Operations Guide.
See the following configuration settings for network
communication:

“Auto Reconnect Timeout” on page 5-16 in Advanced Operations
Guide.
“Enable Auto Reconnect (Windows/NetWare only)” on page 516 in Advanced Operations Guide.
“Listen IP Address” on page 5-17 in Advanced Operations Guide.
“Supported Protocols” on page 5-17 in Advanced Operations
Guide.
“TCP/IP Multihomed” on page 5-18 in Advanced Operations
Guide.
“TCP/IP Port” on page 5-18 in Advanced Operations Guide.
6-3
Setting Up TCP/IP Support
By default, TCP/IP is supported between Pervasive PSQL clients and
remote database engines. If you have modified the default settings or
need to verify that TCP/IP support is available, refer to this section.
Note To perform any of the tasks in this section, you must have full
administrator-level rights on the machine where the database engine is
running, or be a member of the Pervasive_Admin group defined on the
machine where the database engine is running.
³ Enabling TCP/IP Support
Complete the following steps to ensure that the database engine can
communicate with clients over TCP/IP networks.
Remember that you also need to confirm that your client computers
are configured to use TCP/IP, as well. See Chapter 18, “Configuring
Network Communications for Clients.”
1
Start Pervasive PSQL Control Center (PCC) from the Pervasive
program on the Start menu.
2
In the PCC Pervasive PSQL Explorer, double-click Engines to
display a list of the engines registered with PCC.
3
Right-click on the icon representing your target engine then
click Properties. Login if prompted. Click on Communication
Protocols.
In the window to the right, a list of Supported protocols
displays. If the list of supported protocols shows the option TCP/
IP as checked, then TCP/IP is already supported. Skip the
remaining steps in this task.
If the list of selected protocols does not show the option TCP/IP
as checked, complete the remaining steps.
6-4
4
Click the option for TCP/IP in the list of supported protocols.
5
Click OK.
6
Click Yes to restart the database engine.
³ Enabling Multihomed TCP/IP Support
Follow this procedure if your Windows server computer has two
network cards installed.
1
2
If the engine you want to configure is not listed, right-click on
Engines and click New Server. Provide a server name or IP
address then click Finish.
3
click Properties. Login if prompted.
4
Click on Communication Protocols.
In the window to the right, you can see the current setting for
TCP/IP Multihomed.
5
If you want the server engine to listen for client connections on
both network cards, click the option for TCP/IP Multihomed.
If you only have one network card, this setting is ignored.
If you want the server engine to listen on only one card, deselect
(uncheck) the option.
6
Click OK.
7
You do not need to make any changes to client settings.
Note If your server computer has two network cards, and you set the
value of TCP/IP Multihomedto Off, you must edit the setting Listen IP
Address and specify the TCP/IP address of the card on which you want
the database engine to listen. If you do not specify an IP address, the
database engine will not receive communications from either network
card.
6-5
Setting Up SPX Support
SPX is supported between Pervasive PSQL clients and servers. If you
have modified the default settings or need to verify that SPX support
is available, refer to this section.
Your network’s SPX Frame Type setting does not have any effect on
Pervasive PSQL.
Note In order to perform any of the tasks in this section, you must
have administrative rights on the NetWare server, or be a member of
the Pervasive_Admin group defined on the server.
³ Enabling SPX Support
Complete the following steps to ensure that the database server
engine can communicate with clients over SPX networks.
are configured to use SPX, as well. See Chapter 18, “Configuring
Network Communications for Clients.”
Note In an all-Microsoft environment, SPX can be used with
applications that use only the Pervasive PSQL transactional interface.
With ODBC applications that use the relational interface, a NetWare
server must be present to provide name resolution for SPX.
Applications that use only the transactional interface do not require
name resolution with SPX.
6-6
1
2
3
4
5
displays. If the list of supported protocols shows the option SPX
as checked, then SPX is already supported. Skip the remaining
steps in this task.
If the list of selected protocols does not show the option SPX as
checked, complete the remaining steps.
6
Click the option for SPX
7
Click OK.
8
6-7
Avoiding Unavailable Protocols
It may be possible to improve performance on the initial connection
to the database by disabling database communication support for
any protocols that are not available on your network or that you do
not wish to use.
have full administrator-level rights on the machine where the database
engine is running, or be a member of the Pervasive_Admin group
defined on the machine where the database engine is running.
³ To Remove Support for a Specific Network Protocol
are configured to use same protocol(s) as the database engine. See
Chapter 18, “Configuring Network Communications for Clients.”
Note This task does not affect your operating system configuration in
any way. This this prevents only the database communication system
from attempting to communication on unavailable or undesired
protocols.
6-8
1
2
3
4
5
displays. Protocols for which the option is selected (check
marked) are considered available for use by the database engine.
6
If the list of selected protocols includes any protocols that are not
supported on your network or that you do not wish to use,
uncheck the option for that protocol.
Avoiding Unavailable Protocols
You must leave at least one protocol selected in the Selected
protocols list.
7
Click OK.
8
6-9
6-10
chapter
Upgrading Your Pervasive PSQL
Installation for Windows
7
Instructions for Upgrading an Existing Pervasive PSQL Installation
This chapter contains information specific for upgrading your
current Pervasive product installation to Pervasive PSQL v9 Service
Pack 2. The number of required steps in the upgrade process is small,
but depending on your environment, it can be a time-consuming
process.

“Upgrading to Pervasive PSQL Server from Earlier Pervasive
PSQL Versions or Btrieve 6.x” on page 7-5
“Custom Installation Path,” on page 7-14
7-17
Throughout this document, when an explicit version number is not
specified (for example: Pervasive.SQL 7, Pervasive.SQL 2000, or
Pervasive PSQL v9 Service Pack 2), all versions are included.
7-1
Upgrading Your Pervasive PSQL Installation for Windows
Before You Begin
Before upgrading to Pervasive PSQL v9 Service Pack 2, begin by
reviewing the following documents for important information:
R Chapter 2, “Preparing to Install Pervasive PSQL” - This chapter
provides important information including system requirements
and platform specific notes that are relevant to your operation.
R README file - This file is located on the distribution media and
Considerations Once you have reviewed the latest product information, review this
list of considerations to complete your upgrade installation
preparation.
R Pervasive PSQL Applications - Be aware of what applications you
have currently using previous versions of Btrieve or Pervasive
PSQL in your environment. Remember to include both client
and server-based applications.
R Vendor-Specific Information - Be sure and check with your
application vendors for any specific information regarding their
product with Pervasive PSQL.
R TCP/IP Protocol - DOS applications require different requesters,
preferably BTRBOX95, BTRDRVR, or BREQTCP.
Requesters or Server First? - Pervasive's upgrade and support
policy dictates that you should always use requesters that are the
same version as your Server database engine. Typically, a client
requester that is an older version than the database engine with
which it interacts will work. In some situations, depending on
the type of SDK access method used by your application, an
older version requester will not work with the database engine.
Your application will be unable to communicate with the
database engine. For those situations, you must use client
requesters that are the same version as the database engine. See
“Engine and Client Version Conflicts” on page 19-12.
7-2
Before You Begin
Therefore, Pervasive recommends that you upgrade your
requesters along with your server engine. You should install the
server first and immediately upgrade all the client machines.
R New Features and File Rebuilding - In order to make use of all the
new version features, you must rebuild your data files so that
they use the newest version file format. Advanced Operations
Guide includes a chapter that details using the Rebuild Utility to
rebuild your data files, if you would like to take advantage of
newer features.
R Back Up Data Files - Make sure you have a current backup of all
your data files prior to beginning upgrade installation.
Platform Notes
This section contains installation information specific to the
Windows platform.

Migration of
Existing
Configuration
Settings
To install Pervasive PSQL for Windows, you must have full
administrator-level rights on the machine where you will install
the product. You need administrative rights to make the client
installation directories available to your workstations.
If you want your individual client machines to install the
requesters from the server, you must copy the requester
programs from the Pervasive PSQL installation media to folders
on the server and give the clients permission to access those
folders. Refer to the “Clients” folder on the installation media.
You can also install clients directly from the installation media.
During the installation process, all of your existing server
configuration values are migrated to the new server engine, with
several exceptions. The exceptions are documented in Table 7-1.
Value in V8
Server Debugging
File Location
C:\pvsw\bin\mkde.tra [default]; or bin\mkde.tra file
in selected installation directory.
Trace
Server Directories
Transaction Log Directory
C:\pvsw\bin\mkde\log [default]; or bin\mkde\log
subdirectory of selected installation directory.
Server Compatibility
Create File Version
9.x. By default, new data files are always created
in the most recent file format.
7-3
Installing Over
Existing
Pervasive
Products
Value in V8
Server Memory Usage
System Cache
Off. With the addition of Level 2 database cache
in V8, the system cache should not be used.
Server Data Integrity
Transaction Durability
Off. With the addition of a new setting,
Transaction Logging (default: On), Transaction
Durability is not needed to ensure multi-file
transaction atomicity and data integrity. If your
application requires true Transaction Durability,
you will need to use Configuration to turn this
setting On.

Accessing
README file
information
7-4
If you are upgrading from older product versions such as Btrieve
6.15 and wish to make use of all the new version features, you
must rebuild your data files so they use the latest file format. See
“Converting Data Files” on page 14-1 in Advanced Operations
Guide section for detailed information on how to use the
Rebuild Utilities to convert your data files.
If you install Pervasive PSQL v9 Service Pack 2 over an existing
version such as Pervasive.SQL V8, Pervasive.SQL 2000, or
Btrieve 6.15, then those products will be archived when you
install Pervasive PSQL v9 Service Pack 2 so that there are no
component conflicts. You can use Pervasive System Analyzer
later to restore the archived products if necessary. Your licenses
from previous Pervasive products are not migrated to Pervasive
PSQL v9 Service Pack 2.
It is highly recommended that you go through the README file to
find out the latest changes and additions to Pervasive PSQL v9
Service Pack 2. The README file is located in the root directory of
the installation media.
Upgrading to Pervasive PSQL Server from Earlier Pervasive PSQL Versions or Btrieve 6.x
Upgrading to Pervasive PSQL Server from Earlier Pervasive
PSQL Versions or Btrieve 6.x
You must install the Pervasive PSQL Server upgrade at the server
itself; you cannot install it remotely from a client machine.
target installation directory, the installation log file (psqlinst.log) can
be found in the directory specified by the %TEMP% environment
variable. This directory is often c:\windows\temp or c:\winnt\temp.
³ To upgrade to Pervasive PSQL Server:
1
machine.
c. Insert the Pervasive PSQL Server for Windows CD in the
d. If the installation does not start automatically, click Start
2
Click the button for the “Server” installation.
If a dialog appears advising you that a reboot is required, see
“Installation Tips” on page 4-2.
3
4
5
Click the “accept” option to enable the Next button.
7-5
6
Click Next.
7
Type, or paste, a license key into the License field, or install the
default evaluation license.
number of users specified in the license key.
evaluation license. Click Next to evaluate the product for a trial period
The trial version license is valid for 30 days, then expires.
You may run the License Administrator utility at a later time to view or
install a user count license key. The License Administrator utility is
7-6
8
Complete).
following components to drive C:

interface)
Client requesters (MS-DOS, Win32)
Utilities
Note Client installation images for Windows and Linux are not part of
the server installation. You must run a separate installation program
for Pervasive PSQL clients. See “Installing Pervasive PSQL Clients for
Windows” on page 5-1 for more information.
components.
9
Custom:

step.
7-7

installation.
settings.
10 Click Install.
with the Pervasive PSQL installation. A dialog box appears if
applications are running that can interfere with the installation
of Pervasive PSQL.
Next.
Ignore.
may interfere.
7-8

Script operations
File copying
Shortcut creation
Sample database creation
Pervasive System Analyzer (PSA) Wizard. The PSA Wizard
allows you to test the transactional and relational interfaces.
These tests ensure that your database engine is working as
expected.
7-9
properly.
Note that the tests use your current machine name and the
sample demodata database. Use these values unless you
specifically wish to test a different database. To test a different
database, enter the Machine Name and Engine DSN for the
engine data you want to test.
7-10
is installed.
registration page.
7-11
corner).
Pervasive PSQL v9 Service Pack 2 product.
7-12
Note If you have any trouble with the installation, see Chapter 19,
The installation program modifies the PATH and CLASSPATH
environment variables at the end of the installation process. These
settings control how your Windows operating system finds Pervasive
components. OnWindows 32-bit platforms, these environment
variables are stored in System information, which you access from the
Control Panel.
What to do Next See “Common Questions After Installing Pervasive PSQL” on page
7-17.
7-13
Pervasive PSQL v9 Service Pack 2. This topic continues a discussion
from step 9 on page 7-7.
1
on the Windows Client icon.
Figure 7-12 Example of Installation Choices
2
Decide how you want to install each program feature and click
that choice.
Installation Choice
Meaning
available.
installation.
You may exclude any of the following:

7-14
Utilities (except minimum set)
Windows Client image
DOS Client image
Linux Client in RPM or Tar format
You may not exclude the minimum set of utilities. The minimum
set includes Function Executor, Database Password Utility
(pvdbpass), Network Password Utility (pvnetpass), and the
following command-line interface (CLI) utilities: Maintenance,
Rebuild, and License Administrator.
If you exclude utilities, you will be unable to configure your
Pervasive PSQL Server product. The product is installed using all
recommended that you include the utilities unless you are
certain that you do not require the functionality provided by
them.

Table Designer and SQL Data Manager
All wizards
If you exclude client images, you will be unable to install the
client requesters from a Pervasive PSQL Server machine. You
may install them from the CD media. Client machines require
requesters to access database files on a Pervasive PSQL Server
machine.
3
Optionally, change the location where the Pervasive PSQL Server
product and its features are installed.
4
Optionally, click on a feature to check the amount of storage
space it requires.
7-15
5
Optionally, check the amount of storage space available on the
physical drives.
Click on a feature, then click Space. The resulting dialog shows
you by storage volume, the total disk space, the available disk
space, the space required for the feature, and difference between
the available space and space required. Click OK after you finish
checking storage capacity.
6
Click Next.
7-16
This section contains information that you should read after
running the installation program. If you are having problems with
your installation, go to Chapter 19, “Troubleshooting After
Installation,” or get help online from our Knowledge Base website at
http://support.pervasive.com/eSupport.
How to Handle Data Source Names (DSNs)
The following table describes the procedures for upgrading your
DSNs after you have installed the Pervasive PSQL upgrade.
Table 7-2 How to Proceed After Installing Server and Client Software
If your situation is like this....
... then you should do this next:
You have existing
Pervasive.SQL 7 DSNs already
defined.
You must delete and re-create all existing
Pervasive.SQL 7 DSNs before you can access
existing databases. Follow the instructions
provided in Pervasive PSQL User's Guide
Chapter 2, sections “Deleting DSNs” and
“Setting Up Database Access on Windows.”
You have existing
Pervasive.SQL 2000 DSNs
already defined.
You should be able to access your databases by
connecting to the existing DSNs. Follow the
instructions provided in Pervasive PSQL User's
Guide, Chapter 2, section “Accessing Data via
ODBC From Other Applications.”
You do not have any Pervasive
PSQL DSNs defined
You should be able to connect to the sample
DEMODATA database now. Refer to Pervasive
PSQL User's Guide for general information on
working with Pervasive PSQL. Refer to
Advanced Operations Guide for detailed
information on working with databases and
database engines.
How Do I Convert My Data Files From Previous Pervasive
Products?
You are not required to rebuild your data files from previous releases
after you upgrade your version of Pervasive PSQL. Pervasive PSQL is
completely backward compatible in respect to data file formats
supporting file formats 6.x, 7.x, and 8.x.
7-17
However, note that certain Pervasive PSQL features and
functionality are unavailable if you do not rebuild your data files to
the latest version format.
The following table lists some of the main features of Pervasive PSQL
releases to help you determine if you want to rebuild data files.
File Version
Product Features
6.x
Performance improvements
Transaction Logging and Durability if your data file
contains a unique key
International Sort Rule (ISR) support
7.x
64 GB file size limit
Transaction Logging and Durability if your data file
does not contain a unique key
8.x
Turbo Write Accelerator
9.0
Higher than 64 GB file size (up to 128 GB)
8K page size
9.5
File size up to 256 GB
16K page size
The Rebuild utility can convert older data files to the current
Pervasive PSQL format. See “Converting Data Files” on page 14-1 in
Advanced Operations Guide.
The documentation for Win32 platforms is in JavaHelp format. You
access the documentation from the Pervasive program on the Start
menu. Note that JavaHelp requires a Java Runtime Environment
(JRE), which is installed by default with the Pervasive PSQL Server
or Pervasive PSQL Client.
(PDF) files. These PDF files are available on the Pervasive PSQL
installation media in the “Books” directory.
A README file in the root directory of the distribution media lists
important last-minute information.
7-18
Please see that document for information on user licenses.
7-19
7-20
chapter
Application Configuration
Scenarios
8
Common Scenarios for Setting up Your Server
This chapter explains how to configure your server for several
common application scenarios.

“Support for Active Directory Service” on page 8-2
“Multiple Client Applications” on page 8-11
“Concurrent Local and Remote Applications” on page 8-13
8-1
Application Configuration Scenarios
Support for Active Directory Service
This section describes how to install and configure Pervasive PSQL
in an environment that uses Microsoft Active Directory service.
What Is Active
Directory?
Active Directory is a central component of the Windows 2000
operating system network architecture. Active Directory provides a
directory service specifically designed for distributed networking
environments.
The Microsoft Web site provides much information about Active
Directory. The following Web links provide information to help you
learn about Active Directory.

Installation of
Active
Directory
Home page for Active Directory — http://www.microsoft.com/
windows2000/technologies/directory/ad/default.asp
Overview of Active Directory — http://www.microsoft.com/
windows2000/server/evaluation/features/dirlist.asp
Overview of Active Directory Service — http://
www.microsoft.com/windows2000/server/evaluation/business/
addatasheet.asp
Ensure that Active Directory service is installed and functioning
correctly before you install Pervasive PSQL into the environment.
Microsoft provides step-by-step guides to help you install and
configure Active Directory service. The following Web links provide
information to help you install and manage Active Directory.

Windows 2000 Step-by-Step Guides — http://
www.microsoft.com/windows2000/techinfo/planning/
walkthroughs/default.asp
Installing a Windows 2000 Server as a Domain Controller —
http://www.microsoft.com/windows2000/techinfo/planning/
server/serversteps.asp
Managing Active Directory — http://www.microsoft.com/
windows2000/techinfo/planning/activedirectory/
manadsteps.asp
Note that Windows 2000 implements TCP/IP as the default protocol
and relies on TCP/IP for most of the services associated with the
operating system, including Active Directory service. Integration of
8-2
Active Directory with NetWare Directory Services is possible with
Microsoft Directory Synchronization Services (MSDSS) and
DirSync. For more information, refer to the Microsoft Web site:
http://www.microsoft.com/WINDOWS2000/sfn/msdss.asp.
Installation of
Pervasive
PSQL
The installation of the Pervasive PSQL database engine in an Active
Directory environment requires no special steps. Install it as
described in “Installing Pervasive PSQL Server” on page 4-4.
The following environment modes are supported:

Native mode — all domain controllers run Windows 2000
Mixed mode — some domain controllers run Windows 2000
You may install the Pervasive PSQL database engine on a domain
controller if you choose. Be aware, however, that activity on the
domain controller may affect the performance of the database
engine. For this reason, you may prefer to install Pervasive PSQL on
a server that is not a domain controller.
Server and Client Support
Pervasive PSQL Server runs on Windows 32-bit Servers within an
Active Directory environment. The Pervasive PSQL clients run on all
Windows 32-bit platforms within an Active Directory environment.
The DOS TCP/IP requester (BREQTCP) is supported within an
Active Directory environment. The DOS SPX requester
(BREQUEST or BREQNT) is not supported because it requires the
SPX protocol.
Directory and File Permissions
The database engines enforce directory and file permissions set at the
operating system level. An Active Directory environment does not
change this behavior. For example, if you set “read only” permission
on a Pervasive PSQL table file, you will be unable to write to the
table.
Microsoft Terminal Services Support
Pervasive PSQL Server is supported for use with Microsoft Terminal
Server and Citrix MetaFrame running within an Active Directory
environment. For more information about Terminal Services and
8-3
Citrix MetaFrame, see “Pervasive PSQL and Terminal Services” on
page 3-1.
Pervasive
Administrative
Authority
Active Directory service manages the security of the network. You
must grant the correct access authority at the operating system level
to users who need Pervasive administrative privileges.
See “Active Directory Tasks” on page 8-4 for the steps to set access
authority. Users must have the following authority on the machine
running the database engine:

Log on locally
Administrator privileges or belong to the Pervasive_Admin
group
You may grant the Log on locally authority directly to a user or to the
Pervasive_Admin group (and add the user to the group).
You may create the Pervasive_Admin group on the machine running
the database engine (the local machine), on the domain controller
for the local machine, or on both. The database engine checks
privileges first on the domain controller for the local machine then
on the local machine.
An example helps illustrate this. Suppose you have two servers in
your domain that run the Pervasive PSQL database engine, Server A
and Server B. You could create a Pervasive_Admin group on each
server and on the domain controller. You then add User 1 to the
group on Server A, User 2 to the group on Server B, and User 3 to the
group on the domain controller. User 1 has administrative privileges
for the database engine only on Server A. Similarly, User 2 has
administrative privileges only on Server B. User 3, however, has
administrative privileges for the database engines on both Server A
and Server B.
If you create the Pervasive_Admin group on a domain controller,
then the group must be a domain local group. If you create the
Pervasive_Admin group on a machine that is not a domain
controller, then the Pervasive_Admin group must be a local group.
Active
This section explains the tasks needed to ensure users have Pervasive
Directory Tasks administrative privileges. The tasks assume the following:

8-4
Network user IDs have been added for users who need Pervasive
administrative privileges

A Pervasive_Admin group has been created on the domain
controller and users added to the group
Windows 2000 Server is the operating system on the domain
controller.
³ To Create the Pervasive_Admin Group on a Domain
Controller
1
Click Start Programs Administrative Tool Active Directory
Users and Computers.
2
Expand the tree for the domain to which you want to add the
Pervasive_Admin group (click the plus sign).
For example, the following image shows the expanded tree for
the ADSTEST.com domain.
8-5
3
Right-click on the Organizational Unit or folder that you are
using in your Active Directory environment to house groups,
then click New Group. For example, the following image shows
an Organizational Unit named “Groups,” but your
Organizational Unit may be named differently.
Note If your Active Directory environment does not have an
Organizational Unit to house groups, you need to create one. Click on
the domain root (for example, in the figure above, you would rightclick on ADSTEST.com), then click Action New Organizational
Unit. Type a meaningful name for the unit, then click OK.
4
For Group name, type Pervasive_Admin. Click Domain local
for group scope.
Note The Pervasive_Admin group must have a scope of Domain local.
Do not use Global or Universal.
5
8-6
Click OK.
Now that the Pervasive_Admin group exists, you need to add
users to it.
6
On the Active Directory Users and Computers window, rightclick on the Pervasive_Admin group, then click Properties. (You
may also double-click the group.)
7
Click the Members tab on the properties dialog.
8
Click Add on the Members tab.
9
Click on the user in the Name list that you want to add to the
Pervasive_Admin group, then click Add.
The user is added to the list on the bottom. For example, the
following image shows that user ADS_USER1 has been added.
10 Click OK.
8-7
The user you added now appears as a member of the
Pervasive_Admin group.
11 Click OK to exit the properties dialog.
12 Add the Pervasive_Admin group to the Log on locally privileges
(complete the task “To Grant Log On Locally Privileges to the
Pervasive_Admin Group”).
³ To Grant Log On Locally Privileges to the
Pervasive_Admin Group
1
Click Start Settings Control Panel.
2
Double-click Administrative Tools (or right-click then click
Open) to open the Administrative Tools window.
3
Double-click Domain Controller Security Policy (or right-click
then click Open) to open the Domain Controller Security Policy
window.
Note Ensure that you open Domain Controller Security Policy and not
Domain Security Policy.
4
Expand the following security settings (click the plus signs):

8-8
Security Settings

Local Policies
5
Click User Rights Assignment.
6
Scroll the policies in the right pane until you locate Log on
locally.
7
Double-click the Log on locally policy (or right-click the policy
then click Security).
The policy setting dialog appears.
8
Click Add.
The dialog appears on which you add users and groups.
8-9
9
Type Pervasive_Admin in the Users and group names field.
You may also specify the group by clicking Browse and
navigating to the group through dialogs.
10 Click OK.
The Security Policy Setting dialog appears with
Pervasive_Admin added.
11 Click OK to exit the Security Policy Setting dialog.
12 Exit the Domain Controller Security Policy window.
8-10
Multiple Client Applications
Multiple Client Applications
Sometimes, two or more client/server applications may use the same
database server. You will need to configure the server differently
depending on whether the applications are used at the same time.
If your vendors supply configuration guidelines for Server
configuration parameters, you will need to adjust your configuration
based on these guidelines.
If the applications run concurrently (that is, if two or more
applications are using the database server at the same
time) ...
You should configure the server by adding together all the
recommended values for each parameter. For example, if one
application vendor suggests Performance Tuning | Number
of Input/Output Threads should be set to 4, and another
application vendor suggests this parameter should be set to 8,
then you should set it to 12.
If the default value is higher than the sum of the recommended
settings, then do not change the default value.
Do not add up the recommended values for any buffer size
settings, or log file size settings. Use the largest recommended
setting. Again, do not change the default if it is larger than any
vendor recommendation.
If the applications do not run concurrently (that is, if only
one application is running at any given point in time) ...
You should configure the server by using the largest
recommended value for each parameter. For example, if one
application vendor suggests Performance Tuning | Number
of Input/Output Threads should be set to 4, and another
application vendor suggests this parameter should be set to 8,
then you should set it to 8.
If the default value is higher than the largest recommended
setting, then do not change the default value.
Settings
Affected by
Multiple
Applications
Most server settings are not affected when you are running multiple
applications. This section explains the settings that may need to be
adjusted for multiple applications.
8-11
Compatibility | Create File Version
Some applications may require that new files be created with version
7.x file format, while other applications may require version 9.x file
format (the default).
These applications can run concurrently only if new files are not
created during run time. There is no way to toggle the setting back
and forth for each application, unless you wish to do it by hand or
write a program to do so using the Distributed Tuning Objects.
If the applications do not create new files during runtime, then this
setting is not relevant for multiple applications.
Data Integrity | Transaction Durability
Some applications may require durable transactions, while others
may not. If you have two application vendors recommending
different values for this parameter, then you should set it to On.
Generally, having transaction durability turned on does not affect
applications that do not use transactions, but will incur a
performance penalty.
8-12
Concurrent Local and Remote Applications
Concurrent Local and Remote Applications
The Server engine allows both remote client requests as well as
communications from applications running on the same computer
as the server. This section explains what server Configuration
settings are used to enable remote and local access.
Note To perform these steps, you must have full administrator-level
rights on the machine where the database engine is running, or be a
member of the Pervasive_Admin group defined on the machine where
the database engine is running.
³ To enable database connections from both remote
and local applications
1
You must be sitting at the Windows server computer where the
database server runs. Access the Pervasive commands on the
Start menu and click Pervasive PSQL Control Center.
2
In the Pervasive PSQL Explorer window, double-click on
Engines to display a list of the engines registered with Pervasive
PSQL Control Center.
3
Right-click on the icon representing your target engine and
select Properties. Login if prompted. Click Access.
4
In the right-hand window pane, ensure that Accept Remote
Requests is enabled. If you wish to prevent the server from
accepting client connections from other computers, uncheck the
value. Click OK.
5
In the Pervasive PSQL Explorer window, expand Local Client.
6
Right-click on MicroKernel Router and select Properties. Login
if prompted.
7
Click Access. In the window to the right, ensure the following
settings are properly set:

Use Local MicroKernel Engine. Set the value to On.
Use Remote MicroKernel Engine. If you want to be able to
access databases on other computers, enable this setting. If
you plan to access data on this computer only, disable this
setting.
8-13
8-14
8
Click OK.
9
You must restart the server engine for the changes to take effect.
N ET W ARE
FOR
chapter
Server for NetWare
9
Instructions for NetWare Server Installation or Patching
This chapter contains procedures for installing Pervasive PSQL v9
Service Pack 2 on a NetWare server.

“Installing the Pervasive PSQL Server Components” on page 9-9
9-17
9-1
Installing Pervasive PSQL Server for NetWare
Before You Begin
familiar to install Pervasive PSQL v9 Service Pack 2. Before installing
Pervasive PSQL v9 Service Pack 2, begin by reviewing the following
documents:

Platform Notes
for NetWare
This section contains notes that may be helpful in installing
Pervasive PSQL v9 Service Pack 2 on a NetWare server.

Native file access protocols (NFAP) is a feature of NetWare 6.0
(and a beta product for NetWare 5.1). This feature allows
workstations to access and store files on NetWare servers
without requiring a Novell Client or the Microsoft Client Service
for NetWare. NFAP uses the same protocol (referred to as native)
as the client workstation to copy, delete, move, save, and open
files. Windows workstations perform these tasks using the
Common Internet File System (CIFS) protocol.
Note that Pervasive PSQL v9 Service Pack 2 supports NFAP even
though the feature is new with NetWare 6.0. You do not have to
change the default settings for the Pervasive PSQL engines or
clients to take advantage of NFAP. However, the following items
do apply to the use of NFAP:

9-2
The MicroKernel authentication uses Pervasive PSQL
runtime server support (RTSS). The MicroKernel uses the
NDS password; it does not use the simple password feature
of NFAP. (The default setting for RTSS is "Complete,"
meaning that a user must supply a valid user name. A
password is optional.)
Before You Begin
If you customize the network environment with a CIFS.CFG
file, use the -SHARE parameter to point to the root of the
volume. That is, do not use the -SHARE parameter to point
directly to the Pervasive PSQL data files. The MicroKernel
resolves locations specified by the -SHARE parameter only if
the share points to the root of the volume.
Because some versions of NetWare include Btrieve 6.10, Btrieve
system files already exist on the server and possibly on the
clients. Back up these files and then remove them. If you do not
remove them, set them to read/write so that the installation can
overwrite them (the installation routine also backs them up).
Refer to Btrieve 6.10 documentation for a component list.
To install Pervasive PSQL v9 Service Pack 2, you must have rights
to the SYS: volume and to the System directory on the server on
which the product is being installed.
The Pervasive PSQL server component is installed in the System
directory of the SYS: volume, and all other supporting files are
installed, by default, to subdirectories of the PVSW directory in
the root of the SYS: volume (as described in “What Files Are
Installed as Part of Pervasive PSQL v9 Service Pack 2?” on page
9-18.)
NetWare versions below NetWare 4.11 are not supported.
NetWare 4.x only: Ensure that the CPU Hog Timeout setting is a
value greater than or equal to 60 seconds or you may encounter a
server abnormal ending (abend) when installing Pervasive PSQL
v9 Service Pack 2. The default value is 60 seconds. In addition,
Unicode must be installed on the NetWare machine.
NetWare 5.1 only: The command file AUTOEXEC.NCF for
NetWare 5.1 includes an entry that launches another command
file named SQLC.NCF. The command file SQLC.NCF loads a
version of ODBC.NLM that is incompatible with Pervasive
PSQL. On NetWare 5.1, it is necessary to comment out the line
containing SQLC.NCF in your AUTOEXEC.NCF file.
Otherwise, you will encounter errors when using Pervasive
PSQL or performing SQL operations. Btrieve is unaffected by
this issue.
In all versions of NetWare, before starting Pervasive PSQL v9
Service Pack 2 the NetWare Loadable Module appropriate to the
communication protocol being used must be loaded before
starting Pervasive PSQL v9 Service Pack 2. If the SPX

9-3

Installing Over
Existing
Pervasive
Products

Installation
Tips
9-4
communication protocol is being used, then SPXS.NLM must
be loaded on the server before starting Pervasive PSQL v9
Service Pack 2. If the TCP/IP protocol (the default) is being used,
then TCP/IP must be correctly configured on the server before
starting Pervasive PSQL v9 Service Pack 2.
Prior to installing Pervasive PSQL v9 Service Pack 2, any existing
Pervasive PSQL applications must be stopped on the client
machines.
Running the NetWare install from a Windows 2003 machine can
produce Windows security warning messages that reference files
install is trying to copy. If you receive such dialogs starting with
“Some files can harm your computer”, click Open and Install will
complete normally.
The installation of Pervasive PSQL Server for NetWare does not
install the client installation programs. If you need client
components on the Windows machine from which you installed
NetWare, run the separate client installation from the installation
media.
Your previous versions of Pervasive products will be archived
when you install Pervasive PSQL v9 Service Pack 2 so that there
are no component conflicts. You can use Pervasive System
Analyzer later to restore the archived products if necessary. Your
licenses from previous Pervasive products such as Btrieve 6.x,
Scalable SQL 4.x, and Pervasive.SQL 2000 will not be migrated
to Pervasive PSQL v9 Service Pack 2.
If you wish to make use of all the new version features, you must
rebuild your data files so they use the version 9 file format. See
the Advanced Operations Guide section for detailed information
on how to use the Rebuild utilities to convert your data files.
When installing Pervasive PSQL v9 Service Pack 2 for the first time
on a system, Setup will check if all of the needed system files meet the
minimum requirements. In some cases, these files are locked by the
operating system and a reboot is required before Setup can continue.
The following dialog box is displayed if this is the case.
Before You Begin
Figure 9-1 Pervasive PSQL v9 Service Pack 2 Setup Reboot Required
Click Yes to reboot the system. Setup is then automatically restarted.
Note It is strongly recommended that you reboot your system if you
encounter this message. If you do not reboot your system, Setup will
encounter failures during engine and utilities configuration.
If you have any trouble with the following installation, see Chapter
19, “Troubleshooting After Installation.”
NetWare
Security and
Configuration
Issues
This section details security issues relating to installing Pervasive
PSQL v9 Service Pack 2 on the NetWare platform.
Rights Required to Install
To install Pervasive PSQL v9 Service Pack 2 on a NetWare server you
should be an administrator of the server on which you are installing
the database. Just having supervisor rights is not adequate. This will
allow you to configure, monitor, and set up DSNs for the server after
installation. However, you can do an installation if you just have
read/write rights to the root of the server, but you will not be allowed
to configure, monitor, or add DSNs.
In addition to the rights required on the NetWare server, you must
have administrative rights on the Windows machine from which you
are installing the Pervasive PSQL v9 Service Pack 2 NetWare server.
Easiest Method to Authorize Users to Administer
Databases
All other users that are administrators for the NetWare server object
where Pervasive PSQL v9 Service Pack 2 is installed will have rights
9-5
to perform administrative functions on the database too. This means
the user must have Supervisor rights to the NDS Server itself, not just
Supervisor rights to the SYS: volume.
This implementation is the easiest to set up and administer and is
adequate if your users can be administrators for both the NetWare
server and the Pervasive PSQL v9 Service Pack 2 database.
Alternative and More Restrictive Method to Authorize
Users to Administer Databases
After installation, you can optionally add a group named
Pervasive_Admin and add members who have the right to
administer only the database engine without giving them full
administrative rights on the entire server. To add this group and
users to it, you must have the proper Novell NetWare rights enforced
to add objects into the NDS tree on NetWare 4.11 or later.
On NetWare 4.x or later, the Pervasive_Admin group object must be
set up in the same NDS container as the server (or servers) with
Pervasive PSQL v9 Service Pack 2 installed. If all your Pervasive
PSQL v9 Service Pack 2 servers are installed at the same level in your
NDS tree, then only one Pervasive_Admin group is required for all
of them.
Here is an example of correct levels for Pervasive_Admin.
Root]
| - Pervasive
(organization)
| - Group A
(group object)
| - Admin
(user object
| - Manufacturing
(organization unit)
| - PVSV
(server object)
| - EveryOne
(group object)
| - Pervasive_Admin
(group object)
| - Steve
(user object)
| - R_and_D
(organization unit)
| - PVRD0
(user object)
| - Tawanda
(user object)
| - Pervasive_Admin
(group object)
If you have multiple Pervasive PSQL v9 Service Pack 2 servers at
varying levels in your NDS tree, you must set up multiple
Pervasive_Admin groups, one for each NDS context level running a
Pervasive PSQL engine. You do not need to have the same member
list for each Pervasive_Admin group.
9-6
Before You Begin
Note If the Pervasive_Admin group is created at a lower level in the
NDS tree than the Novell server to which it corresponds, members of
the group cannot access the database engine unless they have Novell
administrator rights. The attempted login to the Pervasive PSQL server
from the fails with the message “You have entered an invalid password
or user name.”
If you have additional questions on this topic or would like to review
examples of NDS trees and user rights, please refer to the section
"Additional Information on Pervasive_Admin and NDS" in the
HTML file:
http://www.pervasive.com/support/updates/psqlall.asp#NetWare
TurboFat on NetWare Servers
On NetWare 4.x, 5.x, and 6.x servers, data files can become corrupt
in the NetWare cache or Turbo cache. The actual data file on the disk
is fine, and if you rebuild the data file you will not lose any records.
If you do lose records while rebuilding, that would indicate true
corruption and not the turbo cache problem.
One solution has been to down the server to clear the cache. This can
be used as a test as well by getting a status 2 on a read of a record,
downing the server to clear the cache, and then reading that same
record again. If you can read it successfully, it is a good indication
that the problem is in the turbo cache.
This issue is not unique to Btrieve files; it can be any type of file that
Novell loads into its cache.
There are 2 possible methods to work around this situation.

Method #1: Disable NetWare’s Turbo cache
This can be done by using TURBOD2.EXE from Novell. See
Novell’s document TID 2960009 “TURBODIS.NLM to prevent
database corruption” for more information. Its properties say it
is for troubleshooting purposes and is not officially tested or
supported. Experience has shown that this does not always
eliminate the problem.

Method #2: Serialize all I/O on a ‘per file’ basis in the NetWare
MicroKernel.
9-7
The avoids the problem and has had outstanding results. It
serializes all I/O on a per file basis in the NetWare MicroKernel.
There have been no reports of this causing any problems or
performance issues, so it is recommended to everyone.
To implement this method, follow these steps.
1
Edit the file SYS:ETC\PSRGSTRY.INI
2
In the section titled [MicroKernel] find the Use FileIO Mutex
setting and set it to YES as shown in this example:
Use FileIO Mutex=YES
(Note: capital letter 'I' and capital letter 'O').
3
Ensure that there is not a second entry anywhere else that sets it
to No.
4
Restart the server for this change to take effect.
Cache Allocation Size
Beginning with NetWare 5.1, Novell deliberately sets the default
Pervasive PSQL memory cache size to 1 MB, which is far too small
for most applications. After you install Pervasive PSQL, you should
set the Cache Allocation Size configuration parameter to 20% of the
physical memory on the NetWare server, to avoid poor database
performance. To access this configuration parameter within, doubleclick the icon representing the NetWare server, double-click the
Configuration, double-click Server, then Performance Tuning.
Double-click on Cache Allocation Size and set the value in bytes.
9-8
Installing the Pervasive PSQL Server Components
You cannot install the NetWare server from the local console. You
must install the Pervasive PSQL for NetWare server remotely from a
Windows client machine on which you have administrative rights.
You can run multiple NetWare server installations from the same
Windows client machine. The NetWare install does not copy any files
to the Windows client machine.
target installation directory, the installation log file (install.log) can be
found in the directory specified by the %TEMP% environment
³ To install Pervasive PSQL on a NetWare server:
1
Map a drive letter to the remote server.
a. Double-click My Computer. If the toolbar is not visible,
click View and select Toolbar. Click the Map Network Drive
button.
b. Map a drive letter to the SYS: volume on the remote server
as shown in the Map Network Drive dialog box.
Figure 9-2 Mapping a Drive
2
Launch the installation program from a client workstation.
a. Insert the Pervasive PSQL v9 Service Pack 2 Server for
NetWare CD in the CD-ROM drive of your client machine.
9-9
b. If the installation does not start automatically, click Start
Note See “Installation Tips” on page 9-4 regarding the Pervasive PSQL
v9 Service Pack 2 Setup Reboot Required dialog box.
3
4
5
Click I accept the terms in the license agreement to accept the
terms of the agreement and enable the Next button.
6
Click Next.
7
Type, or paste, a license key into the License field.
9-10
number of users specified in the license key. When the update is
complete, a dialog box informs you that you have increased your
user count license to support that number of simultaneous
users.
evaluation license. You can evaluate the product for a trial period of 30
days. After 30 days, the evaluation license expires.
You may run the License Administrator utility at a later time to install
a user count license key. The License Administrator utility is
8
Click Next.
9
Specify the location for the system files. The default location is
SYS:SYSTEM. If you want to change the default location, click
Change, specify a location, then click OK.
In the following example dialog, the SYS: volume is mapped to
drive letter P.
Figure 9-5 Location for System Components (NetWare Server)
10 Click Next.
11 Specify the location for the Pervasive files.
The default location is SYS:PVSW. If you want to change the
default location, click Change, specify a location, then click OK.
In the following example dialog, the SYS: volume is mapped to
drive letter P.
9-11
Figure 9-6 Location for Pervasive Files (NetWare Server)
12 Click on the Setup Type desired: Complete or Custom (the
default is complete).
Note For either setup type, Complete or Custom, Pervasive System
Analyzer (PSA) is installed locally. That is, on the Windows machine
from which you are installing Pervasive PSQL Server for NetWare. The
local components are installed to osdrive:\Program Files\Common
Files\Pervasive Software Shared, where osdrive is the drive letter where
your operating system is installed.
installation.
The system components for the Pervasive PSQL Server engine
are copied by default to SYS:\SYSTEM. You can specify a
different location for the system components.
The non-system components are copied by default to
SYS:\PVSW. You can select a different location for the nonsystem components.
The Complete server installation installs the following
components to SYS:SYSTEM:

9-12
interface)
The Complete server installation installs the following nonsystem components to SYS:PVSW:

Script files
DEMODATA sample database
NIS files
Sample files
components.
If You Choose
Custom Install
If you choose Custom install, skip now to “Custom Installation
Path” on page 9-15. At the end of that section you will return to
this set of steps to continue the installation.
13 Click Next.
14 Click Install to continue with the installation.
A dialog appears that gives you a status of the installation
process.
Figure 9-8 Installation Status Dialog Box (NetWare Server)

Script operations
File copying
Registering the product
Publishing product features
9-13
A dialog appears at the end of a successful installation.
15 Click Finish.
Caution To avoid poor database performance on NetWare 5.1 and
later, follow the instructions provided under “Cache Allocation Size”
on page 9-8 to increase Novell’s factory setting for the database engine
cache size.
16 Start Pervasive PSQL on your NetWare machine:
a. Perform a DOWN command at the command prompt on
the NetWare server.
b. Perform a SERVER command at the command prompt on
the NetWare server.
You must restart the NetWare server to load the new version of
BTRIEVE.NLM. The NetWare operating system has
dependencies on BTRIEVE.NLM,
Your installation is complete. Thank you for choosing Pervasive
PSQL.
Note If you had any trouble with the installation, see Chapter 19,
9-14
Pervasive PSQL v9 Service Pack 2. This topic continues a discussion
from step 12 on page 9-12.
1
on the Client icon.
Figure 9-9 Example of Installation Choices (NetWare)
2
Decide how you want to install the program features.
Installation Choice
Meaning
available.
installation.
Note You may exclude the utilities except for a minimum set. The
minimum set includes the Password Utility and the following
command-line interface (CLI) utilities: Maintenance, Rebuild, and
License Administrator.
Client machines require the client requesters to access database files
on a Pervasive PSQL Server machine. You install clients from the CD
media. The client installation programs are not part of the program
features included with the server database engine.
9-15
3
Click on the desired installation choice.
If desired, click on a feature to check the amount of storage space
it requires.
If desired, check the amount of storage space available on the
physical drives.
Click on a feature, then click Space. The resulting dialog shows
you by storage volume, the total disk space, the available disk
space, the space required for the feature, and difference between
the available space and space required. Click OK after you finish
checking storage capacity.
4
Click Next.
Return to Steps 5
for Complete
Installation
9-16
The Custom installation rejoins the Complete installation at this
Note This section contains information that you should read
after running the installation program. If you are having
problems with your installation, go to Chapter 19,
“Troubleshooting After Installation” or get help online from our
Knowledge Base Web site at http://support.pervasive.com/kb.
How Do I Use NetWare Directory Services (NDS) with
Pervasive PSQL v9 Service Pack 2?
For information on Pervasive PSQL support of NDS, see the topic
“NetWare Directory Services (NDS) Formats” on page 18-6.
More documentation on how NDS relates to Pervasive PSQL is
available in the Knowledge Base of Pervasive’s Home Page (http://
support.pervasive.com/kb). Search using the keyword “NDS” on the
Support section of the site.
The NetWare installation does not include any documentation aside
from the README on the distribution media. Run a Windows client
installation on the client that you will use to administer the NetWare
server.
On the Windows client, Pervasive PSQL documentation is provided
in JavaHelp format. To read the documentation, access the Pervasive
Documentation commands on the Start menu and click Pervasive
(PDF) files. These PDF files and an installation program for an
Acrobat reader is available on the Pervasive PSQL v9 Service Pack 2
(Server Edition) CD-ROM.
There is also a README file on the distribution media that has the
latest changes and additions to Pervasive PSQL v9 Service Pack 2.
9-17
Please see that document for information on user licenses.
What Files Are Installed as Part of Pervasive PSQL v9
Service Pack 2?
Once installed, the Pervasive PSQL files reside in the following
directory structure. This structure is located on the SYS volume.
\SYSTEM
NLMs and all other system files
\PVSW
\BIN
9-18
\DEMODATA
A sample SQL database.
\SAMPLES
Sample data file SAMPLE.BTR and sample alternate
collating sequence file UPPER.ALT. This database is the
default database for Btrieve security.
chapter
Network Settings for Server
Engine on NetWare
10
How to Configure Network Settings for a NetWare-based Pervasive PSQL Server
This chapter explains the default network settings for your database
server engine and how to customize these setting if your network
requires changes to the default values.
The chapter contains the following sections:

“Determining What Kind of Network You Have” on page 10-2
“Default Settings” on page 10-3
“Setting Up TCP/IP Support” on page 10-5
“Setting Up SPX Support” on page 10-7
“Disabling Certain Protocols” on page 10-8
10-1
Network Settings for Server Engine on NetWare
This section explains how to determine the network protocol that
you should use with the database engine. If you already know what
protocol or protocols are supported on your network, you can skip
this section.
Server Engine
on NetWare
If you have a NetWare network, you must determine whether it is
running SPX, TCP/IP, or both. You can find out whether TCP/IP is
supported by checking to see if TCPIP.NLM is loaded on the server.
Mixed NetWare
and Microsoft
Network
It is possible to run Btrieve applications over SPX on Microsoft
networks, but ODBC applications over SPX require a NetWare server
for name resolution. If you do not have a NetWare server on your
network, you may not use SPX for ODBC applications.
10-2
Default Settings
Default Settings
When using Pervasive PSQL on a NetWare server, you can use either
TCP/IP or IPX/SPX protocols.
When both network protocols are available, however, Pervasive
PSQL clients will first attempt to use TCP/IP.
If you wish to use only IPX/SPX, you can disable TCP/IP using the
Configuration properties as documented in “Disabling Certain
Protocols” on page 10-8.
This section explains what server Configuration settings are related
to networking support, and what the default values mean.
You can change these settings within by double-clicking
Configuration for the given database engine, then double-clicking
Server, then Communication Protocols.
Auto Reconnect Timeout
Default: 180 seconds
If Pervasive Auto Reconnect is enabled, this setting specifies how
long the engine and client attempt to contact each other after a
network interruption has occurred. By default, the client and server
attempt to connect for three minutes before giving up. If the value of
Enable Auto Reconnect is Off, then the Auto Reconnect Timeout
value is ignored.
Enable Auto Reconnect
Default: Off
This setting determines whether the client and server attempt to
reconnect to each other in the event of a network outage. If set to On,
it allows the database connections to recover from intermittent or
temporary network interruptions. If this value of this setting is Off,
then the client returns a status code to the application immediately
upon any failure to connect to the server, and the connection context
is not preserved.
If you have this setting turned On, you can specify how long the
client and database engine should attempt to reconnect by using the
setting Auto Reconnect Timeout.
10-3
Listen IP Address
Default: 0.0.0.0
This setting specifies the IP address of the network interface card that
the MicroKernel should listen on when the server computer has two
network cards installed. This value is ignored if the server computer
has only one network card, or if the value of TCP/IP Multihomed is
On. This value is also ignored if TCP/IP is not in use by the database
engine.
Supported Protocols
Default: SPX, TCP/IP
This setting specifies the vendor protocols that the database engine
should attempt to use. When more than one protocol is specified,
upon start up, the engine attempts to connect on all specified
protocols. The protocol that connects first is then used for the
remainder of the session.
You can often improve initial connection performance by removing
the protocols that are not used on your network. For example, if you
have a Server engine on an all-TCP/IP network, removing NetBIOS
and SPX support may reduce the wait time during initial
connections to the engine.
TCP/IP Multihomed
Default: On
If your server computer has two network interface cards installed,
you can use this setting to specify whether the server engine should
listen on both network connections. If your computer has two
network cards and this setting is turned off, you must use the setting
Listen IP Address to specify which network card the server engine
should use.
10-4
By default, TCP/IP is supported between Pervasive PSQL clients and
remote engines. If you have modified the default settings or need to
verify that TCP/IP support is available, refer to this section.
³ Enabling TCP/IP Support
Follow this procedure to ensure that the database engine can
communicate with clients over TCP/IP networks.
1
Access the Pervasive commands on the Start menu and click
Pervasive PSQL Control Center.
2
In the window, double-click on Engines to display a list of the
engines registered with Pervasive PSQL Control Center.
3
select Properties. Login if prompted. Click on Communication
Protocols.
4
displays. If the list of Supported protocols shows the value TCP/
IP checked, then TCP/IP is already supported.
If the list of Selected protocols does not include TCP/IP, then you
should select the checkbox next to TCP/IP and click OK.
5
You need to restart the engine for the changes to take effect.
6
Remember that you also need to confirm that your client
computers are configured to use TCP/IP, as well. Please refer to
Chapter 18, “Configuring Network Communications for
Clients.”
10-5
³ Enabling Multihomed TCP/IP Support
Follow this procedure when your server machine has two network
cards installed.
1
From the Start menu, access the Pervasive commands on the
2
If the engine you want to configure is not listed, right-click on
Engines and choose New Server.
10-6
3
Protocols. In the window to the right, you can see the current
setting for TCP/IP Multihomed.
4
If you want the server engine to listen for client connections on
both network cards, select the checkbox. If you want the server
engine to listen on only one card, deselect the checkbox. Click
OK. If you only have one network card, this setting is ignored.
5
If your server computer has two network cards, and you set the
value of TCP/IP Multihomed to Off, you must edit the setting
Listen IP Address and specify the TCP/IP address of the card you
want the database engine to listen to. If you do not specify an IP
address, the database engine will not receive communications
from either network card.
6
You do not need to make any changes to client settings.
By default, SPX is supported between Pervasive PSQL clients and
servers. If you have modified the default settings or need to verify
that SPX support is available, refer to this section.
Your network’s SPX Frame Type setting does not have any effect on
Pervasive PSQL.
³ Enabling SPX Support
Follow this procedure to ensure that the server engine can
communicate with clients over SPX networks.
Note Prior to loading Pervasive PSQL, SPXS.NLM must be loaded.
1
2
3
Protocols.
4
displays. If the list of Supported protocols shows the value SPX
checked, then SPX is already supported.
If the list of Selected protocols does not include SPX, then you
should select the checkbox next to SPX and click OK.
5
6
computers are configured to use SPX, as well. Please refer to
Chapter 18, “Configuring Network Communications for
Clients.”
10-7
Disabling Certain Protocols
It may be possible to improve performance on the initial connection
to the database by disabling database communications support for
any protocols that are not available on your network or that you do
not wish to use.
have administrative rights on the computer where the database engine
is installed, or be a member of the Pervasive_Admin group defined on
that computer.
³ To Remove Support for a Specific Network Protocol
Note This procedure does not affect your operating system
configuration in any way. This procedure only prevents the database
communications system from attempting communications on
unavailable or undesired protocols.
10-8
1
2
3
Protocols.
4
displays. Protocols that are selected on this dialog are considered
available for use by the engine.
5
If the list of Selected protocols includes a value that is not
supported on your network or that you do not wish to use,
uncheck the value. Repeat for any other protocols you do not
wish to use. You must leave at least one protocol in the Selected
protocols list.
6
Click OK.
7
Disabling Certain Protocols
8
computers are configured to use the protocol remaining in the
Supported protocols list. Please refer to Chapter 18,
“Configuring Network Communications for Clients.”
10-9
10-10
chapter
Application Configuration
on NetWare
11
Issues for Configuring Applications on the NetWare Platform

“Local Applications on NetWare Servers” on page 11-2
“NSS Volume Support” on page 11-3
11-1
Application Configuration on NetWare
Local Applications on NetWare Servers

11-2
You can run NLM-based local NetWare applications in NetWare
4.2, 5.0 and above, and 6.0.
The NLM environment does not recognize drive letters or
environment variables. Thus, for commands that require a
filename, the name must include the full path name, such as
SYS:\NWSQL\DEMODATA\PATIENTS.DTA. If you do not
specify a volume, the utility assumes SYS: is the volume.
NSS Volume Support
NSS Volume Support
Pervasive PSQL supports NetWare Storage Services (NSS) volumes
on NetWare 5 and up, provided that you load the NSS volumes prior
to starting the database engine. For example, you should issue the
BSTART or MGRSTART command only after loading the NSS
volumes as shown here:
LOAD NSS
MOUNT ALL
SYS:ETC\INITSYS.NCF
MGRSTART or BSTART
Also, please note that database updates performed against data files
on NSS volumes may run more slowly than with earlier versions of
NetWare. As noted in Novell TID 2952147 (http://www.novell.com),
“NSS is optimized for reading files.” Updates “will almost always
perform a little faster on the legacy file system.”
Based on this information, you may wish to store frequentlyupdated data files on regular NetWare volumes rather than NSS
volumes.
11-3
Application Configuration on NetWare
11-4
L INUX
FOR
chapter
Server for Linux
12
Instructions for First-time Installation of Pervasive PSQL v9 Service Pack 2 Server
This chapter contains procedures for installing or uninstalling
Pervasive PSQL v9 Service Pack 2.
If you have an existing version of a Pervasive PSQL Server and need
to upgrade to the current version, see “Upgrading Your Pervasive
PSQL Installation for Linux” on page 15-1.

“Installing Pervasive PSQL Server Using RPM” on page 12-3
“Installing Pervasive PSQL Server Using Tar” on page 12-5
“After Installation” on page 12-7
“Uninstalling the Server Engine” on page 12-12
12-1
Installing Pervasive PSQL Server for Linux
Before You Begin
This section contains information you need to be familiar with to
successfully install Pervasive PSQL Server.
Before installing, review the following documents:

Chapter 2, “Preparing to Install Pervasive PSQL” – This chapter
and platform specific notes.
README file – This file is located on the distribution media and
Samba Package If you are planning to access the Pervasive PSQL transactional
interface across a network from a Windows-based client, we
Installation
recommend that the Samba package be installed on the server. Please
refer to the Samba website, http://www.samba.org, for installation
and configuration instructions.
After installing Pervasive PSQL Server, review “Supported Path
Formats for Samba” on page 16-7 for information regarding Samba’s
path configuration.
Platform Notes
You must have at least kernel 2.4 to install the Server engine.
If you have any trouble with the installation, see Chapter 19,
12-2
The RPM format allows you to install the product if your Linux
distribution contains the Red Hat Package Manager (RPM). Version
4 or greater of RPM is required.
The name of the PCC installation package conforms to a convention
of Pervasive.SQL-x.xx-yyy.yyy.i486.rpm, where x.xx designates a
release number and yyy.yyy designates a build number. Refer to the
distribution media for the actual name of the package.
Note To install this package, you must be logged in as root. If you are
installing from the CD, you must be at the CD root directory.
³ To install Pervasive PSQL Server:
Note This task is for a first-time installation of Pervasive PSQL Server.
If you have a previous version of Pervasive PSQL on your Linux
machine, see “Upgrading Your Pervasive PSQL Installation for Linux”
on page 15-1.
1
Log in as the root user.
2
Assuming the RPM package is in the current directory, enter the
following command.
rpm -ivh Pervasive.SQL-release-build.rpm
Note You must substitute release-build with the information from the
package name to perform the installation. Verify the complete package
name from the distribution media.
If the RPM package is in another directory, preface the package
name with a path.
The package script installs the product and performs other tasks
as noted in “After Installation” on page 12-7.
12-3
Note If you have any trouble with installation, see Chapter 19,
You can verify that the RPM packager installed the Pervasive
PSQL Server by executing the following case-sensitive command
at a terminal window:
rpm -q ‘Pervasive.SQL’
You can verify which Pervasive PSQL products have been
installed by the RPM packager by executing the following casesensitive command at a terminal window:
rpm -qa | grep ‘Pervasive’
12-4
Installing Pervasive PSQL Server Using Tar
Installing Pervasive PSQL Server Using Tar
The tar format allows you to install the product if you have a Linux
distribution that does not support the RPM format or if you prefer
not to use RPM.
of Pervasive.SQL-x.xx-yyy.yyy.i486.tar.gz, where x.xx designates a
³ To install the product using tar:
1
2
Change to the /usr/local directory.
cd /usr/local
3
Copy the tar into /usr/local
cp path_to_tar/Pervasive.SQL-release-build.tar.gz .
For example, if you downloaded the tar into the /home/bholly
directory:
cp /home/bholly/Pervasive.SQL-release-build.tar.gz .
name from the distribution media..
4
Unpack the tar using the following command.
tar -xzf Pervasive.SQL-release-build.tar.gz
5
Change directories to the /usr/local/psql/etc folder where the
installation scripts reside.
cd psql/etc
6
Run the pre-installation script:
12-5
sh preinstall.sh
7
Run the post installation script:
sh postinstall.sh
Your tar installation is complete. Read the next section “After
Installation” on page 12-7 to understand what actions the postinstall
script performs.
12-6
After Installation
After Installation
The post-installation script performs the following tasks:

Creates user psql and group pvsw
Sets user:group ownership to psql:pvsw for the installed files
Stops Pervasive PSQL daemons if they are running
Applies a 10 user, 30 day limited license
Launches the Pervasive PSQL daemon – mkded
Creates a new ODBC DSN (data source name) for the
DEMODATA test database
Creates a new Samba share PSQLDATA if Samba configuration file
is found
Creates startup/shutdown scripts for Pervasive PSQL daemons
After the installation script is finished, you should verify that the
engine daemon (mkded) is running with the Linux ps utility:
Type the following at the command prompt:
ps -e | egrep ‘mkded’
User Count
License
Once you have completed installation, you may need to update your
user count license by using the clilcadm utility. The update can be
done anytime before using Pervasive PSQL from a client.
Information about how to do this can be found in Pervasive PSQL
User's Guide (see “License Administrator” on page 4-1). Detailed
information about clilcadm can also be found in the man pages and
in the documentation for clilcadm located in the “Linux
Supplementary Documentation” section of Pervasive PSQL User's
Guide.
Note You must be a member of group pvsw to run the clilcadm
utility. See “Pervasive PSQL Account Management on Linux” on page
16-4 for more information.
Accessing
README File
Information
The README file, readme.htm, contains late-breaking product
news that could not be included as part of the JavaHelp
documentation.
You can access the README file from two different locations:
12-7

Configuration
The root directory on the distribution media.
In the following directory: /usr/local/psql/bin/plugins/
com.pervasive.help.ui_1.0.0 (provided you install the JavaHelp
documentation).
Generally, the default configuration settings for Pervasive PSQL
Server are sufficient. See “Configuration” on page 16-6 for settings
that you may want or need to set.
Common
If you are have problems with your installation, see Chapter 19,
Questions After “Troubleshooting After Installation” or get help online from our
Knowledge Base website at http://support.pervasive.com/eSupport.
Installation
The only documentation installed with Pervasive PSQL Server is a
set of man pages for the command-line utilities. The Pervasive PSQL
manuals, in JavaHelp format, must be installed separately. See
“Installing PCC and Documentation on Linux” on page 14-1.
Where Do Files Reside After Installing The Server
Engine?
For a given OS platform, installing the Server engine creates the
directories listed in the table below. For certain directories, the table
also lists the primary files. $PVSW_ROOT refers to the root
directory where Pervasive PSQL files are installed. By default it is set
to the following:
Default $PVSW_ROOT
/usr/local/psql
Path from
$PVSW_ROOT
File
Description
./
LICENSE
License information
bcfg
Configuration utility
bdu
Bulk data import utility
./bin
12-8
After Installation
Path from
$PVSW_ROOT
File
Description
bmon
Monitor utility
btadmin
Add Pervasive user and
passwords
butil
Btrieve maintenance utility
clilcadm
License administrator utility
dbmaint
Database maintenance utility
dsnadd
Add DSN utility
event.log
Pervasive PSQL event log
instwrap
isql
ODBC client utility
mkded
Btrieve database server daemon
odbcci.so
ODBC driver shared object
psregsvr
Pervasive Services
pvdbpass
Database password utility
pvddl
Data dictionary language utility.
pvswauth
./bin/plugins
An empty directory that is used for
for PCC and JavaHelp
documentation if you install them.
They are separate installations.
./data/DEMODATA
Sample University database
billing.mkd
Billing table
class.mkd
Class table
course.mkd
Course table
dept.mkd
Department table
enrolls.mkd
Enrolls table
faculty.mkd
Faculty table
12-9
Path from
$PVSW_ROOT
File
Description
field.ddf
Field DDF file
file.ddf
File DDF file
index.ddf
Index DDF file
person.mkd
Person table
room.mkd
Room table
student.mkd
Student table
tuition.mkd
Tuition table
sample.btr
Sample Btrieve file
upper.alt
Alternate collating sequence
.PSRegistry
This directory, and its subordinate
directories, comprise the
Pervasive registry, where
configuration settings are
retained
btpasswd
User passwords file
dbnames.cfg
Master table of database names
odbc.ini
ODBC settings
preinstall.sh
Shell script that runs before
product installation
postinstall.sh
Shell script that runs after product
installation
preuninstall.sh
product removal
postuninstall.sh
removal
psregistry.ini
Registry information for server
./data/samples
./etc
./lib
12-10
Library shared objects
After Installation
Path from
$PVSW_ROOT
File
Description
./log
Log files directory
./man/man1
Directory that includes man
pages for the command-line
utilities
What to Do Next?
To install the Pervasive PSQL Client for Linux, see “Installing
Pervasive PSQL Client for Linux” on page 13-1.
See “Using Pervasive PSQL on Linux” on page 16-1 for information
on using the Pervasive PSQL products after you install them.
If you are having difficulties after installing, see Chapter 19,
For information about user licenses, see Pervasive PSQL User's Guide
- Chapter 4, “License Administrator”.
12-11
Uninstalling the Server Engine
This section describes how to remove the Pervasive PSQL Server
product from your Linux machine.
The uninstall program does not remove the system databases
DEFAULTDB, TEMPDB, and SYSTEMDB, or the sample database
DEMODATA.
³ To uninstall the RPM version:
1
Log in as the root user using the “su” command.
2
Execute the following case-sensitive command:
rpm -e ‘Pervasive.SQL’
The package manager removes all files, links, and configuration
settings made by the initial installation.
³ To uninstall the Tar version:
1
Log in as the root user using the su command.
2
Change directory to the etc folder, which resides at the root level
of your Pervasive PSQL folder.
cd /usr/local/psql/etc
3
Execute the uninstall scripts in the following sequence:
sh preuninstall.sh
sh postuninstall.sh
The product is now removed.
Note Run the scripts in sequence: preuninstall first followed by
postuninstall.
4
The uninstall scripts remain in the /usr/local/psql/etc
directory after the product is removed. You may want to remove
the scripts themselves as follows:
rm preunistall.sh
rm postunistall.sh
12-12
Uninstalling the Server Engine
12-13
12-14
chapter
Client for Linux
13
Instructions for First-time Installation of Pervasive PSQL v9 Service Pack 2 Client for
Linux
This chapter contains steps for installing or uninstalling the
Pervasive PSQL v9 Service Pack 2 Client software for Linux.
If you have an existing version of a Pervasive PSQL Client and need
to upgrade to the current version, see “Upgrading Your Pervasive
PSQL Installation for Linux” on page 15-1.

“Installing the Pervasive PSQL Client Using RPM” on page 13-3
“Installing the Client Using Tar” on page 13-5
“After Installation” on page 13-7
“Uninstalling the Pervasive PSQL Client” on page 13-11
13-1
Installing Pervasive PSQL Client for Linux
Before You Begin
familiar to successfully install the Pervasive PSQL Client for Linux.
Before installing, review the following documents:

Hardware/
Software
Requirements
in the JavaHelp documentation.
This section lists the requirements needed to install the Client.
Hardware
See “Check the Hardware Requirements” on page 2-6.
Software

Kernel version 2.4 or higher.
Glibc 2.2 or higher
Samba 2.2.6 (if you have Windows clients in your environment)
PAM Libraries (if PAM is selected for security)
iODBC or unixODBC if using ODBC/SQL in your applications.
Some Linux distributions come with iODBC pre-installed. The
Pervasive PSQL Client is installed with a version of the
unixODBC driver manager.
See also “Check the Software Requirements” on page 2-9.
Linux Client in
Conjunction
with Server
Engine
The Linux Client can be installed in the following configurations:

On a Linux machine with no Pervasive PSQL products currently
installed.
On a Linux machine with a Pervasive PSQL v9 Service Pack 2
Server engine installed.
Linux Client and Status 3031
If your server engine does not match the requirements listed, your
applications may receive the following status code: “status 3031:
Linux requester cannot connect to this server.” This status code
indicates client/server incompatibility. In some cases, you may
13-2
Before You Begin
receive a permissions error status instead: “94: The application
encountered a permission error.”
13-3
Installing the Pervasive PSQL Client Using RPM
of Pervasive.SQL-Client-x.xx-yyy.yyy.i486.rpm, where x.xx
designates a release number and yyy.yyy designates a build number.
Refer to the distribution media for the actual name of the package.
³ To install Pervasive PSQL Linux Client:
1
2
following command.
rpm -ivh Pervasive.SQL-Client-release-build.rpm
name with a path.
If you are installing to a non-RPM based Linux installation such
as Slackware, you need to add the --nodeps option so that the
package manager does not check for RPM dependencies that are
not present on your system. For example, rpm -ivh --nodeps
Pervasive.SQL-Client-release-build.rpm.
The package script installs the product and performs other tasks as
noted in “After Installation” on page 13-7. See also “Configuring
Network Communications for Clients” on page 18-1.
13-4
Installing the Pervasive PSQL Client Using RPM
Verifying an
RPM
Installation
You can verify that the RPM packager installed the Pervasive PSQL
package by executing the following case-sensitive command at a
terminal window:
rpm -q ‘Pervasive.SQL-Client’
The command should return the specific client version that you just
installed (Pervasive.SQL-Client-release-build).
13-5
Installing the Client Using Tar
not to use RPM.
The name of the documentation installation package conforms to a
convention of Pervasive.SQL-Client-x.xx-yyy.yyy.i486.tar.gz, where
x.xx designates a release number and yyy.yyy designates a build
number. Refer to the distribution media for the actual name of the
package.
³ To install Pervasive PSQL Client:
1
2
cd /usr/local
3
cp path_to_tar/Pervasive.SQL-Client-releasebuild.tar.gz .
For example, if the tar resides in the /home/bholly directory:
cp /home/bholly/Pervasive.SQL-Client-releasebuild.tar.gz .
4
tar -xzf Pervasive.SQL-Client-release-build.tar.gz
The unpacking action creates a directory named “psqlclient.”
5
Create the following directory:
mkdir /usr/local/psql
6
Copy the contents of the psqlclient folder into the psql folder.
cp -R psqlclient/* /usr/local/psql
7
13-6
Change directories to the /usr/local/psql/etc folder where
the Pervasive PSQL installation scripts reside.
Installing the Client Using Tar
cd psql/etc
8
sh clientpreinstall.sh
9
sh clientpostinstall.sh
Your tar installation is complete.
See “After Installation” on page 13-7 to understand what actions the
script performed. See also “Configuring Network Communications
for Clients” on page 18-1.
13-7
After Installation
This section discusses information applicable after you install the
Pervasive PSQL Client.
If using the RPM format of installation, the two installation scripts
are run automatically before and after the package manager copies all
necessary files onto disk (default location is /usr/local/psql).
If using the tar format, you run only the clientpostinstall.sh
script manually during the installation as described in “Installing the
Client Using Tar” on page 13-5.
Whether run automatically or manually, the scripts perform the
following tasks:

Verifies necessary permissions to complete install
Archives certain files if components from a previous engine are
in conflict with the new client installation. Archived files are
placed in /usr/local/psql/PVSWARCH
Configuring the For network communications involving clients, see “Connecting
Clients to a Sample Database” on page 17-1. All configuration
Linux Client
settings for the Linux client are discussed fully in “Linux Client
Configuration Parameters” on page 5-55 in the Advanced Operations
Guide.
Linux Clients and the Monitor Utility
This information applies only to Linux clients that use a static IP
address. Ignore this subsection if you use DHCP and have a DSN to
resolve named addresses.
When you monitor Linux clients using the Pervasive PSQL Monitor
utility, the client IP address that gets transmitted across the network
originates from the “host” file. If the system name and IP have not
been added to the “host” file, network communication uses the local
host's IP address, which is 127.0.0.1 (a loopback address).
If you change the loopback address to the correct IP, or if you add the
system’s name and IP to the “host” file on the Linux client, the client
name correctly displays when in the Monitor utility.
13-8
After Installation
Mounting NetWare Volumes
The Pervasive PSQL Client for Linux only supports mounting using
NFS. You cannot use ncpmount to mount your NetWare volumes.
For example, the following is a valid mount command:
mount -t nfs nfs_volume local_dir options
Common
Installing the
Linux Client
The only documentation installed with Pervasive PSQL Client is a set
of man pages for the command-line utilities. The Pervasive PSQL
manuals, in JavaHelp format, must be installed separately. See
“Installing PCC and Documentation on Linux” on page 14-1.
Where Do Files Reside After Installing The Client?
For a given OS platform, installing Pervasive PSQL v9 Service Pack 2
creates the directories listed in the table below. For certain
directories, the table also lists the primary files. $PVSW_ROOT
refers to the root directory where Pervasive PSQL files are installed.
By default it is set to the following:
Default $PVSW_ROOT
/usr/local/psql
Path from
$PVSW_ROOT
File
Description
bcfg
Configuration utility
bmon
Monitor utility
butil
Btrieve maintenance utility
dsnadd
Add DSN utility
isql
ODBC client utility
./bin
13-9
Path from
$PVSW_ROOT
./bin/plugins
File
Description
psinstall
Pervasive installation utility (for
use by the Pervasive install
scripts - not a general use utility)
psregedit
Pervasive Registry editor utility
psregsvr
Pervasive Services component
registration utility
pvddl
Pervasive DDL utility
pvnetpass
Pervasive Network Password
utility
rbldcli
Rebuild utility
com.pervasive.help.ui
Pervasive JavaHelp user interface
com.pervasive.help.
docs.psql.enus
Pervasive PSQL documentation
and README
odbc.ini
ODBC settings
clientpreinstall.sh
product installation
clientpostinstall.sh
installation
clientpreuninstall.sh
product removal
clientpostuninstall.sh
removal
./etc
./lib
Library shared objects
./log
Log files directory
./man/man1
Man pages directory
What to Do Next?
13-10
After Installation
See “Connecting Clients to a Sample Database” on page 17-1 and
“Configuring Network Communications for Clients” on page 18-1
for additional information about clients.
If you are having difficulties after installing, see Chapter 19,
13-11
Uninstalling the Pervasive PSQL Client
This section describes how to remove the Pervasive PSQL Client
product from your Linux machine.
1
2
rpm -e ‘Pervasive.SQL-Client’
settings made by the initial installation.
1
2
3
Run the uninstall scripts in the following sequence:
sh clientpreuninstall.sh
sh clientpostuninstall.sh
Note Run the scripts in sequence: clientpreuninstall first followed by
clientpostuninstall.
4
the scripts themselves with the following commands:
rm client*.sh
13-12
chapter
Installing PCC and
Documentation on Linux
14
First-time Installation of Pervasive PSQL PCC and Documentation on Linux
This chapter contains steps for installing or uninstalling Pervasive
PSQL Control Center (PCC) and JavaHelp documentation. The
chapter contains the following sections:

“Installing Pervasive PSQL Control Center Using RPM” on page
14-4
“Installing Pervasive PSQL Control Center Using Tar” on page
14-6
“Installing Pervasive PSQL Documentation Using RPM” on
page 14-8
“Installing Pervasive PSQL Documentation Using Tar” on page
14-10
“How to Access the Documentation” on page 14-12
“Common Questions After Installing PCC and Documentation”
on page 14-14
“Uninstalling Pervasive PSQL Control Center” on page 14-15
“Uninstalling Pervasive PSQL Documentation” on page 14-16
14-1
Installing PCC and Documentation on Linux
Before You Begin
successfully install Pervasive PSQL Control Center, JavaHelp
documentation, or both. Review the following documents before
attempting the installation:

Pervasive
PSQL Control
Center
in the JavaHelp documentation.
Pervasive PSQL Control Center (PCC) is an easy-to-use, graphical
tool designed to help you create and manipulate databases and
control your DBMS. See “Using Pervasive PSQL Control Center” on
page 3-1 in Pervasive PSQL User's Guide.
PCC contains its own installation packages and is an optional utility.
(The command-line utilities that are required for Linux are installed
as part of the Server installation or Client installation. See
“Command Line Interface Utilities” on page 8-1 in Pervasive PSQL
User's Guide.)
The PCC installation does not install the Pervasive PSQL JavaHelp
documentation.
Note The PCC installation requires that a Pervasive PSQL Server
engine or a Pervasive PSQL Client already be installed.
Documentation The Pervasive PSQL documentation for Linux is provided in
JavaHelp format. The documentation contains its own installation
packages and is optional. (Man pages are provided for the
command-line utilities. The man pages are installed as part of the
Server or Client installation and not as part of the JavaHelp
installation.)
14-2
Before You Begin
Note The documentation provides help information for PCC. If you
install PCC, no help is available for the utility unless you also install the
documentation.
Required
Conditions for
Installation
The following conditions are required for both the PCC installation
and the documentation installation. Requirements specific to either
product are listed in the installation section for that product.

A Linux kernel version of at least 2.4.
An RPM version of at least 4 (if you install the RPM package).
A compatible Java Runtime Environment (JRE) Standard
Edition. You must manually install the JRE, which is available for
download from http://java.sun.com. Refer to the Pervasive
PSQL README file for the supported versions of the JRE. See
“README File” on page 14-13.
You must be logged in as root. If you are installing from the CD,
you must be at the CD root directory.
JRE Missing or Incorrect Version
The installation scripts for PCC and JavaHelp determine if the JRE is
missing or if you have an incompatible version. The scripts warn you
for either condition but allow you to continue the installation.
If you receive such a warning but continue the installation, then you
must complete the following steps before using PCC and JavaHelp:
1
Install JRE 1.5.0 or greater.
2

pccpostinstall.sh for PCC
docspostinstall.sh for JavaHelp
By default, the post installation scripts are located in the /usr/
local/psql/etc directory.
Note You may also receive either warning if you installed a compatible
version of the JRE but did not add it to the root user default
environment that is loaded at login time. If so, add the JRE to the
default environment for the root user before using PCC or JavaHelp.
14-3
Installing Pervasive PSQL Control Center Using RPM
distribution contains the Red Hat Package Manager (RPM).
of Pervasive.SQL-PCC-x.xx-yyy.yyy.i486.rpm, where x.xx designates
a release number and yyy.yyy designates a build number. Refer to the
The PCC installation requires that a Pervasive PSQL Server engine or
a Pervasive PSQL Client already be installed. See “Installing
Pervasive PSQL Server for Linux” on page 12-1 and “Installing
RPM
Installation
Steps
³ To install PCC using RPM:
1
2
Assuming that the RPM package is in the current directory, enter
the following command.
rpm -ivh Pervasive.SQL-PCC-release-build.rpm
name with a path.
The package script installs the product.
Note Certain requirements must be met before you can run PCC. See
“Starting PCC On Linux” on page 3-4 in Pervasive PSQL User's Guide.
After
Installation
You can verify that the RPM packager installed PCC by issuing the
following case-sensitive command at a terminal window:
rpm -q ‘Pervasive.SQL-PCC’
14-4
Installing Pervasive PSQL Control Center Using RPM
You can verify all Pervasive PSQL products that have been installed
by the RPM packager by executing the following case-sensitive
command at a terminal window:
Accessing
README file
information
Pervasive Software recommends that you review the README file
for additional information pertaining to the product. See “README
File” on page 14-13.
14-5
Installing Pervasive PSQL Control Center Using Tar
not to use RPM.
of Pervasive.SQL-PCC-x.xx-yyy.yyy.i486.tar.gz, where x.xx
The PCC installation requires that a Pervasive PSQL Server engine or
a Pervasive PSQL Client already be installed. See “Installing
Pervasive PSQL Server for Linux” on page 12-1 and “Installing
Tar Installation
Steps
³ To install PCC using tar:
1
2
Change to the /usr/local/ directory.
cd /usr/local
3
Copy the tar to the /usr/local directory.
cp path_to_tar/Pervasive.SQL-PCC-releasebuild.tar.gz .
directory:
cp /home/bholly/Pervasive.SQL-PCC-releasebuild.tar.gz .
4
tar -xzf Pervasive.SQL-PCC-release-build.tar.gz
5
cd psql/etc
14-6
Installing Pervasive PSQL Control Center Using Tar
6
sh pccpreinstall.sh
7
sh pccpostinstall.sh
Your tar installation is complete.
Note Certain requirements must be met before you can run PCC. See
“Starting PCC On Linux” on page 3-4 in Pervasive PSQL User's Guide.
Accessing
README file
information
14-7
Installing Pervasive PSQL Documentation Using RPM
distribution contains the Red Hat Package Manager (RPM).
convention of Pervasive.SQL-DOC-x.xx-yyy.yyy.i486.rpm, where
package.
RPM
Installation
Steps
³ To install documentation using RPM:
Note This procedure is only for a first-time installation. If you have a
previous version of documentation on your machine, see “Upgrading
Your Pervasive PSQL Installation for Linux” on page 15-1.
1
2
following command.
rpm -ivh Pervasive.SQL-DOC-release-build.rpm
name with a path.
The package script installs the product.
To view the documentation, see “How to Access the
Documentation” on page 14-12.
After
Installation
You can verify that the RPM packager installed the documentation
by issuing the following case-sensitive command at a terminal
window:
rpm -q ‘Pervasive.SQL-DOC’
14-8
Installing Pervasive PSQL Documentation Using RPM
You can verify all Pervasive PSQL products that have been installed
by the RPM packager by executing the following case-sensitive
command at a terminal window:
Accessing
README file
information
14-9
Installing Pervasive PSQL Documentation Using Tar
If you are using a Linux distribution that does not support the RPM
format, or you prefer not to use RPM, you can use the tar installation
format.
convention of Pervasive.SQL-DOC-x.xx-yyy.yyy.i486.tar.gz, where
package.
Tar Installation
Steps
³ To install documentation using tar:
1
2
cd /usr/local
3
Copy the tar to the /usr/local directory.
cp path_to_tar/Pervasive.SQL-DOC-releasebuild.tar.gz .
directory:
cp /home/bholly/Pervasive.SQL-DOC-releasebuild.tar.gz .
4
tar -xzf Pervasive.SQL-DOC-release-build.tar.gz
5
cd psql/etc
6
sh docspreinstall.sh
14-10
Installing Pervasive PSQL Documentation Using Tar
7
sh docspostinstall.sh
Your tar installation is complete. To view the documentation, see
“How to Access the Documentation” on page 14-12.
Accessing
README file
information
14-11
After Installation
This section contains information applicable after you install the
products. If you are having problems with your installation, go to
Chapter 19, “Troubleshooting After Installation” or get help online
from our Knowledge Base website at http://support.pervasive.com/
eSupport.
How to Access The Pervasive PSQL documentation for Linux includes the
following:
the
Documentation JavaHelp format of all books

Man pages for the command-line utilities
README file
JavaHelp
The JavaHelp format requires a Java Runtime Environment (JRE)
Standard Edition. You can download the Standard Edition from
java.sun.com.
JavaHelp Configuration
To run the Javahelp documentation, you must have a variable set for
the following:

PVSW_ROOT
JAVA_HOME (or the PATH must contain the location of the
JRE’s bin directory).
PVSW_ROOT
If PVSW_ROOT is not set, set it to /usr/local/psql and export the
variable:
PVSW_ROOT=/usr/local/psql
export PVSW_ROOT
JAVA_HOME
If a JAVA_HOME environment variable is set, Pervasive PSQL
JavaHelp assumes that the Java executable is at <JAVA_HOME>/bin/
java. JAVA_HOME is not set by the JRE install. Other vendors
require a JAVA_HOME variable so it may be set on your system. If it
is, then it takes precedence over any PATH statements.
14-12
After Installation
Export the variable after you modify or create it:
JAVA_HOME=/usr/local/java
export JAVA_HOME
Without a JAVA_HOME, Pervasive JavaHelp assumes that the PATH
environment variable contains the location of your JRE’s bin
directory. For example, the PATH would include something similar
to the following:
PATH=/usr/local/java/bin
Note Some Linux distributions include gcj, a GNU compiler for the
Java programming language. If your Linux distribution includes the gcj
compiler, check your PATH environment variable. Ensure that the path
to the Standard Edition JRE appears before the path to the gcj or that
you have a JAVA_HOME variable set to the Standard Edition.
³ To view documentation:
1
Open a terminal window.
2
Run the shell script pvswdocs.sh:
sh /usr/local/psql/bin/plugins/
com.pervasive.help.ui_1.0.0/pvswdocs.sh
A slight delay occurs the first time that the JavaHelp instantiates.
Man Pages
Man pages are provided for the command-line utilities. To make
these man pages available, add $PVSW_ROOT/man to your MANPATH
environment variable.
Note that the man pages are installed with Pervasive PSQL Server
and with Pervasive PSQL Client. They are not installed as part of the
JavaHelp documentation.
See also “Man Pages” on page 16-2.
README File
documentation.
14-13

The root directory on the distribution media
com.pervasive.help.ui_1.0.0
For your convenience, the “welcome” page of the JavaHelp
documentation contains a link to the README file.
Common
Questions After
Installing PCC
and
Documentation
“Troubleshooting After Installation” or get help online from our
What If I Get Errors Trying To Start PCC?
See “Starting PCC On Linux” on page 3-4 in Pervasive PSQL User's
Guide.
What If No Help Displays from PCC?
The JavaHelp documentation provides the help for PCC. The
JavaHelp must be installed separately from PCC. See “Installing
Pervasive PSQL Documentation Using RPM” on page 14-8 and
“Installing Pervasive PSQL Documentation Using Tar” on page 1410.
See “How to Access the Documentation” on page 14-12.
14-14
Uninstalling Pervasive PSQL Control Center
Uninstalling Pervasive PSQL Control Center
This section describes how to remove Pervasive PSQL Control
Center from your Linux machine.
1
2
rpm -e ‘Pervasive.SQL-PCC’
settings from the initial installation.
1
2
3
Run the uninstall script:
sh pccpostuninstall.sh
4
The uninstall script remains in the /usr/local/psql/etc
the script itself with the following commands:
rm pcc*.sh
14-15
Uninstalling Pervasive PSQL Documentation
This section describes how to remove the JavaHelp documentation
from your Linux machine.
1
2
rpm -e ‘Pervasive.SQL-DOC’
The package manager removes all files installed by the initial
installation.
1
2
3
Run the uninstall script:
sh docspostuninstall.sh
4
The uninstall script remains in the /usr/local/psql/etc
the script itself with the following commands:
rm docs*.sh
14-16
chapter
Upgrading Your Pervasive PSQL
Installation for Linux
15
How to Upgrade an Existing Installation of Pervasive PSQL on Linux
This chapter contains procedures for upgrading an existing
installation of a Pervasive PSQL product on the Linux platform.
If you need to perform a first-time installation of a Pervasive PSQL
product, see “Installing Pervasive PSQL Server for Linux” on page
12-1 and “Installing Pervasive PSQL Client for Linux” on page 13-1.

“Upgrading Pervasive PSQL Server Using RPM” on page 15-3
“Upgrading Pervasive PSQL Server Using Tar” on page 15-6
“Upgrading Pervasive PSQL Client Using RPM” on page 15-9
“Upgrading Pervasive PSQL Client Using Tar” on page 15-11
“After Upgrading” on page 15-14
15-1
Upgrading Your Pervasive PSQL Installation for Linux
Before You Begin
successfully upgrade Pervasive PSQL v9 Service Pack 2.
Before upgrading, review the following documents:

Samba Package If you are planning to access the Pervasive PSQL transactional
interface across a network from a Windows-based client, we
Installation
recommend that the Samba package be installed on the server. Please
refer to the Samba website, http://www.samba.org, for installation
and configuration instructions.
After installing Pervasive PSQL Server, review “Supported Path
Formats for Samba” on page 16-7 for information regarding Samba’s
path configuration.
Platform Notes
You must have at least kernel 2.4 to install the Server engine.
If you have any trouble with the following installation, see Chapter
19, “Troubleshooting After Installation.”
15-2
Upgrading Pervasive PSQL Server Using RPM
of Pervasive.SQL-x.xx-yyy.yyy.i486.rpm, where x.xx designates a
Upgrade
Pervasive
PSQL 9
³ To upgrade Pervasive PSQL Server:
Note These upgrade steps apply only to Pervasive PSQL v9 Service
Pack 2. See “Upgrade Versions Older than Pervasive PSQL 9” below if
you have a product version prior to Pervasive PSQL v9 Service Pack 2.
1
2
Assuming the the new Pervasive PSQL RPM package is in the
current directory, execute the following command.
rpm -Uvh Pervasive.SQL-release-build.rpm
name with a path.
as noted in “Installation Information” on page 15-4.
If you have any trouble with installation, see Chapter 19,
15-3
Upgrade
Versions Older
than Pervasive
PSQL 9
Note These steps retain the configuration settings made for the
previous version even though you uninstall the previous version.
1
2
Uninstall the previous version Pervasive PSQL package.
rpm -e ‘Pervasive.SQL-server’
3
Assuming the new Pervasive PSQL v9 Service Pack 2 RPM
package is in the current directory, execute the following
command.
rpm -ivh Pervasive.SQL-release-build.rpm
name with a path.
If you had any trouble with installation, see Chapter 19,
Installation
Information
For all installations, the package manager copies all necessary files
onto disk (default location is /usr/local/psql) and runs a postinstallation script which performs the following tasks:

15-4
Stops Pervasive PSQL daemons if they are running
Applies a 10 user, 30 day limited license
Launches the Pervasive PSQL daemon – mkded
Creates a new ODBC DSN (data source name) for the
DEMODATA test database

Creates a new Samba share PSQLDATA if Samba configuration
file is found
Creates startup/shutdown scripts for Pervasive PSQL daemons
After the installation script is finished, you should verify that the
engine (mkded) is running with the Linux ps utility. Type the
following at the command line:
You can verify that the RPM packager upgraded the Pervasive PSQL
package by issuing the following at the command prompt:
rpm -q ‘Pervasive.SQL’
User Count
License
Once you have completed installation, you may need to update your
user count license by using the clilcadm utility. The upgrade can be
done anytime before using Pervasive PSQL from a client.
Information about how to do this can be found in Pervasive PSQL
User's Guide (see “License Administrator” on page 4-1). Detailed
information about clilcadm can also be found in the man pages and
in the documentation for clilcadm located in the “Linux
Supplementary Documentation” section of Pervasive PSQL User's
Guide.
Note You must be a member of group pvsw to run the clilcadm
utility. See “Pervasive PSQL Account Management on Linux” on page
16-4 for more information.
Accessing
README file
information
documentation.

The root directory on the distribution media.
com.pervasive.help.ui_1.0.0 (provided you install the JavaHelp
documentation).
15-5
Upgrading Pervasive PSQL Server Using Tar
not to use RPM.
of Pervasive.SQL-x.xx-yyy.yyy.i486.tar.gz, where x.xx designates a
Upgrade
Pervasive
PSQL 9
1
2
cd /usr/local
3
directory:
Note You must substitute the package name for the variable
Pervasive.SQL-release-build.tar.gz to complete the installation. Verify
the package name from the distribution media.
4
15-6
Upgrading Pervasive PSQL Server Using Tar
5
cd psql/etc
6
sh postinstall.sh
Your tar upgrade is complete.
Upgrade
Versions Prior
to Pervasive
PSQL 9
1
2
3
sh preuninstall.sh
sh postuninstall.sh
The previous version product is now removed.
Note Run the scripts in sequence: preuninstall first followed by
postuninstall.
4
directory after the product is removed. Remove the scripts
themselves with the following commands:
cd etc
rm preuninstall.sh
rm postuninstall.sh
5
cd /usr/local
6
15-7
directory:
Note You must substitute the package name for the variable
Pervasive.SQL-release-build.tar.gz to complete the installation. Verify
the package name from the distribution media.
7
8
cd psql/etc
9
sh postinstall.sh
Your tar upgrade is complete.
15-8
Upgrading Pervasive PSQL Client Using RPM
Upgrading Pervasive PSQL Client Using RPM
of Pervasive.SQL-Client-x.xx-yyy.yyy.i486.rpm, where x.xx
Upgrade
Pervasive
PSQL 9
³ To upgrade Pervasive PSQL Client:
1
2
Assuming the the new Pervasive PSQL RPM package is in the
current directory, execute the following command.
rpm -Uvh Pervasive.SQL-Client-release-build.rpm
name with a path.
If you have any trouble with installation, see Chapter 19,
15-9
Upgrade
Versions Prior
to Pervasive
PSQL 9
1
2
Uninstall the previous Pervasive PSQL client package.
rpm -e ‘Pervasive.SQL-client’
Note You cannot use the rpm -Uvh command to upgrade the package
because the package name has changed.
3
Assuming the new Pervasive PSQL v9 Service Pack 2 RPM
package is in the current directory, issue the following
command.
rpm -ivh Pervasive.SQL-Client-release-build.rpm
name with a path.
If you had any trouble with installation, see Chapter 19,
15-10
Upgrading Pervasive PSQL Client Using Tar
not to use RPM.
of Pervasive.SQL-Client-x.xx-yyy.yyy.i486.tar.gz, where x.xx
Upgrade
Pervasive
PSQL 9
1
2
cd /usr/local
3
4
15-11
5
6
cd psql/etc
7
Upgrade
Versions Prior
to Pervasive
PSQL 9
1
2
3
sh clientpreuninstall.sh
sh clientpostuninstall.sh
The previous version product is now removed.
Note Run the scripts in sequence: clientpreuninstall first followed by
clientpostuninstall.
4
directory after the product is removed. Remove the scripts
themselves with the following commands:
cd etc
rm client*.sh
5
cd /usr/local
6
15-12
Copy the current release tar into /usr/local
7
8
9
cd psql/etc
10 Run the post installation script:
Your tar upgrade installation is complete.
15-13
After Upgrading
This section discusses information applicable after you upgrade a
product.
Configuration
Server are sufficient. See “Configuration” on page 16-6 for settings
that you may want or need to set.
If you want to explore all of the configuration settings, see the
following chapters in Advanced Operations Guide:

“Changing Your Configuration” on page 4-1
“Configuration Reference” on page 5-1
Common
If you are have problems with your installation, go to Chapter 19,
Upgrading
The only documentation installed with Pervasive PSQL Server or
Pervasive PSQL Client is a set of man pages for the command-line
utilities. The Pervasive PSQL manuals, in JavaHelp format, must be
installed separately. See “Installing PCC and Documentation on
Linux” on page 14-1.
What Files Were Installed as Part of Pervasive PSQL v9
Service Pack 2?
During the upgrade, your existing Pervasive PSQL files were updated
to the latest versions. See “Where Do Files Reside After Installing The
Server Engine?” on page 12-8 and “Where Do Files Reside After
Installing The Client?” on page 13-9.
What to Do Next?
For information about user licenses, see Pervasive PSQL User's Guide
- Chapter 4, “License Administrator.”
15-14
chapter
Using Pervasive PSQL on
Linux
16
Working With the Installed Products

“Finding What You Need” on page 16-2
“Pervasive PSQL Account Management on Linux” on page 16-4
“Configuration” on page 16-6
“Client Information” on page 16-8
“Setting Up Web-based Data Access” on page 16-13
“Using Perl and ODBC with Pervasive PSQL” on page 16-22
16-1
Using Pervasive PSQL on Linux
Finding What You Need
Accessing the See “How to Access the Documentation” on page 14-12.
JavaHelp
Documentation
Man Pages
The man pages are installed with Pervasive PSQL Server or Client.
The following man pages are available:
bcfg
bdu
bmon
btadmin
butil
clilcadm
dbmaint
dsnadd
isql
mkded
psregedit
psregsvr
pvdbpass
pvddl
pvnetpass
rbldcli
To make these man pages available, add $PVSW_ROOT/man to
your MANPATH environment variable. If you need more detailed
information on a utility or application, see “Linux-Only CLI
Utilities” on page 8-5.
Note Check the man pages for the most current information. Every
effort is made to ensure that the information in this guide matches that
in the man pages. On occasion, last-minute changes may be included
in the man pages after this guide has been published.
Exclusions
16-2
Because the Linux platform is unique, the following area areas in the
Pervasive PSQL documentation do not apply to Linux.
Finding What You Need

The sections, “Understanding the Pervasive Component
Architecture” on page 3-1 of the Advanced Operations Guide
regarding “Overview of Smart Components,” on page 3-9
“Component Identification,” on page 3-11 or “Unique
Component Naming” on page 3-12 do not apply to Pervasive
The section, “Understanding the Pervasive Component
Architecture” on page 3-1 of the Advanced Operations Guide
regarding “Pervasive PSQL Event Logging” on page 3-16 is
different for Pervasive PSQL v9 Service Pack 2 on Linux.
Pervasive PSQL v9 Service Pack 2 uses the standard Linux
logging system. Depending on the configuration of /etc/
syslog.conf, messages are sent to the syslogd daemon, which
does one of the following:

logs it in an appropriate system log
writes it to the system console
forwards it to a list of users
forwards it to syslogd on another host over the network
More information can be found in the man pages for syslogd
and syslog.conf.

The section, “Configuration Reference” on page 5-1 of the
Advanced Operations Guide regarding the settings for “System
Cache (Windows/Linux engines only)” on page 5-34 and
“Accept Remote Request (Windows/Linux engines only)” on
page 5-7 are ignored in Pervasive PSQL v9 Service Pack 2 for
Linux.
The chapter, “Manipulating Btrieve Data Files with
Maintenance” on page 13-1 of the Advanced Operations Guide
works only on the client for Pervasive PSQL v9 Service Pack 2.
16-3
Pervasive PSQL Account Management on Linux
This section discusses information on Linux user accounts with
respect to operation of Pervasive PSQL.
After
Installation
Behavior

The User
Environment
16-4
You must be logged in as user psql to run utilities (except for
PCC). User psql has no password and can only be accessed
through the root account by using the su command.
All Pervasive files have user:group ownership psql:pvsw
You must be logged in as root to run the start and stop scripts
for the Pervasive PSQL engines.
You can run utilities on other user accounts if you add the
necessary environment variables to the user .bash_profile or
system /etc/profile as described in “Using Utilities from
Users Other than psql” on page 16-5.
In addition to the instructions outlined in “Using Utilities from
Users Other than psql,” users other than ROOT must be a
member of the group pvsw to perform functionality with the
following utilities:

Pervasive PSQL Control Center (PCC) to administer the
local server.

License Administrator utility (clilcadm) for functions
other than displaying current licenses.

Named Database Maintenance utility (dbmaint) for
functions other than displaying current databases.

Pervasive Services Registry Editor (psregedit) for
functions other than displaying the registry.

Linux command-line configuration (bcfg).
The Java Runtime Environment (JRE) is required to use the
Pervasive PSQL JavaHelp documentation. The Pervasive PSQL
documentation installation detects whether a compatible JRE is
present. If not, you must manually install the JRE before you can
install the JavaHelp documentation.
The single environment variable $PVSW_ROOT is used to determine
the location of installed components. The generic location for
configuration files are $PVSW_ROOT/etc. For executable files, the
Pervasive PSQL Account Management on Linux
location is $PVSW_ROOT/bin, and for shared libraries the location is
$PVSW_ROOT/lib.
It is recommended that you add $PVSW_ROOT/bin to your PATH
environment variable, and $PVSW_ROOT/lib to LD_LIBRARY_PATH as
described in the following section.
Using Utilities
To use utilities from user accounts other than psql, you must first
make modifications to the user account configuration. Add the
from Users
Other than psql following to either the profile for a specific user or to the profile that
all users inherit.
/home/username/
.bash_profile.
Profile for the user. Similar to the /etc/
profile file but only for the current user.
Look in /home/username for this file.
/etc/profile
Default profile for all user accounts on
the system. Copy the lines below into
this text file if you want all user accounts
on the machine to have access to
Pervasive PSQL utilities.
This does not give the users
administrative privileges or access to
Pervasive PSQL data.
Here is an example of a modified profile:
PVSW_ROOT=/usr/local/psql
PATH=$PATH:$PVSW_ROOT/bin:/bin:/usr/bin
LD_LIBRARY_PATH=$PVSW_ROOT/lib:$PVSW_ROOT/bin:/usr/lib
MANPATH=$MANPATH:$PVSW_ROOT/man
BREQ=$PVSW_ROOT/lib
LD_BIND_NOW=1
Ensure that you export all variables specific to Pervasive PSQL.
16-5
Configuration
Server and Client are sufficient. You typically do not have to
configure any settings for the database engine and clients to
communication and function together correctly. This subsection
discusses two settings that you may want or need to configure:

“Configuration File”
“Authentication”
If you want to explore all of the configuration settings, see the
following chapters in Advanced Operations Guide:

“Changing Your Configuration” on page 4-1
“Configuration Reference” on page 5-1
Configuration
File
The Server configuration setting “Configuration File” defines the
path to the Samba configuration file (smb.conf), which is parsed on
engine startup to determine mapping between share names and
server directory locations. See “Configuration File (Linux engines
only)” on page 5-12 in Advanced Operations Guide.
Authentication
This option specifies which type of authentication to use for access
to the server engine. The available options are:

Emulate Workgroup Engine. Use this value when Samba is used
to authenticate user access on the system.
Proprietary Authentication (using btpasswd). Use this value
when not using Samba and the user does not have an account on
the server. This allows a separate password file to be maintained
when connecting to the Linux system.
If you are using BTPASSWD or PAM authentication on your
Linux server, user names and passwords must be set up using the
pvnetpass utility from clients connecting to this server. See
“pvnetpass” on page 8-36 in the Pervasive PSQL User's Guide.

16-6
Standard Linux Authentication. Use this value when not using
Samba but users have accounts on the Linux system.
Configuration
Supported Path From a Pervasive PSQL Client on a Windows 32-bit platform, the
order of path parsing is as follows:
Formats for
Samba

\\server\share\relative\path
share denotes a valid Samba share, made accessible to a
Windows client.
server reads smb.conf to determine the absolute path to the
shared directory, then combines it with the relative path to get a
full UNIX path. The location of smb.conf is essential for valid
resolution of the file path supplied in this format on the client. If
the relative path is not correct, status 12 is returned.

Drive:\path
drive must be a Samba drive mapped on the client. It is the
client responsibility to convert it into the latter format and pass
to a server, which never knows a drive mapping on the client.
Note Client users must be advised that share names on a Linux server
are case sensitive. When mapping drives to a Linux server they must
pay careful attention to the case of the share name if they want all their
utilities to work properly.

If neither smb.conf nor the share name are found, the path
defaults to \\server\absolute\path format. If the absolute
path is not correct, status 12 is returned.
16-7
Client Information
A Pervasive PSQL Client can connect to any of the Pervasive PSQL
Servers provided the client and server machines can communicate
with a shared protocol. Because of such commonality, the majority
of information about client communications is consolidated in a
single chapter. See “Connecting Clients to a Sample Database” on
page 17-1. In addition to that chapter, this section includes
information specific to Linux.
Authentication
to Remote
Machines
To connect to a remote machine using the Linux client, you need to
have authentication to the remote machines. This is accomplished by
entering a specific username and password for the server using the
pvnetpass utility. This utility enters the username and password for
that particular server in the Pervasive registry on the client machine.
If you do identify user names and passwords, your applications can
receive status code 3119.
See “pvnetpass” on page 8-36 in Pervasive PSQL User's Guide.
Creating a
Client DSN
A client data source name (DSN) is required if applications on the
client use the Pervasive PSQL relational interface through ODBC. To
create a client DSN, you use the dsnadd utility included with the
Pervasive PSQL Client for Linux. See “dsnadd” on page 8-22 in
Pervasive PSQL User's Guide and the man page for dsnadd located in
/usr/local/psql/man/man1.
Internationaliza This subsection discusses encoding issues and the level of support for
internationalization when using the Pervasive PSQL Client for
tion with the
Linux.
Client
Btrieve
When using the Btrieve API, you must provide file names and paths
in EUC-JP or another encoding used in your application. The client
converts this to UTF8 when passing the request to the server, and
then the server converts the UTF8 encoding to the local encoding.
ODBC
When using ODBC, Win32 encoding is expected to be SHIFT-JIS.
16-8
Client Information
Japanese versions of Linux by default have their encodings typically
set to EUC-JP or UTF8.
When using Japanese versions of Linux, a client can connect to
another Linux server (for example, locally), or to a Win32 SHIFT-JIS
server. It is also possible to connect to a database encoded in SHIFTJIS but located on a Linux server.
Use the following instructions for your listed configuration. In each
case, it is assumed that the application itself does not do any
conversion and uses the encoding that is native for the machine.

“Connecting a Linux EUC-JP Client to a Win32 SHIFT-JIS
Server”
“Connecting a Linux UTF8 Client to a Win32 SHIFT-JIS Server”
“Connecting a Linux EUC-JP Client to a Linux EUC-JP Server”
“Connecting a Linux UTF-8 Client to a Linux UTF-8 Server”
“Connecting a Linux UTF-8 Client to a Linux EUC-JP Server”
“Connecting a Linux EUC-JP Client to a Linux EUC-JP Server,
with SHIFT-JIS Encoding Used to Store Data on the Server”
Connecting a Linux EUC-JP Client to a Win32 SHIFT-JIS Server
The server requires that everything is received as SHIFT-JIS. The
client requires that the server send everything as EUC-JP.
To accomplish this, the client DSN settings in ODBC.INI (located by
default in /usr/local/psql/etc) used to connect to the given
database should be set up as follows:
[dbclient]
Driver=/usr/local/psql/lib/libodbcci.so
Description=Pervasive ODBC Client Interface: JPN2000SERVER:1583/dbclient
ServerDSN=DEMODATA
ServerName=JPN-2000SERVER:1583
TranslationDLL=/usr/local/psql/lib/libxlate.so.9
TranslationOption=90000932
The TranslationDLL line specifies the translation library that the
ODBC client interface should use.
The TranslationOption line specifies that the translation needs to
occur from 9000 (representing EUC-JP) to 0932 (representing
SHIFT-JIS).
16-9
Using this example, all data coming from the client will be translated
into SHIFT-JIS before it gets to the server, and to EUC-JP before the
data is received by the client.
Connecting a Linux UTF8 Client to a Win32 SHIFT-JIS Server
The server requires that everything is received as SHIFT-JIS. The
client requires that the server send everything as UTF8.
To accomplish this, the client DSN settings in ODBC.INI ( by default
in /usr/local/psql/etc ) used to connect to the given database should
be set up as follows:
[dbclient]
ServerDSN=DEMODATA
occur from 9001 (representing UTF8) to 0932 (representing SHIFTJIS).
into SHIFT-JIS before it gets to the server, and to UTF8 before the
data is received by the client.
Connecting a Linux EUC-JP Client to a Linux EUC-JP Server
Using this configuration, no changes to the DSN description are
needed. Use the DSN as it was created by the dsnadd utility.
Connecting a Linux UTF-8 Client to a Linux UTF-8 Server
Using this configuration, no changes to the DSN description are
needed. Use the DSN as it was created by the dsnadd utility.
Connecting a Linux UTF-8 Client to a Linux EUC-JP Server
The server requires that everything is received as EUC-JP. The client
requires that server send everything as UTF-8.
16-10
Client Information
To accomplish this, the client dsn settings in ODBC.INI ( by default
in /usr/local/psql/etc ) used to connect to the given database should
be set up as follows:
[dbclient]
ServerDSN=DEMODATA
occur from 9001 (representing UTF-8) to 9000 (representing EUCJP).
into EUC-JP before it gets to the server, and to UTF-8 before the data
is received by the client.
Connecting a Linux EUC-JP Client to a Linux EUC-JP Server,
with SHIFT-JIS Encoding Used to Store Data on the Server
This situation is possible if you have a SHIFT-JIS database on a
Win32 engine, and you want to move all the files to the Linux EUCJP server. In this case, the database resides on a EUC-JP Linux
machine, but all the data inside the DDF files and data files are in
SHIFT-JIS.
In this case, your DSN should be set up as follows:
[dbclient]
ServerDSN=DEMODATA
CodePageConvert=932
The last line specifies that even though the server uses EUC-JP
encoding, it should treat the data on the server as SHIFT-JIS.
16-11
DTI
The Distributed Tuning Interface (DTI) requires that you use
SHIFT-JIS encoding. The DTI is part of the Pervasive PSQL Software
Development Kit (SDK) and is documented in the SDK manuals.
16-12
Setting Up Web-based Data Access
This section contains information about configuring web servers to
provide access to Pervasive PSQL data and provides connection
snippets and samples for connecting to Pervasive PSQL data from
web applications on Linux.
ODBC Behavior When you first install Pervasive PSQL, the odbc.ini file is written to
/usr/local/psql/etc
If you have other ODBC driver managers such as unixODBC, they
might be using a different odbc.ini file located, for example, at /etc/
odbc.ini.
One way to unify the ODBC setup is to add soft links from where
unixODBC expects the odbc.ini file to be located over to the
Pervasive PSQL directories.
su
cd /etc
ln -s /usr/local/psql/etc/odbc.ini
Configuring
Web Server
This section shows how you should set up the machine where the
web server such as Apache resides.
You should make the user account under which you run any web
server such as Apache a member of the group pvsw. These user
accounts run under restricted accounts such as nobody
To find the user account, see your Apache configuration file,
typically located at /etc/httpd/conf/httpd.conf
In this file, the following lines show what user the Apache server uses
to operate under.
User nobody
Group nobody
Options ExecCgi Indexes
You should add this user to the pvsw group, substituting the name
used in your Apache configuration file.
/usr/bin/gpasswd -a nobody pvsw
PHP
PHP allows for easy development of web applications, using a style
that is similar to both ASP in the Microsoft world and JSP in the Java
16-13
world. Using PHP, you enclose database calls in special tags and
format the output using HTML.
Pervasive PSQL PHP Requirements

PHP - obtain from http://www.php.net
DSN pointing to the database (use dsnadd)
PHP Connection Snippet
This code segment shows the essential part of connecting to a
Pervasive PSQL database using PHP.
// connect to DEMODATA database no uid or password
$connect = odbc_connect("demodata", "", "");
// set the query variable to your SQL
$query = "SELECT * from Department";
// obtain a result object for your query
$result = odbc_exec($connect, $query);
PHP Sample
This complete sample presents the user a choice of three
DEMODATA tables and then displays the table.
<HTML>
<HEAD>
<TITLE>PVSW PHP Sample</TITLE>
</HEAD>
<BODY>
<H1>Pervasive Hello World Samples - PHP using PHP
ODBC APIs)</H1>
<P>
This sample will display the DEMODATA database
tables in the following drop-down
by using PHP.
</p>
<?
// -------MAIN MENU---------------------------// if there is no function specified in the URL
16-14
if (!(isset ($HTTP_GET_VARS["_function"]))):
// -------------------------------------------?>
<p>Please select from the following tables</p>
<form method=post
action='<?=$PHP_SELF?>?_function=showtable'>
<select name="selecttable">
<option SELECTED value="Department">Department
<option value="Course">Course
<option value="Room">Room
</select>
<p>
<input type=submit value="Show table">
</p>
</form>
<?
// ------SHOWTABLE----------------------------Elseif ($HTTP_GET_VARS["_function"] ==
"showtable"):
// -------------------------------------------print("<p>Return to <a href='$PHP_SELF'>Sample 1
Main menu</a></p>");
$thetable = $HTTP_POST_VARS["selecttable"];
// determine from FORMS data which table to open
$connect = odbc_connect("demodata", "", "");
// connect to DEMODATA database no uid or password
$query = "SELECT * from $thetable";
// set the query variable to contain the SQL you
// want to execute
$result = odbc_exec($connect, $query);
// perform the query
// print out the entire resultset as HTML table
// (uncomment following line)
// odbc_result_all($result);
// or format the output yourself and display
// a nicer table (but more code required)
16-15
// initialize row counter
$i = 0;
// determine number of columns
$numcols = odbc_num_fields($result);
// start HTML table
print("<table border=1 cellpadding=5>");
// PRINT COLUMN HEADINGS
print("<tr>"); // start of row
while ($i < $numcols)
{
$i++;
$colname = odbc_field_name($result, $i);
print("<th>$colname</th>");
}
$i=0;
print("</tr>");
// end of row
// PRINT TABLE DATA
// while there are still rows
while(odbc_fetch_row($result))
{
print("<tr>");
// start row
while ($i < $numcols)
{
$i++;
$tablecell = odbc_result($result, $i);
print("<td>$tablecell</td>");
}
print("</tr>");
$i = 0;
}
print("</table>");
// end row
// reset counter
// end odbc_fetch_row
// end HTML table
odbc_close($connect); // CLOSE THE CONNECTION
// END OF SHOWTABLE
16-16
// ---CATCH INVALID MENU OPTIONS----------------Else:
// ---------------------------------------------print("<p>An Invalid function was entered. Please
<a href='$PHP_SELF'>try again</a>.</p>");
Endif;
?>
</BODY>
</HTML>
Additional PHP Sample
A more comprehensive PHP sample application that simulates the
operations of a video store is available online at the location where
you downloaded the Linux client:
http://www.pervasive.com/linuxrc
This sample uses the Pvideo database that is included with the
Pervasive PSQL SDK. If you do not have the SDK installed, you can
download the Pvideo database separately with the sample
application.
Perl
Perl allows for both command line and web-based applications using
Pervasive PSQL.
Pervasive PSQL Perl Requirements

Perl
ODBC-DBD library
CGI library
DSN pointing to the database
Perl Connection Snippet
This code segment shows the essential part of connecting to a
Pervasive PSQL database using Perl.
# specify use of Perl’s database interface (DBI)
16-17
use DBI;
# connect to DEMODATA database no uid or password
$dbInfo = "DBI:ODBC:DEMODATA";
$dbUserName = "";
$dbPassword = "";
# set the query variable to your SQL
$query = "SELECT * FROM Department";
# Connect to the server
$connect = DBI->connect($dbInfo, $dbUserName,
$dbPassword);
# Prepare the SQL query
$myRecordSet = $connect->prepare($query);
# Execute the query and obtain a recordset
$myRecordSet->execute();
Perl Sample
This complete sample presents the user a choice of three
DEMODATA tables and then displays the table.
# Perl sample
use CGI":cgi-lib";
$cgiquery = new CGI;
$functionreq = $cgiquery->url_param('_function');
# use ‘url_param’ for GET and ‘param’ for POST
print &PrintHeader;
print &HtmlTop("Pervasive PSQL Hello World Sample Perl");
print <<ENDOFMENU;
<H1>Pervasive Hello World Samples - Perl</H1>
<P>
This sample will display the DEMODATA database
tables in the following drop-down
by using Perl/DBI.
</p>
ENDOFMENU
# -----MAIN MENU-------------------------------
16-18
# if there is no function specified in the URL
if (!$functionreq) {
# --------------------------------------print <<ENDOFTEXT;
<p>Please select from the following tables</p>
<form method=post
action="$ENV{'SCRIPT_NAME'}?_function=showtable">
<select name="selecttable">
<option SELECTED value="Department">Department
<option value="Course">Course
<option value="Room">Room
</select>
<p>
<input type=submit value="Show table">
</p>
</form>
ENDOFTEXT
} #
!($function)
# ------SHOWTABLE------------------------------elsif ($functionreq eq "showtable") {
print("<p>Return to <a
href='$ENV{'SCRIPT_NAME'}'>Perl Hello World Sample
- Main Menu</a></p>");
# determine from FORMS data which table to open
$thetable = $cgiquery->param('selecttable');
use DBI;
$dbInfo = "DBI:ODBC:DEMODATA";
$dbUserName = "";
$dbPassword = "";
$query = "SELECT * FROM $thetable";
$connect = DBI->connect($dbInfo, $dbUserName,
$dbPassword);
$myRecordSet = $connect->prepare($query);
$myRecordSet->execute();
16-19
# start HTML table
print "<table border=1 cellpadding=5>";
# PRINT COLUMN HEADINGS
$num_fields = $myRecordSet->{NUM_OF_FIELDS};
$count = 0;
print "<tr >";
while ($count < $num_fields) {
$column_name = $myRecordSet->{NAME}->[$count];
print "<th>$column_name</th>";
$count++;
}
print "</tr>\n";
$count = 0;
# PRINT TABLE DATA
while(@row=$myRecordSet->fetchrow_array) {
print "<tr>\n";
while ($count < $num_fields) {
print "<td>$row[$count]</td>\n";
$count++;
}
print "</tr>\n";
$count = 0;
}
print "</table>";
# END OF SHOWTABLE
}
# end HTML table
# -----CATCH INVALID MENU OPTIONS---------------else {
print "<p>An Invalid function was entered. Please
<a href='$ENV{'SCRIPT_NAME'}'>try again</a>.</p>";
}
print &HtmlBot;
16-20
Additional Perl Sample
A more comprehensive Perl sample application that simulates the
operations of a video store is available online at the location where
you downloaded the Linux client:
http://www.pervasive.com/linuxrc
This sample uses the Pvideo database that is included with the
Pervasive PSQL SDK. If you do not have the SDK installed, you can
download the Pvideo database separately with the sample
application.
16-21
Using Perl and ODBC with Pervasive PSQL
Note This procedure assumes you have a working installation of
Pervasive PSQL v9 Service Pack 2, Perl, and an ODBC distribution. A
free version of ODBC is available at http://www.iODBC.org. Perl can
be found at http://www.perl.org
³ To Get Pervasive PSQL to work with Perl's ODBC
Interface:
1
Download the DBI (database interface) support for Perl.
Read the README or INSTALL for instructions.
2
Download the ODBC DBD database driver for Perl.
Please see the installation instructions in the README or
INSTALL file.
3
Code Snippet
for Perl and DBI
Make sure you have the proper environment variables set, as
shown in the following example. Note, this is also explained in
the iODBC docs.
print "using odbc...\n";
use DBI;
$dbName = "DBI:ODBC:DEMODATA";
$dbUserName = "";
$dbPassword = "";
print "connecting...\n";
$sql = "SELECT * FROM class";
$dbh = DBI->connect($dbName, $dbUserName,
$dbPassword);
$dataObject = $dbh->prepare($sql);
$dataObject->execute();
while(@row=$dataObject->fetchrow_array)
{
print "$row[0]\t$row[1]\t$row[2]\n\n"
}
16-22
W ORKING W ITH P ERVASIVE
PSQL C LIENTS
chapter
Connecting Clients to a
Sample Database
17
How to Connect Clients to the Sample Database on a Pervasive PSQL Server Machine
A sample database called DEMODATA is included with every
Pervasive PSQL server installation. This chapter shows how to use a
Pervasive PSQL client to:
R Connect to a machine that is running a Pervasive PSQL engine.
R Use the Pervasive PSQL Control Center to find the DEMODATA
database.
R Access information in DEMODATA tables using Pervasive PSQL
Control Center.

“Basics About Pervasive PSQL Engines and Clients” on page 172
“Connect a Client to a Pervasive PSQL Server” on page 17-3
“Use the Client to Obtain Data from the Server” on page 17-4
“Become an Expert User” on page 17-6
17-1
Connecting Clients to a Sample Database
Basics About Pervasive PSQL Engines and Clients
You should note the following about Pervasive PSQL engines and
clients.
Every Engine is
Also a Client

The client components of Pervasive PSQL 9 are installed with
every engine install. So if you have a Pervasive PSQL engine
installation, you can use your machine to connect to other
remote engines as a client.
Clients

You can use Pervasive PSQL Control Center to connect to
remote machines on which a server engine of Pervasive PSQL is
installed.
You will need to login as an administrative user on the remote
server to perform most functions. This means that you must
have full administrator-level rights on the remote machine or be
a member of the Pervasive_Admin group defined on the remote
machine.

17-2
Connect a Client to a Pervasive PSQL Server
Connect a Client to a Pervasive PSQL Server
This task shows how to connect to a Pervasive PSQL server.
1
Start Pervasive PSQL Control Center (see “Starting PCC” on
page 3-3 in Pervasive PSQL User's Guide).
2
Register an engine in the Pervasive PSQL Control Center.
Right-click on Engines (displayed in your Pervasive PSQL
Control Center in the Pervasive PSQL Explorer) and select New
Server.
The Pervasive PSQL Explorer is the column on the left side of the
window that contains a list of machines to which you are
connected.
Note The machines listed in your Pervasive PSQL Explorer will
remain between sessions. To remove a machine, right-click on the
machine name and select Delete.
Figure 17-1 Registering a New Engine
A dialog is displayed that allows you to choose the machine name
where the Pervasive PSQL v9 Service Pack 2 database engine resides.
Figure 17-2 Choosing a Computer Name
3
You need to be authenticated on the remote engine, and a dialog
displays prompting you for a user name and password. Enter the
values in the appropriate field and click OK.
4
You are now connected to the remote Pervasive PSQL engine.
17-3
Use the Client to Obtain Data from the Server
Once you are connected to the database:
1
Expand the Databases list for your server as shown in Figure 17-3
on page 17-4.
Figure 17-3 Expanding the Databases List for a Machine
2
Find DEMODATA in the list and click on the plus (+) sign.
3
Expand Tables from the list.
4
Click on the table Dept as shown in Figure 17-4 on page 17-4.
Figure 17-4 Selecting the Department Table in DEMODATA
5
17-4
By default, a “SELECT * FROM” query is run and the table
results are displayed in an active grid as shown in Figure 17-5 on
page 17-5
Use the Client to Obtain Data from the Server
The active grid that loads when your data is displayed is
updateable. That is, changes you make to the data in that grid are
stored to the database.
Figure 17-5 Displaying the Department Table in DEMODATA
6
Refine your query
To show how to modify a basic query, restrict the results to only
departments that start with the letter ‘M’ by altering the query at
the top half of the screen and clicking the Execute in Grid
button, which is shown in Figure 17-5.
SELECT * FROM Dept WHERE Name LIKE ‘M%’
You can see the results of the query in Figure 17-6 on page 17-5.
Figure 17-6 Refining Your Query - Department Table in DEMODATA
17-5
Become an Expert User
Now that you can do some basic database access using Pervasive
PSQL Control Center, you may want to continue learning about
other features.
User’s Guide
This manual contains an overview of the Pervasive PSQL Control
Center and instructions for performing basic tasks.
Advanced
Operations
Guide
This manual contains advanced operating and maintenance tasks,
including database operations.
17-6
chapter
Configuring Network
Communications for Clients
18
How to Configure Network Communications for Your Pervasive PSQL Clients
To access network files from a workstation using a Pervasive PSQL
application, you must use the appropriate client requester at that
workstation. Your application’s Pervasive PSQL calls go through the
client, which sends them to the server for processing and then
returns the reply to your application.
communication and function together correctly.
This chapter contains the following sections.

“Default Settings” on page 18-2
“How to Configure the Pervasive Clients” on page 18-4
“Network Path Formats Supported by Pervasive Requesters” on
page 18-5
“Using TCP/IP to Connect to a NetWare Server” on page 18-9
“Using SPX to Connect to a NetWare Server” on page 18-11
“Using TCP/IP to Connect to a Windows 32-bit Server” on page
18-12
“Using SPX to Connect to a Windows 32-bit Server” on page 1815
“NetBIOS and the Pervasive PSQL Server Engine” on page 18-19
“Using TCP/IP to Connect to a Linux Server” on page 18-20
“Using the DOS Requesters” on page 18-23
18-1
Configuring Network Communications for Clients
Default Settings
Pervasive PSQL Clients have several settings that can be configured.
This section informs you of the default values for three settings that
are commonly used with clients. If you want to review all settings,
and their default values, refer to the chapter “Configuration
Reference” in Advanced Operations Guide. Steps for how to configure
settings are in the chapter “Changing Your Configuration,” also in
Enable Auto Reconnect
Default: Off
This setting determines whether the client and server attempt to
reconnect to each other in the event of a network outage. If set to On,
it allows the database connections to recover from intermittent or
temporary network interruptions. If this value of this setting is Off,
then the client returns a status code to the application immediately
upon any failure to connect to the server, and the connection context
is not preserved.
If you have this setting turned On, you can specify how long the
client and database engine should attempt to reconnect by using the
setting Auto Reconnect Timeout in the Server configuration.
Note This setting is not available on 16-bit clients nor does the
Pervasive PSQL Server for Linux support this setting. On Linux, you
can use the Auto Reconnect feature only from a Linux client
connecting to a Windows or NetWare server.
Supported Protocols
Default: varies depending on platform
TCP/IP is the default protocol for Pervasive PSQL. That is, TCP/IP is
tried first if more than one protocol is set to be available.
This setting specifies the vendor protocols that the database engine
should attempt to use. When more than one protocol is specified,
upon start up, the engine attempts to connect on all specified
protocols. The protocol that connects first is then used for the
remainder of the session.
18-2
Default Settings
You can often improve initial connection performance by removing
the protocols that are not used on your network. For example, if you
have a Server engine on an all-TCP/IP network, removing SPX
support may reduce the wait time during initial connections to the
engine.
On Linux platforms, TCP/IP is the only supported protocol on the
server.
Note Server engines do not support the NetBIOS protocol.
Connection Timeout
Default: 15 seconds
This setting specifies the number of seconds the requester should
wait for a TCP/IP connect request to succeed before timing out.
18-3
How to Configure the Pervasive Clients
communication and function together correctly.
If you choose to configure a client, refer to the following sections in
Advanced Operations Guide for applicable topics:

“Configuration Through PCC” on page 4-4
“Configuration Through CLI Utility” on page 4-5
“Win32 Client Configuration Parameters” on page 5-43
“Linux Client Configuration Parameters” on page 5-55
“Win16 Client Configuration Parameters” on page 5-59
Win32
Configuration
Notes
Win32 clients include Window 98/ME and all Windows 32-bit
platforms supported as client platforms.
Win16
Configuration
Notes
Clients using the 16-bit requesters have only transactional access to
the data files. No relational access is be available.
WOW Application Users: The Win16 Requester provides thunking
over to the Win32 Requester, which then handles your request as it
does one from a Win32 application. To use these thunking
capabilities, be sure to use the requesters included with the Pervasive
PSQL package, and not those from an earlier version of Btrieve.
To access a Windows 32-bit server platform, your workstation must
have the Microsoft Network Client for DOS and Windows loaded.
You also need the NetWare SPX protocol stack. Pervasive Software
recommends using the ODI drivers from Novell. You do not need to
run NETX.EXE or be logged in to a NetWare server.
WOW Application Users: You must install both the Win16 Requester
and the Win32 Requester. The Win16 Requester provides thunking
over to the Win32 Requester, which then handles your request as it
does one from a Win32 application. To use these thunking
capabilities, be sure to use the requesters included with this package,
and not those from an earlier version of Btrieve. Also, be sure to
enable the Requester’s Use Thunk option.
18-4
Network Path Formats Supported by Pervasive Requesters
When using your Requester, you connect to the Pervasive server
engine to access data files. This section shows the variations on
network file syntax you can use to access files on your network using
Btrieve or SQL applications.
Pervasive PSQL supports the Universal Naming Convention (UNC)
and Drive path formats (explicit and current) across the majority of
operating environments, including:
Table 18-1 Supported UNC and Drive Path Formats
Application
Types
Environments
Network
Client
Novell Login
Types
Transactional
Windows (32-bit)
Microsoft
Bindery
Relational
Windows (16-bit)
Novell
NDS
DOS
For more information on the path formats, see the sections that
follow:

Universal
Naming
Convention
(UNC) Path
Formats
“Universal Naming Convention (UNC) Path Formats” on page
18-5
“Drive-based Formats” on page 18-6
“NetWare Specific Formats” on page 18-6
“Linux Path Formats” on page 18-8
The following UNC path formats are supported on all clients to all
servers:
\\ServerName\volume\path\file
\\ServerName\volume:[\]path\file
UNC syntax is resolved correctly regardless of the actual type of
network operating system (NOS) that is operating on the target
server.
18-5
Note In all instances above, backslashes (\) can be interchanged with
forward slashes (/) except for the double backslash (\\). The syntax [\]
indicates that the backslash is optional.
Drive-based
Formats
The following drive representations are supported on all clients to all
servers:
Note Do not map drive letters to the \\Tree\VolumeObject format
found in Network Neighborhood. See “NetWare Directory Services
(NDS) Formats” on page 18-6.
drive:file
drive:[\]path\file
file
[\]path\file
..\file
NetWare
Specific
Formats
NetWare path formats on all clients only to NetWare servers:
volume:[\]path\file (ServerName is derived from current
drive)
NetWare Directory Services (NDS) Formats
Pervasive PSQL provides complete integration with Novell Clients,
which has the following benefits to users and network
administrators:

Better integration with NDS authentication capabilities when
accessing the Pervasive PSQL Server Engine for NetWare.
Ability to resolve server names into network address by querying
NDS instead of relying on the NetWare Bindery.
Support for NDS Volume and Directory Map objects in Btrieve
file operations.
Note Pervasive does not support the \\Tree\VolumeObject format
found in Network Neighborhood. See “NetWare Directory Services
(NDS) Formats” on page 18-6.
18-6
Support for Novell Clients for NetWare
Pervasive PSQL was tested with the following Novell clients:

Novell Client for Windows 2000/2003/XP 4.90
Novell Client for Windows 98/ME 3.40
Each of these clients provide the set of NDS specific APIs needed by
the Pervasive PSQL requesters to integrate fully with the NDS
environment. All Pervasive PSQL requesters will detect these clients’
presence automatically; no additional Pervasive PSQL configuration
changes are required. When these clients are available to the
Pervasive PSQL requesters, the following operations are supported:

Network login via NDS (bindery context does not need to be set
on the target server)
NetWare server address resolution for SPX addresses
Drive letters mapped to NDS Volume Objects through either the
Map utility or Network Neighborhood may be used to specify
Btrieve file names or SRDE dictionary and data directories
NDS Volume Objects and Directory Map Objects may be used
to specify Btrieve file names with Win32, and Win16
applications
The file name and path formats supported by the Pervasive PSQL
requesters through the Novell clients are listed in the table below:
Table 18-2 File name and Path formats for Novell Clients for NetWare
Format
Btrieve
Apps
Notes
SQL Apps
<drive letter>:[\]path\file
\\server\volume\path\file
\\server\volume:[\]path\file
server\volume:[\]path\file
volume:[\]path\file
(4)
VolumeObject:[\]path\file
(2) (3)
\\VolumeObject\path\file
(2) (3)
(1)
18-7
Table 18-2 File name and Path formats for Novell Clients for NetWare
Format
Btrieve
Apps
Notes
SQL Apps
DirectoryMap:[\]path\file
(2) (3)
\\DirectoryMap\path\file
(2) (3)
\\Tree\VolumeObject\path\file
\\Tree\DirectoryMap\path\file
1 <drive letter> can be redirected to a server\volume:, or NDS Volume or
Directory Map object.
2 Not supported by the Btrieve DOS requester.
3 See Novell documentation for rules about specifying NDS context when
using NDS objects.
4 Requires that the current drive is mapped to the target NetWare server.
Linux Path
Formats
Incoming paths on a Linux server using Samba will be processed as
follows in order of relative priority:
Share names
\\<server>\<sharename>\<path>
The smb.conf file must be configured to accept <sharename>,
otherwise it will default to the following:
Absolute paths
\\<server>\<absolute_path>
If the smb.conf file is not configured properly or not found on the
target server, the absolute path is used.
18-8
Using TCP/IP to Connect to a NetWare Server
Using TCP/IP to Connect to a NetWare Server
This section documents the use of TCP/IP when connecting to a
Pervasive PSQL server running on a NetWare machine.
Configuring Pervasive PSQL to use TCP/IP
TCP/IP is the default protocol when connecting to NetWare servers,
meaning that if both TCP/IP and SPX protocols are available, TCP/
IP is the first one the Communications Requester attempts to use.
If you have a working TCP/IP setup from your client to your NetWare
server, you should not have to do anything in addition to make
Pervasive PSQL work with TCP/IP and NetWare.
Configuring a Client For the Server IP Address
When Pervasive PSQL operates in a TCP/IP network, your client
must be able to obtain the IP address of your NetWare server from
the name given to that server by your network administrator. There
are two mechanisms that enable this address to name translation:

DNS (Domain naming service)
Editing the Hosts file (a method typically used in small to
medium sized networks)
The following procedures show how to set up the IP address using
each method.
Using DNS to Configure the Server IP Address
When you use DNS, you specify settings that allow your computer to
look up the address of the server in a database of servers. Your
network administrator can provide the information you need to
configure DNS.
³ To configure your clients to use DNS to resolve the
server IP address:
For Windows 98/ME clients:
1
Click Start
Settings
Control Panel.
2
Double-click Network,
3
select Protocols, select TCP/IP and click Properties.
18-9
4
Click the DNS tab.
5
Enable DNS and enter the appropriate server information from
your network administrator.
For clients on Windows 32-bit server platforms:
1
Click Start
Settings
Control Panel.
2
Double-click Network and Dial-up Connections, select Local
Area Connection and click Properties.
3
From the component list, select TCP/IP and click Properties.
4
Using the Hosts File to Configure the Server IP Address
The Hosts file is a way to manually enter a relationship between a
name and an IP address. Use this method if DNS is not used in your
organization.
³ To Edit the Hosts file on your Windows client
1
Find your Hosts file as follows on your Windows machine.
For Windows 32-bit platforms:
\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS
For Windows 98/ME:
\WINDOWS\SYSTEM\DRIVERS\ETC\HOSTS
2
Edit the Hosts file with a text editor such as Notepad.
3
Enter your server’s IP address and name in the hosts file as a new
line as shown in the following example. Your network
administrator can provide you with the IP address of your server.
# the following is an example of a Hosts file entry
146.23.45.2
18-10
acctserver
Using SPX to Connect to a NetWare Server
Using SPX to Connect to a NetWare Server
This section documents the use of SPX when connecting to a
Pervasive PSQL server running on a NetWare machine.
Configuring Pervasive PSQL to use SPX
SPX is a native protocol to NetWare. There should be no special
requirements for operating Pervasive PSQL with SPX on NetWare.
However, note the following:
SPX is not the default protocol for Pervasive PSQL. Consequently, if
you have both TCP/IP and SPX installed, Pervasive PSQL attempts
to use TCP/IP first. If you want SPX to be used, follow these steps:
³ To Configure your Clients to use SPX with NetWare
Servers if Both TCP/IP and SPX are Installed:
1
Click Control Center from the Pervasive program on the Start
menu.
2
In the Pervasive PSQL Explorer, expand Local Client.
3
Right-click on MicroKernel Router and select Properties.
4
Click Communication protocols. In the window to the right, a
list of Supported protocols displays.
5
Uncheck TCP/IP from the list of selected protocols.
6
Click OK.
18-11
Using TCP/IP to Connect to a Windows 32-bit Server
This section documents the use of TCP/IP when connecting to a
Pervasive PSQL server running on a Windows 32-bit server
platform.
Tasks
Configuring a Client for the Server IP Address
must be able to obtain the IP address of your Windows server from
the name given to that server by your network administrator. There
are two mechanisms that enable this address to name translation:

each method.
configure DNS.
server IP address:
1
Click Start
Settings
Control Panel.
2
3
4
Click the DNS tab.
5
For clients on Windows 32-bit platforms:
1
18-12
Click Start
Settings
Control Panel.
Using TCP/IP to Connect to a Windows 32-bit Server
2
3
4
organization.
1
On Windows 32-bit platforms:
On Windows 98/ME:
2
3
146.23.45.2
acctserver
18-13
Preventing the Windows Dial-Up Network Dialog Box from
Displaying When Using a Pervasive Application with TCP/
IP
The Windows Dial-Up Networking dialog box can display when a
TCP/IP request is made to Windows. Usually, this is to make an
Internet connection, but this feature can be an annoyance when
using Pervasive applications and TCP/IP.
³ To Prevent the Dial-Up Networking Dialog Box from
Displaying Automatically:
1
Click Start
Settings
Control Panel.
2
Double-click the Internet Options icon.
3
Click the Connection tab.
4
Clear the option titled Dial whenever a network connection is
not present.
Note While this stops the dialog box from displaying with Pervasive
applications, this also has the side effect that other applications such as
Internet browsers will no longer automatically spawn the Dial-Up
Networking dialog box when a connection to the Internet is needed. In
that case, you need to connect to the Internet manually using Dial-Up
Networking.
According to Microsoft, the Connect to the Internet As Needed check
box is designed to launch Dial-Up Networking whenever TCP/IP is
used by an application, so this behavior is correct.
18-14
Using SPX to Connect to a Windows 32-bit Server
Using SPX to Connect to a Windows 32-bit Server
This section documents the use of SPX when connecting to a
Pervasive PSQL server running on a Windows 32-bit machine.
Tasks
Configuring Pervasive PSQL to use IPX/SPX
IPX/SPX is not a native protocol on the Windows 32-bit platforms.
If you want to use IPX/SPX, perform all of the following procedures
to ensure proper operation with Pervasive PSQL.
Changing Pervasive’s configuration to use IPX/SPX with a
Windows 32-bit platform:
³ If you have both TCP/IP and IPX/SPX Installed in the
Network Icon of the Control Panel, you must remove
TCP/IP from the client configuration to make IPX/SPX
function with Pervasive applications:
1
Click Control Center from the Pervasive program on the Start
menu.
2
In the Pervasive PSQL Explorer, expand Local Client.
3
Right-click on MicroKernel Router and select Properties. Login
if prompted.
4
Click Communication protocols. In the window to the right, a
list of Supported protocols displays.
5
Uncheck TCP/IP from the list of selected protocols.
6
Click OK.
Changing Windows Configuration to Make IPX/SPX Run with
Pervasive PSQL:
Ensure that your IPX/SPX settings are correct
1
Click Start
Settings
Control Panel.
2
Double-click on the Network and Dial-up Connections icon.
3
Right-click Local Area Connection then click Properties.
4
Scroll down to IPX/SPX/NetBIOS Compatible Transport,
highlight and click the Properties button.
18-15
5
In the Frame Type field, ensure that the correct frame type for
your network is selected. Do not use Auto Detect.
6
In the Network number field, enter a non-zero value for your
network address. For information about what your network
address should be, contact your system administrator.
³ Ensure that your IPX/SPX Maximum Packet size
(MaxPktSize) is set correctly in the Windows registry:
1
Click Start then Run.
2
Type regedit and press Enter.
Find the registry entry using the following paths:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Service
s\NwlnkIPX\Parameters\Adapters\name\MaxPktSize.
3
18-16
Ensure that the MaxPktSize setting in the Windows registry is set
to 576 decimal or 240h.
Changing the Default Communication Ports
Changing the Default Communication Ports
Pervasive PSQL communicates through three ports. Your firewall(s)
and routers need to allow access to the following ports for remote
access with the server database engine:

3351 for the transactional interface
1583 for the relational interface
139 for named pipes (see note)
Typically, you do not need to modify the ports unless you have a
conflict with them.
Note The Windows operating system uses port 139 for authentication
to the operating system. An alternative to allowing access to port 139
through a firewall is to enable security on the Pervasive PSQL database.
Once security is enabled, users, such as “Master,” are authenticated to
the database through the database’s own security features. See “To turn
on security using Pervasive PSQL Explorer” on page 3-28 and “To
create a new user using Pervasive PSQL Explorer” on page 3-33, both
in Advanced Operations Guide.
Port assignments 1583 is configurable for the server through the
Pervasive PSQL utilities. See “TCP/IP Port” on page 5-18 in
Advanced Operations Guide. This port is manually configurable for
clients as explained in this section.
Port assignment 3351 is manually configurable for the server and the
clients as explained in this section.
Ensure that the port configurations match on both the server and all
clients. You must stop then start the database engine for the port
assignments to take effect.
Services File
The services file is a text file used by the operating system for network
communications. In the services files, you can manually assign the
18-17
ports used by Pervasive PSQL Server and its clients. The following
table summarizes this.
Platform
Location of Services File
Example Addition To Services File1
Windows 32-bit
\WINDOWS\SYSTEM32\DRIVERS\ETC
To specify that you want to use port 1580
for the relational interface, add the line:
or
\WINNT\SYSTEM32\DRIVERS\ETC
Windows 98/ME
\WINDOWS
NetWare
SYS:\ETC
Linux
/etc
1
psql
1580/tcp
To specify that you want to use port 3355
for the transactional interface, add the
line:
btrieve
3355/tcp
Entries are case-sensitive in the Linux services files and in the Windows services file for 32-bit platforms. Entries in the NetWare services file are not case-sensitive.
Note After changing port assignments in the services file, you must
stop then start the Pervasive PSQL database engine for the changes to
take effect. See “Starting and Stopping the Database Engine” on page
2-2 in Pervasive PSQL User's Guide.
18-18
NetBIOS and the Pervasive PSQL Server Engine
NetBIOS and the Pervasive PSQL Server Engine
Pervasive PSQL Server engine does not support NetBIOS. Only the
Workgroup engine supports NetBIOS.
18-19
Using TCP/IP to Connect to a Linux Server
Your Samba must be properly configured on your Linux server to
properly network with Windows-based clients. See “Configuration”
on page 16-6 for more information.
Tasks
Configuring a Client for the Server’s IP Address
must be able to obtain the IP address of your Linux server from the
name given to that server by your network administrator. There are
two mechanisms that enable this address to name translation:

each method.
configure DNS.
server IP address:
1
Click Start
Settings
Control Panel.
2
3
4
Click the DNS tab.
5
For clients on Windows 32-bit platforms:
1
18-20
Click Start, point to Settings and select Control Panel.
Using TCP/IP to Connect to a Linux Server
2
3
4
organization.
1
For Windows 32-bit platforms:
For Windows 98/ME:
2
3
146.23.45.2
acctserver
Preventing the Windows Dial-Up Network Dialog Box from
Displaying When Using a Pervasive Application with TCP/
IP
The Windows Dial-Up Networking dialog box can display when a
TCP/IP request is made to Windows. Usually, this is to make an
Internet connection, but this feature can be an annoyance when
using Pervasive applications and TCP/IP.
³ To Prevent the Dial-Up Networking Dialog Box from
Displaying Automatically:
1
Click Start
Settings
Control Panel.
2
Double-click the Internet Options icon.
18-21
3
Click the Connection tab.
4
Clear the option titled Dial whenever a network connection is
not present.
Note While this stops the dialog box from displaying with Pervasive
applications, this also has the side effect that other applications such as
Internet browsers will no longer automatically spawn the Dial-Up
Networking dialog box when a connection to the Internet is needed. In
that case, you need to connect to the Internet manually using Dial-Up
Networking.
According to Microsoft, the Connect to the Internet As Needed option
is designed to launch Dial-Up Networking whenever TCP/IP is used by
an application, so this behavior is correct.
18-22
Using the DOS Requesters
This section documents the use of DOS requesters.
Overview
Pervasive PSQL v9 Service Pack 2 supports DOS Btrieve applications
in several different ways. The exact method, however, depends on the
current configuration and environment of the workstation.
Requesters
Available
The following choices are available:

Win32 DOS Box support: Allows a DOS application to run in a
DOS box on a Windows 32-bit platform or on a Windows 98/
ME workstation. This enables direct communication to the
Windows 32-bit workstation components rather than to the
database engine. This configuration can be used with either a
local Pervasive PSQL Workgroup engine, or a remote Pervasive
PSQL server engine. The TCP/IP or SPX protocol supported for
client/server access depends on the configuration of the
Windows 32-bit components.
Note DOS Box support must be used for Workgroup engines. These
engines do not support the DOS requesters described below.

DOS TCP/IP requester (BREQTCP): Allows a DOS application
to run in any Windows DOS box or on a DOS workstation, and
communicate to a remote Pervasive PSQL server engine via the
TCP/IP protocol.
DOS SPX requester (BREQUEST or BREQNT): Allows a DOS
application to run in any Windows DOS box or on a DOS
workstation, and communicate to a remote Pervasive PSQL
server engine via the SPX protocol.
18-23
There are different reasons for using these different options,
including:

Supported
Configurations
The Pervasive PSQL Workgroup engine and server engines
running local applications support only the Win32 DOS Box
configuration.
DOS operating system requires the DOS TCP/IP or SPX
requesters when accessing a remote server engine.
Any given network environment must have only one of the
supported protocols available.
The table below shows the DOS requester configurations that are
supported.
Table 18-3 Supported DOS Requester Configurations
Requester
Workgroup
or Server
Engine on
Windows 98/
ME (Local
application)
Workgroup
or Server
Engine on
Windows 32bit Platforms
(Local
application)
Client on
Windows 98/
ME to
Remote
Server
Engine
Client on
Windows 32bit Platforms
to Remote
Server
Engine
BREQTCP
TCP/IP only
TCP/IP only
BREQNT
SPX only
SPX only
BREQUEST
SPX to
NetWare only
SPX to
NetWare only
DOS Box
The preferred Requester for Windows is BTRBOX. You can use this
Requester even for legacy DOS applications, and for Workgroup
applications.
Note Use the BREQUEST/BREQNT/BREQTCP Requesters ONLY if
you experience a problem with BTRBOX. These Requesters are
supported for access to Server engines only, not to Workgroup
engines.
18-24
Win16 and DOS The Requesters for non-Win32 boxes are:
Workstations

BREQUEST

BREQNT
BREQTCP
The following sections document the steps for running DOS
applications on Windows 32-bit platforms, Windows 98/ME, and
DOS.

Running DOS
applications on
Windows 32-bit
Platforms
“Running DOS applications on Windows 32-bit Platforms”
“Running DOS applications on Windows 98/ME”
“Verifying the DOS Configuration”
“DOS TCP/IP Technical Information”
“Configuring the Pervasive PSQL DOS Requester”
To run a Pervasive application on a Windows 32-bit workstation or
locally on a Windows 32-bit server, you should always install the
Windows client components. The Pervasive PSQL Client
installations are separate programs on the installation media. Refer
to the “Clients” folder on the installation media.
After the Windows client component installation, you will have
everything you need to run a DOS, Windows 16-bit, or Windows 32bit application. The default DOS application support installed is the
Win32 DOS Box configuration.
Using/Disabling Win32 DOS Box Support
On Windows 32-bit platforms, the DOS Box Install configures the
drivers to be completely transparent. Thus, you are able to
immediately open a command prompt and run a DOS Btrieve
application. The CONFIG.NT file, located in the
WINNT\SYSTEM32 directory, contains the command that enables
DOS application support. This file is similar to the old Config.SYS in
DOS. The Windows operating system loads the driver for each DOS
session opened. In the configuration file, the Install places the
following path to load the Win32 DOS Box driver:
DEVICE = C:\PVSW\BIN\BTRDRVR.SYS
To disable the Win32 DOS box support to use the DOS TCP/IP or
SPX requester, you must follow these steps:
18-25
1
Remove the files BTRDRVR.SYS and BTRVDD.SYS from your
system; these are installed by default in the \pvsw\bin directory.
2
Edit the Config.NT file (using Notepad) in the folder
WINNT\SYSTEM32. Delete or invalidate the line:
DEVICE=C:\PVSW\BIN\BTRDRVR.SYS
Note Each configuration (Win32 DOS Box, DOS TCP/IP and DOS
SPX Support) is mutually exclusive. You must disable the existing
configuration before configuring your machine for a new
configuration.
Using DOS TCP/IP Support (BREQTCP)
To use the DOS TCP/IP requester on a Windows 32-bit workstation,
you must first disable the Win32 DOS Box support as described
above, and then enable the DOS TCP/IP requester configuration.
To enable BREQTCP support, follow these steps:
1
Copy the following six files into your %SystemRoot%\SYSTEM
directory. %SystemRoot% refers to your Windows directory,
typically C:\WINNT. You can determine the value for
%SystemRoot% by opening a DOS box and entering the SET
command.
BREQTCP.EXE
BREQTCP.MSG
JSBDOSWS.EXE
JSBDOSWS.DLL
MSOCKLIB.RC
VSLDOS.INI
2
Access the Environment Variables, which are part of System
information (the steps to do this vary by operating system).
(System information is accessed from the Control Panel.)
3
Add the following environment variable:
VSL=%SystemRoot%\SYSTEM
Note There must NOT be a trailing semicolon in this statement.
18-26
Once the DOS TCP/IP requester is setup, follow the following steps
to run a DOS application:
1
Start a DOS session.
2
Run JSBDOSWS.EXE
3
Load BREQTCP.EXE from the \pvsw\bin directory; this needs to
be loaded in each DOS session running a Btrieve application.
4
Run your application.
Note The commands to load JSBDOSWS and BREQTCP can be put in
your AUTOEXEC.NT file. You can load JSBDOSWS with the Load
High command.
To stop a DOS application, unload the requester components by
entering the command BREQTCP /u followed by JSBDOSWS /u in
the DOS box before closing it.
Using DOS SPX Support (BREQUEST/BREQNT)
There are two DOS SPX Btrieve requesters:

BREQNT.EXE is the "dual mode" requester that can be used by
a DOS application to communicate to either a Windows 32-bit
server or a NetWare server.
BREQUEST.EXE is a NetWare-only version of the DOS SPX
requester.
BREQUEST exists for historical purposes before Windows 32-bit
support was available, and is still provided because it requires smaller
memory than BREQNT. If you are accessing Pervasive PSQL on a
NetWare server and if you are running low on DOS conventional
memory, you may need to use BREQUEST. If you are accessing a
Windows 32-bit server, you must use BREQNT.
In order to use the DOS SPX requester on a Windows 32-bit
workstation, you must first disable the Win32 DOS Box support as
described above; there are no special steps required to enable the
DOS SPX requester configuration.
A DOS application can be run with the SPX protocol to a remote
server engine by following these steps:
1
18-27
2
Load BREQNT.EXE or BREQUEST.EXE from the \PVSW\BIN
directory; this needs to be loaded in each DOS session running a
Btrieve application.
3
To stop a DOS application, unload the requester by entering the
command BREQUEST /u or BREQTCP /u in the DOS box before
closing it.
Running DOS
To run a Pervasive application on a Windows 98/ME workstation,
applications on you must always install the Windows client components. The
Windows 98/ME Pervasive PSQL Client installations are separate programs on the
installation media. Refer to the “Clients” folder on the installation
media.
After the Windows client component installation, you will have
everything you need to run a DOS, Windows 16-bit, or Windows 32bit application. The default DOS application support installed is the
Win32 DOS Box configuration.
Using/Disabling Win32 DOS Box Support on Windows 98/
ME
Note Legacy DOS applications must use the BTRBOX configuration
on Windows 98/ME. In fact, it is the only supported configuration with
the Workgroup engine. However, with client/server products, you can
run DOS applications with either the BTRBOX configuration, or the
legacy 16-bit DOS requesters.
If the DOS application is being run on a DOS or Windows 16-bit
operating system, then the legacy 16-bit DOS requesters MUST be
used. BTRBOX works on Win32 operating systems only.
Installation Instructions
To run a DOS application with the Win32 DOS Box configuration
follow these steps:
1
Start BTRBOX95:
a. Access the Pervasive Other Utilities commands on the Start
menu and click BTRBOX95.
18-28
b. Load from the \pvsw\bin directory. A minimized dialog
appears indicating active support. You must leave this
dialog running.
Closure of this dialog will unload BTRBOX95. You will only
need to run BTRBOX once -- you may have multiple DOS
sessions open using a single instance of the driver.
2
3
Load BDOSSTUB.EXE from the \pvsw\bin directory; this needs
to be loaded in each DOS session running a Btrieve application.
4
Note You MUST reboot after the initial installation of the Windows
client components in order for the Win32 DOS Box support to
function. A device driver (VxD) is registered and will not load until
reboot.
The proper order to stop a DOS application is as follows:
1
Stop the DOS application.
2
Close the DOS box.
3
Stop BTRBOX95.
If you do not follow this order, BTRBOX95 or the database engine
may not unload properly.
In situations where stopping and restarting all clients is
recommended, you should perform all three steps above. Simply
stopping and starting your client applications is not sufficient.
To disable the Win32 DOS box support in order to use the DOS TCP/
IP or SPX requester, you must follow these steps:
1
Remove the files BTRBOX95.EXE, BDOSSTUB.EXE, and
BTRBOX95.VXD from your system; these are installed by
default in the \pvsw\bin directory.
2
Using REGEDIT, remove the following key from your registry:
HKEY_LOCAL_MACHINE\System\Current Control Set\
Services\VXD\BtrBox95
18-29
Each configuration (Win32 DOS Box, DOS TCP/IP and DOS
SPX Support) is mutually exclusive. You must disable the
existing configuration before configuring your machine for a
new configuration.
Caution Editing your registry is dangerous and can cause you to
reinstall your entire computer. If you do not feel comfortable doing
this, please obtain the services of a qualified technician. Pervasive can
accept no responsibility for a damaged Registry.
To use the DOS TCP/IP requester on a Windows 98 workstation you
must first disable the Win32 DOS Box support as described above,
and then enable the DOS TCP/IP requester configuration using the
following steps:
1
Ensure you have the following five files in your PVSW\BIN
directory. These files are installed as part of the clients\win
installation. Make sure PVSW\BIN is included in your path.
BREQTCP.EXE
BREQTCP.MSG
JSBDOSWS.VXD
MSOCKLIB.RC
VSLDOS.INI
2
Use a text editor such as Notepad to edit your AUTOEXEC.BAT
file located in your root directory. Make sure the following line
is in the file:
SET VSL=C:\PVSW\BIN
3
Edit your SYSTEM.INI file with a text editor such as Notepad.
SYSTEM.INI is a Windows system file that is located in your
Windows directory (for example, C:\WINDOWS). In the
section [386enh], ensure the following line exists
DEVICE=JSBDOSWS.VXD
4
Restart Windows 98/ME to register your changes.
Once the DOS TCP/IP requester is setup, follow these steps to run a
DOS application:
1
18-30
2
Load BREQTCP.EXE from the \pvsw\bin directory; this needs to
be loaded in each DOS session running a Btrieve application.
3
To stop a DOS application, enter the command BREQTCP /u in the
DOS box to unload the requester.
There are two DOS SPX Btrieve requesters. BREQNT.EXE is the
"dual mode" requester used by a DOS application to communicate to
either a Windows 32-bit server or a NetWare server.
requester. This exists for historical purposes before Windows 32-bit
support was available, and is still provided because it requires smaller
memory than BREQNT. If you are accessing Pervasive PSQL on a
NetWare server and if you are running low on DOS conventional
memory, you may need to use BREQUEST. If you are accessing a
Windows 32-bit server, you must use BREQNT.
To use the DOS SPX requester on a Windows 98 workstation, you
must first disable the Win32 DOS Box support as described above;
there are no special steps required to enable the DOS SPX requester
configuration.
1
2
Load BREQNT.EXE or BREQUEST.EXE from the \pvsw\bin
directory; this needs to be loaded in each DOS session running a
Btrieve application.
3
closing it.
Running DOS Applications
DOS Btrieve application support on DOS workstations is only
available through the DOS TCP/IP or DOS SPX requesters.
18-31
Both allow a DOS application to communicate to a Windows 32-bit
server or NetWare server running the client/server version of
To use the DOS TCP/IP requester on a DOS or Windows
workstation, you must have one of the following TCP/IP stacks:

Microsoft LAN Manager
Novell LAN Workplace
FTP Software 2.2 or greater
You can enable the DOS TCP/IP requester configuration using the
following steps:
1
Copy the following files to the target directory. If you are
running DOS, the target directory is the directory where you
installed the Pervasive PSQL DOS client software. These files can
be found in the “Clients” directory on your Pervasive PSQL
installation media.

2
3
18-32
BREQTCP.EXE
BREQTCP.MSG
M3OPEN.EXE
MNOVLWP.EXE
MFTP22.EXE
MSOCKLIB.RC
VSLDOS.*
Rename your VSLDOS file to VSLDOS.INI in your target
directory.
If Your TCP stack is
Rename this file to VSLDOS.INI
VSLDOS.M3
VSLDOS.LWP
FTP Software
VSLDOS.FTP
Edit AUTOEXEC.BAT file located in the root directory. Add the
following line to the file:
SET VSL=[jsb-location]
where [jsb-location] is the fully-qualified path of the directory
where you placed the VSLDOS.INI file. For example,
C:\PVSW\BIN for DOS.
4
Restart the computer to register the AUTOEXEC.BAT changes.
Once the DOS TCP/IP requester is setup, follow these steps to run a
DOS application:
1
Make sure your TCP/IP components are loaded, as described by
your TCP/IP stack provider.
2
Run the JSB executable appropriate for your TCP stack:

M3OPEN.EXE (Microsoft)
MNOVLWP.EXE (Novell)
MFTP22.EXE (FTP)
3
Load BREQTCP.EXE.
4
VENDOR-SPECIFIC NOTES
MICROSOFT LAN MANAGER
1
Ensure that the NUMSOCKETS parameter in the [SOCKETS]
section of TCPUTILS.INI is set to the maximum concurrent
number of connections required.
2
SOCKETS.EXE is a Terminate and Stay Resident (TSR) program
that allows applications to use the Microsoft LAN Manager TCP/
IP stack. SOCKETS.EXE must be located in the same directory
as the other Microsoft LAN Manager TCP/IP executable.
NOVELL LAN WORKPLACE
Using Novell's LAN Workplace for DOS with BREQTCP.EXE
requires that the environment variable EXCELAN be set to the
Novell base directory. For example, if you installed LAN Workplace
in the C:\NET directory, do a SET EXCELAN=C:\NET prior to
loading MNOVLWP.EXE and BREQTCP.EXE.
FTP SOFTWARE
1
Ensure that you allocate enough TCP and packet buffers for your
application within the FTP kernel.
18-33
e.g. 'kernel-name' -t 16 -p 20
allocates 16 TCP connections and 20 packet buffers.
2
Once the maximum number of connections is reached, it may
prove difficult to effect any connection thereafter until all, or
almost all, connections have been closed. You are therefore
recommended to set the maximum number of connections to a
high number.
To stop a DOS application, unload the requester components by
entering the command BREQTCP /u at the DOS prompt, followed
by [JSB executable] /U, where [JSB executable] is either
M3OPEN.EXE, MNOVLWP.EXE, or MFTP22.EXE. If running in a
Windows DOS box, unload the requester components before closing
the DOS box.
There are two DOS SPX Btrieve requesters. BREQNT.EXE is the
"dual mode" requester that can be used by a DOS application to
communicate to either a Windows 32-bit server or a NetWare server.
requester. This exists for historical purposes before Windows 32-bit
support was available, and is still provided because it has a smaller
memory requirement than BREQNT. If you are accessing Pervasive
PSQL on a NetWare server and if you are running low on DOS
conventional memory, you may need to use BREQUEST. If you are
accessing a Windows 32-bit server, you must use BREQNT.
1
At a DOS prompt, load BREQNT.EXE or BREQUEST.EXE from
the \pvsw\bin directory; this needs to be loaded in each DOS
session running a Btrieve application in a Windows
environment.
2
closing it.
18-34
Verifying the
DOS
Configuration
To verify that the install completed successfully, you need a pure
DOS Btrieve application. One of the simplest application ships with
the server engines. You will find BUTIL.EXE under the “Clients”
directory on the installation media. Running this command by itself
will show a list of available commands. Do this one time to ensure
the copyright information says Butil for DOS. You will then want to
access a Btrieve file. You can use the BUTIL -STAT command to do
this. If the command completes successfully, your DOS support is
functioning as designed.
Try a command like this:
BUTIL -STAT f:\pvsw\samples\sample.btr
Here, "f:" is a drive letter mapped to your server and
"f:\pvsw\samples\sample.btr" is the path and filename of an existing
Btrieve data file. A successful completion will return information
about the data file. Otherwise, you will see a status code indicating
the problem. Pervasive Technical Support can help you resolve any
problems.
DOS TCP/IP
Technical
Information
BREQTCP.EXE is a DOS executable that runs on various DOS and
Windows platforms. It is built using JSB Corporation's Virtual
Socket Library (VSL). VSL implements an API based on the Berkeley
4.3 sockets standard that enables development of platformindependent and transport-independent network applications. For
information about JSB Corporation, visit their site at http://
www.jsb.com.
Components of the Btrieve TCP/IP Requester

DOS TCP/IP Requesters: BREQTCP.EXE, BREQTCP.MSG
VSL DOS components: M3OPEN.EXE, MNOVLWP.EXE,
MFTP22.EXE
VSL Windows 98/ME components: JSBDOSWS.VXD
VSL Windows (other than 98/ME) components:
JSBDOSWS.EXE, JSBDOSWS.DLL
VSL Platform specific configuration files - VSLDOS.INI,
VSLDOS.M3, VSLDOS.LWP, VSLDOS.FTP
VSL Multi-platform resource file: MSOCKLIB.RC
18-35
System Requirements for Btrieve TCP/IP Requester
Server software requirements

TCP/IP configured correctly at server
You must have one of the following client operating systems:

Windows 32-bit operating system with latest service packs
Windows 98/ME
DOS 5.0
DOS 6.0 or greater
For DOS, you must have one of the following TCP/IP stacks:

FTP Software 2.2 or greater
Conventional memory required to load with defaults

Windows 32-bit operating systems

BREQTCP.EXE 81984

JSBDOSWS.EXE 30400 (Upper memory)
Windows 98/ME

BREQTCP.EXE 85792

JSBDOSWS.VXD 0 (No conventional memory used)
DOS 5.0 or greater

BREQTCP.EXE 81456

M3OPEN.EXE 43280 (Microsoft LAN Manager)

MNOVLWP.EXE 66880 (Novell LAN Workplace)

MFTP22.EXE 69424 (FTP Software PC/TCP)
Accessing NetWare Servers
You must have your Pervasive PSQL server IP address configured
properly on your clients for Pervasive PSQL to function. There are
two ways to do this.
To configure your clients to use the server's IP address, do ONE of
the following:
18-36

Use the Control Panel to enable DNS
In Windows 98/ME or NT:
a.
b.
c.
d.
e.
Click Start Settings Control Panel.
Select Network, TCP/IP and click Properties.
Click the DNS tab.
Enable DNS and enter the appropriate server information.
Verify correct configuration using the TCP/IP 'ping' to ping
the server by name.
In Windows 32-bit platforms:
a. Click Start Settings Control Panel.
b. Select Network and Dial-up Connections, and the Local
Area Connection.
c. From the component list, select TCP/IP and then click
Properties.
d. Enable DNS by selecting the corresponding button and
entering the appropriate server information.
e. Verify correct configuration using the TCP/IP 'ping' to ping
the server by name.
or

Enter your Server IP address/name in the hosts file:
\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS file (Windows 32-bit
operating system).
\WINNT\SYSTEM\DRIVERS\ETC\HOSTS file (Windows 98/ME).
Note BREQTCP will return Btrieve status 20 if it is unable to resolve
the server name into an IP address, or if the IP address is incorrect or
unreachable.
Known Issues
This section contains notes on technical issues.
Multiple DOS Boxes
When running BREQTCP on Windows 98/ME, only one DOS box is
supported. Unloading BREQTCP is not sufficient to release the JSB
18-37
VxD. The DOS box must be closed before another DOS box can load
BREQTCP.
On Windows 32-bit operating system, there is no restriction on the
number of DOS boxes that can be invoked.
Use of DOS Requesters on a Windows 32-bit Platform
There are some configuration requirements when you use the DOS
Requester (BREQTCP, BREQNT or BREQUEST).

To run a DOS application using the DOS requester in a Windows
DOS box to access a NetWare server, NW16.EXE must be loaded
prior to loading BREQTCP. Pervasive Software recommends you
load it from AUTOEXEC.NT. If the NWLink IPX/SPX
compatible transport is installed, these files are located in the
WINNT\SYSTEM32 directory.
DOS applications are not supported through the DOS Requester
when running on a Windows server where the data files you are
trying to access reside. You must use the Win32 DOS Box
Support as installed by Pervasive PSQL v9 Service Pack 2 to
access local files.
IP Address caching in Windows 98/ME
After adding a target IP address for a NetWare server in the local
Windows 98/ME hosts file, BREQTCP must be unloaded and
reloaded.
After correcting a target IP address for a NetWare server in the local
Windows 98/ME hosts file, the Windows 98/ME system may need to
be restarted to restart the JSB VxD.
BREQTCP caches both valid and invalid IP addresses while the JSB
VSL VxD caches valid IP addresses. The result is that modifications
to the hosts file will not affect BREQTCP and may not affect the JSB
VSL VxD depending upon prior attempts cached. This can be
confusing when you are trying to modify a target IP address in the
local host’s file or on a DNS server.
Note The Windows 98/ME 'ping' utility does not exhibit this behavior,
so ping may work while BREQTCP requires that Windows 98/ME be
restarted.
18-38
Diagnosing BREQTCP.EXE initialization failures
You may receive the following error message when loading
BREQTCP:
BREQTCP-10: The function InitSocketLibrary returned
an error.
If you see this message, you can determine the cause by using this
checklist:
R Verify that the JSB VSL components appropriate to your
workstation are loaded. Refer to the "Using DOS TCP/IP
Support (BREQTCP)" section for your operating system for
instructions on loading the JSB VSL components.
R Verify that you set the VSL environment variable to the directory
where you placed the VSLDOS.INI file.
R Verify that the VSLDOS.INI you are using is correct. You should
copy the appropriate VSL platform specific configuration file
into your installation directory and renamed it VSLDOS.INI. It
is not necessary to modify the VSLDOS.INI file. Refer to the
"Using DOS TCP/IP Support (BREQTCP)" section for your
operating system to find the correct version of the configuration
file for your platform.
R On Windows 98/ME, ensure another DOS box using BREQTCP
is open. This is the multiple DOS box condition described above.
Configuring the
Pervasive
PSQL DOS
Requester
You manually configure the settings for the Windows 16-bit client
requester in the file BTI.INI. See “To configure settings in BTI.INI”
on page 5-59 in Advanced Operations Guide.
Note that no DOS requestor is available for the Pervasive PSQL
relational interface. All database transactions on DOS must be done
through the Pervasive PSQL transactional interface.
Before configuring the Pervasive PSQL DOS Requester, review this
section for any information necessary to your operation. You should
also read the READDOS.TXT file on the distribution media.
You must load the Pervasive PSQL DOS Requester at a workstation
running DOS before that workstation can access network data files.
18-39
There are three versions of the DOS Requester: BREQUEST,
BREQNT, and BREQTCP.
Communication
Protocol Used
Version
Used On
BREQUEST
Local area networks that use only NetWare
servers. BREQUEST uses less memory than
BREQNT in accessing NetWare servers.
SPX
BREQNT
Local area networks that use Windows 32-bit
platforms (or a combination of NetWare and
Windows 32-bit platforms). BREQNT requires
that the DOS workstations accessing the file
server have the following components loaded:
SPX
To run BREQNT from DOS or Windows,
load the Microsoft Network Client for MSDOS and Windows. You also must use the
NetWare SPX protocol stack. Pervasive
recommends using the ODI drivers from
Novell. You do not need to run NETX.EXE
or be logged on to a NetWare server if you
are using a Windows LAN.
BREQTCP
18-40
Local area networks that use NetWare or
Windows 32-bit servers.
TCP/IP
The DOS Requester loads into a DOS workstation’s memory as a
Terminate and Stay Resident (TSR) program. You can access local as
well as remote files by running a Pervasive PSQL engine on your
machine.
Use of DOS Requesters on a Windows 32-bit Platform
There are some configuration requirements when you use the DOS
Requester.

To run a DOS application using the DOS requester in a Windows
DOS box, NW16.EXE and NWIPXSPX.EXE must be loaded
prior to loading BREQNT or BREQUEST. Pervasive Software
recommends you load them from AUTOEXEC.NT. If the
NWLink IPX/SPX compatible transport is installed, these files
are located in the WINNT\SYSTEM32 directory.
DOS applications cannot run on the Windows 32-bit server
where the data files you are trying to access reside. If attempted,
a nonzero status code results.
Loading the Btrieve DOS Requester
Load the DOS Requester at the workstation by entering one of the
following commands:
[path] BREQUEST [options]
[path] BRREQNT [options]
[path] BREQTCP [options]
path
The path to the directory where the DOS Requester is stored. You can
omit the path name if the DOS Requester is stored on the default drive
or if it is located in a directory in your search path.
option
Any of the configuration options described in “Btrieve DOS Requester
Options” on page 18-42.
For example, if the Requester is on the default drive and you want to
specify a 2,048 byte data message length, enter BREQNT /D:2048.
Note The forward slash (/) before the configuration option is the only
valid character you can use. If you specify a dash (-) or a backslash (\),
the Requester may load improperly.
18-41
Unloading the Btrieve DOS Requester
To unload the DOS Requester, use the /U parameter of the DOS
Requester (BREQUEST, BREQNT, or BREQTCP; see “Unload
Requester (/U)” on page 18-46), or the DOS Requester utility,
BREQUTIL.EXE. At the workstation where the DOS Requester is
loaded, enter BREQUTIL -STOP.
To determine the version of your DOS Requester, you can enter
BREQUTIL -VER.
If files have been left open (for example, when an application does
not issue a Close operation for each open file, or does not issue a
Reset), simply logging out of one or more servers from a workstation
does not close data files or terminate the Btrieve communications
connection to the server. To close data files and terminate the
connection, you must unload the Btrieve requester.
Btrieve DOS Requester Options
There are several configuration options for the Btrieve DOS
Requester.
NetWare Runtime Server Support (/C)
Range: /C:0 | /C:1 | /C:1,username,password
Default: /C:1
Memory Required: Not applicable
Runtime Server Support allows access to the MicroKernel running
on a NetWare Server that the user is not attached to. The workstation
must have a network connection to one or more servers, but not
necessarily the target Btrieve server. Using this option, you can
enable or disable NetWare Runtime server support.
18-42
.
/C:0
Disables NetWare Runtime Server support.
/C:1
Enables NetWare Runtime server support. The MicroKernel looks at the username for the drive
(current server) on which you are presently running.
If the username is SUPERVISOR or ADMIN, the MicroKernel searches for another username
in the table of usernames for the servers to which you have a network connection.
If the username is not SUPERVISOR or ADMIN, the MicroKernel searches for that username
on the NetWare Runtime server. If it is not a valid username, the MicroKernel returns Status
Code 94, Permission Error, at the time of the Open or Create request on the NetWare Runtime
server.
/C:1, username, password
Enables NetWare Runtime server support. The MicroKernel Database Engine verifies the
specified username and password for the NetWare Runtime server. The MicroKernel returns
an error if the specified username is not found or the password is invalid.
username
Preferred login name on the NetWare runtime server. If you specify
SUPERVISOR for the username, the MicroKernel returns status 99 at the time
of the Open or Create.
password
Login password for the specified user.
Data Message Length (/D)
Range: 532 through 57,000 bytes (55,512 bytes is the upper limit for
BREQNT)
Default: 4096 bytes
Memory Required: 355 bytes + data message length
This option specifies the length of the largest record (or the largest
portion or chunk of a record) you want to access through the
MicroKernel. (If you omit this option, the Requester uses the default
value, 4096). The Requester uses this value to calculate the length of
the data message buffer reserved for passing records between the
MicroKernel and your applications. The requester maintains one
copy of the data message buffer.
The value you enter here should not exceed the largest
communication buffer size you configure for the MicroKernel
through the configuration properties since that is the maximum
message that the server communication agent can receive.
18-43
Specify the data message length in bytes. For example, if the largest
record your application uses is 3,000 bytes, specify the /D option as
follows:
/d:3000
Note Specifying a higher value than you need for the /D option does
not improve performance and could waste workstation memory.
DOS Session Load (/L)
Range: Not applicable
Default: Not applicable
To run a DOS-based Btrieve application in a Windows DOS box, you
must have the DOS Requester loaded in each DOS session. However,
if you have already loaded the DOS Requester before loading
Windows, you cannot load the DOS Requester in any subsequent
DOS session. Consequently, you cannot run the DOS-based Btrieve
application in the DOS box.
In each Windows DOS session that will be running a Btrieve-based
application, load the DOS Requester with the /L option. Doing so
loads another instance of the DOS Requester that is available only to
the DOS session. This operation provides the DOS session with its
own copy of the DOS Requester that is available only to the DOS
session, and prevents the DOS session from using the instance of the
DOS Requester that you loaded before starting Windows.
Note Versions of Btrieve for NetWare prior to 6.15 required the DOS
requesters to be loaded before Windows in order to run Win16
applications. This is no longer necessary.
18-44
Receive Packet Size (/M)
Range: 532-4,096
Default: 532 (BREQUEST) or 1514 (BREQNT or BREQTCP)
Memory Required: 3 * Receive Packet Size
This option serves the same function as the Receive Packet Size
setting for the NetWare Btrieve Communications Manager server
setting (described in Pervasive PSQL User's Guide). It has the same
range as the server parameter but has different default that is
optimized for the DOS requester.
Real-Time Data Compression (/O)
Range: None
Default: No compression
Memory Required: Approximately 32 KB on the workstation and 32
KB per client on the server
In many cases (such as when implementing extended reads or huge
records), this option can help reduce network traffic and increase
performance by reducing the number of packets required to
complete a request to the MicroKernel. This option may, however,
adversely affect memory and performance due to the compress and
uncompress work that must be done.
Compressing and decompressing data takes extra CPU time on both
the server and client sides. Because of overhead, do not use this
option with fast networks or with slow workstations for clients.
Note This is not to be confused with Data Compression Flag. For more
information on Data Compression Flag, see Advanced Operations
Guide.
Number of Servers (/S)
Range: 1 through 8, or more if memory permits
Default: 8
Memory Required: 27 bytes per server
The /S option specifies the number of MicroKernel Database Engine
with which the requester can simultaneously communicate.
18-45
Number of Tasks (/T)
Range: 1 through 32,000
Default: 0
Memory Required: 9 bytes per task
The /T option specifies the maximum number of workstation tasks
that can access the server engine at one time using the BTRVID
function. Applications that use the BTRV function are not affected
by this option. For more information about whether you should set
this option, refer to the documentation for your Btrieve application.
Unload Requester (/U)
Range: Not applicable
Default: Not applicable
This option unloads the Btrieve requester from memory. It performs
the same function as a BREQUTIL -STOP command.
Help (/?)
The /? option lists the options that are available.
18-46
A FTER I NSTALLATION
chapter
Troubleshooting After
Installation
19
How to Proceed When You Encounter Errors During Installation
Pervasive Software provides several features and tools in Pervasive
PSQL v9 Service Pack 2 that help to prevent configuration and
installation problems.
Some of these utilities are installed and run as part of the installation
process and all can be run later to evaluate configuration and registry
settings and to troubleshoot problems. They are shown in Table 19-1
on page 19-2.

“Troubleshooting Tools” on page 19-2
“Troubleshooting Strategies” on page 19-3
“Configuration for Special Installation Situations” on page 19-4
“Diagnosing Problems with Pervasive System Analyzer (PSA)”
on page 19-5
“Verifying Database Engine is Running” on page 19-6
“Obtaining File, Client, and Engine Version Number” on page
19-8
“Issues After Uninstalling Pervasive PSQL on Windows” on page
19-11
“Engine and Client Version Conflicts” on page 19-12
“How to Get Additional Help” on page 19-14
19-1
Troubleshooting After Installation
Troubleshooting Tools
The following table describes some tools that can help you avoid or
solve problems.
Table 19-1 Pervasive Tools that Assist in Installation and Problem
Determination
19-2
Feature/
Component
Function
For More
Information
Pervasive System
Analyzer
Analyzes system components, runs
communication tests, and archives
or restores previous database
engine files on your system.
See “Diagnosing
Problems with
Pervasive System
Analyzer (PSA)” on
page 19-5.
Smart
Components
Smart Components is an internal
design in Pervasive PSQL that
ensures that Pervasive software
components always load with
compatible components.
Refer to Advanced
Operations Guide.
Knowledge Base
Provides information about many
Pervasive software configurations
and common environments.
Search the Pervasive
Knowledge base at:
http://
support.pervasive.
com/eSupport
Troubleshooting Strategies
Troubleshooting Strategies
Pervasive Software hopes that your installation process completes
without experiencing any problems. However, this depends on a
number of factors, including proper network support, and operating
system configuration.
If something does go wrong during an installation, Pervasive offers
some tools that can help in diagnosing the problem. This chapter
explores some of the troubleshooting techniques that you can use.
target installation directory, the installation log file (install.log) can be
found in the directory specified by the %TEMP% environment
Checklist for
Problems
Troubleshoot
the Problem
R
R
R
R
R
Did you see any error messages displayed during installation?
Does the Network function correctly?
Is the Engine running?
Is the Client software correctly functioning?
Are there errors in your PVSW.LOG file?
The rest of this section contains procedures that you can use in
verifying your installation.

“Configuration for Special Installation Situations” on page 19-4
“Diagnosing Problems with Pervasive System Analyzer (PSA)”
on page 19-5
“Verifying Database Engine is Running” on page 19-6
“Obtaining File, Client, and Engine Version Number” on page
19-8
“How to Get Additional Help” on page 19-14
19-3
Configuration for Special Installation Situations
This section lists some scenarios where the default configuration
settings for Pervasive PSQL need adjusting for proper database
operation.
The following table summarizes some of these situations. If you find
that your configuration matches an issue, please see the reference
included for more information.
If your computing environment
includes...
Then you need to:
Microsoft Active Directory Service
Read the following section:
“Support for Active Directory Service”
on page 8-2
Multiple network interface cards (NICs)
Enable a configuration setting for Multihomed setting
In Advanced Operations Guide, see:
“TCP/IP Multihomed” on page 5-18
“Listen IP Address” on page 5-17
NetWare 5.x servers
Increase the default Cache Allocation
size. NetWare 5.x includes Pervasive
PSQL and Novell set the default cache
size to 1MB, which is too small for most
applications.
See “Cache Allocation Size” on
page 9-8 for more information.
A network that is subject to outages
Enable a configuration setting that tries
to auto-reconnect to a server when a
network outage occurs
In Advanced Operations Guide, see
“Pervasive Auto-Reconnect” on
page 3-21.
Database files that have embedded
spaces
Enable a configuration setting that
instructs Pervasive PSQL to accept
files with embedded spaces.
In Advanced Operations Guide, see
“Embedded Spaces” on page 5-53
19-4
Pervasive System Analyzer is a diagnostic utility included with
Pervasive System Analyzer (PSA) is conveniently integrated into the
product installation and available as a stand-alone diagnostic tool to
help you with a the following tasks:

Troubleshoot network problems
Detect previous installations of Btrieve or Pervasive PSQL on
your system
Note other factors that influence your networking environment
Perform archives and/or restorations of previously-installed
versions of Pervasive PSQL
Delete components or previous archived versions
View current component set and versions
PSA replaces the features that were previously offered by SmartScout
and InstallScout.
How to Start
PSA
³ To start PSA
1
Access the Pervasive commands on the Start menu and click
Pervasive System Analyzer.
Documentation The use of Pervasive System Analyzer is detailed in Pervasive PSQL
User's Guide. Please see “Pervasive System Analyzer (PSA)” on page
for PSA
7-1 of Pervasive PSQL User's Guide for complete information
regarding Pervasive System Analyzer
SmartScout
Replaced by
PSA
Note SmartScout was replaced by Pervasive System Analyzer starting
in Pervasive.SQL 2000i Service Pack 3. The documentation on
SmartScout has been removed.
19-5
Verifying Database Engine is Running
To verify that the Pervasive PSQL server engine is running, see the
procedure for your platform:

Windows
“Windows” on page 19-6
“Linux” on page 19-7
“NetWare” on page 19-7
You can use the Services function of the Windows control panel.
³ Using the Control Panel to Check Pervasive Services
on Windows Servers:
1
At the operating system, click Start
2
Double-click Administrative Tools, then double-click Services.
3
Scroll the list of services until you reach the following services.

Settings
Control Panel.
Pervasive.SQL (transactional)
Pervasive.SQL (relational)
Both of these services must be started if Pervasive PSQL v9
Service Pack 2 is to function correctly.
The Status column displays whether or not the service is
currently running. The Startup column indicates whether the
service is set to automatically start on system startup or start
manually.
Figure 19-1 Displaying the Services Status
4
19-6
If a service is not started, right-click on it then click Start.
Verifying Database Engine is Running
Linux
You can verify that the engine (mkded) is running with the Linux ps
utility:
Type the following at a command line:
³ To start the Pervasive PSQL services in Linux:
Enter the following at the command line under the root user
account:
etc/rc.d/init.d/psql start
NetWare
You can verify that both engines are running by issuing the same
commands that start the engines. NetWare will notify you that they
are already loaded.
BSTART
MGRSTART
19-7
Obtaining File, Client, and Engine Version Number
You can use Pervasive PSQL utilities to verify that the client and
engines have the version number you expect, or to check the version
of a particular file.
Determining
Client and
Engine Version
You can check the engine and client versions using Function
Executor on Windows platforms or using the BUTIL command-line
utility on all platforms:
Using Function Executor
1
From the Pervasive program on the Start menu, click Function
Executor in the list for Other Utilities.
Function Executor is a utility that simulates Btrieve client
operations using the Pervasive PSQL requesters.
2
Select the Btrieve Version Info button, which appears as a clock
icon. The correct button is shown in Figure 19-2.
Figure 19-2 Selecting the Btrieve Version button
3
19-8
After choosing the Btrieve Version Info button, a dialog displays
that indicates the version of the client requesters and the engine.
Obtaining File, Client, and Engine Version Number
Figure 19-3 Btrieve Version Info Display
Using the BUTIL Utility
From a command prompt, enter the following:
BUTIL -VER
The requester and engine versions are then displayed.
Determining a
File Version
You can determine the file version of a MicroKernel data file using
Function Executor on Windows platforms, or using the BUTIL
command-line utility on any platform:

Using Function Executor to open and then query the version of
a file.
Using BUTIL command-line utility to query the statistics of the
file.
Using Function Executor
The Function Executor utility can simulate Btrieve operations and
can be used to determine the file version by performing the following
operations:
1
Open (0)
2
Version (26)
The Function Executor utility is documented in more detail in
Using BUTIL command-line utility
Use the -stat parameter of BUTIL to query the file statistics, which
includes information about:

File version
Pages
Records
Keys
19-9
Type the following at a command prompt:
butil -stat <filename>
For example, to query the statistics of the file DEPT.MKD of the
DEMODATA database included with Pervasive PSQL:
butil -stat dept.mkd
The BUTIL utility (available on Windows, NetWare, and Linux) is
documented in more detail in Advanced Operations Guide.
19-10
Issues After Uninstalling Pervasive PSQL on Windows
Issues After Uninstalling Pervasive PSQL on Windows
When you uninstall Pervasive PSQL using the Add/Remove
Programs mechanism in Windows, you should not have any
database engine files remaining on your system. However, some
actions such as installing multiple times to the same machine or
restoring archived components can cause a significant number of
files to be left on your system. This is a side effect of how the
installation process works with the Windows operating system and
can be corrected using Pervasive System Analyzer (PSA).
In the situations described previously, the files are left because
Windows has the files marked with usage counts that indicate that
they are being used by more than one program, and therefore the
uninstallation program does not remove them from your system.
This is expected behavior, but it may lead you to conclude that the
Pervasive PSQL uninstall program is not functioning correctly.
In order to correct this condition, run the PSA Delete function and
remove all Pervasive components from your system. PSA deletes the
files and the Windows registry entries that caused the files to remain
on your system. At that point, you should have a system that is free
of Pervasive PSQL components, and the next installation of
Pervasive PSQL will have correct usage counts.
For information on how to use the PSA Delete function, see
“Pervasive System Analyzer (PSA)” in Pervasive PSQL User's Guide.
19-11
Engine and Client Version Conflicts
If you update your engine to the latest Pervasive PSQL version
without also updating your client requesters, you may encounter
warning messages from Pervasive PSQL indicating the version
conflict. The message displayed is:
An engine to client component mismatch was found
When you receive such a message, it is also logged to your Pervasive
Event Log (PVSW.LOG).
This message is a warning. The client is not prevented from
connecting to the engine in this situation. Note, however, that
the database engine.
If circumstances in your organization dictate that you cannot
upgrade the clients for some time, you may want to disable the
dialogs that appear when your client components are activated.
However, you cannot disable the entries in the Pervasive Event Log,
and you should note that over time this log could grow to a large size
as these entries are logged.
To permanently solve the problem, update your client requesters to
the same version as your server engine.
19-12
Engine and Client Version Conflicts
Disabling the
Client
Mismatch
Warning
Messages
³ To disable the client component mismatch error
1
On the client with the older version of Pervasive PSQL, go to the
Registry Editor (from the Start menu, select Run and type
Regedit).
2
Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive
Software\Microkernel Router\Version 7\Settings
directory within the Registry Editor.
3
The MicroKernel Router settings will appear in the right hand
frame of the Registry Editor. Add a new string value Engine
Version Check and give it a value of No.
Caution Use care when editing the Windows registry.
19-13
How to Get Additional Help
Pervasive Software strives to ensure that your product installation is
easy and successful. If you encounter problems during the
installation that are not covered in this manual, please contact
Pervasive Software in one of the following ways and we will address
your problem promptly.
For general questions, common problem resolution, client/server
issues, your first line of support should be the Pervasive Software
Knowledge Base, a web-based searchable index of all Pervasive
technical information: http://support.pervasive.com/eSupport.
For developer-related issues, visit the following web sites:

Pervasive Developer Center
http://www.pervasive.com/developerzone
TechWire and NewsWire are e-mail based newsletters on all
things Pervasive: learn about Beta cycles and releases, Service
Pack releases, current topics, FYIs, Q & As, Pervasive Software
events in your area, trade shows where you can find us, and
much more!
To subscribe to these e-mail newsletters, visit the Subscription
Center at http://www.pervasive.com/support/subscription.asp.
If your installation is not successful, or you encounter problems not
documented in the Pervasive PSQL manuals or on the Knowledge
Base, contact Pervasive Software Customer Support in one of the
following ways:
You may obtain technical support from the following Web-based
support options:

Pervasive Knowledge Base at http://support.pervasive.com/
eSupport

To open a support incident, http://www.pervasive.com/
support/index.asp. Click on Open an Electronic Incident.
To report a product defect, http://www.pervasive.com/support/
index.asp. Click on Report a product defect.
If you require something other than what Web-based support
options provide, contact Pervasive Support by phone:

19-14
800-287-4383 option 3 (the Americas)
How to Get Additional Help

CIC: +00.800.1212.3434 (Belgium, France, Germany, Italy,
Luxembourg, The Netherlands, Spain, Sweden, Switzerland,
and the U.K)
CIC: +32.0.23.37.61 (Any other European, Middle Eastern,
African or Asian countries, excluding Japan)
For technical support and discussions about Pervasive products in
general:

Visit the DevTalk forum at http://www.pervasive.com/devtalk.
Visit http://www.pervasive.com/company/contact/index.asp for
other contact information.
Thirty-Day Free If you still have questions or problems relating to your Pervasive
PSQL v9 Service Pack 2 installation, you can obtain help from the
Technical
Pervasive Customer Support department.
Support
Your purchase of Pervasive products entitles you to 30 days of free
technical support for installation and configuration problems.
See the following section, “Pervasive PSQL Resources and Contacts”
on page 20-1 for information on how to contact Pervasive Software
Customer Support.
19-15
19-16
chapter
Pervasive PSQL Resources
and Contacts
20
A Guide to Pervasive PSQL Customer Information Resources
Pervasive Software strives to ensure that your experience with
Pervasive PSQL is successful. This chapter describes the resources
and information available to you as a valued customer of Pervasive
Software.
The following variety of resources can help you get answers to your
questions, troubleshoot problems, and interact with the Pervasive
team as well as with other customers:

“” on page 20-12
“Developer Center” on page 20-3
“Pervasive PSQL Knowledge Base” on page 20-4
“FTP Site” on page 20-5
“Online Documentation” on page 20-6
“Webinars” on page 20-7
“Subscription Based E-mail Services” on page 20-8
“DevTalk” on page 20-9
“Newsgroup” on page 20-10
“E-Mail Contacts” on page 20-11
“Technical Support” on page 20-12
20-1
Pervasive PSQL Resources and Contacts
Printed Documentation
A complete suite of online documentation is installed on Windows
when you choose the Complete installation procedure. It is available
as an option in the Custom installation procedure. The
documentation is accessible from the Btrieve 7.50 program on the
Start menu.
Printed versions of each manual are available for purchase separately,
or you may purchase the entire documentation set. See “Using
Pervasive PSQL Documentation” on page 1-17 in Pervasive PSQL
User's Guide for a description of the manuals in the set.
To order, contact Pervasive Software online at http://
www.pervasive.com/ecommerce/Scripts/default.asp, e-mail
[email protected], or telephone 1-800-287-4383.
20-2
Developer Center
Developer Center
The Pervasive Software Web site is a great source for Pervasive PSQL
information: http://www.pervasive.com. It is your most immediate
source for assistance with the product.
The link shown below is commonly referred to as Developer Center.
It is a great starting point from which to navigate to available
downloads, documentation, product updates, news articles, sample
code and tutorials. Developer Center also provides access to an
expansive technical library and training information.
http://www.pervasive.com/developerzone/
20-3
Pervasive PSQL Knowledge Base
The Pervasive PSQL Knowledge Base Online is a searchable database
for technical information regarding installation, configuration,
component management, product defect status, and answers to the
frequently asked questions (FAQs). The Knowledge Base, shown
below, uses an associative problem-solving technology to perform
contextual searches and can be used to quickly find specific answers
to your questions about Pervasive products.
http://support.pervasive.com/eSupport/
20-4
FTP Site
FTP Site
Pervasive Software strives to maintain close ties to developers using
Pervasive PSQL for their database applications. On the Pervasive
FTP site, you can find practical resources such as downloadable
updates and patches to our product offerings as well as additional
debugging tools, documentation, third-party tools, and beta
releases.
ftp://ftp.pervasive.com/support/
20-5
Online Documentation
The latest versions of Pervasive PSQL product manuals are available
for download from the Pervasive Software web site:
http://www.pervasive.com/support/technical/online_manuals.asp
Pervasive
Library
You can also view all the current documentation online, along with
technical papers, discussion forums, and other resources.
http://www.pervasive.com/library
20-6
Webinars
Webinars
Pervasive Software offers a series of Webinars (web-based seminars)
that are focused on singular subjects and have been designed to
maximize the transfer of knowledge to our partners and developers
without expense of travel.
This forum also offers opportunities for live contact with subject
matter experts from Pervasive Software in lively discussions during
informal and open question-and-answer periods provided
throughout the conferences.
For more information, see http://www.pervasive.com/training/
calendar/index.asp.
20-7
Subscription Based E-mail Services
TechWire and NewsWire are newsletters on all things Pervasive:
learn about Beta cycles and releases, Service Pack releases, current
topics, FYIs, FAQs, Pervasive Software Events in your area, trade
shows where you can find us, and much more!
To subscribe to these free e-mail services, see the following website.
http://www.pervasive.com/support/subscription.asp
20-8
DevTalk
DevTalk
Pervasive Software’s DevTalk discussion forums are a great way to
share ideas with other customers, get technical questions answered,
and give feedback directly to Pervasive Software.
http://www.pervasive.com/devtalk/
20-9
Newsgroup
Many Pervasive PSQL customers enjoy participation in a
newsgroup—a learning environment in which users help users, with
some participation by Pervasive Software. The newsgroup is
managed by the end-user community, posting and answering
questions as they wish.
Pervasive Software is represented in the worldwide network of news
discussion groups at:
news://comp.databases.btrieve.
20-10
E-Mail Contacts
E-Mail Contacts
Pervasive Software welcomes your comments, suggestions and
requests for assistance via e-mail. Please submit to the following
contacts:

[email protected]
For information about Pervasive PSQL sales matters such as
contacts, pricing, and product specifications.

[email protected]
For developer relations. A great way for developers to
communicate their ideas about all Pervasive products, interfaces
and programs.

[email protected]
For general information about the company, marketing efforts,
public relations, and other general questions.

[email protected]
For questions from investors.
20-11
Technical Support
You may obtain technical support from the following Web-based
support options:

Pervasive Knowledge Base at http://support.pervasive.com/
eSupport
To open a support incident, http://www.pervasive.com/
support/index.asp. Click on Open an Electronic Incident.
To report a product defect, http://www.pervasive.com/
support/index.asp. Click on Report a product defect.
If you require something other than what Web-based support
options provide, contact Pervasive Support by phone:

800-287-4383 option 3 (the Americas)
CIC: +00.800.1212.3434 (Belgium, France, Germany, Italy,
Luxembourg, The Netherlands, Spain, Sweden, Switzerland,
and the U.K)
CIC: +32.0.23.37.61 (Any other European, Middle Eastern,
African or Asian countries, excluding Japan)
For technical support and discussions about Pervasive products in
general:

20-12
Visit the DevTalk forum at http://www.pervasive.com/
devtalk.
Visit http://www.pervasive.com/company/contact/
index.asp for other contact information.
Index
A
Abend
avoiding with CPU Hog Timeout setting 9-3
About Pervasive PSQL 1-1
Accessing
readme file 7-4
Active Directory 8-4
administrative rights required for 8-4
create Pervasive_Admin group on domain
controller 8-5
defined 8-2
directory and file permissions 8-3
grant log on privileges to Pervasive_Admin group
8-8
installation 8-2
installation of Pervasive PSQL with 8-3
mixed mode 8-3
native mode 8-3
Pervasive PSQL clients used with 8-3
tasks 8-4
use of Terminal Services with 8-3
web links to 8-2
Administrative rights
for Active Directory 8-4
needed for installation 2-9
Advantages of Pervasive PSQL 1-2
Analyzing
network 19-5
Application
compatibility 2-9
Applications
configuration scenarios 8-1
configuring concurrent local and remote 8-13
configuring for multiple 8-11
Authentication 16-6
Auto Reconnect Timeout configuration parameter
10-3
B
Beginning installation 5-2
BREQNT.EXE 18-23
BREQTCP.EXE 18-23
BREQUEST.EXE 18-23
BSTART, loading NSS volumes first 11-3
BTRBOX 18-23
Btrieve
licenses 7-4, 9-4
requesters
configuration 18-39
BUTIL
determining file version 19-9
C
Cache Allocation Size
too small on NetWare 5.1 and later 9-8
Checklist
for installation 2-5
Citrix MetaFrame 3-2
see also Terminal Services
Client
determining version 19-8
DOS support 18-23
installation 5-6
custom 5-14
Linux 13-1
NetBIOS support 18-19
Pervasive PSQL 2-2
ports used by 18-16
SPX support 18-15
system requirements
Linux 2-7
TCP/IP support 18-9, 18-12, 18-20
uninstall on Linux 13-12
Communication ports
used by Pervasive PSQL 18-16
Communications
testing 19-5
troubleshooting 19-5
Compatibility
of vendor applications 2-9
Complete Setup
installation option 2-4
Index 1
Components
of Pervasive PSQL 2-2
Configuration
Linux 12-8, 15-14
server 16-6
Pervasive PSQL clients 18-4
requesters
DOS 18-39
settings affected by multiple applications 8-11
Configuration parameters
server
Authentication 16-6
Configuration settings
migration of existing, during upgrade 7-3
Configuring
application scenarios 8-1
concurrent local and remote applications 8-13
database engine on Terminal Services 3-5
multiple applications, for 8-11
server engine with two network cards 6-5, 10-6
SPX support for Windows server 6-6, 10-7
TCP/IP
for Windows server 6-4
TCP/IP support for Windows server 10-5
Connection
testing 19-1
Connectivity, testing 19-1
Contacting
Pervasive resources 20-1
Converting
data files 7-18
CPU Hog Timeout setting 9-3
Create File Version
multiple applications and 8-12
Custom Installation
client 5-14
server, Windows 4-13, 7-14, 9-15
Custom Setup
installation option 2-5
D
Database
engine
checking status 19-6
Database client
2 Index
Database engine
ports used by 18-16
uninstall on Windows 4-17
Determining
type of network 6-2, 10-2
DevTalk, web forum 20-9
Diagnosing
system problems 19-5
Documentation
accessing man pages on Linux 14-13
accessing on Linux 14-12, 14-13
accessing readme file on Linux 14-13
before you begin installing on Linux 14-1
installing on Linux 14-1
installing on Linux using RPM 14-7
installing on Linux using tar 14-10
Linux 12-7, 15-5
NetWare 9-17
Pervasive PSQL 2-3
readme file 2-11
uninstall JavaHelp on Linux 14-16
Windows 4-16, 7-18
DOS box 18-23
preferred for Windows 98 and Windows 32-bit
platforms 18-24
DOS requesters
alternate versions 5-18
using 18-23
with Active Directory 8-3
E
E-mail
Pervasive newsletter 20-8
Enable Auto Reconnect 10-3, 18-2
Engine
components
different version than client 19-11
determining version 19-8
supported
with previous releases 2-9
F
Features
Comparison of Server and Workgroup 1-4
of Pervasive PSQL 1-4
File
version, determining 19-9
File access
native file access protocols 9-2
File Conversion
Windows 7-17
Files installed
Linux 12-8, 13-9, 15-14
NetWare 9-18
Firewall
ports used by Pervasive PSQL 18-16
Firewalls
ports used by Pervasive SQL 18-16
Frame type 6-6, 10-7
Function Executor utility 19-9
G
Group
pervasive_admin on NetWare 9-6
pervasive_admin SPX support on NetWare 10-6
pervasive_admin SPX support on Windows 6-5
pervasive_admin TCP/IP support on NetWare
10-4
pervasive_admin TCP/IP support on Windows
6-3
H
host file 13-8
How
to obtain more help 20-1
I
install.log file 4-4, 7-5, 9-9, 19-3
Installation
before you begin 5-2
checklist 2-5
client 5-6
Linux 13-1
custom
client 5-14
Windows 4-13, 7-14, 9-15
JRE incompatible version warning 14-3
JRE missing warning 14-3
Linux
before you begin 12-2, 13-2
log file location 4-4, 7-5, 9-9, 19-3
NetWare
on Terminal Services 3-4
options 2-4
Complete 2-4
Custom 2-5
over existing Pervasive products 7-4, 9-4
overview 2-2
permissions needed 2-9
problems during 19-1
required conditions for PCC on Linux 14-3
Samba 12-2, 15-2
scheduling upgrade 2-9
server
Linux 12-1, 12-3, 12-5, 15-1, 15-3, 15-4, 159, 15-10
NetWare 9-9
Windows 4-1, 4-4, 7-1, 7-5
tips for NetWare 9-4
tips for Windows 4-2
Windows
Installation location (server)
Pervasive PSQL 1-4
Installing
documentation
documentation on Linux 14-1
documentation using RPM 14-7
documentation using tar 14-10
into Active Directory environment 8-3
PCC
PCC on Linux 14-1
PCC using RPM 14-4
PCC using tar 14-6
Introduction
Pervasive PSQL 1-1
IPX/SPX 18-15
Index 3
J
JavaHelp
accessing on Linux 14-12, 14-13
JRE
required for Linux JavaHelp 14-3
required for Linux PCC 14-3
warning when installing PCC or JavaHelp on
Linux 14-3
L
License key
and user count 4-5, 7-6, 9-10
Licenses
Btrieve 6.x 7-4, 9-4
Pervasive PSQL 1-4
Scalable SQL 4.x 7-4, 9-4
Licensing
database engine on terminal server 3-3
Linux
before you begin installing documentation 14-1
before you begin installing PCC 14-1
client installation 5-6
configuration 12-8, 15-14
server 16-6
documentation
accessing 14-12, 14-13
engine status 19-6
files installed 12-8, 13-9, 15-14
in Monitor utility 13-8
installation 12-1, 12-3, 12-5, 15-1, 15-3, 15-4,
15-9, 15-10
before you begin 12-2, 13-2
Linux 12-3
installing documentation on 14-1
installing PCC on 14-1
IPX/SPX not used 2-8
JRE incompatiable version warning 14-3
JRE missing warning 14-3
man pages
accessing 14-13
manual pages 16-2
network requirements 2-8
online documentation 12-7, 15-5
path formats 16-7, 18-8
PCC required conditions for installation 14-3
4 Index
PCC system requirements 2-8
platform notes 12-2, 15-2
pre-installation notes 12-2, 15-2
readme file
accessing 14-13
system requirements 2-7
TCP/IP 2-8
uninstall client 13-12
uninstall JavaHelp documentation 14-16
uninstall PCC 14-15
user count licenses 12-7, 15-5
Linux Client
Listen IP Address 10-4
Loading
NSS volumes before BSTART/MGRSTART 11-3
Local applications
concurrent with remote 8-13
M
Man pages
accessing on Linux 14-13
Manual pages 16-2
MetaFrame
see Citrix MetaFrame
MGRSTART, loading NSS volumes first 11-3
Microsoft Terminal Services
see Terminal Services
Migrating
configuration settings 7-3
Monitor
Linux clients 13-8
mounting NetWare volumes 13-8
Multihomed TCP/IP network support 10-4
Multiple
applications
configuring for 8-11
network cards
configuring server engine for 6-5, 10-6
N
Named pipes
port used by 18-16
Native file access protocols 9-2
NetBIOS
not supported by Server engine 6-2
support 18-19
NetWare
CPU Hog Timeout setting 9-3
default cache size too small 9-8
engine status 19-7
files installed 9-18
installation 9-9
installation, tips 9-4
mapping drives 9-9
mounting from Linux 13-8
network requirements 2-8
NSS volumes 11-3
slower on updates 11-3
online documentation 9-17
path formats 18-6
pervasive_admin group 9-6
pervasive_admin group and SPX support 10-6
pervasive_admin group and TCP/IP support 104
platform notes 9-2
preventing abend 9-3
support for native file access protocols 9-2
system requirements
server 2-7
Network 2-8
determining what type 6-2, 10-2
path formats 18-5
drive-based formats 18-6
Linux 18-8
NetWare 18-6
UNC 18-5
ports used for communication 18-16
protocol
removing unused 6-8, 10-8
requirements
Linux 2-8
NetWare 2-8
Windows 2-8
setting up SPX for Windows server 6-6, 10-7
setting up TCP/IP for Windows server 6-4, 10-5
Network cards
configuring multiple 10-4
configuring server engine for multiple 6-5, 10-6
Network communications
testing 19-5
Network configuration
Auto Reconnect Timeout
configuration parameter 10-3
Enable Auto Reconnect 10-3, 18-2
Listen IP Address 10-4
supported protocols 10-4, 18-2
TCP/IP Multihomed 10-4
TCP/IP timeout 18-3
News
obtaining via e-mail 20-8
nfsmount 13-8
NSS volume support 11-3
O
ODBC
requires NetWare server if SPX protocol used 62, 10-2
Online documentation
Linux 12-7, 15-5
NetWare 9-17
Pervasive PSQL 2-3
readme file 2-11
Windows 4-16, 7-18
Options
for Complete installation 2-4
for Custom installation 2-5
Overview
P
Path formats
drive-based 18-6
Linux 18-8
NetWare 18-6
network 18-5
UNC 18-5
PCC
before you begin installing on Linux 14-1
installing on Linux 14-1
installing on Linux using RPM 14-4
installing on Linux using tar 14-6
required conditions for installation on Linux 143
system requirements on Linux 2-8
Index 5
Performance
NSS volumes slower on updates 11-3
Pervasive Control Center
configure database through Terminal Services 35
Pervasive PSQL
about 1-1
Additional User count licenses 1-4
advantages 1-2
Client 2-2
Components 2-2
Database Engine 2-2
engines, status of 19-6
features 1-4
installation location (server) 1-4
introduction 1-1
Online Documentation 2-3
relational access 1-3
software configuration 18-4
DOS requesters 18-39
transactional access 1-3
Pervasive Software Website 19-14
Pervasive System Analyzer 19-5
Pervasive_admin
and NetWare 9-6
and SPX support on NetWare 10-6
and SPX support on Windows 6-5
and TCP/IP support on NetWare 10-4
and TCP/IP support on Windows 6-3
Pervasive_Admin security group
use with Active Directory 8-4, 8-5, 8-8
Platform notes
Linux 12-2, 15-2
NetWare 9-2
Windows 4-2, 7-3
Port 139 18-16
Port 1583 18-16
Port 3351 18-16
Ports
used for network communication 18-16
Pre-installation notes, Linux 12-2, 15-2
Previously released engines
support for 2-9
Protocol
6 Index
determining correct 6-2, 10-2
IPX/SPX 18-15
NetBIOS not supported by server 6-2
removing unused 6-8, 10-8
SPX 18-11
supported network 10-4, 18-2
TCP/IP 2-8
Protocols
native file access 9-2
PVSW.LOG
client and server compatibility 19-11
R
Reading
readme file 7-4
Readme file 2-11
accessing 7-4
accessing on Linux 14-13
as part of installation 4-2, 5-2, 7-2, 13-2
Rebuild utility 7-17
Relational access
using Pervasive PSQL 1-3
Relational interface
port used by 18-16
Remote
applications
concurrent with local 8-13
Remote configuration with PCC
on Terminal Services 3-5
Removing
Pervasive PSQL components 19-11
Requester
configuration
DOS 18-39
preferred for Windows 98 and Windows 32-bit
platforms 18-24
use with Active Directory 8-3
Requirements
Linux network 2-8
system 2-6
Rights
administrative authority for Active Directory 8-4
needed for installation 2-9
Terminal Services 3-4
Router
ports used by Pervasive PSQL 18-16
RPM
installing documentation with 14-7
installing PCC with 14-4
S
Samba installation 12-2, 15-2
Scalable SQL
v4.x licenses 7-4, 9-4
Security
pervasive_admin group on NetWare 9-6
pervasive_admin support for SPX on NetWare
10-6
pervasive_admin support for SPX on Windows
6-5
pervasive_admin support for TCP/IP on
NetWare 10-4
pervasive_admin support for TCP/IP on
Windows 6-3
Server
installation
Linux 12-1, 12-3, 12-5, 15-1, 15-3, 15-4, 159, 15-10
NetWare 9-9
Windows 4-1, 4-4, 7-1, 7-5
system requirements
Linux 2-7
NetWare 2-7
Windows NT 2-6
Server engine
NetBIOS not supported 6-2
previous releases supported 2-9
Server Features
in comparison to Workgroup 1-4
Service Pack 4
support for native file access protocols in
NetWare 6.0 9-2
Services
Setup Type
Complete 2-4
Custom 2-5
SmartScout 19-5
Software configuration
DOS requesters 18-39
SPX 18-11
frame type 6-6, 10-7
requires NetWare server for ODBC applications
6-2, 10-2
support
for clients 18-15
setting up for Windows server 6-6, 10-7
Status, of database engine 19-6
Support
obtaining technical 19-15
Supported protocols 10-4, 18-2
System requirements
Client
Linux 2-7
Network 2-8
PCC on Linux 2-8
Server
Linux 2-7
NetWare 2-7
Windows NT 2-6
T
Tar
installing documentation with 14-10
installing PCC with 14-6
TCP/IP 2-8
for clients 18-9, 18-12, 18-20
setting up for Windows server 6-4, 10-5
TCP/IP Multihomed 10-4
TCP/IP Timeout for Communication Requester 183
Technical support
Terminal Server
see Terminal Services
Terminal Services 3-2
configure database engine with PCC 3-5
database engine licensing 3-3
environments supported 3-2
installing on 3-4
permissions 3-4
use within Active Directory environment 8-3
user counts 3-3
Testing
network connectivity 19-5
Transaction Durability
multiple applications and 8-12
turned off by default 7-4
Index 7
Transactional access
using Pervasive PSQL 1-3
Transactional interface
port used by 18-16
Troubleshooting 19-1
communications 19-5
components 19-5
Types
of installation 2-4
Complete 2-4
Custom 2-5
U
Uninstall
Pervasive Control Center on Linux 14-15
Pervasive JavaHelp on Linux 14-16
Pervasive PSQL Client on Linux 13-12
Pervasive PSQL Server on Linux 12-12
Pervasive PSQL Server on Windows 4-17
Uninstalling
files not removed 19-11
Universal Naming Convention See Network path
formats, UNC.
Updates
slower on NetWare NSS volumes 11-3
Upgrading
installation 2-9
migration of existing configuration settings 7-3
User count
additional 1-4
Terminal Services and 3-3
User count licenses
license key 4-5, 7-6, 9-10
Linux 12-7, 15-5
Utilities
Pervasive PSQL 2-2
Rebuild 7-17
SmartScout 19-5
V
Vendor Compatibility 2-9
Verifying
engine status 19-6
Version
engine and client 19-8
how to determine in files 19-9
8 Index
W
Web sites
Pervasive Software 19-14
Windoes
pervasive_admin group and SPX support 6-5
Windows
file conversion 7-17
installation 4-1, 7-1
custom 4-13, 7-14, 9-15
tips 4-2
online documentation 4-16, 7-18
pervasive_admin group and TCP/IP support 6-3
platform notes 4-2, 7-3
Windows NT
server 2-6
Workgroup engine
features compared to Server 1-4
running as a service 3-5