Conference azur::mcc

72.0. "DNS Problem with EFT1" by CCIIS1::ROGGEBAND (_ �hili��e _) Fri Mar 09 1990 04:10

    Hello,
    
    I am experiencing some problems with DNS since I upgraded from MCC
    IFT to MCC EFT1.
    
    I followed the release notes, deregistered all my Phase IV nodes,
    created the DNA$Node directory and added access rights to the directory
    for all users :
    
    DNS>ADD ACCESS *::* DIRECTORY .DNA$Node /RIGHTS=(READ,WRITE,DELETE)
    
    When I register Nodes, the condition returned by the MCC routine is
    failure, "No access right", yet the node seems to have been registered
    registered successfully ,and I can perform Directory operations and
    wildcards on Node4 global entities. I can also store reference
    attributes, which I believe are stored in DNS ? 
    
    Is this a bug or have I missed something ?
    
    I am appending a log of the MCC session.
    
    �hR.
    
    
$ mcc

DECmcc (T1.0.0)


MCC> register node4 ccei0

Node4 62.20 

AT  9-MAR-1990 09:56:20



The requested operation cannot be completed
                      MCC Routine Error = %DNS-E-ACCESSDENIED, No rights to perf
                                          orm requested operation

MCC> register node4 netman
Node4 62.61 

AT  9-MAR-1990 09:56:32



The requested operation cannot be completed
                      MCC Routine Error = %DNS-E-ACCESSDENIED, No rights to perf
                                          orm requested operation

MCC> dir node4 *
Node4 CCEI0 

AT  9-MAR-1990 09:56:48



Directory successful.
                                   Name = CCEI0

Node4 NETMAN 

AT  9-MAR-1990 09:56:49



Directory successful.
                                   Name = NETMAN

MCC> show node4 * all char
Node4 62.20 

Characteristics

AT  9-MAR-1990 09:57:01



Examination of Attributes shows:
                         Identification = "DECnet-VAX V5.2,  VMS V5.2    "
                     Management Version = V4.0.0
                         Incoming Timer = 45

			.....



Node4 62.61 

Characteristics

AT  9-MAR-1990 09:57:08



Examination of Attributes shows:
                         Identification = "DECnet-VAX V5.2,  VMS V5.2    "
                     Management Version = V4.0.0

                        .....

MCC> show node4 * all reference
Node4 CCEI0 

Reference

AT  9-MAR-1990 09:57:17



Examination of Attributes shows:
                    Implementation Desc = ""
                               Location = ""
                           MAIL Account = ""
                           Phone Number = ""
                                Remarks = ""
                     Responsible Person = ""
                              Text File = ""

Node4 NETMAN 

Reference

AT  9-MAR-1990 09:57:19



Examination of Attributes shows:
                    Implementation Desc = ""
                               Location = ""
                           MAIL Account = ""
                           Phone Number = ""
                                Remarks = ""
                     Responsible Person = ""
                              Text File = ""

MCC> set node4 ccei0 Responsible Person "Toto"
Node4 CCEI0 

Reference

AT  9-MAR-1990 09:57:34


Modifications completed successfully
                     Responsible Person = "Toto"

MCC> exit
    

>>    When I register Nodes, the condition returned by the MCC routine is
>>    failure, "No access right", yet the node seems to have been registered
>>    registered successfully ,and I can perform Directory operations and
>>    wildcards on Node4 global entities. I can also store reference
>>    attributes, which I believe are stored in DNS ? 


kjn>> the node was NOT registered successfully, you can tell that by the 
      fact that the address does not get returned when you issue a
      DIRECTORY command.

      documented in the release notes, you will find mention of a short
      term anommaly where MCC cannot determine when we have added an
      entry to the namespace and when we have augmented an already 
      existing entry.  Therefore, the entry always gets written into the
      namespace, even when the REGISTER fails.  You must follow a failed
      REGISTER with a DEREGISTER or ERASE.

kjn>> it appears, from the symptoms described that the access problem is
      not with the global entry itself, but with the backtranslation tree

      you must also have read/write/delete access to the DNA$BackTranslation 
      directory and all of its children

    Thanks for the pointer, the problem was access rights to the area
    subdirectory of DNA$BackTranslation. What I don't understand though
    is why it worked ok with the IFT kit, as the only directory I modified
    when I installed the EFT kit was DNA$Nodes which became DNA$Node ?

    �hR.

HI,

So okay note 39.0 DOES specify  the area number for :
  .DNA$BackTranslation.<area>  in HEX  
It still took me two days to figure out that I was using decimal #s!
This needs more emphasis.
As asked before, DNS NEEDs to be documented for MCC --ALL the other products
don't use the p4-p5 dirs/objs.

How about handing out Stan Goldfarb's tools early for the folks that are using
private namespaces. I was willing to write a com to register nodes but now
I also have to create HEX DNS directories  -ugly.

===Steve