[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

3996.0. "IP Autoconfig NOT working on DECnet/OSI PhaseV" by OSLACT::BJORN (Why are diper's so wet?) Fri Oct 30 1992 06:54

Hi,

I'm now starting to worry real seriously about DECmcc implementation on top of
DECnet/OSI for VMS. Some weeks ago I were studying the Event Dispatcher and the 
DECmcc use of event reporting, and found that it wasn't possible to get DECnet 
Phase IV Events logged in DECmcc on top of DECnet/OSI for VMS.

Now I'm trying TCP/IP Autoconfig, and I've found two problems.

DNS V2.0 doesn't include DNS$CONTROL.BIN or DNS$LIB.EXE, and MCC_IP_AUTOCONFIG 
does a check for these files, and returns with an error if these files are not
present on the system. Furthermore, if you comment out these checks from the 
procedure, the DNS$CONTROL SHOW DIR namespace_name:.node4_Dir.dir. fails becaues
DNS V2.0 doesn't allow a "." after the directory, but the 
MCC_AUTOCONFIG_PREFIX.DAT file requires the dot "." after the directory name.

This doesn't work

DNS> SHOW DIR .NWO.MCC.DOMAIN.		<-- the trailing dot is included

This works

DNS> SHOW DIR .NWO.MCC.DOMAIN		<-- the dot is not included

Your response to this?

Any more non-conformant bugs?

Bj�rn Olav Haugom
T.RTitleUserPersonal
Name		DateLines
3996.1ANyone else seeing this?OSLACT::BJORNWhy are diper&#039;s so wet?Thu Nov 12 1992 04:1311
How many of you all runs DECmcc on top of DECnet/OSI for VMS?
How many of you are running the "real" DNS V2.0 implementation, i.e. with DNS 
V2.0 database?

The problem I described in .0 has to do with DNS$CONTROL.BIN not existing in V2
and the same goes for DNS$LIB.EXE. 

Am I the only one seeing this problem? 

Bj�rn Olav HAugom
3996.2Does look like a bugTOOK::MINTZLKG2-2 near pole X3, cube 6072, dtn 226-5033Thu Nov 12 1992 07:303
You may be ahead of the crowd in discovering this problem, but it still
looks like a problem.  Could you please enter a QAR?  See note 7 for info.
3996.31st half of .0 already QAR'd; Please QAR 2nd halfTOOK::FIGWERUlla Figwer LKG2-2/T2 x226-7858Fri Nov 13 1992 10:3622
                      
    Hello,
    
    Please note that a QAR has already been filed for the first half
    of Bj�rn's note.  The associated work-around is documented
    in note 3667.1 (the V1.2 QAR number is in 3667.2).  That covers
    use of DNS$CONTROL.BIN, etc.  

    The second half of the note may be a new problem and should be
    QAR'd.  The version of DNS which we used for testing did allow
    the trailing dot for a DNS SHOW DIR.

    Validation of the prefixes in MCC_AUTOCONFIG_PREFIX.DAT was added
    to try to reduce the chances of registration errors that could
    be easily avioded.  Namely those caused by missing DNS directories
    to match the prefixes.
    
    Modifying the validation routine to removing the trailing dot from
    the prefix should be relatively easy.
    
    Ulla