Directory entry records can have one or more blanks (for
indentation) before the keyword. There can be multiple blanks between
the keyword and the value. The value is a single string and can contain
blanks only when it is enclosed in quotes. Everything after the value
in a record is treated as a comment and is ignored.
A minimum entry consists of a name line and one or more
attributes associated with that name. Each entry is ended by the next
entry (class or name) or the end of the file. More specifically, an
entry consists of the following items:
- The class of a list of entries. The class applies to all succeeding
entries until another class is specified. The first nonblank item
on the line is the keyword "class", followed by the class attribute,
or type (separated from the "class" keyword by at least one blank).
The only types of classes are:
The first entry in the file must start with a class record,
or a "no class specified" message is issued, and initialization
or reloading of the table fails. Subsequent entries can omit the class
record if these entries belong to the last class specified.
- The name attribute. This is the string against which the search
is made, within the class. The first nonblank item on the line is
the keyword "name", followed by the value of the name (a string
in single quotes), separated from the keyword by at least one blank.
Multiple entries with the same name value may exist in the directory
definition file, providing all attributes under entries with that
name value are different.
- After the name attribute, an attribute associated with an entry.
The first nonblank item on the line is the keyword for a particular
attribute, followed by the value (a string in single quotes) of the
attribute, separated from the keyword by at least one blank. The
current attributes used by CMIP services for the class, managed object,
are:
The current attributes used by CMIP services for the class,
aetitle, are:
- name
- address
- associationKey
- timeSync
If an attribute is encountered that has already been defined
for a particular name value (for example, a duplicate attribute entry,
such as two different associationKey values), the second one produces
a "duplicate attribute" message, and initialization or table
reloading fails. Individual attributes are optional on any particular
entry.
Each record in the file can extend over many lines, up
to a maximum of 2080 character spaces. This includes any leading spaces
before an attribute at the beginning of the line. The maximum logical
record length (LRECL) for the directory definition file is 2080. The
record format (RECFM) for the file must be FIXED.
Code entries as one or more records in the following format:
Column 1 |
End of line |
|
|
[…]attribute[ value]… |
...& |
- …
- Indicates blanks. One or more blanks can precede the first attribute.
- attribute
- Represents a characteristic of the managed object. Directory entry
records can have one or more blanks before the attribute and can have
multiple blanks between the attribute and the value. Separate the
attribute from the value with one or more blanks.
- value
- The value can have intervening blanks, if it is enclosed in quotation
marks.
- &
- If the entry requires several records, code the continuation character
(&) in the last position on the line.
- #
- Comment lines begin with the # symbol in column 1. Comments are
not processed. Blank lines are treated as comments.
The following information shows a sample entry in a directory
definition file. The first line is a scale to show column positions.
Every tenth column position is indicated by a number.
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7...
class managed object
name '1.3.18.0.2.4.6=USIBMNR;2.9.3.2.7.4=(name NR55550I)'
aetitle '1.3.18.0.2.4.6=USIBMNR;2.9.3.2.7.4=(name "NR55555I");1.3.18.0.2.4.12=OSISMASE'
Observe the following rules if more than one record is
required for an entry.
- Code the line up to the point where you want to break the line.
This point can be anywhere on the line.
- At the end of the line, code the continuation character &;
The & symbol does not form part of the line that is processed.
- Continue the entry in the first column of the next line. A comment
line cannot follow a continuation line.
- Continue coding lines with continuation characters until the entry
is finished.
- Entries can be coded on as many lines as needed.