Conference azur::mcc

    To validate that the DECnet Phase IV AM is actually working, issue some
    SHOW NODE4 (node name/address) all status requests, and maybe some
    other requests dealing with line or circuit.
    One reason for registering a node4 entity is so that a Phase V Fullname
    can be used in place of a Phase 4 node name. The only other reason for
    registering a node name is for the line entity and use of the ALL CHAR
    request. There's a previous note (a few down) when I mention that the
    line entity has an "orphaned" attribute (line speed) which is not
    supported by the entity but that the AM must support via the DNS
    namespace. If you don't register the line entity, you will receive
    an error on both the ALL CHARACTERISTICS and ALL INITIAL ATTRIBUTES
    requests.
    
    So you don't need to register the node names in order to test the AM to
    make sure that it's working ok. 
    If you issue various commands and things seem to be going well except
    for register node4, then the only thing I would suggest is qar the 
    problem.
    			Cindy
                             

>    To validate that the DECnet Phase IV AM is actually working, issue some
>    SHOW NODE4 (node name/address) all status requests, and maybe some
>    other requests dealing with line or circuit.

vanloo# mcc
DECmcc (T1.0.1)

MCC> show  node4  vanloo all char
Node4 vanloo
Characteristics
AT  7-SEP-1990 14:30:02


Internal Error Occurred in DECnet Phase IV AM.
                              VMS Error = %SYSTEM-F-ACCVIO, access violation,
                                          reason mask=!XB, virtual address=!XL,
                                          PC=!XL, PSL=!XL
MCC>

    Nothing appears in the DNS namespace when I attempt to register VANLOO.
    I think that is fundamental to the above not working. However I'm at a
    loss to know what is wrong with my DNS configuration. Again, is there a
    logfile for the REGISTER command? Is there trace that I can enable to
    find out my possible DNS problems?

    

    
    I'll ask an easy question, what type of system are you running on?
    (VS 2000...)
    
    jill
    

    Our system is an 8530. Thanks to Daryl Ball we have a new
    MCC_DNA4_AM.EXE that has fixed this. Brill, we're in the race.

    Cheers,

    Michael.

MCC> show node4 vanloo all char 

Node4 44.591 
Characteristics
AT  7-SEP-1990 17:05:28


Examination of Attributes shows:
                         Identification = "DECnet-VAX V5.4,  VMS V5.4    "
                     Management Version = V4.0.0
                         Incoming Timer = 45 Seconds
                         Outgoing Timer = 60 Seconds
                         Incoming Proxy = Enable
                         Outgoing Proxy = Enable
                            NSP Version = V4.1.0
                          Maximum Links = 300 Links
                           Delay Factor = 80
                           Delay Weight = 5
                       Inactivity Timer = 60 Seconds
                      Retransmit Factor = 10
                        Routing Version = V2.0.0
                                   Type = EndNodeIV
                          Routing Timer = 600 Seconds
                Broadcast Routing Timer = 180 Seconds
                        Maximum Address = 1023
                       Maximum Circuits = 16
                           Maximum Cost = 1022
                           Maximum Hops = 30
                         Maximum Visits = 63
                           Maximum Area = 63
           Maximum Broadcast NonRouters = 64
              Maximum Broadcast Routers = 32
                    Maximum Path Splits = 1
                      Maximum Area Cost = 1022
                      Maximum Area Hops = 30
                        Maximum Buffers = 100
                            Buffer Size = 576 Bytes
                     NonPrivileged User = "DECNET"
                         Default Access = Both
                         Pipeline Quota = 10000
                    Alias Maximum Links = 32
        

In response to .2 the problem has been addressed/located and a fix has been
implemented.

      Darryl, where is the fix? Do I need to copy the savesets or is there
    somewhere I can just get the AM.exe ?
    
    thanks!
    

    
    The next kit to be released will include the fix. This is due out
    next week. Sorry for the inconvenience of waiting but it is preferrable
    that we only have clean installs during field test.
    
    If you are experiencing the same type of access violations and can
    not wait please send mail to Mike Densemore or Darryl directly stating
    your request and reasons.
    

    
    re .-1
        
    >> If you are experiencing the same type of access violations and can
    >> not wait please send mail to Mike Densemore or Darryl directly stating
    >> your request and reasons.
    
    Gee.  I get back from OIW and find out that Jill thinks I'm pretty
    dense too :-}
    
    					Mike *DENSMORE*

	Has this problem been fixed in the 17th Sept Release?  We are still
	getting internal errors in the DECnet phase IV AM module with this
	release.  NB. The date of the MCC_DNA4_AM.EXE is 4-SEP-1990.

	Regards,

	Alan

	

    
    The SSB .exe is dated the 11th of september so it is possible the
    fix is not included until that version. I will request clarification
    for you.
    

    Darryl Ball says that it didn't get in until the SSB kit.