Consultor Eletrônico

Status: Unverified

GOAL:

DOS Executable Modules and Why You Need Them

FACT(s) (Environment):

Progress 6.x

CAUSE:

This older solution describes what the various DOS Progress modules are used for. The original intent was to help you decide which files can be removed without losing any desired functionality.
Although it applies to older Progress releases (Version 6.x) and some of the files have changed, the solution contains some valuable background information.

FIX:

Progress requires a more considerable amount of disk space than in previous releases. While a developer might use most of the Progress facilities, a runtime user probably would not and there is a lot of disk space that can be saved by taking away modules that are not used.
Read through the following list and determine what files you don't need in the /DLC directory and then remove them.

Basically, you need only one of the combinations of files from
Section 1 and the files in Section 2 to run an application. But
depending on the application and the machine you have, you will
probably also need some of the files in Section 3. The files in
section 4 are additional features and are not needed for runtime
users.

Section 1:

1) _progres.exe
The memory saver executable and overlay file needed.
_progres.ovl (132 + 696K)
if your computer isn't configured with extended memory
and you want to run Progress either locally or on an SPX
or NETBIOS network.

2) _proxln.exe
The executable and overlay file needed for running.
_proxln.ovl (151 + 700 K)
Progress (memory saver) on a EXCELAN TCP/IP TCP/IP
network.

3) _proftp.exe
The executable and overlay file needed for running.
_proftp.ovl (150 + 699 K)
Progress (memory saver) on a FTP TCP/IP network.

4) _pprogrs.exe
The protected mode executable used if your 914 K computer
is configured with at least 1 MB of extended memory.
prorpc.exe
The prorpc.exe executable is used together with
_pprogrs.exe to run Progress on a proxln.exe network. It
also uses either proncs.exe (SPX - NETBIOS - FTP TCP/IP)
or proxln.exe (EXCELAN TCP/IP).

Section 2:

To be able to run Progress, you need one of the above
combinations complemented with:

- progress.cfg
A binary configuration file that contains information
about the Progress license.

- Promsgs (147 K)
The file that contains the Progress messages.

Section 3:

If the application does OS-escapes you will need rundos.exe. If
it uses the QUOTER function, you will need quoter.exe.

A file that isn't needed to run Progress but that is strongly
recommended to save anyway is:

_proutil.exe (385 K)
This executable is used for a number of different
actions such as truncating the before-image file,
bulk-loading data and performing the Progress Index
Rebuild Utility.

If you are going to run an application that is originally written
in an earlier Progress version than the one that you are
currently using, you probably need:

newkywd
ASCII file with a list of all the new keywords in
Progress Version 6.x.

If you intend to run Progress in protected mode, under some
circumstances you also need:

- config.286
This file is normally not needed unless your machine
is an IBM PS-2 model 70. To determine if you need to
use config.286, read Page 2-10 in Progress System
Administration 1. If you need to use config.286,
remember to set the AIA environment variable to point
to where you have placed it.

- tune.exe
The tune utility adjusts to the _pprogrs executable,
enabling it to run in your machine's extended memory.
After you have run tune you can delete it.

Section 4:

The following files are optional and are not necessarily needed
in a runtime environment:

quoter.c
Source code for the quoter executable.

empty.db
The Progress empty database.

demo.db
The Progress demonstratio.n database.

progress.dat
ASCII file containing your license number.

proutil.bat
Start script for _proutil.exe.

readme.pro
ASCII file with information about the release.

Cmpdb.exe
Command used to compare two databases.

dbf.exe
Used for import/export of database files.

chkcrc.exe
Only used for troubleshooting, not needed if Progress
works correctly.

dms6.exe
Used when running HLC with memory save Progress.

ovl.lst
ASCII file listing of all overlay files.

testcl.exe
Used for testing CLIENT-SERVER communication on a
testsv.exe network.

prodb.exe
Prompts you for a database name, makes a copy of
it, and lets you give the copy a new name.

