The Question is:
I have a client-server application based on sockets running on UNIX and now I'm
porting this application to OpenVMS. The problem is the server (daemon)when a
accept a new connection should launch a ".com" procedure (I'm using vfork and
execvp), but in thi
s point the socket on the client side is closed. Why the socket is closed on
the client side (the client is a PC) ?
I have tested to launch a ".exe" program from the daemon and every thing is
working fine, the problem appears when I try to launch a ".com" prodedure. Is
the OpenVms system who close the socket ?
The Answer is :
The OpenVMS Wizard will assume this is TCP/IP Services V5.0A with
the current ECO, or later.
This would initially appear to involve differences in the run-time
environment between a command procedure and an executable image.
Topics 3995 and 2474, and the auxillary server might well be of interest.
When contacting the Compaq Customer Support Center for assistance in
resolving this, the particular sequence of executable code involved
here will likely be of interest.