[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

2119.0. "Help on deleting MIR information." by CUJO::HILL (Dan Hill-Net.Mgt.-Customer Resident) Wed Jan 15 1992 14:43

    Can someone please do a sanity check for me?
    
    I had an AM when I was running DECmcc V1.1 that is no longer needed in
    V1.2; however, I had entities registered using this AM.  Can I just 
    delete references in DNS, or must I delete them from the MIR as well.
    
    If I must delete from the MIR, what is the syntax and what is the tool
    to use?  I need to delete them as domain members, also.  As you know,
    I can't do it from MCC>.
    
    -Thanks,
     Dan
T.RTitleUserPersonal
Name
DateLines
2119.1Can use DNS$CONTROL to remove Identifier and Reference InfoTRM::KWAKWed Jan 29 1992 16:0664
    
    RE: .0
    
    The configuration information (both IDENTIFIER and REFERENCE) is stored 
    in DNS.
            
    The REFERENCE information is stored in a DNS object's attribute
    in the ILV-encoded format. (the attribute is the Binary attribute,
    and cannot be seen using DNS$CONTROL program. But, the "dnscp"
    program on Ultrix DECnet/OSI does display the binary attribute.
    The reference information is removed when you delete the DNS
    object.
    
    Suppose you create a domain called .site1.foo, MCC creates two
    DNS group objects - .site1.foo and .site1.foo_MCC_EXT000.
    Since there is the limitation in record size for storing one
    DNS object, MCC creates the first 10 members in the 'primary
    domain' (.site1.foo), and the next 80 members in the first domain
    extension (.site1.foo_MCC_EXT000), and another 80 members in the second
    domain extension (.site1.foo_MCC_EXT001), and so on. The second and
    consequent domain extensions are created on-demand.
    
    If you want see all members of a domain .site1.foo in
    DNS$CONTROL, do following until domain extensions are exhausted:
    	DNS> show object .site1.foo attribute DNS$MEMBERS
        DNS> show object .site1.foo_MCC_EXT000 attribute DNS$MEMBERS
        DNS> show object .site1.foo_MCC_EXT001 attribute DNS$MEMBERS
                            ....
    
    When you add a member to a domain, MCC performs two tasks:
        1. Add the members fullname to Group object's DNS$MEMBERS attribute
        2. Add the domain name in the member's MCC_DOMAIN_LIST attribute.
    The attribute contains the list of domains the member object
    belongs to.
    
    The following is what you can do to remove V1.1 information:
        1. Use DNS$Control program to find the Domain list to which a
           ICMP_AM object belongs, and remove the ICMP_AM object from the
           domain (group object). Assume that the ICMP_AM object is
    	   .site1.foo, and it belongs to .domain.bar1 and .domain.alpha.
    
            DNS> show object .site1.foo attr MCC_DOMAIN_LIST
                    (* This is shown in 'ASCII and Hexadecimal' format)
    
    
            DNS> remove member .site1.foo group .domain.bar1
            DNS> remove member .site1.foo group .domain.alpha
    
        2. Use DNS$Control program to delete ICMP_AM objects:
            DNS> delete object .site1.foo
    
        3. If the ICMP_AM has Alternate Identifiers, there are DNS softlinks
           in .MCC_ICMP_Backtranslation directory. Please delete these
           softlinks.
    
            DNS> show dir .MCC_ICMP_Backtranslation known link
    
            DNS>! for each known softlink:
            DNS> delete link .MCC_ICMP_Backtranslation.--------
            DNS> delete link .MCC_ICMP_Backtranslation.--------
            DNS> delete link .MCC_ICMP_Backtranslation.--------
            DNS> delete link .MCC_ICMP_Backtranslation.--------