[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

114.0. "What are the big files for?" by NSSG::R_SPENCE () Tue May 01 1990 21:37

    I have some questions about the data files used by MCC.
    
    MCC$DEFINITION.DAT;1
    MCC$DICTIONARY.DAT;1
    MCC$META_DICTIONARY.DAT;1
    MCC$MIR_ATTRIBUTE.DAT;1
    MCC$MIR_DIRECTORY.DAT;1
    MCC$PTB_PARSER.DAT;1
             
    Some of these files are very large, the MCC$DEFINITION.DAT and the
    MCC$DICTIONARY.DAT particularly. What is in these files such that
    they have to be this large?
    
    Also, what is in the other files?
    
    And another related question...
    
     Where is the reference information for an entity stored. I looked in
    DNS for it but it didn't jump out at me so I guess I missed it.
    
    Thanks
    
    rob

T.R Title User Personal
Name Date Lines

114.1 I never metadata I didn't like TOOK::SWIST Jim Swist LKG2-2/T2 DTN 226-7102 Wed May 02 1990 12:49 8

T.R	Title	User	Personal Name	Date	Lines
114.1	I never metadata I didn't like	TOOK::SWIST	Jim Swist LKG2-2/T2 DTN 226-7102	`Wed May 02 1990 12:49`	8
	Most of the the data storage represented in those file is the MCC dictionary and the associated parse tables. In MCC UT1_0_0 there were 23084 dictionary instances stored. Every possible attribute, directive, response, exception, argument, and subentity definition for every entity class must be stored in the dictionary. DECNET Phase V definitions are more than half of that metadata.

    Most of the the data storage represented in those file is the MCC
    dictionary and the associated parse tables.
    
    In MCC UT1_0_0 there were 23084 dictionary instances stored.  Every
    possible attribute, directive, response, exception, argument, and
    subentity definition for every entity class must be stored in the
    dictionary.  DECNET Phase V definitions are more than half of that
    metadata.