Re: Remote SQL job priority

Brian,

bdietz@3x.com wrote:
> 
> 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.

Yes, you could accomplish this with an exit program, but as you
guessed, the overhead would be similar for a CHGJOB via strored
procedure or an exit program.  

Remember that a server job is typically reused 200 times by
potentially different users/devices, so remember to treat each new
request as if it were a new job (or else check if it's a request
from a new user).  Also, with an exit program you can only affect
the job prior to the server invocation (not after) so you would
want to re-set the priority at the beginning of each SQL init.

In any case, If you run a test of 10,000 calls, I think that
you'll find the performance impact to be trivial.

jte


--
John Earl                               johnearl@400security.com
The PowerTech Group                     206-575-0711
PowerLock Network Security              www.400security.com
--
+---
| 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
+---