COBDATA=path-name[[:path-name][...]]
COBDATA 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.
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.
The following 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.
COBDATA=:demo:/home/data:progs
DB2DBDFT=path-name/database-name
ES_DB_FH={[Y|true]|[N|false]}
ES_DB_FH=N
ES_DB_SERVER=server-instance
ES_DB_SERVER=MYSERVER
In this example, your database configuration file would need to contain something similar to the following:
<datastores usevault="false">
<server name="MYSERVER" 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>
ES_LOCKDB=region-db
ES_RLS_FILE_SUPPORT=Y
Parameter values are not case sensitive.
EXTFH=file-name.cfg
EXTFH=/home/mydir/myconfig.cfg
FHREDIR=[path-name/]prefix.cfg}
FHREDIR=/home/mydir/myconfig.cfg
FS=file-name.cfg
FS=fs.cfg
FS=myfsconf.cfg
FSCOMMS="\$local"
LIB=path-name
MFDBFH_CONFIG=path-name/file-name
Specifies the type of record locking that it is to be used when the database file handler is in effect.
MFDBFH_RECORD_LOCKING={table|database}
MFDBFH_RECORD_LOCKING=table
MFDBFH_SCRIPT_DIR=path-name
MFDBFH_SCRIPT_DIR=$COBDIR/etc/mfdbfh/scripts
MFDBFH_VAULT=vault-name
TXFILEP={path-name|datastore-location}