The job tables are nearing capacity in our iSeries, we have purged some OUTQ's as well, please could some one let u know any other house keeping methods?
Software/Hardware used:
as400 performance
ASKED:
January 12, 2011 10:21 AM
UPDATED:
January 18, 2011 9:53 PM
Save your QUTQ’s to tape with their spooled files. Deleted Old Spooled files from the system. Delete job logs.
For background, run DSPJOBTBL. Then review the <help> text for Initial, Additional and Available job structures. The <help> text describes the relationships between those values and different system values that you might want to adjust.
Also, press ‘F11=In-use entries’ to see if ‘Pending’ joblogs might be a source of rising numbers of jobs.
How many jobs show in your system? What OS version/release are you running?
Tom
Enter command WRKUSRJOB QSECOFR if you find the job below
SRVMON0001 QSECOFR BATCH JOBLOG PENDING
The job number ranges 0001 to 0076, and there can be hundreds of them in joblog pending, simply delete them with option LOGLMT(0)
Apart from this do you regularly schedule IPL’s ?
There’s a good 2-part article on this on the 400 Guru website:
Part one: http://www.itjungle.com/fhg/fhg092408-story03.html
Part two: http://www.itjungle.com/fhg/fhg100108-story03.html
Good luck!
The two IT Jungle articles mostly cover what can cover here if we get a little more info on where the excessive jobs are coming from.
There is a third article in the series — Admin Alert: When System Job Tables Attack, Part III. And that article links to a useful IBM Redpiece — Best Practices for Managing IBM i Jobs and Output (and a few other special tips).
We can provide sample code for some cleanup work if we are told what needs to be cleaned up. E.g., a utility to clear away “pending” joblogs might be appropriate.
Tom
This this Redpaper: Best Practices for Managing IBM i Jobs and output(and a few other special tips)