🚀 go-pugleaf

In article <1993May21.171454.14557@visionware.co.uk>, chetanm@visionware.co.uk (Chetan Mistry) writes:
|> 
|> Hi all,
|> 	I'm having a few problems talking to objects on VMS. I have registered
|> a server on our VMS box using NCP.
|> eg.
|> ncp> set object echo1d file echo1d.exe number 250
|> ncp> show object echo1d
|>  
|> Object Volatile Summary as of 21-MAY-1993 17:31:53
|>  
|>    Object   Number  File/PID                   User Id          Password
|>  
|>   ECHO1D       250  ECHO1D.EXE
|> 
|> This "echo1d.exe" loops in a while loop reading from stdin and writing
|> to stdout.
|> 
|> On an ultrix machine running decnet I have the following client 
|> program ("bacon" is our VMS host) :-
|> 
|> main()
|> {
|> 	int sock;
|> 
|> 	sock = dnet_conn("bacon", "#250", 0, 0, 0, 0, 0);
|> 
|> 	if (sock < 0) { 
|> 		nerror("dnet_conn"); perror("dnet_conn"); exit();  
|> 	}
|> 	fprintf(stderr, "Connected...\n");
|> 
|> 	write/read operations on sock ......
|> }
|> 
|> Running this client I get :-
|> % a.out
|> dnet_conn: Connect failed, No response from object
|> dnet_conn: Connection timed out
|> 
|> The server "echo1d.exe" is executed because I have configured it so that it
|> echo's a message to a file in the very first line.
|> 
|> What's happening ? Whats the client expecting from the server ?
|> 
|> TIA
|> Chet [email: chetanm@visionware.co.uk]
|> 
|> 

	It's quite possible that the error message is correct. I've had lots of
problems with timeouts on our DECnet network. You can use ncp to show you the 
timers and errors that have occured. Tell ncp to "show count node abc" where 
abc is the node you are trying to communicate with. Also tell ncp to "show exec char"
and see what the incoming and outgoing timers are. You can change them with
a "set incoming timer", "set outgoing timer", "define incoming timer" etc.

-- 

Glenn Horton            SAS Institute Inc.
sasdgh@unx.sas.com      SAS Campus Dr.
919-677-8000 x6640      Cary, N.C. 27513