Hello David,

thanks for your input!

Am 26.10.2021 um 16:09 schrieb David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

Do I get this correct? You had a socket listener running (as PJ?),
and dynamically spawn workers?
I did something like that for my TCP servers.
Although I had a user configurable number of workers pre-spawned.

Like the Apache httpd does.

I didn't use PJ jobs ... I just submitted regular batch jobs to QUSRNOMAX.

I understand. But submitting these would impose a penalty in terms of CPU spikes and time until the batch job is ready to run, and can continue servicing requests from the socket connection. As said, I want to make my idea run as efficient as possible on my 150. :-)

I don't really understand what the queue is meant to do. A deposit
for communication between the socket listener and the peer
application?
The data queue is used to hand the socket descriptor from the monitor
job to the worker job.

The socket descriptor is AFAIR just a number. Why not pass it as a parameter? Or is "entry arrived in the *DTAQ" the signal for the already running worker to, well, start work?

So each worker listens to the *DTAQ waiting until there is an entry in the *DTAQ to retrieve?

:wq! PoC


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.