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
UNIX:
COBDATA=pathname[:pathname]...
export COBDATA
Windows:
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
UNIX:
COBDATA=:demo:/home/data:progs
export COBDATA
Windows:
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
Enables or disables database file handler support. This is required if your data files are stored in a datastore, or your enterprise server region stores some of its resources in a database; see Micro Focus Native Database File Handling and Enterprise Server Region Database Management for more information.
Syntax
UNIX:
ES_DB_FH=value
export ES_DB_FH
Windows:
SET ES_DB_FH=value
Values
Default
Database file handler support is disabled.
Specify the name of the database server to be used for region database operations.
There also needs to be a corresponding <server> entry for the database server within the configuration file specified by the MFDBFH_CONFIG environment variable. <dsn> entries for the region, cross-region and master databases must also be specified in the configuration file to enable use of region database operations.
Syntax
UNIX:
ES_DB_SERVER=server-instance
export ES_DB_SERVER
Windows:
SET ES_DB_SERVER=server-instance
Values
server-instance is the name of a valid database server instance. For example, set ES_DB_SERVER=(local)\SQLEXPRESS.
Default
Not set.
Using the example above, you would be required to have something similar to that below in your database configuration file:
<?xml version="1.0" encoding="utf-8"?>
<datastores usevault="false">
<server name="(local)\SQLEXPRESS" type="sqlserver" access="odbc">
<dsn name="SS.MYMASTER" type="database" dbname="master"/>
<dsn name="SS.CAS.ESDEMO" type="region.cas" region="ESDEMO" feature="all"/>
<dsn name="SS.CAS.CROSSREGION" type="crossregion.cas"/>
</server>
</datastores>
Specifies the region database that is to process resource locking (step- and system-scoped ENQs) for an enterprise server within a cluster, where resources (such as spool queues and catalogs) are deployed to a database.
Syntax
UNIX:
ES_LOCKDB=region-db
export ES_LOCKDB
Windows:
SET ES_LOCKDB=region-db
Parameters
Syntax
UNIX:
ES_RLS_FILE_SUPPORT=value
export ES_RLS_FILE_SUPPORT
Windows:
SET ES_RLS_FILE_SUPPORT=value
Values
Default
RLS file support is off.
Syntax
Windows:
SET EXTFH=filename.cfg
UNIX:
EXTFH=filename.cfg
export EXTFH
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET EXTFH=/home/mydir/myconfig.cfg
UNIX:
EXTFH=/home/mydir/myconfig.cfg
export EXTFH
Syntax
Windows:
SET FHREDIR=filename.cfg
UNIX:
FHREDIR=filename.cfg
export FHREDIR
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET FHREDIR=/home/mydir/myconfig.cfg
UNIX:
FHREDIR=/home/mydir/myconfig.cfg
export FHREDIR
Specifies a configuration file to be used by the Fileshare Server.
Syntax
Windows:
SET FS=filename.cfg
UNIX:
FS=filename.cfg
export FS
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET FS=myconfig.cfg
UNIX:
FS=myconfig.cfg
export FS
Syntax
Windows:
SET FSCOMMS="\$local"
UNIX:
FSCOMMS="\$local"
export FSCOMMS
Parameters
"\$local" Run the Fileshare System in single user mode.
Syntax
Windows:
SET HCOBND=pathname
Windows:
HCOBND=pathname
export HCOBND
Parameters
pathname The directory that the DB2 ECM is to use to store bind files.
Example
SET HCOBND=d:\mydir\binds
SET HCOBND=/mydir/binds export HCOBND
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.
For EBCDIC datasets, translates from EBCDIC to ASCII using a PUT, and ASCII to EBCDIC using a GET.
Syntax
MFFTP_ASCII_CMD_XLATE={Y|N}
Comments
When set to Y, must be used with TYPE A or ASCII sub command.
Specifies the location and the name of the configuration file that defines the database server instances and associated databases.
Syntax
UNIX:
MFDBFH_CONFIG=value
export MFDBFH_CONFIG
Windows:
SET MFDBFH_CONFIG=value
Values
value represents the full path and filename of your database configuration file.
Default
Not set.
Specifies the type of record locking that it is to be used when the database file handler is in effect.
Syntax
UNIX:
MFDBFH_RECORD_LOCKING=table|database
export MFDBFH_RECORD_LOCKING
Windows:
SET MFDBFH_RECORD_LOCKING=table|database
Paramaters
Default
Specifies the location of the scripts and stored procedures required when the database file handler is in effect.
Syntax
UNIX:
MFDBFH_SCRIPT_DIR=value
export MFDBFH_SCRIPT_DIR
Windows:
SET MFDBFH_SCRIPT_DIR=value
Values
value represents a path to the directory containing the required resources.
Default
value defaults to the \etc\mfdbfh\scripts sub directory of your product installation directory.
For more information on secrets vaults, see Vault Facility.
Syntax
UNIX:
MFDBFH_VAULT=value
export MFDBFH_VAULT
Windows:
SET MFDBFH_VAULT=value
Values
value represents the name of a vault.
Default
Not set.
Syntax:
strictvsam=ON|OFF
Parameters:
Properties:
| Default: | OFF |
| IDE equivalent: | None |
Syntax:
SET XFHLOG=DEFAULT
Parameters:
DEFAULT - generates the log file in the current directory.
Comments:
If the XFHLOG variable is not set, the log file is created in C:\ProgramData\Micro Focus\File Handler\[version-number].
where [version-number] represents the version of your Micro Focus product.
The effect of this variable can be overridden by the LOGFILENAME configuration option.