The file has the following basic format of a keyword (case insensitive) usually followed by a value separated by one or more spaces.
keyword <value>
The < > symbols indicate the location of a user defined value and the word an indication of the type of data expected. The < > symbols are are not included, but are used for documentation purposes. For example:
CPU <cpu-nbr>
actual entry -
CPU 2
An optional value is indicated in the documentation by enclosing it with the [ ] symbols. For example:
keyword [<value>]
documentation -
ENABLED [<False>]
actual entries -
ENABLED or
ENABLED false
Strings, if indicated by the keyword, must be enclosed in quotes or tics if it contains an embedded space. For example:
== Description of system
System-description "Production System"
Comments may be included in the file. Lines that begin with the following identifiers are considered comment lines:
!
==
comment
Generally, data is extracted from lines of the CONFMOMI file when a keyword is recognized. Characters past expected data are usually ignored. Comments are not supported within valid input lines (i.e. you can't embedded a comment between a keyword and an expected value).
The following are some examples how comments are used:
comment *** this section documents something ***
=========================================
== this is the MOMI configuration file ==
=========================================
Hst01db $data1.momi.hst01db == MOMI history database
Only one keyword is allowed per line. Spaces preceding or trailing the keyword are ignored. Use the sample CONFMOMI file as a formatting template (it is automatically placed in the same subvolume as MOMI object file during install).
It is not necessary to specify all the available keywords as most have default values. Advanced keywords are provided for limited or special situations.
Some keywords, in order to make it unique, use a numeric value documented as "nn" that represents a number such as 01, 02, 03, etc... . In other words, where you see "nn", such as HSTnnDB, replace it with 01, 02, 03, etc... as indicated in its documentation.
Where you see xx in a keyword, such as PRIORITY-DB-HSTxxDB-CON , it is used 'as is' and applies to all instances.
If a syntax error is encountered: a) that line is ignored, and b) two error messages are logged where the first identifies the file and the second contains the line of ignored text. Servers prior to version 6.18 log one message and later versions log two:
Line of data in Config file bad : <text>
Line of data in $vol.sub.confmomi file bad (line ignored) : <ignored text in 2nd EMS message>