Appendix A: Environment Variables

This appendix lists all the environment variables that Server Express uses, and describes how to specify them.

Environment Variable
Summary
CCITCP2 Locates TCP/IP registration program
CCITRACE Specifies the level of CCI tracing
COBAIF Locates .aif files
COBAIFNAME Specifies basename of .aif files
COBANIMOPT Specifies directives to Animator
COBANIMSRV Attaches Animator to a running program
COBATTR Selects appearance of HIGHLIGHT and LOWLIGHT
COBCONFIG Tailors run-time configurable options
COBCPY Locates copyfiles
COBDATA Locates data files
COBDIR Locates COBOL system software
COBIDY Locates Animator information (.idy) files
COBEXTFHBUF Specifies that fixed length sequential files are to be buffered
COBJVM Specifies which Java Virtual Machine to load
COBKEYTIMEOUT Tunes remote terminal response
COBMAINSTACK Sets the size of the main stack
COBOPT Specifies user default Cob utility options
COBPATH Locates programs for dynamic loading
COBPRINTER Directs output to a print spooler
COBSES Specifies the UNIX Session Recorder functions to perform
COBSW Sets run-time system switches
COBTERMINFO Locates COBOL terminfo terminal database
COLUMNS Specifies screen width
EXTFH Specifies a configuration file for the Callable File Handler
FHREDIR Specifies a configuration file to be used by the Fileshare Client
FS Specifies a configuration file for Fileshare Server
FSCOMMS Specifies that the Fileshare System is to run in single user mode
GNTANLZ Specifies a configuration file for use with GNT Analyzer
HCOBND Specifies a directory for DB2 bind files
LANG Specifies the language environment
LD_LIBRARY_PATH Locates shared libraries
LIBLIST Locates special Cob library list
LIBPATH Locates shared libraries
LINES Specifies screen depth
MFCFCSG Specifies a configuration file to be used by the Client/Server Binding client program
MFCODESET Specifies which translation tables to use
MFLOGDIR Specifies a directory to be used by Client/Server Binding for log files
PATH Locates directories for all UNIX programs
SHLIB_PATH Locates shared libraries
SORTCOMPRESS Specifies that a compression routine should be used on sort records
SORTSPACE Specifies internal work space for SORT operations
TERM Specifies terminal type
TERMINFO Locates UNIX system terminfo database
TMPDIR Locates directory for temporary files

Details on the use of these environment variables can be found in the main body of the manual set. dd_ routines provide an alternative method of assigning values to environment variables. These are detailed in the chapter Filenames in your File Handling book.


Note: The syntax in the following descriptions is shown as required for the sh and ksh shells. Other shells, such as csh, require syntax of the form:

setenv env_var value

where the parameters are:

env_var One of the environment variables shown on the following pages
value A value to which the environment variable can be set

CCITCP2

Specifies the TCP address of the machine running the CCITCP2 registration daemon. It is associated with the Common Communications Interface (CCITCP). See your Configuring CCI book for details.

Syntax:
CCITCP2=hostname
export CCITCP2
Parameters:
hostname TCP hostname or dotted decimal IP address of the machine running the CCITCP2 daemon you wish to contact, as listed in the TCP/IP hosts file.
Comments:

There are two methods of specifying the level of tracing: the CCITRACE environment variable and the control-buffer parameter passed to a CCI-Trace function call.


CCITRACE

Specifies the style of the traced output.

Syntax:
CCITRACE=filename[options] 
export CCITRACE
Parameters:
filename The name of the log file you want the trace output to go to. If you do not specify this parameter, the log file ccitrace.log is created in the current directory with all options set to their default states.
options Can be any one, or all, of the following, and must be upper case:

/A or -A logs the status of CCI functions after a call has completed. The default condition for this option is ON unless /B or -B is specified.

/B or -B logs the status of CCI functions before execution. When B is specified, all parameters are logged to the disk file. The default condition for this option is ON unless /A or -A is specified.

/D or -D logs the contents of all buffers passed to and from the CCI functions. The default condition for this option is OFF.

Comments:

See your Configuring CCI book for detailed information on CCI application call tracing.


COBAIF

Specifies the directories in which Animator searches for or creates the Animator session file (.aif) for the program being animated. The .aif file contains details of breakpoints and monitors.

Syntax:
COBAIF=pathname
export COBAIF
Parameters:

pathname[:pathname]... The directories that Animator is to search.
Comments:

If the .aif file is not found on the path specified by COBAIF, a search is made of the directories specified by the COBIDY environment variable. If the session file is still not found, the current directory is searched.

If an .aif file does not exist, Animator creates it as follows:

There is also an Animator directive COBAIF; see the chapter Directives for Animator in your Debugging Guide for details.


COBAIFNAME

Specifies the basename of the Animator session file (.aif) for the program being animated. The .aif file contains details of breakpoints and monitors.

Syntax:
COBAIFNAME=basename
export COBAIFNAME
Parameters:

basename The basename of the .aif file.
Comments:

You need to specify this evironment variable if you are starting Animator using COBSW=+A and you want to save breakpoints for subsequent animation sessions. You can also specify it if you are starting Animator using the command anim; in this case the basename you specify overrides the application name as the basename of the .aif file. You must still specify the Animator directive COBAIF.


COBANIMOPT

Specifies directives to be used by Animator.

Syntax:
COBANIMOPT=directive-list 
export COBANIMOPT
Parameters:
directive-list A list of directives. Animator directives are described in the chapter Directives for Animator in your Debugging Guide. Must not be a filename.
Example:
COBANIMOPT="MIXEDLANGDEBUG MULTITHREAD"
export COBANIMOPT
Comments:

When you invoke Animator, it first reads the directives you have specified in COBANIMOPT and then uses any directives you specify in the command line (which might override some of the directives you set in COBANIMOPT). For details on the format for specifying directives, see the chapter Debugging Methods in your Debugging Guide.


COBANIMSRV

Identifies which COBOL program a waiting Animator process should attach to.

Syntax:
COBANIMSRV=progid 
export COBANIMSRV
Parameters:
progid An identifier that is used to identify the program to which Animator will attach.
Example:

In one console session:

export COBANIMSRV=myid

myid is now a unique identifier that you can use to match Animator to a program. Type the command to start Animator:

cobanimsrv

The Animator waits for a COBOL program to start that has a matching identifier. In another console session:

export COBANIMSRV=myid
cobrun prog1.int

When prog1.int starts the unique identifier myid matches that of Animator; therefore, Animator attaches to this process. In console session 1, the Animator main screen is displayed and the cursor placed on the first line of prog1.int.

Comments:

This environment variable is particularly useful for starting cross-session debugging. See the chapter Debugging Methods in your Debugging Guide.


COBATTR

Specifies non-standard behavior for HIGHLIGHT and LOWLIGHT clauses used with ACCEPT and DISPLAY statements. It provides compatibility with earlier COBOL products. You should avoid using it wherever possible as support might be discontinued at some future date.

Syntax:
COBATTR=n
export COBATTR
Parameters:
n A value in the range 0 through 7. It can be one of the following values, or a cumulative value; for example, specifying a value of 6 would result in the behavior described for values 4 and 2.
0 Provides standard, default behavior.

When a COBOL program displays text subject to a HIGHLIGHT or LOWLIGHT clause, the run-time system uses respectively the bold or dim mode specified in the terminfo entry for the terminal. If the bold or dim mode is not specified, then the HIGHLIGHT or LOWLIGHT clause respectively has no effect.

1 When a COBOL program displays text subject to a HIGHLIGHT clause, the run-time system uses the bold mode. The run-time system uses the default mode for normal text. Specifying dim mode in the terminfo entry for the terminal has no affect. The LOWLIGHT clause has no effect.
2 High and low intensity space characters are not assumed to be the same as normal mode space characters.
3 As for 1 and 2 above
4 Provides compatibility with default behavior of products before COBOL version 3.2.

When a COBOL program displays text subject to a HIGHLIGHT clause, the effect depends on whether the dim mode is specified in the terminfo entry for the terminal. If dim mode is specified, then the run-time system uses the default mode for highlighted text and the dim mode for normal text. If the dim mode is not specified, then the run-time system uses the bold mode for highlighted text and default mode for normal text. The LOWLIGHT clause has no effect, giving the same appearance as normal text.

See the chapter Terminfo Database and Terminal Devices for details on terminfo entries.

Example:
COBATTR=1
export COBATTR 

COBCONFIG

Specifies a run-time configuration file that tailors the run-time configurable options in some way. See the chapter Run-time Configuration for information on available run-time configurable options.