prodel.exe
Deletes a database (.db .bi .lg).

prolog.exe
Truncates your database.lg file, leaving only the last
few entries.

config.pro
Example of a config.sys file.

autoexec.pro
Example of an autoexec.bat file.

pro.bat
Start script for a Progress single-user session.

mpro.bat
Start script for a Progress multi-user session.

bpro.bat
Start script for a Progress batch single-user session.

mbpro.bat
Start script for a Progress batch multi-user session.

proxcom.bat
Start script invoking the -rx startup option to enable
runtime users to compile encrypted source code and
access the Dictionary.

Hello
version
The hello and version files are displayed during an
executution of one of the Progress non-batch startup
scripts.

prostart.p
Standard Progress startup procedure used by pro.bat
and mpro.bat.

login.p
Procedure used by prostart.p to establish UserID for
each connected database.

help.p
The procedure being executed when the "help" key is
pressed from within the Progress editor. See also
PROHELP <LIB> below.

dict.p
Progress Data Dictionary main program. See also
PRODICT <LIB> below.

applhelp.p
The default help procedure being executed whenever the
user presses the "help" key while running a program.

proterm.cap
A DOS substitute for the protermcap file used if you,
for example, want a special output to a printer.

whatmem.exe
Executable giving you information about the memory
configuration in your machine.

PROHELP <LIB> (700 K)
The prohelp directory holds the procedures performing
the functions on the "help" menu you access through
help.p. There are two subdirectories, msgdata (contains
text that describes all Progress error messages), and
indata (with Progress functions and statements).

PROGUIDE <LIB> (240 K)
The proguide directory holds 3 files containing the
examples for the Progress manuals in a packed format
and a program for unpacking them.

PRODEMO <LIB> (1000 K)
The prodemo directory holds (also in packed 1000 K
format) all the files that can be extracted using the
"p" = Access to the procedure library entry on the
"help" menu, and procedures to manage those files.

PROLA.NG <LIB> (600 K)
In the prolang directory you find the non-English
promsgs files. You can either replace the promsgs file
in the DLC directory with the promsgs version that you
wish to use, or you can set the PROMSGS environment
variable to point to the desired promsgs file.

PROBIN <LIB> (540K)
The probin directory contains scripts for a number of
Progress utilities and the executables that actually
perform the action.

Progress roll forward utility:
rfutil.bat which calls for rfutil.exe.

The following all call for _dbutil.exe:

- Progress database backup - probkup.bat.
- Progress database restore - prorest.bat.
- PROGRESS create multi-volume structure files -
prostrct.bat.
- Progress copy data into multi-volume database -
procopy.bat.

PRODICT <LIB> (3200 K)
If you choose the "d" = dictionary option on the "help"
menu or run dict.p from the editor, you will access the
programs in the prodict directory. The actions
performed by the files in PRODICT are disclosed by the
file named prefixes:

dict* - dictionary kernel routines.
dump* - export programs.
help* - dictionary on-line help (reserved).
list* - reporting programs.
load* - import programs.
menu* - menu programs.
os* - opsys-specific functions.
run_* - programs compiled on-the-fly (always .i).
tool* - tools.
user* - user interface.
pro_* - Progress gateway drivers.
sql_* - Progress/SQL drivers.
rms_* - RMS GATEWAY drivers.
rdb_* - RDB GATEWAY drivers.
ora_* - Oracle GATEWAY drivers.

If you only want to be able to run an application, you need the
minimum configuration as follows:

With 640 KB RAM With 2 MB RAM
-------------------- --------------------
_progres.exe 132 K _pprogrs.exe 914 K
_progres.ovl 696 K promsgs 147 K
promsgs 147 K progress.cfg 0.05 K
progress.cfg 0.05 K ------
------ 1061 K
975 K


Reference to Written Documentation:

Progress Installation Guide Version 6 (DOS).

Progress System Administration II..