🚀 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 ?

It sounds like your server is expecting stdin and stout to be the DECnet link.
That's not how DECnet-VAX works.  When the program that is your server object
runs, logical name SYS$NET points to the DECnet link.  You must open SYS$NET
as a file for input and/or output.  This performs two functions:  first, it
accepts the DECnet logical link and completes the connection, and second, it
lets you communicate over the logical link.

Since your server never opened SYS$NET, it never completed the network
connection and eventually the client side timed it out, with the results that
you saw.

--PSW