We have been using c programs to fork processes on MPE, but open the
database in each forked process.  We set a fairly low limit (3-5) on the
number of concurrent forked processes.   These programs do not crash the
system, or crash for any other reason.



Peter writes:
> Luckily, I only need to implement a Server in COBOL :-).

If your server will only maintain one connection or handle only one request
at a time, then you'll be OK.  Otherwise, you'll want to look for another
Interex article called "Serving Sockets without a fork".  This described a
way to use the CREATE and ACTICVATE intrinsics to launch multiple jobs per
request.  When I tried it, it seemed to drop some requests under a heavy
load (that would be me clicking the reload button as fast as I can).  The
reason the author is avoiding the fork is twofold: you can crash MPE with a
fork without the right patches and the new process cannot access any open
databases.  Well I shouldn't say can't, but I don't know how Image could
tell the two processes apart.

Mark

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *