CCITCP2=host-name
CCITRACE={/|-}{F|P|D}[...]
CCITRACE=/F/D
CASRDO44_NEWSUB={ON|OFF}
CASRDO44_NEWSUB=ON
COB_LIVE_RECORD=[path-name/]file-prefix
Animator can update the information file to record information held between sessions.
COB_LIVE_RECORD_SIZE=mem-size
COB_LIVE_RECORD_SIZE=268
When the limit is reached, the buffer is cycled so that the oldest events are removed to make space for the most recent events.
An adequate range for 32-bit systems is between 500 and 1000.
You might need to experiment to determine the most optimal setting
COB_LIVE_RECORD_SIZE=756
COBAIF=path-name[:path-name[...]]
Animator can update the session file to record information held between sessions.
The .aif file contains details of breakpoints and monitors.
COBAIFNAME=base-name
The .aif file contains details of breakpoints and monitors.
COBANIMOPT=directive-name[:directive-name[...]]
COBANIMOPT=MIXEDLANGDEBUG:MULTITHREAD
COBANIMSRV=prog-id
export COBANIMSRV=myid
myid is now a unique identifier that you can use to match Character Animator to a program. Type the command to start Character Animator:
cobanimsrv
The Character 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 Character Animator; therefore, Character Animator attaches to this process. In console session 1, the Character Animator main screen is displayed and the cursor placed on the first line of prog1.int.
COBATTR={0|1|2|3|4|5|6|7}
COBATTR=0
COBATTR=1
COBCONFIG=path-name
COBCONFIG=/home/mydir/cobconfig
COBCPY=path-name[[:path-name][...]]
COBCPY=%COBCPY%;C:\Program Files (x86)\Micro Focus\Enterprise Developer\cpylib; C:\Program Files (x86)\Micro Focus\Enterprise Developer\cpylib\basecl; C:\Program Files (x86)\Micro Focus\Enterprise Developer\cpylibguicl; C:\Program Files (x86)\Micro Focus\Enterprise Developer\cpylibolecl
The following causes the Compiler to search for a copybook in /home/group/sharedcopy, then in the current directory, and finally in ./mydir/mycpy until either the copybook is found or it can be considered not found.
COBCPY=/home/group/sharedcopy:.:mydir/mycpy
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
COBDIR=path-name
This example causes the compiler to search the directory /home/products/cobse20 for the Micro Focus COBOL system software.
COBDIR=/home/products/cobse20
COBIDY=path-name[:path-name[...]]
COBKEYTIMEOUT=trans-time
The run-time system calculates an appropriate default value for n from the baud rate of the terminal.
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.
COBLPFORM line-number[[:line-number][...]]
In the following example, C01 equals 1, C02 equals 3, and so on:
COBLPFORM 1:3:5:7:9:11:13:15:17:19:21:23
In this next example, C01 equals 3, C02 equals 5, C03 equals 1, and C04 equals 9. C03 equals 1 because its value is a space and therefore undefined, and channels C05 - C12 are also undefined:
COBLPFORM :3::5: :9
COBMAINSTACK=stack-size
You might need to set COBMAINSTACK in any of the following circumstances:
COBMODE={32|64};
COBMODE=32;
COBOPT="[set environment-variable=parameter] [option[...]] [[cobextn: .ext [.ext]][...]]"
or
COBOPT=[path-name/]file-name
If a line does not begin with one of the identifiers set or cobextn: then it is taken as an options line.
This example enables ANSI 85 standard COBOL syntax and sets COBCPY to the specified list of paths.
COBOPT="CANS85 set COBCPY=$COBDIR/srclib/:$HOME/mylib:" export COBOPT
This next example specifies that cob options are contained in the file options in the temp directory:
export COBOPT=temp/options
COBPATH=path-name[:path[...]]
When more than one path-name is specified, a null path name represents the current working directory.
COBPATH=/home/mydir/srclib:otherlib
COBPRINTER="command-line"
COBPRINTER="myspooler -a $TMPDIR/spoolfile"
COBSES={option}[[:option][...]]
| -a | Include keystrokes made to and screen output from the Animator |
| -f file-name | Play back recording in file-name in fast forward mode |
| -p file-name | Play back recording in file-name at normal speed |
| -r file-name1 | Record keystrokes in file-name |
| -s file-name | Record screen output in file-name |
| -t terminal-number | Terminal number for multi-user screen recordings |
| 1 Do not combine with either -f or -p. | |
COBTERMINFO=path-name[[:path-name][...]]
COBTERMINFO=$COBDIR/terminfo
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.
Micro Focus recommends 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 nonportable details.
COBTERMINFO=$COBDIR/terminfo:/home/mydir/terms
COBSW={+|-}switch[...]
COBSW=-A
COBSW=+0+D
COLUMNS=number-of-columns
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.
COLUMNS=100
ENTRYNAMEMAP={file-name|directory}[:...]
ES_CAS_API=ON
ES_JES_ENFORCE_EXPIRE_DATE={Y|N}
ES_JES_ENFORCE_EXPIRE_DATE=Y
ES_JES_LEVEL={VSE|JES2|JES3}
ES_JES_LEVEL=JES2
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"
HCOBND=path-name
HCOBND=/mydir/binds
ES_JES_LISTCAT_YMD={Y|N}
ES_JES_LISTCAT_YMD=N
LANG=unix-language[_territory[.code-page]]
| Value | Language |
|---|---|
| en_US | US English |
| en_GB | UK English |
| jp_JP | Japanese (EUC encoding) |
| jp_JP.sjis | Japanese (Shift-JIS encoding) |
| jp_JP.utf8 | Japanese (UTF8 encoding) |
LANG=fr_FR
LD_LIBRARY_PATH={$COBDIR/lib|path-name}[:path-name[...]]
If you have installed the product to a directory other than the default, you must set this variable, and include $COBDIR/lib on all platforms except AIX (which uses LIBPATH). It should also include any directories that contain callable shared objects used by your application.
If you have installed the product in the default directory (/opt/microfocus/EnterpriseDeveloper), you do not need to set this variable.
LD_LIBRARY_PATH=$COBDIR/lib:/home/mydir/myapp:$LD_LIBRARY_PATH
LIBPATH={$COBDIR/lib|path-name}[:path-name[...]]
If you have installed the product in the default directory (/opt/microfocus/EnterpriseDeveloper), you do not need to set this variable.
LIBPATH=$COBDIR/lib:/lib:/usr/lib
LINES=line-depth
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.
LINES=50
MAINFRAME_FLOATING_POINT={true|false}
MAINFRAME_FLOATING_POINT=false
MFCODESET=country-code
MFCSCFG=[path-name/]file-name
MFCSCFG=mfclisrv.cfgThe default path-name is the current working directory, and if not found, the default settings for the configuration entries are used.
MFCSCFG=/home/mydir/mfclisrv.cfg
MFJSERET=ABEND
MFJSTATS={ON|OFF|switch}
MFJSTATS=OFF
MFLECONFIG=path-name/file-name
MFLOGDIR=path-name
MFLOGDIR=/home/mydir/logs
PATH=path-name[;[path-name][...]]
PATH=u:/home/mydir/srclib:otherlib
SORTCOMPRESS={0|1}
SORTCOMPRESS=0
Use this variable to improve memory usage and therefore sort performance when the sort records contain many single, repeated characters; for example, multiple spaces.
The behavior when set to any positive integer is equivalent to SORTCOMPRESS=1.
SORTSCHEME=1
SORTSPACE=memory-spec[K|M|G]
SORTSPACE=1M
Parameter values are not case sensitive.
SORTSPACE=1024K
SORTTEMPSPACE=memory-spec[K|M|G]
SORTTEMPSPACE=32M
Parameter values are not case sensitive.
SORTTEMPSPACE=250M
TERM=term-type-name
TERM=at386
TERMINFO=path-name
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.
TMPDIR=path-name
You might need to use this environment variable if the run-time system needs to page data to disk when creating heaps or sorting.