RE: SYSTEM TUNING

Not sure what could be causing it, but a couple of things to check are:

1. do a DSPJOBTBL.  If you have loads of "available" entries, you'll need to
compress the job table at the next ipl - do a CHGIPLA and F4 to set it up.
I'd also set it to check the job table for the next ipl also.
2. Do you have loads of spool files on your system?  These stay as "jobs"
until the output is either deleted or printed....
3. Check system values QACTJOB, QADLACTJOB, QADJTOTJOB, QRCLSPLSTG, QTOTJOB

HTH

Stuart


> -----Original Message-----
> From: DAsmussen@aol.com [SMTP:DAsmussen@aol.com]
> Sent: Thursday, October 28, 1999 4:09 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: SYSTEM TUNING
> 
        <snip>

> Which raises a question for me personally that must have something to do
> with 
> RISC processors but I've never encountered on another RISC.  What would
> cause 
> commands that work with jobs to perform _very_ slowly?  WRKACTJOB isn't
> bad, 
> nor is WRKUSRJOB, but WRKSBMJOB and WRKSBSJOB can take five minutes to
> come 
> up.  What's up with that?
> 
> JMHO,
> 
> Dean Asmussen
> Enterprise Systems Consulting, Inc.
> Fuquay-Varina, NC  USA
> E-mail:  DAsmussen@aol.com
> 
> "The only stupid question is the one you were too proud to ask." -- Me
> 
+---
| 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
+---