RE: QZDASOINIT job running in interactive priority

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

Agreed, but for this to be the actual problem the CPU would have to be
running at 100% nearly all of the time and no task with a priority
greater than 20 would ever get any CPU.  Since CPU constraints are
usually easy to diagnose my guess was that this box is more likely
memory constrained.

If the task priorities are changed to favor the interactive users the
next complaint will come from the web users.  If the system is not sized
properly for its workload the solution is *SPENDMONEY*

The best bet would be to profile the interactive transactions to find
the bottleneck, see:
http://www-912.ibm.com/s_dir/slkbase.nsf/90402cf55bdbcdc786256ffd0076ec0
5/b488791484788c8e8625661300723456?OpenDocument&Highlight=2,profile,inte
ractive,transaction

That should tell the story.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Wed, 15 Mar 2006 17:29:23 +0000
from: vhamberg@xxxxxxxxxxx
subject: RE: QZDASOINIT job running in interactive priority 

The post said at priority 20, not in the interactive pool. Is that
right? So the issue is that interactive users and JDBC clients are given
the same level of access to the CPU.

-------------- Original message --------------
From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> 

> The QZDASOINIT jobs should not be running in the interactive pool. 
> 
> If they are truly constraining your interactive users it is probably 
> due to QPFRADJ stealing memory from the interactive pool. You might 
> try "pinning" memory to your interactive pool (use WRKSHRPOOL >> F11) 
> or your system might just need more memory.
> 
> What does WRKSYSSTS show? 
> 
> Regards,
> 
> Scott Ingvaldson
> iSeries System Administrator
> GuideOne Insurance Group
> 
> 
> -----Original Message----- 
> date: Tue, 14 Mar 2006 15:40:28 -0600 
> from: "Lim Hock-Chai" 
> subject: QZDASOINIT job running in interactive priority 
> 
> Our web team has a multi threaded jobs that basically do jdbc
connection 
> to AS400 and call a store procedure to update our database. These jobs

> (about 36 of them) are long running jobs that calling the store 
> procedure in loop. 
> 
> The problem we are having is that server jobs QZDASOINIT are running
at 
> priority of 20 which are cause these long running job to slow down
AS400 
> interactive user. Is there a way to change the running priority for 
> QZDASOINIT job for those jobs only?