Run-time Tunables and Configurables - Overview

When your run-time system or linked executable starts up, it attempts to read the run-time configuration file. The run-time configuration file specifies values for the run-time tunables and environment varibales.

If you use the Interface Mapping Toolkit to generate COBOL services for execution in Enterprise Server, you can specify settings for some tunables for the application container, a version of the run-time system used in Enterprise Server. If a setting specified by the Interface Mapping Toolkit conflicts with a setting in the configuration file, the setting specified in the Interface Mapping Toolkit always takes precedence.

The run-time configuration file is shared by all users of the run-time system.

You create or edit the run-time configuration file with a text editor. It is an optional file - no error is issued if it does not exist. You specify the location and name of the run-time configuration file using the COBCONFIG environment variable. For example, if you want to use a configuration file called myconf, you would set COBCONFIG as follows:

COBCONFIG=$HOME/myconf
export COBCONFIG

Format of the Configuration File

The configuration file conforms to this format:

Each run-time tunable or environment variable appears on a new line.
Blank lines are ignored.
A comment line starts with a # character. However, as the configuration file is processed at run-time, we advise that you limit the number of comments, in order to keep to a minimum the time taken to process the configuration file.
The maximum number of characters permitted in a comment line is 80, including any new-line or carriage return characters that might be placed at the end of the line by some editors.
Each space in the definition can be replaced with tabs or more than one space.

The format of each tunable is:

set name=value

The format for each environment variable is:

setenv name value

where:

name

The name of the run-time tunable or environment variable described in the appendix Environment Variables. For details on dd_ filename mappings see your File Handling Guide .

value

The value to be assigned to the run-time tunable or environment variable.

For a run-time tunable, value is validated according to the type and values allowed for that tunable, and the value of cobconfig_error_report.

Where value is numeric, a leading zero indicates that the value should be treated as octal (that is, base 8). For example, 07 (octal) is 7 (decimal), while 010 (octal) is 8 (decimal); however, 08 (octal) and 09 (octal) are invalid octal values. Hexadecimal values can also be set by using numeric values that begin with with 0x.