Syntax:
COBCONFIG=pathname
export COBCONFIG
Parameters:
pathname The name of the configuration file that tailors the run-time configurable options.
Example:
COBCONFIG=/home/mydir/cobconfig
export COBCONFIG 
Comments:

If $COBCONFIG is not set then the file $COBDIR/etc/cobconfig is searched for instead.


COBCPY

Specifies the directory or directories that the Compiler and Animator should search for copyfiles.

Syntax:
COBCPY=pathname[:pathname]...
export COBCPY
Parameters:
pathname A directory that the Compiler and Animator are to search when looking for copyfiles. When more than one pathname is present, a null pathname represents the current working directory.
Example:
COBCPY=/home/group/sharedcopy::mydir/mycpy
export COBCPY

causes the Compiler to search for a copyfile in /home/group/sharedcopy, then in the current directory and finally in ./mydir/mycpy until either the copyfile is found or it can be considered not found.


COBDATA

Specifies the directory or directories that the run-time system is to search for data files. Provides you with the facility to map data files globally, thus enabling you to put working data files in a directory whose name is not known until run time.

Syntax:
COBDATA=pathname[:pathname]...
export COBDATA
Parameters:
pathname A directory that the run-time system is to search when looking for application data files. When more than one pathname is present, a null pathname represents the current working directory.
Example:
COBDATA=:demo:/home/data:progs
export COBDATA

causes COBDATA to be set to instruct the run-time system to search for data files in the current directory, then in the directory ./demo, then in the directory /home/data and finally in ./progs.

Comments:

COBDATA affects the compiler and other utilities. During compilation, for example, program source is regarded as a data file by the compiler. If you intend to use any COBOL development system utilities, we recommend that the COBDATA value starts with a colon (:).

COBDATA is considered set if there is an environment variable of this name in your environment space, and its value is non-empty.

The full mapping order for files is:

  1. Any dd_ environment mappings

  2. Any ASSIGN TO EXTERNAL mappings

  3. Any COBDATA environment variable mappings

For multiple directory paths specified either in the COBDATA environment variable or a dd_ environment variable, the system searches the first directory specified followed by a slash (/) as a prefix to the user name.

If the filename is not found, or is not readable, the search continues with the next directory until the final directory has been searched. If no file is found, the first directory is used if a file is to be created.

Any dd_ and COBDATA mappings are ignored for any filename that starts with a hyphen (-) or a slash (/). In addition, it is illegal to have a hyphen in an environment variable name.

When using this facility, you should not use a filename that starts with "COB... "(these are reserved for the COBOL system).

You can use the COBDATA environment variable for files open in any mode (including OUTPUT) and for fixed or variable length files. If you are using indexed files, both the data and index files must be in the same directory.

The COBDATA environment variable affects file deletes, using the rules given here, as well as file opens.

If you intend to use COBOL development system programs, we recommend that you first unset COBDATA, as many of these programs open data files and are thus affected by the value of COBDATA. If you have to set COBDATA, you should include the paths :$COBDIR/dynload/helptbox.lbr and :$COBDIR/dynload/check.lbr at the beginning of the COBDATA value. If you want to see the Animator Help pages, also include $COBDIR/dynload/advanim.lbr.


COBDIR

Specifies the directory where the required Micro Focus COBOL system is installed. Many of the COBOL system components and utilities require and use this information. If the COBDIR environment variable is not set then the COBOL system acts as if it had been set to the default COBOL system directory. This default directory is /usr/lpp/cobol on AIX, or /opt/lib/cobol on other UNIX systems.

Syntax:
COBDIR=pathname
export COBDIR
Parameters:
pathname The directory that contains the required Micro Focus COBOL system software. The pathname must not exceed 51 characters in length.
Example:
COBDIR=/home/products/cobse20
export COBDIR

This causes the Cob utility to search the directory /home/products/cobse20 for the Micro Focus COBOL system software.

Comments:

The Micro Focus COBOL system is normally installed in the default COBOL system directory (see above) and so does not require COBDIR to be set. COBDIR only needs to be set when your COBOL system has been installed in a different directory such as when more than one version of the COBOL system is available at the same time.

See Also:

LD_LIBRARY_PATH
LIBPATH
PATH
SHLIB_PATH


COBIDY

Specifies the directory that Animator is to search for the information (.idy) file for the program being animated if it is not found in the same directory as the intermediate code (.int) file. Animator can update the information file to record information held between sessions. There is also a Compiler directive COBIDY; see the topic COBIDY for details.

