How to create a LAT socket and address it?
For creating the socket, should it be something like :
lats = socket(PF_LAT,STREAM,AF_LAT);
or?
Were can I get some information about this? How to
address a LAT-socket with connect, bind, read, write?
I need information about the most common socket commands
like : socket, setsockopt, bind, connect, read and send - for
LAT usage...
Please...
Thanks!
Greetings Fredrik.
--
Cheers,
+OpenVMS [Sys|Net] HardWorker .......................................+
Russia,Delta Telecom Inc, Cel: +7 (901) 971-3222
191119,St.Petersburg,Transportny per. 3 116-3222
+http://starlet.deltatel.ru ................. SysMan rides HailStorm +
Use LATCP to create to create a device ("port"), then open, read, write
and close like any other device.
...or did I miss your point?
--
David J. Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Aren't the LAT protocol implemented for
sockets? Maybe the socket functionality
were designed to support LAT in the future?
Is the QIO Interface the 'only' way to access
LAT driver?
Someone who have a sample C source that
are using LAT?
Thanks!
Greetings Fredrik.
"Fredrik Blomstedt" <fredrik....@bnearit.se> skrev i meddelandet
news:3cce5872$1...@news.wineasy.se...
Maybe if you need some of the more fancy features of
the QIO system calls, you might need to go that way.
Jan-Erik Söderholm.
Under Ultrix, and I assume, Tru64 LAT and DECnet Phase IV were
implemented via the socket concept, something UNIX programmers
were already familiar with, and failry easy to reach from C based
languages. (Anybody ever to to call socket() from a UNIX f77?)
Under VMS, programmers are more familiar with $QIO, something
failry easy to reach from any language.