HP OpenVMS Systems

Sharing TCP/IP Sockets?

» close window

The Question is:

 
Hi Wizard,
 
I am porting a UNIX TCP/IP application to OVMS.
My application has a deamon which receives control from a client
application. Once the deamon receives control he accepts the socket and
creates a child process using vfork. And then it does a execp to process the
request. In the execp attached process AL
L socket calls to the accepted socket return with a code 65535. My question:
is there a problem in shareing sockets in parent and child processed. If so
how do I pass the socket to the child process. I am passing only the socket
number in this case 3 to t
he child process.
The same application on OVMS 7.1 works however my customer has the 6.2
version and we cannot able to upgrade quickly.
 
Thanks for your help
 
Bahram Djavidan
ZING/SOFT GMBH Berlin
 
 

The Answer is :

 
 
There are various concurrent server design methodologies available
for OpenVMS Systems using TCP/IP Services sockets.  The third option
here shares a socket, via sys$qio calls.
 
There are (at least) three ways:
 
1. Using the Auxilliary Server
 
2. Using DECthreads
 
3. Using QIO system services
 
Auxilliary Server Design Methodology

  

     

     
answer written or last revised on ( 20-MAY-1999 )
     
» close window