On 3/11/26 3:53 PM, Konstantin Kolinko wrote:
. . .
# Set job priority to standard for interactive (interactive - 6) by using
# the interactive priority - 6, the helper threads that respond to requests
# will be running at the same priority as interactive jobs.
COMMAND='chgjob job('$JOBNAME') runpty(6)'
. . .
Thanks. I saw the comment in the code, but omitted it when quoting, to
avoid risking having the long comment lines wrap, obscuring the meaning
of the excerpt.
And I have no idea how to go about finding the commit that put that
block into the code, so thank you VERY MUCH for doing that.
It sounds like whoever did commit 421604 didn't understand how run
priority (RUNPTY) works on IBM Midrange boxes. The range is from 1
(highest priority, preempts everything) to 99 (lowest priority,
preempted by everything) As I said, most terminal sessions run at
RUNPTY(20), while most batch jobs run at RUNPTY(50). It's considered
extremely unusual (I've been working with IBM Midrange boxes for 3
decades now, and only just now was made aware of it) for anything other
than the console to run at priority 10 or better.
It's entirely possible that only that individual would be able to
explain what the CHGJOB RUNPTY(6) is doing there.
And I'm not entirely sure how that interacts with threadPriority in
Java, either. Nobody has complained about the JVM job on their Tomcat
server going "runaway" with that RUNPTY(6).
--
James H. H. Lampert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
