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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2955.0. "%NONAME-E-NOMSG MESSAGE NUMBER 02DBC002" by WONDER::BENTO () Tue Jun 19 1990 16:24

    
    	Some USERS are trying to create remote/detached windows across
    	clusters of which thay are members and have valid accounts on
    	by using the following;
    
    	SET DISPLAY/CREATE/NODE=nodename
    	CREATE/TERM/DETACH
    
    	What results is the following error message;
    
    	%NONAME-E-NOMSG	MESSAGE NUMBER 02DBC002
                                           
    	Other USERS, myself included, have no trouble!
    
    	The systems in question are running VMS5.3 and 5.3-1
    
    	Any clue to what the message means?
T.RTitleUserPersonal
Name		DateLines
2955.1forgot some info...WONDER::BENTOTue Jun 19 1990 16:363
    	I forgot to mention that these nodes are satellite members
    	of LAVc's that use to be members of the other cluster that sends
    	the error message back.
2955.2CLUSTER_CONFIG not doing its thing?WONDER::BENTOTue Jun 19 1990 16:4913
    
    	Sorry to have bothered anyone with this as I have found the
    	problem or at least the solution.
    
    	Seems that the removal of a satellite using CLUSTER_CONFIG.COM
    	does not completely remove all network information about a previous
    	member.  What I tried was doing a purge and clear in NCP of
    	the satellites attributes on its former bootnode and only defining
    	the normal noade and address information.
    
    	Then had the USER try creating windows.  It worked!
    
    	Hope this helps someone.
2955.3LESLIE::LESLIEAndy, CS Systems Engineering/VMSTue Jun 26 1990 05:307
    This message means that they hadn't got access set up correctly -
    perhaps some nodes in the cluster hadn't enabled cluster alias
    incomibg/outgoing and they were just using the cluster name in the
    Customize/Security menu?
    
    
    						- andy
2955.4No cluster alias everDECWIN::FISHERPrune Juice: A Warrior's Drink!Thu Jul 05 1990 13:044
re .3:  You can't use the cluster alias in customize security regardless of
whether the alias is set up right.

Burns