Conference azur::mcc

118.0. "Where is Reference info stored?" by NSSG::R_SPENCE () Wed May 02 1990 14:05

       
    
    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.
    
    For example;
    
    MCC> sho station nets all ref
    STATION CLAUDI_NS:.NETS
    Reference
    AT  2-MAY-1990 13:57:50
    
    
    Examination of attributes shows:
                        Implementation Desc = "VS 3100"
                                   Location = "LKG2-1, pole S2"
                               MAIL Account = "NETS::R_SPENCE"
                               Phone Number = "226-7991"
                                    Remarks = "FT1 Testing, 27-Apr-90"
                         Responsible Person = "Rob Spence"
                                  Text File = "nets::sys$manager:ident.txt"
    MCC>
     
    Where is all this info stored. Claudia was able to enter it all from
    the MCC director running on her system and I was able to view it so
    it seemed that it had to be stored in DNS but I can't find it using
    DNS$CONTROL.
    
    This info was put in the STATION entity class because I couldn't find
    anything in the NODE4 class documentation that let me add this info
    for a Node. Is there a way to add reference info for entity classes
    other than STATION?
    
    s/rob   

Reference information is stored in the DECdns namespace, as you 
suspected.  We store it as MCC-define DNS attributes under the namespace 
entry.

You can't see it with dns$control due to a bug in the V1.* server.  Our 
attribute names are binary names.  The default `start' for the server's 
enumeration of attributes is an ascii null.  Since our names a binary, 
they collate before the ascii null and are not returned.

The V2.* server will remedy this.  Once we go to V2, you will be able to 
see the attributes - they will all start with MCC$, but since the names 
are binary, they won't make much sense to you.

Since we store the instance hierarchy as attributes under the global 
entry, we needed a way to carry class hierarcy information in the 
attribute names.  The names are restricted to 31 characters, so we had 
to go to a binary encoding to create attribute names that carried the 
information required.

...kjn

    Thanks. That clears up the mystery.
    
    s/rob