Progress
Installation and Configuration Guide
Version 9
for UNIX
UNIX Environment Variables
This section describes the operating system-specific environment variables for the UNIX operating system.
For information about setting environment variables related to Progress AppServer, Progress WebSpeed, a Progress DataServer, or the Progress SonicMQ Adapter, see the AppServer, WebSpeed, DataServer, or Progress on the Web documentation.
After installation, Progress requires little additional configuration. There are, however, several environment variables that provide for customization and flexibility. For example, the PATH environment variable allows scripts and images to be found easily, and is the only environment variable needed by most UNIX users.
Typically, the default values of Progress environment variables are based on the
DLC
top level variable. If so,DLC
must be set to the directory where Progress is installed.Running the
proenv
script setsDLC
to this directory automatically.Proenv
also adds$DLC/bin
to your path and changes your current directory to the Progress work directory set during installation.You can edit the
.profile
of a user to set up environment variables automatically each time the user logs onto the system. Also, be sure to export environment variables to make them available to child processes.This section describes the purpose of each environment variable. Usage with the Bourne shell is given, yet other shells use similar syntax.
Table 5–1 describes the UNIX environment variables. Read these descriptions to determine the variables you want to set.
NOTES
- $
DLC
is an environment variable for the full pathname of the directory where Progress is installed. You can run Proenv to automatically setDLC
to this directory.- If you want to use a remote DataServer, you must set additional environment variables depending on the type of DataServer you want to use (for example, ORACLE or ODBC). See the DataServer documentation for more information on the other variables set.
- When you first execute a Progress command or utility that requires Java, Progress correctly sets the Java environment variables based on your UNIX platform.
Table 5–1: UNIX Environment Variables Variable Description Code Example DLC
The pathname of the directory where you installed the Progress software. The default value is/usr/dlc
. You must set this variable if you install the Progress software in an alternate directory.DLC=/usr/dlc
PATH
A list of the directories UNIX searches to find any commands that you provide. Progress also searches these directories for UNIX commands or programs you name when using the INPUT THROUGH and OUTPUT THROUGH statements.
Include$DLC/bin
in the PATH environment variable. To keep end users out of the/DLC
directory, you can provide scripts to perform all Progress-related actions. These scripts can reside somewhere else in the PATH and invoke Progress commands with full pathnames. Place your startup, shutdown, and maintenance scripts somewhere in the path directories.
NOTE: If during installation you chose yes to copy scripts to/usr/bin
, just ensure thatPATH
is set to/usr/bin
:PATH=:/usr/bin
.PATH=$PATH:$DLC/bin
PROCFG
The filename (or full pathname) of your product’s configuration file. The configuration file is a data file that identifies the Progress product and components that you are licensed to use. The default value is$DLC/progress.cfg
. Reset PROCFG if you have moved your configuration file from the directory where you installed Progress.PROCFG=$DLC/products.cfg
PROCONV
The filename (or full pathname) of the Progressconvmap.cp
file. Theconvmap.cp
file is a binary file that contains all of the conversion tables that are available to Progress. The default value is$DLC/convmap.cp
. See the Progress Internationalization Guide for more information on theconvmap.cp
file.PROCONV=$DLC/convmap.cp
PROEXE
The pathname of your Progress executable file. The default value is$DLC/bin/_progres
. If you move_progres
out of$DLC/bin
, rename_progres
, or use the PROBUILD utility to generate a customized module, set PROEXE appropriately (or modify your scripts).PROEXE=$DLC/bin/_progres
PROLOAD
The pathname of the directory where you installed the PROBUILD product, if you installed it. The default value is$DLC/probuild
. For example, if you installed PROBUILD in the directory/vol1/devdir/load
, use the code example.PROLOAD=/voll/devdir/load
PROMSGS
The full pathname of your Progress run-time messages file. The default value is$DLC/promsgs
. For example, if you want to use the German run-time messages file, use the code example in your profile. You only set the PROMSGS environment variable if you want to use a run-time messages file different from the default PROMSGS file in the$DLC
directory.PROMSGS=$DLC/prolang/ger/
promsgs.ger PROPATH
A list of directories Progress searches to find procedures.
Progress AppServer and Progress WebSpeed use the PROPATH property in$DLC/properties/ubroker.properties.
Otherwise, by default, Progress searches:
1.$DLC/tty
2.$DLC
3.$DLC/bin
Use the following syntax to set thePROPATH
environment variable:PROPATH=[:]{
dir-name|$
env-var}(:...)
where:
:
Tells Progress to search your working
directory before searching any other
directories.
dir-name
Specifies the name of a directory that you
want Progress to search.
env-var
Specifies the environment variable whose
definition names one or more directories
that you want to search.
(:...
)
Separates multiple dir-name or env-var.;
Ends the definition of the PROPATH
environment variable and indicates the
start of a new command.PROPATH=:persapp:$DLC
PROSRV
The pathname of your executable PROSERVE file. The default value is$DLC/bin/_mprosrv
. The PROSERVE script includes the code example. Therefore, if you move_mprosrv
out of$DLC/bin
, rename_mprosrv
, or use the PROBUILD utility to create a customized module, set PROSRV appropriately (or modify your proserve script).PROSRV=$DLC/bin/_mprosrv
PROSTARTUP
The pathname of the Progress default startup parameter file,startup.pf
. This file is read by all Progress modules at startup; it must exist for Progress to execute properly.PROSTARTUP=$DLC/startup.pf
PROTERMCAP
The full pathname of the terminal definition file that you want your Progress session to use. The default terminal definition file is calledPROTERMCAP
, and is installed by default in the/$DLC
directory. You only have to set the PROTERMCAP environment variable if you want to use a different terminal definition file from the default PROTERMCAP file.PROTERMCAP=$DLC/SPECIALCAP
TERM
The type of terminal you are using. For example, to define your terminal type as wy75, use the code example.TERM=wy75
JDKHOME
Establishes the top-level directory for the Java Developer’s Kit (JDK).NOTE: When you first execute a Progress command or utility that requires Java, Progress correctly sets the Java environment variables based on your version of UNIX.
JDKHOME=$DLC/jdk
JREHOME
Establishes the top-level directory for the Java Runtime Environment (JRE).JREHOME=$DLC/jre
JFCHOME
Establishes the top level directory for the Java Foundation Classes (JFC).JFCHOME=$DLC/jfc
JDKCP
Sets the classpath forclass.zip
; Java Developer’s Kit (JDK) only.JDKCP=$JDKHOME/lib/class.zip
JRECP
Sets the classpath for Java Runtime Environment (JRE); if no JRE, then it sets classpath for JDK.JRECP=$JREHOME/lib/rt.jar
JFCCP
Sets the classpath for Java Foundation Classes (JFC) only.JFCCP=$JFCHOME/swingall.jar
PROGRESSCP
Contains a list of paths, jar files, and zip files for running Progress-specific products.PROGRESSCP=$DLC/java/
progress.zip CLASSPATH
Progress correctly sets the appropriate classpath variable based on the platform in use.CLASSPATH=$JDKCP:$JFCCP:$PROGRESSCP
JIT Sets the just-in-time compiler correctly.JIT="-nojit"
JVMEXE Sets the Java Virtual Machine to run correctly.JVMEXE=jre
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |