Overloading Mapping Files

Overloading of mapping files is permitted and may occur. This means that a file that is found in the first folder will be overwritten by a file with the same identifying characteristics, though not necessarily with the same filename (Internal Mapping Files), found later in any of the succeeding folders. For example, a project mapping file could overload a company mapping file.

The sequence of environment variables is set to the locations of the internal mapping files. The interface will search all the folders pointed to by these variables and locate all files with the suffix .map in each sub-folder called BocadMaps. The .map files will be imported during system initialization as internal mapping files. The internal mapping files then become the basis for locating the external mapping files.

However, this does not alter the search rules for the external mapping files as based on the content of the identification line in the internal mapping file.

The diagram below illustrates how these environment variables may be used to select and overload sets of internal mapping files.

You does not have to use all three defaults variables.