Syntax:
COBIDY=pathname
export COBIDY
Parameters:
pathname The directory that Animator is to search.

COBEXTFHBUF

Specifies that fixed-length sequential files are buffered.

Syntax:
COBEXTFHBUF=buffer-size 
export COBEXTFHBUF
Parameters:
buffer-size The buffer size in bytes.

COBJVM

Specifies which Java Virtual Machine (JVM) to load.

Syntax:
COBJVM=platform_nnn 
export COBJVM
Parameters:
platform_nnn

platform is a three-character code that indicates the platform on which you are running Server Express, for example:

ibm IBM AIX
unx SCO UnixWare
sun Sun SPARC

nnn indicates the version of the JVM, for example:

122 Version 1.2.2
130 Version 1.3.0
Comments:

You might need to set COBJVM if you are developing distributed applications with both COBOL and Java components. For further information see the section Setting up the COBOL and Java Environments in the chapter Before You Start in your Distributed Computing book.

Examples:
COBJVM=ibm_122
export COBJVM

COBKEYTIMEOUT

Specifies the maximum elapsed time, in tenths of a second, for the connected terminal to transmit any valid escape sequence to the run-time system.

When a terminal key is depressed, the terminal might send in response a single character or a group of characters to the run-time system. Typically, such a group of characters starts with an escape character and the group of characters is known as an escape sequence. A terminal might send an escape sequence for one depression of a function key. It might also send the same sequence of characters for a depression of the Escape key followed by the depression of one or more alphabetic or numeric data keys. The only difference apparent to the run-time system is the interval between the arrival of each character; the user cannot type as fast as the escape sequence is generated by the terminal.

If a terminal is connected over a network that sends the characters to the run-time system in discrete packets, then the network can alter the intervals between each character arriving at the run-time system. COBKEYTIMEOUT is available to help compensate for typical network delays so the run-time system identifies escape sequences correctly.

Syntax:
COBKEYTIMEOUT=n 
export COBKEYTIMEOUT
Parameters:
n A number in the range 1 through 126 that represents the maximum elapsed time required for a terminal to transmit any valid escape sequence to the run-time system over the line or network connection. On encountering a lone Escape character, the run-time system waits n tenths of a second before assuming that the character does not introduce an escape sequence. The run-time system calculates an appropriate default value for n from the baud rate of the terminal.

COBMAINSTACK

Specifies the size of the main stack.

Syntax:
COBMAINSTACK=n 
export COBMAINSTACK
Parameters:
n A number in the range 1 through nnn that represents the size of the main stack.
Comments:

You might need to set COBMAINSTACK in any of the following circumstances:

Examples:
COBMAINSTACK=262144
export COBMAINSTACK

COBOPT

Specifies user default options to the Cob utility.

Syntax:
COBOPT="[set environment-variable=value]
[options] ...
[cobextn: .ext [.ext] ... ]"
export COBOPT

or:

COBOPT=[pathname/]filename
export COBOPT
Parameters:
environment-variable Any one of the environment variables supported by the COBOL system and listed in this appendix.
value The value to which you want to set the specified environment variable.
options One or more cob command line options. See the chapter COBOL System Interface (cob) for details on the format of cob options.
.ext A filename extension that, in addition to the standard ones of .cob, .CBL, or .cbl, denotes a file that Cob should treat as a COBOL source file. The extension must begin with a period, and if more than one is specified on one line then they must be separated by a space or tab character. You can use more than one cobextn line.
pathname The directory that the COBOL system is to search for an options file.
filename The name of a file containing cob options.

If a line does not begin with one of the identifiers set or cobextn: then it is taken as an options line.

Comments:

COBOPT can either contain options that supplement or override the system default options defined in $COBDIR/etc/cobopt, or it can specify the path of a file that contains such options. The options can extend over more than one line and each line must have the same format as described for the file $COBDIR/etc/cobopt in the chapter COBOL System Interface (cob).

Examples:
COBOPT="-C ANS85
set COBCPY=$COBDIR/srclib/:$HOME/mylib:"
export COBOPT

This enables ANSI'85 standard COBOL syntax and sets COBCPY to the specified list of paths.

COBOPT=temp/options

Specifies that cob options are contained in the file options in the directory temp.


COBPATH

