Kbase 714: Where to install files on a DOS LAN (also distributing files
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/22/2001 |
|
Where to install files on a DOS LAN (also distributing files
910626-GSS01
INTRODUCTION: Date Last Modified: 6/26/91
=============
This Product Services Technical Support Knowledgebase entry explains
where to install PROGRESS on your DOS Local Area Network (LAN) and
how to distribute files across the LAN to help improve performance.
WHY YOU WOULD WANT TO DO THIS:
==============================
Proper installation and distribution of files can help reduce disk
space usage and increase system performance.
PROCEDURAl APPROACH:
====================
Installing PROGRESS:
PROGRESS should be installed on the network file server.
In Version 5, all single user system files are installed in
the \DLC directory by default and all multi-user system files
are installed in the \DLC\LAN directory by default.
In Version 6, the LAN product is divided into two separate
modules, the DOS Server module and the DOS & OS/2 Client
module. By default, each is installed in the \DLC directory,
so you must either install the modules in separate directories
or choose the merge option when installing the second module in
the same directory as the first. While installing the second
module, if you specify the directory where you installed the
first module, PROGRESS lets you know that the directory
already exists and gives you three options:
1. Delete the contents of that directory and continue with
the installation.
2. Quit and select another installation directory.
3. Merge the Server module and Client module into the same
directory. Both modules must have the same version number.
After you install PROGRESS, there are several ways of improving
performance by distributing system, procedure, database and session
files across your LAN.
System Files:
On each of the application workstations with a hard disk, make a
local \DLC directory and copy the following files into it from
the \DLC directory on the network file server:
?
_PROGRES.EXE
_PROGRES.OVL
_PPROGRS.EXE
PRONCS.EXE
PRORPC.EXE
PROMSGS
RUNDOS.EXE
On the PROGRESS database engine with a hard disk, make a local
\DLC directory and copy the following files into it from the \DLC
directory on the file server:
PROMSGS
_MPROSRV.EXE
Make sure that the environment variables for these files are
set to point at the local copies of these files.
Procedure Files:
Procedure files are files that contain PROGRESS source or object
procedures. If an application workstation has a fast local hard
disk, you may see some system performance improvement by storing
copies of these procedure files locally on that machine. If you do
this, be sure that the first directory searched in your PROPATH
environment variable is the one local to that machine.
Database Files:
If your LAN has one machine as the dedicated network files server
and another machine as the dedicated PROGRESS database engine,
place the database files (.db, .bi and .lg) on the database engine.
Some network operating systems contain features that eliminate
bottlenecks in disk I/O at the file server and increase disk
performance. You may be able to improve system perfomance by
placing the PROGRESS database (.db file) on the file server. If
you do this, store the PROGRESS before image file (.bi) on the
database engine to ensure database integrity. Use the PROGRESS
before image file name (-g) startup option to set the before image
file.
If your LAN is using one machine for the network file server
and the PROGESS database engine, you have to put all the database
files on that machine. This type of configuration is not optimal,
because it tends to severely degrade performance and compromises
database integrity. It jeopardizes database integrity because the
network file server buffers disk writes and PROGRESS depends on
immediate writes to the before image file to keep the database
and before image file in synchronization.
?
Session Files:
Session files are temporary files that PROGRESS creates and
deletes during a PROGRESS session. These files have the following
prefixes and descriptions:
LBI - local before image file
PGE - program edit buffer file
SRT - sorting and/or session compile file
TRP - schema trap file
By default, PROGRESS stores these session files in the user's
current working directory. Because local write access may be
much faster than network write access, you may see system
perfomance improve if you direct these session files to the local
hard disk of each application workstation whenever possible. Use
the temproary directory (-T) startup option to name the directory
where these temporary files should be stored.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Version 5:
Installation Notes : version 5.2I or higher (DOS LAN)-
Installing PROGRESS Software
System Administration Guide - Startup Options
Environments Guide - Preparing to Use LAN PROGRESS
Version 6:
Installation Guide : PROGRESS Version 6 (DOS) - Installing PROGRESS
System Administration Guide II - Startup Options
System Administration Guide I - PROGRESS and DOS LANs
Progress Software Technical Support Note # 714