Re: QUSLJOB overflow - how many jobs in system?

Hi Fran,

Would that be Jean-Paul Lamontre's WRKJOBS command?
http://jplamontre.free.fr/AS400/WRKJOBS.htm

QUSLJOB is (as far as I know) only limited by the size of a user space. (Actually, you can call it repeatedly to get more data... but many programmers don't incorporate that functionality.) User spaces are limited to approx 16mb. The API returns approx 256 bytes of header data. Each job takes up an additional 64 bytes, plus variable field data... which field data depends on how it's called... but even if we go crazy and guess that the utility is using 640 bytes per job, that still allows more than 26000 jobs -- more than double what the subfile allows, and well over the 3000 you're referring to.

I know that doesn't solve your problem -- but it's food for thought.

If this is Jean-Paul's utility, you might try asking your question on the System iNetwork forums, since he's a regular over there.
http://www.systeminetwork.com/isnetforums/

Alternately, you could e-mail Jean-Paul directly. His contact info is on his web site.


Frances Denoncourt wrote:

I have a WRKJOBS command I got years ago from some magazine somewhere and it is suddenly failing. Looks like we are going beyond 9999 for dspf.
The job calls QUSLJOB among others.
However, my question is - how else can I see how on earth there could possibly be so many jobs in the system to make WRKJOBS TX* fail.
We're not very big.
Did a wrksplf *ALL and queried the results - way too many (over 3000) but not enough to cause that problem.
Any ideas? Thanks
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Receipt of this message does not grant you permission to send me Unsolicited Commercial Email