Re: JOBS REMAIN IN EOJ STATUS FOR LONG TIME

One might think that 2 seconds isn't a long time, but with 400 jobs I can
see how that adds up.

Just to be clear, you're talking about one job does it's work, comes to
it's end, goes into EOJ status for about 2 seconds, and then the next job
can finally start, right?

Can you come up with a very simple job and see if that job also takes two
seconds? Here's an example of a very simple job:
SBMJOB CMD(SNDMSG MSG(TEST) TOUSR(QSYSOPR)) JOB(TEST)
To test a string of them try
HLDJOBQ...
and submit 10 of them. Then release the job queue.
Now, if they are not tying it up for 2 seconds of EOJ then perhaps the
original jobs are opening a lot of files without closing them, starting a
number of activation groups or any other errata that is cleaned up at EOJ.
If, however, even the test is taking a long time then perhaps it's time to
evaluate your system performance. If adjusting memory and whatnot you may
need to bust out the checkbook for a hardware upgrade. Assuming you are
on our calendar year the sooner you get on this the better so that your
management can get it in the budget for next year.


Rob Berendt