BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Programming BEA Tuxedo ATMI Applications Using COBOL   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


Setting Environment Variables

Initially, the application administrator sets the variables that define the environment in which your application runs. These environment variables are set by assigning values to the ENVFILE parameter in the MACHINES section of the UBBCONFIG file. (Refer to Setting Up a BEA Tuxedo Application for more information.)

For the client and server routines in your application, you can update existing environment variables or create new ones. The following table summarizes the most commonly used environment variables. The variables are listed by functional category.Programming-related Environment Variables

Function

Environment Variable

Defines the . . .

Used by . . .

Global

TUXDIR

Location of the BEA Tuxedo system binary files.

BEA Tuxedo application programs.

Configuration

TUXCONFIG

Location of the BEA Tuxedo configuration file.

BEA Tuxedo application programs.

Compiling

ALTCC1

Command that invokes the COBOL compiler. Default is cobcc.

buildclient() -C and buildserver() -C commands.

ALTCFLAGS1

Link edit flags to be passed to the COBOL compiler. Link edit flags are optional.

buildclient() -C and buildserver() -C commands.

COBOPT

Arguments that you may want to use on the compile command line.

buildclient() -C and buildserver() -C commands.

COBCPY

Directories that contain a set of the COBOL COPY files to be used by the compiler.

buildclient() -C and buildserver() -C commands.

Data compression

TMCMPPRFM

Level of compression between 1 and 9.

BEA Tuxedo application programs that perform data compression.

Load balancing

TMNETLOAD

Numeric value that is added to the load value for remote queues, making the remote queues appear to have more work than they actually do. As a result, even if load balancing is enabled, local requests are sent to local queues more often than to remote queues.

BEA Tuxedo application programs that perform load balancing.

Record management

FIELDTBLS or FIELDTBLS32

Comma-separated list of field table filenames for FML and FML32 typed records, respectively. Required only for FML VIEW types.

FML and FML32 record types and FML VIEWs.

FLDTBLDIR or FLDTBLDIR32

Colon-separated list of directories to be searched for the field table files for FML and FML32, respectively. For Windows 2000, a semicolon-separated list is used.

FML and FML32 record types and FML VIEWs.

VIEWFILES or VIEWFILES32

Comma-separated list of allowable filenames for VIEW and VIEW32 typed records, respectively.

VIEW and VIEW32 record types.

VIEWDIR or VIEWDIR32

Colon-separated list of directories to be searched for VIEW and VIEW32 files, respectively. For Windows 2000, a semicolon-separated list is used.

VIEW and VIEW32 record types.

1

On a Windows 2000 system, the ALTCC and ALTCFLAGS environment variables are not applicable and setting them will produce unexpected results. You must compile your application first using a COBOL compiler and then pass the resulting object file to the buildclient or buildserver command.

If operating in a UNIX environment, add $TUXDIR/bin to your environment PATH to ensure that your application can locate the executables for the BEA Tuxedo system commands. For more information on setting up the environment, refer to Setting Up a BEA Tuxedo Application.

See Also

 

back to top previous page next page