On 10/26/21 7:27 AM, Patrik Schindler wrote:
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.
I didn't use PJ jobs ... I just submitted regular batch jobs to QUSRNOMAX.
I don't really understand what the queue is meant to do. A deposit
for communication between the socket listener and the peer
The data queue is used to hand the socket descriptor from the monitor
job to the worker job.
Each time the monitor job hands off a descriptor to a worker job, a new
worker job was spawned to take the place of the job being used.
I'm riding in the American Diabetes Association's Tour de Cure to raise
money for diabetes research, education, advocacy, and awareness. You
can make a tax-deductible donation to my ride by visiting
You can see where my donations come from by visiting my interactive
donation map ... https://mideml.diabetessucks.net/map (it's a geeky
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.