Re: Restricting QZDASOINIT jobs -- MIDRANGE-L

Brian,

Paul offered some good advice. QZDASOINIT jobs by default have a run
priority of 20, which is the same as a 5250 interactive job.

That makes sense if the ODBC jobs are for client/server interactive apps.

If not, then the priority probably should be lowered.

Run priority is a key component of management, but not the only. Assuming
you don't have the expertise in-house. It might be worthwhile to pay for
someone to take a look at make some recommendations.

Not sure what "optimising SQL statements" means, but if it didn't include
looking at the recommended indexes and creating some of them. Then you
need to do that.

If you know which statements are a problem, focus on those.

Otherwise, go into iNav or NavI and clear all advised indexes. Now run for
a few days or a week and go back in and see what's advised.

The only way to make an SQL statement do less work, is to change what you
need (ie. 6 months instead of 12 months) or provide the indexes it needs to
accomplish what you want efficiently.

Charles

On Fri, Jul 15, 2016 at 7:01 AM, Brian Piotrowski <
bpiotrowski@xxxxxxxxxxxxxxx> wrote:

Thanks, Charles.

It's not that I want to see QZDASOINIT jobs at less than x% - it's because
they are having a bona fide impact on the system. We've been struggling
with this forever - we can optimize the sql statements until the cows come
home but it doesn't seem to make a difference - QZDASOINIT jobs consume a
significant amount of CPU cycles.

We're actually going to move to a different ODBC driver from a third party
to see if that solves the problem. But in the meantime I'll read over the
documentation you included and we'll see if it makes sense to implement.

Thanks!

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Thursday, July 14, 2016 4:30 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Restricting QZDASOINIT jobs

At 7.1+ you can assign "workload groups"

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/IBM%20i%20workload%20groups

But only useful if you're running a multiple core machine.

Why do you want to do this?

Assuming your CPU isn't at 100%, all you'd be doing is artificially
slowing down the work being done via ODBC. It won't speed up anything else.

Do you actually have a problem? Or do you just not like seeing QZDASOINIT
using 50%?

If you actually have a problem, you can adjust run priority, memory
available, max active, ect ect to provide more resources for non-ODBC work.

Charles

On Thu, Jul 14, 2016 at 3:59 PM, Brian Piotrowski <
bpiotrowski@xxxxxxxxxxxxxxx> wrote:

Hi all,

A while ago I moved all of my ODBC spawned jobs into their own
subsystem (which I conveniently named "ODBC"). Is there a way I can
restrict how many resources they consume? Whenever I look at my
system status the QZDASOINIT jobs seem to hog a lot of resources (in
excess of 50% CPU utilization). I'd like to restrict them to using a
cumulative percentage of less than 25%, but not sure if it can be done.

Thankee-sai!

/b;

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Manager - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x5995
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com<http://www.simcoeparts.com/>

Please consider the environment. Don't print this e-mail unless you
really need to.

The information contained in this communication is confidential and
intended only for the use of those to whom it is addressed. If you
have received this communication in error, please notify me by
telephone (collect if necessary) and delete or destroy any copies of

it. Thank you!

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.