| As background information, the class data for entities is described in
management specification (.ms) files. The management specifications are
provided by FM's and AM's for each entity they are helping to describe/
define. These .ms files are processed by the MSL translator and the output
is DAP .com input files. The dictionary is then populated with
information from the management specifications using the DAP utility and
the DAP .com input files. Once the Dictionry has been populated, the parse
tables are built using the PTB (Parse Table Builder). The latter two
operations were performed by the MCC$BUILD_DICT.COM command procedure, for
the entity definitions provided by the FM's and AM's on the kit.
The MCC integration team made a decision in November to no longer provide
the DAP .com input files, as well as the MCC$BUILD_DICT.COM command
procedure. A pre-loaded dictionary is supplied with all kits that
includes the entity class data from the management specifications that are
provided by the FM's and AM's that make up the kit. Typically, end-users
and external development groups do not have to build the dictionary from
scratch. They can however add to it. They can add the entity class data
from management specifications that are provided by new management modules
(that they get from other sources, or develope on their own). Information
is provided in Chapter 3 of the DECmcc Toolkit Reference on how to do this.
Once they are done adding the entity class data they can build the parse
tables. Information is provided in Chapter 4 of the DECmcc Toolkit
Reference on how to do this.
Should one need another copy of the preloaded dictionary (i.e., the
dictionary was accidentally deleted), one can retrieve it from the
distribution media, rather than rebuilding it from the DAP .com input
files.
If additional information is required, please feel free to contact me.
regards,
\steve wong
took::wong
8*226-5344
|