Remote SQL job priority

I am trying to figure out a way to separate local(client access) ODBC/SQL
requests from remote (another AS/400) requests.

Right now they are all running at the save priority in the same
subsystem(qserver).  The remote jobs are coming across
the local LAN from an AS/400 webserver and we want those to run at a better
priority than the local ones.

I know I can change the prestart job to change the runpty and memory pool,
but that affects all the jobs.

Is there a way to have the remote jobs run at a different priority from the
local jobs?
I have thought about using stored procedures and within there doing a
CHGJOB.  But I don't want to "waste" cycles
on that.

Would a exit program be the way to go?  I would think that the extra
processing would be about the same
overhead as a CHGJOB in the stored procedure.


Thanks,
Bryan Dietz



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---