I believe the run priority and time slice are defaulted by the job “class”. So, do a WRKSBSD on the subsystem these jobs run in, use the option to display the prestart jobs and find the class. Then take a look at the class (WRKCLS) to see how it is defined. Personally, I would not modifiy an IBM supplied class – but you could create a new one. Did you mean QZDASOINIT? It uses class QPWFSERVER, which already runs Priority 20 and a timeslice of 3000.
You don’t really want to run lower than 20…
Of course, my gut feeling is don’t muck around with the settings – but take a look at the queries. There may be some way to make your queries more efficient.
Your information about the class controlling the run priority is correct, but our problem is that we want to be able to run QZDASOINIT at different priorities, depending on the application that is submitting the query, and there is no way to dynamically change the class (and the run priority) that I can see.
One thought I had was to create additional prestart jobs by cloning QZDASOINT and using different classes with different run priorities, but how do I get ODBC to use these new prestart jobs?