[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2615.0. "DECnet OSI Problem ?" by LISA2::SEPULVEDA (The Sunshine People) Wed Apr 09 1997 23:46

T.RTitleUserPersonal
Name
DateLines
2615.1Some answersIOSG::STANDAGEMy hovercraft is full of eelsThu Apr 10 1997 13:4868
2615.2About the dtssVELI::KORKKOThu Apr 10 1997 23:0918
        Re .0
        
        About the DTSS. Maybe there are not any DECdtss servers in that
        LAN. If this is the case, you can either easily configure your
        system to supply the time or maybe the easiest thing to is just
        to block the event completely, like
        
        $ mc ncl block event dispatcher * global filter -
        	((Node, Dtss), Too Few Servers Detected)
        
        Of course effect of this command would disappear at next reboot
        so he proper (permanent) procedre would be
        
        1) copy sys$manager:net$event_local.template  to 'same'.ncl
        2) then edit that file to contain mentioned "block ..."
        3) execute the file $mc ncl @sys$manager:net$event_local.ncl
        
        _veli
2615.3about SYS$NODEVELI::KORKKOThu Apr 10 1997 23:1624
        Further, about the SYS$NODE as well as SYS$NODE_FULLNAME
        
        The proper way to fix these is to execute 
        
        $ @sys$manager:net$configure advanced
        
        and choose option 2, i.e. "Change namespace/naming information"
        (or something like that...). Go through the stuff and voila,
        SYS$NODE as well as SYS$NODE_FULLNAME are defined properly.
        
        After this is done, check whether there exists (right now!, but
        not after next reboot) a file
        SYS$MANAGER:NET$STARTUP_RENAME.COM.
        
        Check that file and if this file appears to rename your node
        back to something like empty name, just delete this file (before
        rebooting).
        
        Like .1 said, proper value of SYS$NODE is VERY ESSENTIAL to many
        products. Two phase commit protocol (TP_SERVER), LAT, Infoserver
        Client are few which fail to start if SYS$NODE is not defined
        properly.
        
        _veli
2615.4Lack of SYS$NODE is a symtom of a bigger problemTAY2P1::HOWARDWhoever it takesFri Apr 11 1997 01:1016
>        After this is done, check whether there exists (right now!, but
>        not after next reboot) a file
>        SYS$MANAGER:NET$STARTUP_RENAME.COM.
    
    I think it's best to check this file whenever you find it.  I found
    that EWS$DEFINE_NODE creates one of these files to rename your server
    to the name of the latest EWS node you added!  The problem is that you
    don't look for the file, and it only gets executed when you restart
    DECnet (or maybe only when you reboot).  Its syntax is fairly obvious
    to look at, so if it isn't doing what you want, delete it. Getting the
    node back to its correct name is a pain.
    
    Note also that many procedures check the existence of SYS$NODE to see
    if DECnet is up.  So don't define it unitl DECnet is up.  
    
    Ben