Syntax
SET CASSPOOL_LOCK_RETRY_COUNT=count
Values
count The number of retries made to obtain a record lock.
Default
If not specified, this variable defaults to 20.
Allows the specification, in tenths of seconds, of the maximum time out period that will be used with any LSC style application, such as Drag and Drop, SourceConnect, or the Monitor. The maximum value that can be used is 2,147,483,647.
Syntax
SET CCITIMEOUT=value
Default
The default is 1200 (2 minutes).
ExampleSET CCITIMEOUT=2400
Syntax
set CCITCP2=hostname
Parameters
hostname is the TCP hostname or dotted decimal IP address of the machine running the CCITCP2 daemon you wish to contact from that session.
Comments
The environment variable value will always take precedence over any value set using the Configuration Utility. To restore a process to using the value set by the Configuration Utility simply set the environment variable to an empty string, such as
set CCITCP2=
Alternatively, if this environment variable is set system-wide (by creating a system variable in the system environment settings, or by using a CONFIG.SYS file) then this value will always take precedence over any value set using the Configuration Utility.
Syntax
set CCITCP2_PORT=port
Syntax
set CCITCPS_server_name=port
Parameters
Note that this will only work if the server application process is started in the same session or process that has this environment variable set.
Example
set CCITCPS_server_name=MFPORT:3000
If a client is known to be trying to connect to a server with Server Name server_name, and the TCP address and port (e.g. 3000) that the server is using is known, then the client can be made to connect directly to it by setting this environment variable.
Syntax
CCITCPT_server_name=MFNODE:server_hostname,MFPORT:port_number
Note that this can be used instead of setting the client Machine Name value. This is useful if the Machine Name value the client specifies cannot be altered by an application defined method.
Parameters
Example
CCITCPT_server1=MFNODE:server2,MFPORT:3000
Syntax
CCITRACE=filename [options]
| /F or -F | logs the details of CCI API calls to the trace file. The default is OFF, unless a filename any other trace option is specified, in which case it is always ON. |
| /P or -P | logs the details of protocol-level calls to the trace file. The default is OFF. If this flag is OFF, then only the details of the CCI user-level API will be traced. If this flag is ON, the level of function tracing may be greatly increased. |
| /D or -D | logs the contents of all buffers passed to and from the CCI functions. The default is OFF. Data tracing may not be allowed if the application has been coded to prohibit data tracing for security reasons. |
So to create a CCI trace file with the default name of ccitrc1.trc (with matching ccitrc1.idx file) which traces CCI API function flow, along with the underlying protocol function flow, but with no tracing of the user data passed to these calls, the value of the CCITRACE environment variable would be /P.
The CCI.INI file can also be used to control trace options, but any values specified by the CCITRACE environment variable will take precedence.
Specifies a run-time configuration file that tailors the run-time configurable options in some way.
Syntax
SET COBCONFIG=pathname
Parameters
Comments
If $COBCONFIG is not set then the file $COBDIR/etc/cobconfig is searched for instead.
Example
SET COBCONFIG=/home/mydir/cobconfig
Values
Specifies the directory or directories that the Compiler and Animator should search for copyfiles.
Syntax
SET COBCPY=pathname[:pathname]...
Parameters
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
SET COBCPY=/home/group/sharedcopy::mydir/mycpy
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.
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]...
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
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.
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.
SET COBDIR=pathname
Parameters
Comments
The Micro Focus COBOL system is normally installed in the default COBOL system directory 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.
Example
SET COBDIR=/home/products/cobse20
This causes the Cob utility to search the directory /home/products/cobse20 for the Micro Focus COBOL system software.
Specifies which Java Virtual Machine (JVM) to load.
SET COBJVM=platform_nnn
Parameters
platform_nnn where
Comments
You might need to set COBJVM if you are developing distributed applications with both COBOL and Java components.
Example
SET COBJVM=ibm_122
Specifies the maximum elapsed time, in tenths of a second, for the connected terminal to transmit any valid escape sequence to the runtime system.
When a terminal key is depressed, the terminal might send in response a single character or a group of characters to the runtime 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 runtime 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 runtime system in discrete packets, then the network can alter the intervals between each character arriving at the runtime system. COBKEYTIMEOUT is available to help compensate for typical network delays so the runtime system identifies escape sequences correctly.
Syntax
SET COBKEYTIMEOUT=n
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 runtime system over the line or network connection. On encountering a lone Escape character, the runtime system waits n tenths of a second before assuming that the character does not introduce an escape sequence. The runtime system calculates an appropriate default value for n from the baud rate of the terminal.
Example 1:
COBLPFORM 1:3:5:7:9:11:13:15:17:19:21:23
In this example C01 equals 1, C02 equals 3, and so on.
Example 2:
COBLPFORM :3::5: :9
In this example, C01 equals 3, C02 equals 5, C03 equals 1, and C04 equals 9. You can specify only a single line number for each channel.
In example 2 above, channels C05 - C12 are undefined. If a print statement specifies channel C05 - C12, the line is printed at line 1. In addition, in the example shown, C03 equals 1 because its value is a space and therefore undefined.
Any WRITE BEFORE/AFTER PAGE statements cause positioning to be at line 1. Each line advance increases the line number by one. A request to skip to a line number less than or equal to the current line causes a new page to begin. The appropriate number of line feeds are then generated.
Specifies the size of the main stack.
Syntax
SET COBMAINSTACK=n
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:
If you are using the multi-threaded run-time system
If you have IF STATEMENTS with a very large number of ELSE clauses
Specifies the directory or directories that the runtime system is to search for dynamically loadable .int and .gnt files, or callable shared objects.
Syntax
SET COBPATH=pathname[:pathname]...
Parameters
pathname A list of search directories, each item separated by a semicolon, that the runtime 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
SET COBPATH=u:/home/mydir/srclib:otherlib
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
SET COBPRINTER=command-line
Parameters
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.
Example
SET COBPRINTER="myspooler -a $TMPDIR\spoolfile"
Syntax
SET COBSW=[+/-}s...
A list of the runtime switches to set or unset.
Example
SET COBSW=+0+D
This enables runtime switch 0 and the ANSI COBOL debug switch.
Values
Syntax
SET ENTRYNAMEMAP={filename|directory}; ...
Parameters
filename An entry map file.
directory A directory containing an entry name map file. The name of the entry name map file must be mfentmap.dat.
Comments
You must set the entry_name_mapper tunable to enable entry point mapper support.
If ENTRYNAMEMAP is not set, the runtime system searches for an entry name map file called mfentmap.dat in each folder specified by the COBDIR environment variable.
If the runtime system finds more than one entry name map file and same entry point is defined differently in different files, precedence is given to the definition in the entry name map file that was found first. To change the order in which the runtime system finds entry name map files you need to change the order in which the files appear in the COBDIR or ENTRYNAMEMAP environment variable paths.
Syntax
SET ES_ALLOC_EXPAND=value
Values
Y Expands an environment variable used to specify an allocation path.
N Do not expand the variable used in the path.
Default
The default value is Y.
Syntax
SET ES_ALLOC_OVERRIDE=rules-file
Values
rules-file The file path and name of the dataset rules file.
SET ES_CERT_REG=pathname
pathname Pathname of the directory where registrations are stored.
By default no directory is specified. In this case it must be specified on the cascertreg command.
SET CESN_NO_OS390=value
Specific invalid user/password messages will be produced.
ES_CONSOLE_LOG=port export ES_CONSOLE_LOG
Can be any combination of the following:
ES_CSKL_NO_MSG_CONSOLE=value
ES_DDBG_PORT_RANGE=value
Example
ES_DDBG_PORT_RANGE=8001-8040
ES_DISABLE_DFLTUSR_SIGNON=value
ES_ESMAC_DISP_MAX_OVERRIDE=value
Syntax
SET ES_HSF_CFG=cfg-options
Parameters
field_name=value;[field_name=value;]...using the following values:
| Field name | Range | Default |
|---|---|---|
| CUSTOM | 0-5 | 0 |
| CICSF | 0-20 | 5 |
| TSQ | 0-20 | 5 |
| TDQ | 0-20 | 5 |
For example: ES_HSF_CFG=CUSTOM=2;CICSF=10;TSQ=32 generates 2 custom fields, 10 CICS file fields, 5 TSQ fields and 5 TDQ fields.
Custom fields are written to using the ES_WRITE_CUSTOM_HSF library routine.
ES_MAX_CATALOG_LINES=number
Values
Y Enables previous default behavior of cataloging and creating the physical files for dynamic PDS when referenced in a JCL DD statement.
N Physical files for dynamic PDS members are only created and cataloged when created using the JCL utility or by a user program.
Default
The default value is N.
SET ES_OLD_SEC_TSTD=value
SET ES_OTMA_TIMEOUT=seconds
Syntax
SET ES_RLS_FILE_SUPPORT=value
Values
Default
RLS file support is off.
Syntax
ES_SEP_DORMANT_TIME=seconds
Values
Default
Transient SEPs are terminated after 2 seconds of inactivity.
Syntax
ES_SERVER=name
Values
Default
ESDEMO/ESDEMO64
Syntax
SET ES_USR_DFLT_ESMAC=user
Values
Default
mfuser
Syntax
ES_ESM_DISABLE_DFLTUSER_ESMAC=value
Values
Default
Default ESMAC user is not disabled.
Syntax
ES_XA_????_NB_RETRIES=nnnn
Values
Default
5 retries (ES_XA_RECONNECT must have been set).
Syntax
ES_XA_LOG_SUPPRESS=value
Values
Default
By default no value is specified and XA logging is not suppressed.
If this environment variable is set, when an error occurs on a call to XA, the server recycles the SEP and attempts to reconnect to the Resource Manager. The ES_XA_????_NB_RETRIES variable specifies the number of XA call failures allowed before the SEP is recycled and the switch disabled.
Syntax
SET ES_XA_RECONNECT=user
Values
Default
No value is set and the XA reconnect feature is not enabled.
Syntax
SET EXTFH=filename.cfg
Parameters
filename.cgf The name of the configuration file.
Example
SET EXTFH=/home/mydir/myconfig.cfg
Syntax
SET FHREDIR=filename.cfg
Parameters
filename.cfg The name of the configuration file.
Example
SET FHREDIR=/home/mydir/myconfig.cfg
Specifies a configuration file to be used by the Fileshare Server.
Syntax
SET FS=filename.cfg
Parameters
filename.cfg The name of the configuration file.
Example
SET FS=myconfig.cfg
Syntax
SET FSCOMMS="\$local"
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
SET HCOBND=d:\mydir\binds
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.
Syntax
SET MAINFRAME_FLOATING_POINT=fpstatus
Parameters
fpstatus Which format to use for floating point data items. This must be one of:
Setting MAINFRAME_FLOATING_POINT to anything other than true has the same effect as setting it to false.
The setting of this environment variable can be overridden by the NATIVE-FLOATING-POINT directive.
Determines if the MFELX* files associated with a job are also deleted when spool housekeeping is run.
Syntax
SET MF_SPOOL_HK_LEX_SCAN=Y|N
Values
Y The files are deleted.
N The files are not deleted.
Default
The default is Y.
Syntax
SET MF_SPOOL_HK_OUTPRTC=value
Values
Y Files from the Complete queue are deleted.
NFiles from the Complete queue are not deleted.
Default
The default is Y.
Syntax
MF_SPOOL_HK_TESTDATE=YYYYMMDD
Values
YYYYMMDD The date which is to override the normal date.
Default
If this variable is not set, the normal date for the spool housekeeping is used.
Syntax
SET MF_SPOOL_HK_WRITE_PROFILES=Y|N
Values
Y Profile files are created.
N Profile files are not created.
Default
The default is Y.
Syntax
SET MFCSCFG=filename
Parameters
filename The name of the configuration file.
Example
SET MFCSCFG=/home/mydir/mfclisrv.cfg
Comments
The value of MFCSCFG is overridden by any value defined in the command line. If neither of the above yields a filename, the default filename mfclisrv.cfg is assumed, and is searched for in the current directory. If that in turn is not found, the default settings for the configuration entries are used.
Specifies a configuration file for Language Environment (LE) runtime options.
Syntax
SET MFLECONFIG=filename
Parameters
filename The file containing the LE runtime options you want to use.
Syntax
SET MFLOGDIR=dirname
Parameters
dirname The name of the directory for log files.
Example
SET MFLOGDIR=/home/mydir/logs
Specifies the record length for the REXX EXECIO command when reading or writing a line sequential file that has been cataloged with a record length of zero.
Syntax
SET SORTCOMPRESS=5
Parameters
5 This is the only value that you can supply. It allows for run-length encoding of sort records, resulting in much better performance when records contain multiple repeated characters.
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
SET SORTCOMPRESS=5
Syntax
SET SORTSCHEME=1
Syntax
SET SORTSPACE=n[K|k|M|m|G|g]
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
SET SORTSPACE=1024K
Syntax
SET SORTTEMPSPACE=n[K|k|M|m|G|g]
Parameters
n[K|k|M|m|G|g] The amount of memory to be allocated to temporary workspace for SORT operations. K or k indicates kilobytes, M or m indicates megabytes and G or g indicates gigabytes. No letter indicates bytes. 32 megabytes is the lowest amount of memory that can be allocated.
Comments
The memory allocation strategy used by SORT can be adjusted through use of SORTTEMPSPACE, which generally improves performance in systems suffering from memory fragmentation.
Example
SET SORTTEMPSPACE=250MB
Syntax
SET SORTTYPE=2
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\Visual COBOL\[version-number] for .NET applications only. This variable has no effect for native applications; the log file is created in the current directory regardless.
The effect of this variable can be overridden by the LOGFILENAME configuration option.