In <[log in to unmask]> [log in to unmask] writes:

> > Is it possible for a client PC to connect to a NetIPC socket on ah > hp3000
> using either HP's old PC/NetIPC under officeshare, or Berkeley > sockets?  We
> have several client/server programs that run with > officeshare and we are
> looking to migrate to
>  windows nt and it would be > nice if we (I) didn't have to rewrite the server
> programs.  Any > suggestions?

Bill,

Long answer:
  NetIPC and Berkeley sockets are just two programmatic interfaces to
(basically) the same functionality. Though the procedure names you call are
different, and there are some minor options that each have that don't map to
the other, an application (client or server) can be written using either API
and perform the same functions. On the 3000, Berkeley socket calls are
typically used in 'c' programs, since the api was designed for 'c' and common
throughout the Unix world. The NetIPC api is easier to call on the 3000 if
you're using other languages; Cobol/Pascal/Spl(ash)/Fortran/etc, but the
calling sequences are unique to HP3000s so you can't just pick up a book on
NetIPC at the computer bookstore like you can for Berkeley sockets.

Short answer:
  You can write your own server programs using whatever api you want. It
works (we've done lots of servers on the 3000), but it's not a trivial
program. To get optimum performance you need to deal with nowait i/o issues,
ideally keeping a pool of suspended processes waiting to be given a socket
id from a 'father' server process...

Perhaps better solution:
  Look into Samba. It lets your PC users access/share files on the HP3000
(and vice versa) - and it's free. Read details on how to use/install it from
www.3k.com (follow the link to the public domain software area - there's a
link to the samba page).

                   -Chris Bartram