× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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? 
> 
> -- 
> 
> 
> 
> DISCLAIMER: 
> This message and accompanying documents are covered by the Electronic 
> Communications Privacy Act, 18 U.S.C. ?? 2510-2521, and contains information 
> intended for the specified individual(s) only. This information is 
> confidential. 
> If you are not the intended recipient or an agent responsible for delivering 
> it 
> to the intended recipient, you are hereby notified that you have received 
> this 
> document in error and that any review, dissemination, copying, or the taking 
> of 
> any action based on the contents of this information is strictly prohibited. 
> If 
> you have received this communication in error, please notify us immediately 
> by 
> e-mail, and delete the original message. 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.