Re: Performance tuning

Hi, Jim:

Look at the DSPIPLA and CHGIPLA commands. You can tell the system to "compress the job tables" on the next IPL.

It is a good idea to do this once in a while, because, as the total number of jobs in the system grows, these tables go into secondary extents, and then, when the number of jobs shrinks again, those secondary extents are never reclaimed until you "compress the job tables" (at IPL time).

If you notice commands like WRKACTJOB, WRKSBMJOB, WRKUSRJOB, etc., seem to take a long time to display, this is usually a symptom that these job tables need to be compressed.

Hope that helps,

Mark S. Waterbury

> On 9/6/2012 10:49 AM, Lowary, Jim wrote:

Kirk and Rob

I was using both screens the WRKSYSSTS to get Total Jobs in the system
to go with QTOTJOB and QADLTOTJ system values and WRKACTJOB for the
others, using the WRKSYSSTS ASTLVL(*intermed). If I remember correctly
you are right that any job (even ended jobs w/spoolfiles) count in this
total, and that the system has to keep track of these jobs and that is
what the QTOTJOB and QADLTOTJ values correspond to. When this table in
the OS or the Active Job table exceed the initial limit then it has to
be expanded. Used to be when that happened the system kind of suspended
jobs while it did housekeeping and expanded the table(s).

I was just wondering in v6.1 if that still held true. Since we seem to
be bouncing back and forth over limits as our number grow and shrink.
Maybe it doesn't matter as much coming back under a thresh hold, but I
thought the system freed up that space meaning it would have to
reallocate it again when crossing the other direction.

Like I said this was some 15 years ago that I was involved in doing some
heavy tuning and I know a lot has changed. We are having some timeout
issues in some jobs that can't be explained and they could be elsewhere
network, MS servers, etc. but haven't been found yet so fingers are
pointed our way. That was when I noticed the values trying to help
someone figure out the problem and thought from past experience that
they didn't seem to be set to values I would have thought they should.

Thanks,
-- Jim

message: 6
date: Wed, 5 Sep 2012 21:17:29 -0700
from: Kirk Goins <kirkgoins@xxxxxxxxx>
subject: Re: Performance tuning

Jim,
First what screen are you looking at WRKACTJOB or WRKSYSSTS? If I
re,ember
correctly WRKSYSSTS's Jobs in system value includes jobs ( even ended
jobs
) that still have spoolfiles on the system. WRKACTJOB show real running
jobs.