wrksyssts shows many active jobs while wrkactjob shows fewer
One of my AS400 shows 203382 active jobs in wrksyssts screen while only 1136 active jobs in wrkactjob, does anyone kindly advise the reason why there's such a big difference?! Are these printing/splf jobs since they keep many years spool files
Software/Hardware used:
Software/Hardware used:
ASKED:
July 21, 2010 12:35 AM
UPDATED:
July 22, 2010 6:33 AM
Answer Wiki:
<i>...203382 active jobs in wrksyssts screen ...</i>
The WRKSYSSTS screen doesn't show "active jobs". It shows "jobs in system". Usually, the vast majority of jobs in a system are not active.
Commonly, jobs that have ended (and are no longer active) after creating spooled files make up most of the total jobs in the system.
Place the cursor in the "Jobs in system" area of the WRKSYSSTS screen and press <F1>. You should then see a basic explanation of the number. The <F1> key should be your first thought when a question comes up anywhere in the system.
Also, consider using DSPSYSSTS instead of WRKSYSSTS. There are no input fields on a DSPSYSSTS display. An accidental data entry won't be as troublesome.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
It must be due to all the years of spool files which is showing such a large number. Also check your joblogs to see if they are cleared after a reasonable period.
Some sites thru users pressure hoard spool files using up valuable disk space even though these are accessed once in a blue moon! This can have a detrimental effect on performance of the machine,
Good systems will keep immediately need files and archive the old ones. Should look into it.
You may consider changing the systemvalue of QSPLFACN from *KEEP to *DETACH.
This will cause the system to detach any print output from an ended job, keeping the spoolfiles, but not the job and related information.
You can also check on a regular base what jobs are in the system with status *OUTQ (WRKUSRJOB *ALL *OUTQ). Then use option 2 on all that you want to detach and enter parameter SPLFACN(*DETACH). Or write a utility that does this for you, as I did for our system.
May get the number reduced by some 200000.