Conference bulova::decw_jan-89_to_nov-90

429.0. "SCSNODE Problems ??!!" by DARTS::PELKEY (If my ancestors could see me now!) Fri Mar 17 1989 10:32

    Hello,
    
    	hope someone can help,,
    
    	I've propagated a 5.1 system which had DECWINDOWS already
    installed.  
    	
    	In tailoring the system, I'm trying to change SCSNODE to
    correspond with the node name that my VAXStation is known as.
    
    	However, If I leave SCSNODE blank, or change SCSNODE to my
    VAXStations node name, Something in the startup dies, complaining
    about the node not being reachable.  This ofcourse prevents the
    workstation from comming up.
    
    If I boot conversationaly, setting SCSNODE back to the orginal name,
    everything comes up fine, including DECNET (and this is where it gets
    wierd) as the node that I want it to be, (node name should be PELKEY
    and the address is 11.890, however I've blanked out SCSYSTEMID and
    set SCSNODE back to the old name)
    
    	What am I doing wrong ?

    You should be careful that the SCSNODE matches the NCP executor node.
    If it is not the case, DECnet won't start, thus DECwindows.
    
    Pierre.

JBCSYSQUE.DAT has node information that he retrieves from SCSNODE
when batch queues are initially created.  A $SHOW QUEUE will probably
have an old node name associated with it.  Simply delete the old queue, and
then restart the queue manager.

Regards,

          == ken miller ==

    Well thats part of the confusion,,,,
    
    SCSNODE should be PELKEY, which is what the Executor name is...
    
    thanks..

    <<  -< Probably an old QUEUE >-

    	BINGO !
    
   
    Thanks.