Environment variables under BTOS/CTOS for v5 and v6
900621-mlb01INTRODUCTION:
=============
This Product Services Technical Support Library entry explains
environment variables used by PROGRESS on a BTOS/CTOS system.
WHY YOU'LL NEED TO DO THIS:
===========================
Environment variables are system variables used to tailor a user's
working environment: to set search paths for files and set up terminal
definitions. On BTOS/CTOS systems, the environment variables that
PROGRESS uses are set up in an environment variable file. Under normal
circumstances, each user has a corresponding environment variable file.
The name of this file consists of the user's signon name plus the
extension ".ENV" (user-name.ENV).
HIERARCHY OF ENVIRONMENTS FILES:
At startup, PROGRESS checks for user-name.ENV in the [sys]<sys>
directory. If not found there, PROGRESS checks the
[sys]<sys>user-name.USER file for the
:ProgressEnv: variable which shows the name and
location of the .ENV file. The entry might look something like this:
:ProgressEnv:[sys]<dir>filename.ENV.
If not, PROGRESS will use the default environment variable file
[sys]<sys>Progress.ENV
to set up a user's working environment. The default environment
variable file is created when you install the PROGRESS software.
Table 1 provides information on the environment variables PROGRESS
needs to run on a BTOS/CTOS system.
TABLE 1: PROGRESS Environment Variables for BTOS/CTOS Systems
----------------------------------------------------------------------
Variable Description Default
-----------------------------------------------------------------------
DLC Volume and directory that contains [sys]<dlc>
the PROGRESS system software.
DLCFT Volume and directory that contains [sys]<dlcft>
the PROGRESS FAST TRACK system
software.
PROCFG The full pathname of the file that [sys]<dlc>*.CFG
identifies the PROGRESS product and
components you are licensed to use.
PROMSGS The full path name of the file that [sys]<dlc>PROMSGS
contains the PROGRESS system
messages.
PROPATH A list of directories PROGRESS [sys]<dlc>
searches to find procedures.
For example:
PROPATH=:[SYS]<APP>:<PROCS>:[D1]<DEMO>
Tells PROGRESS to search the current
directory (indicated by : with nothing
preceeding it); then the APP directory
on the SYS volume; then the PROCS
directory on the current volume; then
the DEMO directory on the D1 volume.
The DLC directory on the SYS volume (or
the directory indicated by the DLC
variable) and its subdirectories
PRODEMO/, and PROGUIDE/ are searched
by default. If you are running
Test Drive, be sure to include the
directory where you loaded Test Drive
in the PROPATH.
PROTERMCAP The full path name of the file that [sys]<dlc>PROTERMCAP
contains terminal control
information for PROGRESS.
TERM The type of terminal you are using. B20
The following is an example of an environment variable file called
[sys]<Bob>Bob.ENV:
-------------------------------------------
TERM=B26
DLC=[sys]<dlc>
PROTERMCAP=[sys]<dlc>protermcap
PROMSGS=[sys]<dlc>promsgs
PROPATH=:[sys]<dlc>:[work]<progresswork>:
-------------------------------------------
Use the 'PROGRESS Environment Print' command to list the name of your
current environment file and current settings.
The environment variable file entries that must exist for each
PROGRESS product and samples are shown in Table 2.
TABLE 2: Sample BTOS/CTOS Environment Variable
File Entries for PROGRESS Products
PROGRESS Product Environment Variable File Entry
------------------------------------------------------------
PROGRESS Application DLC=[sys]<dlc>
Development System DLCFT=[sys]<dlcft>
(PADS)
PROGRESS 4GL/RDBMS DLC=[sys]<dlc>
PROGRESS Query/Runtime DLC=[sys]<dlc>
PROGRESS Run-Time DLC=[sys]<dlc>
DLCFT=[sys]<dlcft> (optional)
PROGRESS FAST TRACK DLC=[sys]<dlc>
DLCFT=[sys]<dlcft>
PROGRESS QUERY/REPORT DLC=[sys]<dlc>
DLCFT=[sys]<dlcft> (optional)
TEST DRIVE DLC=[sys]<dlctda>
DLCFT=[sys]<dlcft>
DEVELOPER'S TOOLKIT DLC=[sys]<dlc>
DLCTK=[sys]<dlctk>
GENERAL TROUBLESHOOTING HINTS
=============================
If users cannot run a PROGRESS command, be sure they are
using a set of commands that include the PROGRESS commands.
The commands were added to [sys]<sys>sys.cmds at system
installation time.
If users cannot RUN a procedure, be sure the PROPATH
environment file entry indicates the directory of the
procedure they are trying to run.
REFERENCES TO WRITTEN DOCUMENTATION
===================================
Version 5: Ch. 4 PROGRESS Environments Guide
Version 6: Ch. 4 PROGRESS SYSTEM ADMINISTRATION I:
ENVIRONMENTS
BTOS/CTOS System Administration Student Guide
Progress Software Technical Support Note # 5173