This topic lists environment variables that relate to configuring the file and dataset handling.
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
COBDATA=pathname[:pathname]...
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:
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.
Example
COBDATA=:demo:/home/data:progs export COBDATA
SET COBDATA=:demo:/home/data:progs
causes COBDATA to be set to instruct the runtime 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.
Values
Syntax
ES_RLS_FILE_SUPPORT=value export ES_RLS_FILE_SUPPORT
SET ES_RLS_FILE_SUPPORT=value
Values
Default
RLS file support is off.
Syntax
SET EXTFH=filename.cfg
EXTFH=filename.cfg export EXTFH
Parameters
filename.cgf The name of the configuration file.
Example
SET EXTFH=/home/mydir/myconfig.cfg
EXTFH=/home/mydir/myconfig.cfg export EXTFH
Syntax
SET FHREDIR=filename.cfg
FHREDIR=filename.cfg export FHREDIR
Parameters
filename.cfg The name of the configuration file.
Example
SET FHREDIR=/home/mydir/myconfig.cfg
FHREDIR=/home/mydir/myconfig.cfg export FHREDIR
Specifies a configuration file to be used by the Fileshare Server.
Syntax
SET FS=filename.cfg
FS=filename.cfg export FS
Parameters
filename.cfg The name of the configuration file.
Example
SET FS=myconfig.cfg
FS=myconfig.cfg export FS
Syntax
SET FSCOMMS="\$local"
FSCOMMS="\$local" export FSCOMMS
Parameters
"\$local" Run the Fileshare System in single user mode.
Syntax
SET HCOBND=pathname
HCOBND=pathname export HCOBND
Parameters
pathname The directory that the DB2 ECM is to use to store bind files.
Example
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.