Back to Contents


The FGLPROFILE configuration file

Summary:

See also: Programs


Basics

The runtime system uses one or more configuration files in which you can define entries to customize the behavior of the programs.

There is no specific naming convention for the configuration files, however, we recommend to use an extension  such as prf.

There are three different ways to specify the configuration file, with the following order of precedence:

  1. By default, the runtime system reads the configuration file provided in FGLDIR/etc/fglprofile. This file contains all supported entries, documenting the possible values and the default values.
  2. If the FGLPROFILE environment variable is set, the runtime reads entries from the file specified by this environment variable.
  3. If the program specific profile directory contains a file with the same name as the current program, the runtime system reads the entries from that file. The program specific profile directory is by default  (FGLDIR/defaults). This directory can be changed with the fglrun.defaults entry in one of the previously mentioned configuration files (FGLDIR/etc/fglprofile or the one defined in the FGLPROFILE environment variable).

Entry Syntax

Purpose:

An FGLPROFILE entry is a parameter that can be changed in the configuration file. 

Syntax:

entry = value

Notes:

  1. entry identifies the name of the entry. It is composed of a list of words separated by a dot character. By using names like domain.sub-domain.param, entries can be organized by domains and sub-domains.
  2. value is the value of the entry; it can be an numeric value, a string literal, or a Boolean value (true/false).
  3. If an entry is defined in different levels of configuration files (default/specific/program), the runtime system searches for the entry value in the following order: program - specific - default.
  4. For more details about supported entries, see Supported Entries.

Warnings:

  1. Entry names are case sensitive.
  2. If an entry is defined several times in the same file, no error is raised and the last entry is used.

Example:

01 rtm.memory.cachelocals = true
02 rtm.default.logfile = "mytrace1.log"
03 dbi.database.stores.prefetch.rows = 200

Supported Entries

The following table shows the supported FGLPROFILE entries. You can find a complete usage in the corresponding documentation section referenced in the description of the entry. 

Entry Values Default Description
dbi.* N/A N/A Database interface configuration.
See Connections for more details.
gui.chartable string NULL Defines the character conversion table file.
See Dynamic User Interface for more details.
gui.protocol.pingTimeout integer 600 Defines the timeout delay the runtime system waits for a front-end ping when there is no user activity. After this delay the program stops with an error.
See Dynamic User Interface for more details.
fglrun.mmapDisable boolean false Memory mapping control. When set to true, memory mapping is disabled and standard memory allocation method takes place. For more details about memory mapping, run "man mmap" on UNIX.
See Basics for more details.
fglrun.default string NULL Defines the directory where program specific configuration files are located.
See Basics for more details.
fglrun.signalOOB integer 0 Defines the Out Of Band signal number.
See Dynamic User Interface for more details.
fglrun.localization.* N/A N/A Defines load parameters for localized string resource files. 
See Localized Strings for more details.
fglrun.extension.* N/A N/A Defines the Dynamic C Extension libraries to be loaded.
See Implementing C Extensions for more details.
Dialog.fieldOrder boolean false Defines if the intermediate field triggers must be executed when a new field gets the focus with a mouse click.
Provided for V3 compatibility only.
See Runtime Configuration for more details.
key.key-name.text string N/A Defines a label for an action defined with an ON KEY clause.
Provided for V3 compatibility only.
See Settings Key labels for more details.
Report.aggregateZero true/false false Defines if the report aggregate functions must return zero or NULL when all values are NULL.
Provided for V3 compatibility only.
See Report Configuration for more details.