Specifies the directory or directories that the run-time system is to search for dynamically loadable .int and .gnt files, or callable shared objects.

Syntax:
COBPATH=pathname[:pathname]...
export COBPATH
Parameters:
pathname The directory that the run-time system is to search for a dynamically loadable program (.int, .gnt or callable shared object) file. When more than one pathname is specified, a null pathname represents the current working directory.
Example:
COBPATH=u:/home/mydir/srclib:otherlib
export COBPATH 
See Also:

program_search_order run-time tunable.


COBPRINTER

Specifies the name of a print spooler that is to receive, via its standard input stream (stdin), output from any DISPLAY UPON PRINTER statement.

Syntax:
COBPRINTER=command-line
export COBPRINTER
Parameters:
command-line A command line supported by your system and that can be executed by the system shell. Typically, it is simply the name of a print spooler or other executable, but if the shell is escaped when setting the value then any command-line arguments can be used.
Example:
COBPRINTER="myspooler -a $TMPDIR/spoolfile"
export COBPRINTER
Comments:

Each DISPLAY UPON PRINTER statement executed by your COBOL program causes a new invocation of command-line. Each invocation receives the data referenced in the DISPLAY statement, and is followed by a system end-of-file condition.


COBSES

Specifies the UNIX Session Recorder functions you want to perform.

Syntax:
COBSES={option[filename]}...
export COBSES
Parameters:
option One or more of the following flags:

-a Include keystrokes made to and screen output from the Animator
-f Play back recording in fast forward mode
-p Play back recording at normal speed
-r Record keystrokes
-s Record screen output
-t Indicate terminal number for multi-user screen recordings

These flags are all case sensitive. Also, you cannot combine the -r flag with either the -f or -p flag.

You can find more information about these options in the section Using the UNIX Session Recorder with Animator in the chapter UNIX Session Recorder in your Utilities Guide.

filename The name of the file that you require; it is subject to the rules given in the section Session Filenames in the chapter UNIX Session Recorder in your Utilities Guide.
Comments:

For detailed information on the UNIX Session Recorder and the COBSES environment variable, see the chapter UNIX Session Recorder in your Utilities Guide.


Warning: You must unset COBSES when you have finished using the UNIX Session Recorder, or it will interfere with the running of your COBOL programs. To do this, set COBSES to spaces, then export this setting to the shell.



COBSW

Specifies run-time system switch settings for the run-time system to observe when running an application.

Syntax:

export COBSW
Parameters:
Enables (+) or disables (-) the switch s, which is one of the switches described in the chapter Descriptions of Run-time Switches.
Example:
COBSW=+0+D
export COBSW

This enables run-time switch 0 and the ANSI COBOL debug switch.


COBTERMINFO

Specifies the directory or directories to be searched by the run-time system for a terminfo database of terminal information tailored to the needs of COBOL applications. This enables COBOL applications to use different terminfo settings to those used by non-COBOL applications, such as vi, when using the same terminal.

Syntax:
COBTERMINFO=pathname[:pathname]...
export COBTERMINFO
Parameters:
pathname A directory that identifies a terminfo database that contains terminal settings tailored for COBOL applications. A null pathname represents the current working directory.
Comments:

The COBOL system takes the value of the standard UNIX environment variable TERM as the name of the terminal in use. It uses this to search for the appropriate terminal information in a terminfo database. The run-time system first searches the databases identified in COBTERMINFO and then, if the terminal information is not found it searches the database identified in the standard UNIX environment variable TERMINFO.

If COBTERMINFO is not set, the run-time system acts as if it had been set to $COBDIR/terminfo.

We recommend that the first directory listed in COBTERMINFO is $COBDIR/terminfo so that the terminfo database supplied with this COBOL system is found first. For commonly used terminals this terminfo contains settings that are fuller and more appropriate to COBOL than those normally available in the UNIX system terminfo database. When debugging using Animator COBTERMINFO must be set to $COBDIR/terminfo.

COBTERMINFO can also be used to identify a terminfo database that is portable between UNIX systems. Such a database conforms to the standard UNIX database format but does not include any supplementary, UNIX implementation-dependent terminal information. Many UNIX system terminfo databases are not portable because they include such supplementary information. The COBOL system ignores any such non-portable details. See the chapter Terminfo Database and Terminal Devices for further details on using the terminfo database.

