RE: Restrict jobs CPU usage

Where I work we also have a lot of interactive order entry jobs going.
Before we went to RISC several years back, we went through a couple of years
where we couldn't afford to upgrade to the level we needed.  During the
holidays we generally ran close to maxed out and often ran in the mid 90s
during the rest of the year.  As long as we kept a lid on big batch jobs
during the day time, interactive response time was between acceptable and
excellent.     

We also had an operations manager who put a lot of effort into performance
tuning.    

> -----Original Message-----
> From: C. Alan MArtin [mailto:songbird@sumter.net]
> Sent: Thursday, March 30, 2000 1:45 PM
> To: RPG400-L@midrange.com
> Subject: Re: Restrict jobs CPU usage
> 
> 
> We usually try and keep CPU usage at 70-80%. We have a lot of 
> interactive
> jobs running at the same time (taking phone orders from customers).
> Of course if you have a heavy conversion program or batch job 
> that wants to
> hog CPU, you can create a separate pool for jobs that have to run
> immediately. Change priority on any low priority batch job 
> that seems to be
> piggy. Use WRKACTJOB to see who the offending members are.
> Do a WRKSYSSTS and check out % of ASP (Aux Storage Pool) that 
> is being used.
> Our CPU may look maxed out, but if the % of ASP is 
> acceptable, then you
> don't have to worry.
> Look at the Wait-Inel (wait to ineligible) column on the 
> WRKSYSSTS screen
> again. If the pools are below 10%, all is well. Otherwise, 
> adjust the MAX
> Act column for the pool in question until it comes down to under 2%.
> Check out the red book "AS/400 Performance Management " for 
> exact numbers
> for these settings and a better explanation.
> .
> C.A.
> 
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---