Purpose

This document explains in detail how to install the Ashton-Tate SQL
Server on a Novell Netware based network. In the first release of SQL
Server the install program only installed SQL Server on a IBM/Microsoft
Lan Manager system. The steps this document outlines were derived from
several sources as well as trial and error. A useful source of
information was the magazine SQL Server Environment, September/October,
1898,


Installing OS/2

SQL Server is an OS/2 Named Pipes based application and thus requires
a 286 or 386 based machine running OS/2 version 1.1 with a release date
of 89039 or greater. To install this level of OS/2 follow the
instructions in the OS/2 Getting Started manual. (If you find the
release date is less than 89039, you can upgrade the operating system
through the "Corrective Service Diskettes" which may acquired through
the communication group of Systems Programming.)


Installing Netware Requestor

Since SQL Server is a Named Pipe application, so Named pipes support
must be installed on the OS/2 machine. Since the server will be running
on a Netware network, this is accomplished by installing the Netware
Requestor 1.1 for OS/2. The requestor allows OS/2 stations to log into
a Netware file server as well as communicate over a Netware network.

After following the Novell instructions for installing the Requestor for
OS/2, you will need to edit the OS/2 CONFIG.SYS file and remove the REMs
from the SPX and Named Pipe device drivers and daemons. On the Named
Pipes device driver line, you need to add the name that this SQL Server
will have. This is used to access this specific server.
After doing this, you will want to reboot the machine to install the
drivers.


Installing SQL Server

The following explains step by step how to install the SQL software on
the OS/2 machine. All files mentioned below will be found scattered on
the SQL Server software diskettes.

Decide which drive the software is to be installed

Make a directory named \SQL on the drive

Make a directory named \SQL\PGM to contain all the SQL
programs

- Copy the following files to the \SQL\PGM directory
ISQL.EXE
CACHE.EXE
SAF.EXE
DEFNCOPY.EXE
BLDMASTR.EXE
TESTLM.EXE
STARTSQL.EXE
MAKEPIPE.EXE
READPIPE.EXE
DBLIBW.EXE
SQL.HLP
CONSOLE.EXE
BCP.EXE
PROBE.EXE
SQLSERV1.EXE
SQLSERV2.EXE

- Concatenate SQLSERV1.EXE and SQLSERV2.EXE using the
following command.
COPY /b SQLSERV1.EXE+SQLSERV2.EXE /b SQLSERVR.EXE

- Delete SQLSERV1.EXE and SQLSERV2.EXE

- Add \SQL\PGM to the search path

Make a directory named \SQL\EXAMPLES to contain the
programming examples

- Copy all following files into the \SQL\EXAMPLES directory

*.H
*.C
SQLTEST*.*
*.LIB
*.OBJ

Make a directory named \SQL\DLL to contain all the SQL Dynamic
Link Libraries

- Copy all *.DLL files to directory

- Put \SQL\DLL in the LIBPATH of the CONFIG.SYS file.

Make a directory named \SQL\LOG to contain all SQL error logs

Make a directory named \SQL\DATA to contain the SQL master
database

Make a directory named \SQL\INSTALL to contain the SQL
installation scripts

- COPY all *.SQL files into this directory

Build the SQL master database

- BLDMASTR /d d:\SQL\DATA\MASTER.DAT /C

Start SQL Server in single user mode

- SQLSERVR /d d:\SQL\DATA\MASTER.DAT /m

Run the SQL install scripts in the following order

- Run the master database definition script

ISQL /U sa /P /S
- Run the model database definition script

ISQL /U sa /P /S
- Run the pubs practice database definition script

ISQL /U sa /P /S

Run the RECONFIGURE command which commits all changes made by
the scripts

- ISQL /U sa /P /S
1> RECONFIGURE
2> GO
3> QUIT

Dump the master database for backup by following procedures
in the SQL Administrators guide.


Running SQL Server in Multiuser Mode

After all the above steps have been completed. You will want to bring
SQL Server down and restart it in multiuser mode. This can be
accomplished in the following manner.

1. Run ISQL and enter the shutdown command.

ISQL /U sa /P /S

1> SHUTDOWN

2. Restart SQL Server by entering:

SQLSERVR /d d:\SQL\DATA\MASTER.DAT

WARNING!!! You should always avoid turning off the SQL Server machine
without first shutting down SQL Server first. The shutdown assures that
all transactions are finished and file buffers are flushed.