Example:
COBTERMINFO=$COBDIR/terminfo:/home/mydir/terms
export COBTERMINFO
See Also:

TERM
TERMINFO


COLUMNS

Specifies the column width of the terminal screen or window, overriding the specified terminal default.

Syntax:
COLUMNS=n
export COLUMNS
Parameters:
n The width of the terminal screen or window, in column positions.
Example:
COLUMNS=100
export COLUMNS
Comments:

The default, when COLUMNS is unset or null, is to use the cols value defined in the specified terminal's terminfo entry, or the current width of the terminal window if you are using an X terminal. See the chapter Terminfo Database and Terminal Devices for further details on using the terminfo database. The terminal type is specified using the standard UNIX environment variable, TERM.

On non-windowing environments, where the terminal screen area cannot be resized, the COLUMNS values does not need to be set. Terminals that can switch into a wide mode (usually from 80 through 132 columns) have a terminal name ending in "-w" and these are automatically supported, without the need to set COLUMNS.

In windowing environments, where the size of windows can be changed, the initial size of the window is used in preference to the cols value in terminfo. When the window is resized, the new size is reread. If the new size is greater than the initial size then the extra columns might not be used.

If you want to use the full width of the window you might need to set COLUMNS to the current column width of the window on some platforms.

Using COLUMNS values that do not correspond to the actual width of the window produces unexpected results.

Most system software, for example sde, does not function correctly using widths of more or less than 80 columns. Adis functions correctly with any screen size.

See Also:

TERM
LINES


EXTFH

Specifies a configuration file to be used by the File Handler.

Syntax:
EXTFH=filename.cfg 
export EXTFH
Parameters:
filename.cfg The name of the configuration file
Example:
EXTFH=/home/mydir/myconfig.cfg
export EXTFH
Comments:

See the chapter File Handler API in your File Handling book for more details.


FHREDIR

Specifies a configuration file to be used by the Fileshare Client.

Syntax:
FHREDIR=filename.cfg 
export FHREDIR
Parameters:
filename.cfg The name of the configuration file
Example:
FHREDIR=/home/mydir/myconfig.cfg
export FHREDIR
Comments:

See your Fileshare Guide for more details.


FS

Specifies a configuration file to be used by the Fileshare Server.

Syntax:
FS=filename.cfg 
export FS
Parameters:
filename.cfg The name of the configuration file
Example:
FS=myconfig.cfg
export FS
Comments:

See your Fileshare Guide for more details.


FSCOMMS

Specifies that the Fileshare System is to run in single user mode.

Syntax:
FSCOMMS="\$local" 
export FSCOMMS
Parameters:
"\$local" Run the Fileshare System in single user mode.
Comments:

See your Fileshare Guide for more details.


GNTANLZ

Specifies a configuration file for use by the GNT Analyzer utility.

Syntax:
GNTANLZ="filename" 
export GNTANLZ
Parameters:
filename The name of the configuration file.
Comments:

The configuration file specifies the GNT Analyzer options to be used for a file at run time. A default configuration file called gntanlz.cfg is supplied with the GNT Analyzer. For more information on GNT Analyzer and the configuration file, see the chapter GNT Analyzer in your Utilities Guide.


HCOBND

Specifies a directory to be used for bind files generated by the DB2 External Compiler Module (ECM).

Syntax:
HCOBND=pathname
export HCOBND
Parameters:
pathname The directory that the DB2 ECM is to use to store bind files
Comments:

The DB2 ECM uses the specified directory until the variable is unset or reset to a different directory. The DB2 Compiler directive option BIND overrides this environment variable.


LANG

Defines the locale.

Syntax:
LANG=language[_territory[.codepage]]
export LANG
Parameters:
language The language in which your program is to run.
_ (underscore) The delimiter for language and territory, if territory is specified.
territory The country in which your program is to run.
. (period) The delimiter for territory and codepage, if codepage is specified.
codepage The character set to use for your program.
Example:
LANG=fr_FR
export LANG
Comments:

For a full description of this environment variable, see the chapter Internationalization Support in your Program Development book.


LD_LIBRARY_PATH

Specifies the directory or directories for the UNIX system, Cob and the run-time system to search for shared libraries and callable shared objects. It must be set to include $COBDIR/lib on all platforms, except AIX , which uses a different environment variable. It should also include any directories that contain callable shared objects used by your application.

