Mapping files are the main method for mapping function, control, and arrow keys to menu items, FRS commands, and FRS keys. Mapping files can exist at each level of mapping in your environment. For example, you can have an installation-wide mapping file, terminal‑type mapping files for every terminal type in your organization, user mapping files for each user, and application mapping files for every Ingres application.

In Windows, you can have several applications mapping files in addition to the FRS mapping file.

The syntax for the mapping files is the same across all levels of mapping. A mapping file can consist of three components:

Mapping statements designate the actual mappings. These are the most commonly used. The mapping statements can also designate labels for menu items, if you do not use the default labels.

Disabling statements disable the use of function or control keys (and arrow keys in UNIX and VMS).

Comments provide explanatory text.

The statements in a mapping file can appear in any order, except for the placement of disabling statements (see page How to Disable Statements). Each statement must fit entirely on one line. Alphabetic characters within a mapping file can appear in either uppercase or lowercase, with no difference in meaning. Blank lines are ignored.