🚀 go-pugleaf

In article <3lt0m6$dkh@cpcug.org>, kbennett@cpcug.org (Keith Bennett) writes:
<This question pertains to DEC Pathworks for OS/2.  The literature
<mentions communicating over DECNet via sockets.  Assuming a host
<created this socket, how would I connect to it?  Is there an API for
<that?  I have been working with TCP/IP sockets for a while.  How
<similar are DECNet sockets to TCP/IP sockets?

	All PATHWORKS DECnet products support a BSD 4.2 compatible 
socket interface as the native API for DECnet.  This interface is documented
in the PATHWORKS Programmer's Reference Manual.

	PATHWORKS V5 also includes Winsock support for DECnet.

<We have a turnkey product that connects with customers' minis and
<mainframes and receives information from them.  Usually it is a
<TCP/IP network and we use sockets but one customer has advised us
<that their network is a DECNet network.
<
<We are aware that TCP/IP may be available on the customer's DEC
<machines but would like to know about providing native support for
<DECNet.

	Be aware that though the sockets interface is protocol independent,
doing certain name resolution functions is protocol dependent.   A program
the uses DECnet protocols as well as TCP/IP, would have to be careful in
the relm of name to address lookups.  The PATHWORKS socket interface
has a unique set of functions for this. (eg: getnodebyaddr(),
getnodebyname(),etc...)

<If possible, email would be preferred.  Thanks for any help.
	
	More PATHWORKS expertise is availible in the newsgroup:
	
	vmsnet.networks.desktop.pathworks

<--------------------------------------------------------------------------
<Keith Bennett                             Bennett Business Solutions, Inc.
<Silver Spring, MD USA                     OS/2 & DOS Software Development
<kbennett@cpcug.org                        (301) 871-7696

-- 
Dave Mitton,					mitton@dave.enet.dec.com
PATHWORKS Client Eng., NOS Engineering, Digital Equipment Corp.