| 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 |
I issue the command: MCC> REGISTER NODE4 FOO MCC procedes to poll node FOO (via NML) for EXECUTOR CHARACTERISTICS, KNOWN CIRCUIT CHARACTERISTICS, and KNOWN LINE CHARACTERISTICS. The node name and address are stored in DNS. A DNS object is created (.DNA$Node.FOO), and a soft link is placed in the .DNA$BackTranslation.<area> directory. What happens to all the rest of the information? Is it stored in the MIR? Is it stored in a file? Does the MIR = Some_File? Is it stored in DNS? Is it discarded? Also, if I create some reference information for that node, where is it stored? Thanks, Jack
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 75.1 | Hello? | DSTEG::MCCANN | Mon Mar 19 1990 18:59 | 10 | |
We're still wondering where the data gets stored... Did I miss something in the documentation? Does MIR = MCC$MIR_DIRECTORY.DAT + MCC$MIR_ATTRIBUTE.DAT? Are there more files involved? Sorry to be a bug about this... | |||||
| 75.2 | INFO - chapter 2 in SRM | GOSTE::CALLANDER | Tue Mar 20 1990 12:06 | 18 | |
To really understand the MIR you should read chapter 2 of the SRM.
In section 2.4 it descirbes the four types of information stored
in the MIR.
But, to quickly answer your question, the MIR is not one store.
It is actually made up of multiple stores so as to best handle the
storage and retrieval of the four classes of information maintained
in the MIR.
The table on page 16 (table 2.1) shows you which routines to use
to access the different types of MIR data. As to which file or in
memory section we are using, this is hidden behind the implementation.
For some information on these files you should take a look at the
guide to writing an access modules which describes some of this.
| |||||
| 75.3 | where the data goes | TOOK::NELSON | Tue Mar 27 1990 12:02 | 15 | |
Jill is correct, we are trying to keep the implemetation specifics hidden behind the interfaces as we know that eventually we probably want to move to another datastore, such as a distributed database. Currently, however, the Configuration instance database is stored in the DECdns nameserver as part of the namespace. MCC augments the global entries stored there with MCC-defined DNS attributes. For the short term, at least, current values of reference information is also stored by MCC using the MCC-defined attributes modifying the DECdns entries. This allows all instances of MCC in a single network to `see' the same values. ...kjn | |||||