Syntax:
LD_LIBRARY_PATH=pathname[:pathname]...
export LD_LIBRARY_PATH
Parameters:
pathname A directory to be searched for shared libraries.
Comments:

The list of directories must include $COBDIR/lib. The COBDIR environment variable is described earlier in this appendix.

On HP-UX systems LD_LIBRARY_PATH must be set to the same value as the SHLIB_PATH environment variable. Setting SHLIB_PATH and LD_LIBRARY_PATH to different values could have undefined results.

This environment variable is a system environment variable; see your UNIX documentation for more information.

Example:
LD_LIBRARY_PATH=$COBDIR/lib:/home/mydir/myapp:$LD_LIBRARY_PATH 
export LD_LIBRARY_PATH
See Also:

COBDIR
SHLIB_PATH
LIBPATH


LIBLIST

The COBOL system file $COBDIR/lib/liblist contains the list of libraries to be used by the Cob utility when it produces executable program files. LIBLIST specifies an alternative file for Cob to use; you should should not use it unless a Technical Support representative asks you to.

Syntax:
LIBLIST=pathname
export LIBLIST
Parameters:
pathname The full pathname of the alternate file containing the user default library list to be used instead of $COBDIR/lib/liblist.

LIBPATH

Specifies the directory or directories for the UNIX system, Cob and the run-time system to search for shared libraries and callable shared objects. It is only available on AIX-based systems and must be set to include $COBDIR/lib. It should also include any directories that contain callable shared objects used by your application.

Syntax:
LIBPATH=pathname[:pathname]...
export LIBPATH
Parameters:
pathname A directory to search for shared libraries.
Comments:

The list of directories must include $COBDIR/lib. The COBDIR environment variable is described earlier in this appendix. See the AIX documentation for more information.

Example:
LIBPATH=$COBDIR/lib:/lib:/usr/lib 
See Also:

COBDIR
LD_LIBRARY_PATH
SHLIB_PATH


LINES

Specifies the depth of the terminal screen or window, overriding the specified terminal default.

Syntax:
LINES=n
export LINES
Parameters:
n The depth of the terminal screen or window, in lines.
Example:
LINES=50
export LINES
Comments:

The default, when LINES is unset or null, is to use the lines value as defined in the specified terminal's terminfo entry, or the current depth of the terminal window if you are using X windows. See the chapter Terminfo Database and Terminal Devices for further details on using the terminfo database. The terminal type is specified via the standard UNIX environment variable, TERM.

On non-windowing environments, where the terminal screen area cannot be resized, the LINES values does not need to be set.

In windowing environments, where the size of windows can be changed, the initial size of the window is used in preference to the lines value in terminfo. When the window is resized, the new size is reread. If the new size is greater than the initial size then the extra lines might not be used.

If you want to use the full depth of the window you might need to set LINES to the current depth of the window on some platforms.

Using LINES values that do not correspond to the actual depth of the window produces unexpected results.

See Also:

TERM
COLUMNS


MFCSCFG

Specifies a configuration file to be used by the Client/Server Binding client program.

Syntax:
MFCSCFG=filename 
export MFCSCFG
Parameters:
filename The name of the configuration file
Example:
MFCSCFG=/home/mydir/mfclisrv.cfg
export MFCSCFG
Comments:

See the chapter Client/Server Binding in your Distributed Computing book for more details.


MFCODESET

Specifies which ASCII/EBCDIC translation table to use.

Syntax:
MFCODESET=nnnn
export MFCODESET
Parameters:
nnnn A value from 2000 through 9999 that indicates the required translation table. Values below 2000 are reserved for Micro Focus use.
Example:
MFCODESET=2001
export MFCODESET
Comments:

You can modify _CODESET so that it uses ASCII/EBCDIC translation table that you have created. The value you supply to MFCODESET specifies which translation table to use.

See Also:

Configuring CODESET with the Codecomp Utility in the chapter Internationalization Support in your Program Development book.


MFLOGDIR

Specifies a directory to be used by Client/Server Binding for log files.

Syntax:
MFLOGDIR=dirname 
export MFLOGDIR
Parameters:
dirname The name of the directory for log files
Example:
MFLOGDIR=/home/mydir/logs
export MFLOGDIR
Comments:

See the chapter Client/Server Binding in your Distributed Computing book for more details.


PATH

Specifies the directories to be searched by all UNIX programs, including the run-time system, when finding executables to be run.

