UDFrc File

The UDFrc file holds various definitions and option settings which can be used to specify how specific options in some programs operate. The file is found in the directory $UDFTOOL_HOME/ConFigs.

The file consists of comment fields, general definition fields, and program specific fields. All lines which begin with a # are comment lines. They are not parsed or used by any program. General definition fields consist of an Option ID followed by a space separated option definition. General definitions can be picked up and used by multiple programs. A generic general option definition has the form

PROGRAM:OPTION DEFINITION
Program specific definitions are used only by the program which they are set for. They generally allow for additional control over the way in which some of the program options operate. Program option definitions have three fields to them: the name of the UDF program program they are associated with (such as dBAsk or CONTROL) followed by a :, the option id followed by a space and the option definition. The line has the generic format
PROGRAM:ID DEFINITION

Currently used general options are described below.

GENERAL SETTINGS
OPTION DEFINITION
BroWseR The browser you which to have brought up when a program needs to. If the browser is not in your PATH then include the full path name with the browser. Setting the BroWseR will activate the Documentation button in the udfPilot.
Example Usage:
BroWseR   mozilla
TerM A command which will bring up a terminal window. This should at the end the flag which allows a program to be automatically executed in the window.
Example Usage for a GNOME terminal window:
TerM   /opt/gnome2/bin/gnome-terminal -x

Program specific options are are described below. Note that there may be multiple programs which make use of the same option ID.

PROGRAM SPECIFIC SETTINGS
PROGRAM OPTION ID DESCRIPTION
dBAsk
VEdit		 MinQ This option specifies the UDF lineage fields that need to be set when performing a Query function. The generic option definition is defined as P.M.E.I.V which indicates that all fields must be specified. The setting in a new installation is P.M meaning that the PROJECT and MISSION fields must be set. You can remove this option to indicate that no lineage fields need be set. In this case a QUERY with a set of unset lineage fields will attempt to look through all known UDF definitions. This can take considerable time depending on what is installed on the system.
Example Usage:
dBAsk:MinQ   P.M
dBAsk MinD This option specifies the UDF lineage fields that need to be set when performing a Delete in dBAsk. The generic option definition is defined as P.M.E.I.V which indicates that all fields must be specified. The setting in a new installation is P.M meaning that the PROJECT and MISSION fields must be set. You can remove this option to indicate that no lineage fields need be set. In this case a DELETE with a set of unset lineage fields will delete all known UDF data files which are online. Having some required field settings prevents an accidental full delete.
Example Usage:
dBAsk:MinD   P.M.E.I
dBAsk MinP This option specifies the UDF lineage fields that need to be set when performing a PROMOTE in dBAsk. The generic option definition is defined as P.M.E.I.V which indicates that all fields must be specified. The setting in a new installation is P.M meaning that the PROJECT and MISSION fields must be set. You can remove this option to indicate that no lineage fields need be set. In this case a PROMOTE with a set of unset lineage fields will attempt to PROMOTE all UDF data files from all Projects which have archives defined for them. This probably is not what was desired. Having some required field settings prevents an accidental mass promotion of data.
Example Usage:
dBAsk:MinP   P.M.E.I
CONTROL LBoxes This option defines the number of list boxes to show in the main CONTROL menu window. The value can be 1, 2 or 3. The list boxes are used to display the all of the available open menu windows which exist for a menu definition.
Example Usage:
CONTROL:LBoxes   2
CONTROL LBDir This option defines the direction to fill the CONTROL list boxes when more than one list box exists. The options are either vertical or horizontal. With vertical filling the available menus are listed down the list boxex while with horizontal filling the available menus are list across the list boxes.
Example Usage:
CONTROL:LBDir   vertical
udfPilot IDL This option indicates how to invoke idl from udfPilot. There are basically to options: either idlde or NEEDSTERM|idl. The first will invoke the idl idlde program environment and the second will invoke idl directly from a terminal window. In the latter option the general TerM option must be defined.
Example Usage:
idfPilot:IDL   idlde