Re: QZDASOINIT prestart job entry Max Jobs and Uses

Brian,

The fact that QZDASOINIT is taking 60% doesn't mean there's a problem.

Have you noticed interactive or other batch jobs being adversely
affected? If the answer is no, then don't worry about QZDASOINIT
taking 60%. If the system has spare cycles and QZDASOINIT has work
that needs doing, then you want the system to give the cycles to
QZDASOINIT.

Now if you are seeing an adverse effect on other jobs, priority,
timeslice, and the other work management settings are your friends. I
don't know how MAX JOBS and/or USES would make any difference in CPU%
used. Well MAX JOBS will if you set it low enough that you start
rejecting connections from users, but honestly I've never been in a
shop that really wanted to do that.

One other consideration. If you feel 60% CPU is "too high" then what
you really want to do is reduce the work that QZDASOINIT needs to give
you the results requested. Here, the iSeries Navigator's SQL monitor,
index advisers, and Visual Explain and some of the tools you can use
to ensure that your system has the indexs needed by your queries so
that they can be complete with the least amount of work.

HTH,
Charles


On Wed, Dec 16, 2009 at 1:42 PM, Brian Piotrowski
<bpiotrowski@xxxxxxxxxxxxxxx> wrote:

Hi All,

Even though we have changed the priority of the QZDASOINIT job, we are still experiencing an abnormally large amount of CPU utilization (in some instances in the neighborhood of 60% on average based on the numbers reported by WRKACTJOB).  After doing some poking around on the Internet, I came across and article that discusses the prestart job entry parameters for this job.  The article mentioned reviewing the MAX JOBS and USES values.  Looking at our system, I see they are set to *NOMAX and 200 respectively.

If I change these values, I am assuming I will be able to reclaim some of this CPU utilization consumed by QZDASOINIT.  The question is - what is a reasonable number to set these values to so that I have a balance of web pages being serviced in a timely manner without having the QZDASOINIT job consume a large amount of resources?

Also - if I make changes to this job, do I need to IPL the machine, or do I simply stop and restart the QUSRWRK subsystem (we are running 5.4.0)?

Any comments or suggestions would be most appreciated!

Thanks!

/b;

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.