🚀 go-pugleaf

Hello,

We have a set of existing APPC appliciation which we would like to convert
to TCP/IP sockets. The applications in question run NS/DOS under Windows
and talk to APPC/MVS. They are very simple (only one-to-one conversations).

Writing a simple sockets server program on MVS is easy; however, I
see two administrative problems implementing a sockets solution:

(1) Before a client connects to a server program, the server program
must be running. As far as I know, there is no such thing as an inetd
- which would schedule servers on demand - in TCP/IP for MVS.

(2) The server program must run under the security context of the connecting
user. Of course, we would like to avoid to ask for userid/password each time
a connection is made; but we must take care not to break security rules (e.g.
store an unencrypted password on the PC).

Both these issues are no real problem with APPC; APPC/MVS has a scheduler,
and an NS/DOS user can specify a userid/password pair which is sent to a
particular partner node each time a conversation is allocated.

However, we would like to use sockets because we have more options for
client software on PCs (and Macs; NS/DOS is a memory hog and not 100%
stable under Windows).

Any ideas?

-- 
Peter Karrer                                   pkarrer@bernina.ethz.ch