Re: WRKSBMJOB, WRKUSRJOB slug-li -- MIDRANGE-L

WRKSYSVAL F4 & *PRINT will get you a list of system values charting how they 
were shipped from IBM & flagging those that have been changed by someone at 
your enterprise.  Then look in the WORK MANAGEMENT manual for a little essay 
on each of these job table values.  Some of this stuff goes back to zero at 
IPL.

Ask Al Barsa if he is willing to send you his document hand-out from Common 
on EVERYTHING YOU EVER WANTED TO KNOW ABOUT SYSTEM VALUES BUT FORGOT TO ASK 
OR NOT AWARE YOU SHOULD ASK or whatever it is called ... I have it & it is 
GREAT & includes coverage of this topic.  I also have a Performance 
Management book from News/400 that advises capturing this kind of data 
regularly to get an overall picture of what is normal for your shop.

There is some performance tuning advice free from IBM but you have to add 
some PTFs to get started ... check out
www.ibm.com/services/electronic & go to the "How do I get started" section

Essentially ... attempt at a brief non-technical big picture explanation ... 
when you start a job, there is some work space needed for the baggage 
associated with it.  Efficiency is served by having a bunch of these work 
spaces created at one time & hanging onto them so they can be re-used, but 
you do not want excess volume.  Your system can get sluggish if it is 
constantly creating work space because you did not create enough of them in 
the first place, so it is thrashing replacing the not enough, or if you have 
a lot of jobs that appear & disappear & each time they appear they need the 
work space & it has to be created.

In my reality, my users sign on all day, create unprinted reports, launch a 
few things to jobq, there are thousands of open jobs, but only a hundred or 
so active at any moment.  The dynamics of your reality influence what 
provisions you want for permanent as opposed to temporary job structures.

I am forever deleting ancient print outs & I have mine own from nightly jobs 
that I leave for 24 hours so other users can access & I have warned all & 
sundry that I will delete mine in 24 hours unless someone asks to see 
something longer.  GO CLEANUP gets at settings to delete some old stuff 
automatically like messages.  I not remember where I set it, but I have 
reclaim disk space from deleted reports set at 3 days ... my reasoning being 
that if I reclaim too fast, then that will slow access to disk space by 
recurring standard volumes of reports.

Al Macintyre  ���
MIS Manager Green Screen Programmer & Computer Janitor of BPCS 405 CD Rel-02 
running on AS/400 V4R3 http://www.cen-elec.com Central Industries of 
Indiana--->Quality manufacturer of wire harnesses and electrical 
sub-assemblies
+---
| 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
+---