Re: Run priorities on Tomcat server jobs

The job priority is determined by the job description and the routing step invoked. Includes the time slice (which on later
System is not quite the concern, but on older boxes has a significant effect).

So first what job description is on the job then check the routing data which will determine the job class. The class has the initial priority.


Jim Oberholtzer
Agile Technology Architects

On Mar 11, 2026, at 1:17 PM, James H. H. Lampert via JAVA400-L <java400-l@xxxxxxxxxxxxxxxxxx> wrote:

We got a question from a customer.

On a Tomcat server, running on a Midrange box, the Catalina job has RUNPTY(50), but its JVM job, the QP0ZSPWT job, has RUNPTY(6).

For some reason, this customer has been manually changing the JVM job's RUNPTY to 23 (I'm awaiting an explanation of what exactly they are trying to do, and I've directed our support person to make sure they understand what the job is, and that a higher number means less priority).

For whatever reason, they want it to come up that way automatically.

Does anybody here have any insights that might be relevant?

--
JHHL
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.