James writes:
> Instead of monkeying around trying to get COBOL to use BSD sockets, unless
> you have a version of COBOL which has pointers and memory allocation
> routines, I would just write the key functions needed a C routines callable
> from COBOL.

That works fine, and lots of people are doing it that way, however...

> > Can you write a Cobol program that uses BSD sockets??  I know, and have
> > used, NetIPC.  I'm an avid Cobol programmer at heart.  If I can use
> > sockets, that would be great!!

NetIPC and sockets are interfaces to the same thing (TCP), so you ought
to be able to do what you want *with* NetIPC.  Just because the thing on
the other end of the connection is using the sockets API to talk to TCP
doesn't mean that you have to do the same thing on your end.

There are a few functionality differences between NetIPC and sockets,
but generally I've found NetIPC to be more feature-rich and more "3000
like".

G.