Conference azur::mcc

I hope you're working with the corporate DNS folks on this...

    
>    One additonal complication - our DNS and DECmcc installations are
>    currently on two separate nodes.  If possible, I'd like to keep it that
>    way, and have DECmcc node pass the DNS node a hunk of DCL containing
>    DNS$CONTROL commands.  If you're having a kitten laughing about this
>    point, just say so, and I'll (hopefully) install DECmcc on the DNS node.
    
Do you mean the DECdns server is on a different node?  That's no problem, but 
you do need the DNS clerk started on the DECmcc node.  I think what you want to 
create is an MCC script, since REGISTER, etc sends the commands. to DECdns for
you.

Also, why should you need to delete the node object?  You should just be able to
add the additional information.

>>    One additonal complication - our DNS and DECmcc installations are
>>    currently on two separate nodes.  If possible, I'd like to keep it that
>>    way, and have DECmcc node pass the DNS node a hunk of DCL containing
>>    DNS$CONTROL commands.  If you're having a kitten laughing about this
>>    point, just say so, and I'll (hopefully) install DECmcc on the DNS node.
    
>Do you mean the DECdns server is on a different node?  That's no problem, but 
>you do need the DNS clerk started on the DECmcc node.  I think what you want to 
>create is an MCC script, since REGISTER, etc sends the commands. to DECdns for
>you.

Why not just copy the DNS Setup command procedures from MCC_COMMON: to the DNS
server and use them? 

  Directory MCDOUG::DUA1:[MCC]
        
        MCC_DNS_BASIC_SETUP.COM;1
        MCC_DNS_SETUP.COM;1
        MCC_DNS_SETUP_DIR.COM;1
        MCC_DNS_SETUP_IDP.COM;1
        
        Total of 4 files.

/doug

.1> I hope you're working with the corporate DNS folks on this..

Goodness, yes.  I'm working closely with, and with some degree of blessing from
John Regan.  Right, John?  John?  

.1> Do you mean the DECdns server is on a different node? 

Yep.

.1> That's no problem, but you do need the DNS clerk started on the DECmcc node.

I'll give that a whirl, thanks!

.1> I think what you want to create is an MCC script, since REGISTER, etc sends
the commands to DECdns for you.

Ah, hah!  Where can I read up on the creation of MCC scripts?

.1> Also, why should you need to delete the node object?  You should just be able to
add the additional information.

Sounds great to me!  I probably mis-understood John's directions; I thought he 
had told me to, through my site DNS administrator, delete the node object, then
add it back with DECmcc, thus getting the correct attributes and backlinks.

So how can I just add the stuff that DECmcc requires?  I know I need to add
additional attributes?  Is that it, or do I need to create (insert eerie music
here) backlinks?

.2> Why not just copy the DNS Setup command procedures from MCC_COMMON: to the DNS
server and use them? 

  Directory MCDOUG::DUA1:[MCC]
        
        MCC_DNS_BASIC_SETUP.COM;1
        MCC_DNS_SETUP.COM;1
        MCC_DNS_SETUP_DIR.COM;1
        MCC_DNS_SETUP_IDP.COM;1

These procedures don't allow me to (1) modify the existing DNS node objects, as
.1 suggested, nor (2) delete the existing information in DNS, and add it back
again.  The procedure to take a NCP SHOW KNOWN NODES output and turn it into
DECmcc REGISTER commands has promise, though I don't want to do this for all
nodes, but only for those on my site.

Thanks for the suggestions.  We're getting close!
tl

    Let me clarify some things that you "should" be able to do given
    appropriate access.
    
    If there are entries in the namespace for phase IV nodes allready,
    a REGISTER from DECmcc will ADD the needed attributes to the object.
    
    All the softlinks should already be there from the original entries.
    
    Note, there are two sets of almost identical tools for adding decnet
    nodes to the namespace available. One set comes with PHASE V DECnet
    and will put the node in the namespace (the object), put in
    the synonym, and add the backtranslation entry. It doesn't add any
    DECmcc stuff.  The second set comes with the DECmcc kit. It does all
    of the same things as the above one (they shared common sources...)
    and in addition, puts in the DECmcc attributes.
    
    As for MCC scripts, all that is meant is a com file with DECmcc
    commands in it so you can use an edititor to prepare it and do lots
    of cut and paste to minimize typing. The file might look like;
    
    REGISTER NODE4 .DNA_NODE.NETS SYNONYM NETS
    REGISTER NODE4 .DNA_NODE.TOOK SYNONYM TOOK
    REGISTER NODE4 .LKG.S.MIVC    SYNONYM MIVC
    REGISTER NODE4 .LKG.S.DELNI   SYNONYM DELNI
    REGISTER NODE4 .ZKO.S.VORTEX  SYNONYM VORTEX
        etc...
    
    It is most likely that the problems you are having are related to
    access control to the namespace. You do need rwd access to the objects
    in order to add or modify or delete attributes. If you don't have the
    right access to all the parts of the namespace that DECmcc needs to
    access, you may have a partial registration done that perhaps DECmcc
    cannot undo if it doesn't have the authority.
    
    Does this clear things up more (or did I make it more confusing...:-)
    
    s/rob
    

>    If there are entries in the namespace for phase IV nodes allready,
>    a REGISTER from DECmcc will ADD the needed attributes to the object.
    
Hi Rob,

Have things changed lately? The last time I looked at this stuff close (which
admittedly was quite some time ago) MCC wanted to delete the object and then
re-register it, or so I thought. I had actually put in a QAR suggesting a
action more along the lines you describe (add attributes) but I didn't hear
if it ever got changed.

thnaks,
brad...    

    Hmmm, I was sure it worked as I described in time for the V1.0 SSB kit.
    Claudia and I worked on the interoperability of the Transition tools
    and DECmcc for quite a while (drove the developers nuts).
    
    I must admit that I haven't tried it recently... Oh!!! I just
    remembered how it worked... If you have nodes in the namespace
    from use of the transition tools, the DECmcc tools will add the
    attributes, not DECmcc itself.
    
    Claudia, you following this? DO you remenber the names of the tools?
    
    s/rob

Rob,

The tool you want is NET$DNS_REGISTER.COM, it relies on
the use of DNS$CONTROL.EXE, NET$MIGRATE.EXE, and 
NCL to perform it's functions.  Mostly. it will 
work fine for NODE4s, but not for NODE's ... at
least not completely due to the DNA$TOWERS attribute
being provided by OSI session control, but that's
OK.   Note that the MCC_DNS*.COMs are early
and modified versions of the above.

If MCC wants to use it, they will have to obtain the 
code from Stan Goldfarb ... or better yet, get him to
add DECmcc hooks to add/modify/remove the mcc required 
attributes.... the hook might be a simple as a check
for a MCC DIRECTOR logical like MCC_COMMON and a question
in the add/modify/remove like 'Add DECmcc specific 
attributes? [Yes]' ... etc.   The hook would give you
one set of source code/maintenance and save development
time/testing.   

Is that what you had in mind, Rob?

/Claudia