MFSBLD

Section: User Commands (1)
Updated: November 2000
Index Return to Main Contents
 

NAME

mfsbld - XPAT Multi-File/Filter Support (MFS) system FileMap builder  

SYNOPSIS

mfsbld [ -v ] [ -s ] [ -t ] [ -o " text_file" ] -D data_dictionary  

DESCRIPTION

mfsbld reads the MFS specifications in the data_dictionary and generates the MFS FileMap for that database. The FileMap is a directory of all the files that make up the database and is a core component of each MFS database. The data_dictionary must be an MFS Data Dictionary (i.e., it's `Text' section must contain an `MfsFiles' section). Refer to the Database Administration Guide and the mfs(5) man page for further details.

mfsbld builds the following three FileMap files:

-
The FileMap file itself (with a `.fmp' extension)
-
The Filter List file (with a `.lmp' extension)
-
The Compiled FileMap file (with a `.xmp' extension)
 

OPTIONS

The following options are available:
-v
Specify verbose mode. This option tells mfsbld to print out progress messages to the standard output, as it is building the FileMap. By default, mfsbld works silently, only printing a message if an error occurs.
-s
Specify sort mode. This option tells mfsbld to sort the entries in the FileMap in alphabetical order by the file paths. By default, mfsbld adds the file entries into the FileMap in the order the files appear in the directories.
-t
Generate a user meta-data template file. This option tells mfsbld to generate the template file for the user meta-data, instead of building the FileMap files. The template file has the extension `.dat'. Refer to the mfs(5) man page for a description of this file's format, as well as a description of how to enter the actual user meta-data into the template file. Note that you only need a user meta-data file if you are incorporating user meta-data into the FileMap. Also note that the `.dat' file file must be generated and prepared before the FileMap files are built. When you run mfsbld without the -t option, it will automatically look for the template file in the same place as the other three FileMap files (as specified by the `FileMap' section of the Data Dictionary). If it finds the file, it will automatically incorporate its contents into the FileMap.
NOTE: You usually do not run mfsbld by hand. Instead, you usually run dbbuild, which in turn calls mfsbld and all the other index-building programs. Refer to the dbbuild(1) man page for more details.
-o text_file
Generate an output text file. This option tells mfsbld to generate the virtual text of the entire database at the time it generates the FileMap files, and write this text to text_file. This option is normally used by dbbuild (see the dbbuild(1) man page for more details).
 

INTEGRITY CHECK

mfsbld will store some FileMap integrity check values inside the `.xmp' file to ensure that the three FileMap files are always consistent with each other. It is important NOT TO EDIT FileMap files directly. If you edit these files, you will get an error message from xpat when you try to search the database. If this happens, you will have to either restore the unmodified FileMap files, or rebuild the database index files (refer to the Database Administration Guide for details of this process).  

SEE ALSO

data_dict(5), mfs(5), dbbuild(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
INTEGRITY CHECK
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 18:03:38 GMT, March 26, 2001