Syntax:
PATH=pathname[:pathname]...
export PATH
Parameters:
pathname A directory to search for executables.
Comments:

The list of directories should include $COBDIR/bin. The COBDIR environment variable is described earlier in this appendix.

Example:
PATH=$COBDIR/bin:$PATH
export PATH
See Also:

COBDIR
LD_LIBRARY_PATH
LIBPATH
SHLIB_PATH


SHLIB_PATH

Specifies the directory or directories for the UNIX system, Cob and the run-time system to search for shared libraries and callable shared objects. It is only available on HP-UX and must be set to include $COBDIR/lib. It should also include any directories that contain callable shared objects used by your application.

Syntax:
SHLIB_PATH=pathname[:pathname]...
export SHLIB_PATH
Parameters:
pathname A directory to search for shared libraries.
Comments:

The list of directories should include $COBDIR/lib. The COBDIR environment variable is described earlier in this appendix.

On HP-UX systems SHLIB_PATH must be set to the same value as the LD_LIBRARY_PATH environment variable. Setting SHLIB_PATH and LD_LIBRARY_PATH to different values could have undefined results.

See your HP-UX documentation for more information.

Example:
SHLIB_PATH=$COBDIR/lib:/home/mydir/myapp:$SHLIB_PATH
export SHLIB_PATH
See Also:

COBDIR
LD_LIBRARY_PATH
LIBPATH


SORTCOMPRESS

Specifies that a compression routine should be executed on each record to be sorted.

Syntax:
SORTCOMPRESS=5
export SORTCOMPRESS
Parameters:
5 (This is the only value you can supply.) Indicates that single repeated characters should be compressed for the purposes of the sort operation.
Comments:

This variable is recommended if the sort records contain many single repeated characters, for example, multiple spaces, as it can be very effective in improving memory usage and therefore sort performance.

Example:
SORTCOMPRESS=5
export SORTCOMPRESS
See Also:

SORTSPACE


SORTSPACE

Specifies the amount of memory to be allocated to internal workspace for SORT operations.

Syntax:
SORTSPACE=n[K|k|M|m|G|g]
export SORTSPACE
Parameters:
n[K|k|M|m|G|g] The amount of memory to be allocated to internal workspace for SORT operations. K or k indicates kilobytes, M or m indicates megabytes and G or g indicates gigabytes. No letter indicates bytes. Defaults to 1 megabyte.
Comments:

A larger value for SORTSPACE will generally result in a faster sort. However, if you specify a value that exceeds the capacity of main memory in your computer, such that the operating system has to page memory in and out, performance will be degraded.

Example:
SORTSPACE=1024K
export SORTSPACE
See Also:

SORTCOMPRESS


TERM

Defines the type of terminal being used.

Syntax:
TERM=name
export TERM
Parameters:
name The name of the terminal in the terminfo database.
Example:
TERM=at386
export TERM
See Also:

COBTERMINFO
TERMINFO
LINES
COLUMNS
Terminfo Database and Terminal Devices


TERMINFO

Specifies the directory to be searched by all UNIX programs, including the run-time system, for the UNIX system terminfo database.

Syntax:
TERMINFO=pathname
export TERMINFO
Parameters:
pathname The name of a directory that contains the UNIX system terminfo database.
Comments:

The UNIX system terminfo database is used by all UNIX applications that need to use a terminal. However, COBOL applications tend to make much fuller and sophisticated use of the terminal and require a fuller terminfo description than is required by typical UNIX applications such as vi. Some terminal capabilities, such as those set during the initialization of the terminal to control the use of function keys, commonly conflict with the needs of typical COBOL applications. In such cases, the terminal information required by COBOL can be stored in a separate terminfo database and referenced using COBTERMINFO as described earlier in this appendix.

See Also:

COBTERMINFO
TERM
Terminfo Database and Terminal Devices


TMPDIR

Specifies a directory in which to store temporary files in place of the UNIX system default.

Syntax:
TMPDIR=pathname
export TMPDIR
Parameters:
pathname The directory used by UNIX applications for any temporary work files. Temporary work files can be created by COBOL utilities such as Cob or by the run-time system when it executes statements such as SORT. If you do not specify a directory, the system default directory is used.
Comments:

You might need to use this environment variable if the run-time system needs to page data to disk when creating heaps or sorting.



Copyright © 2003 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.