for the prestart jobs setup. much easier in new version with some SQL
services:
https://ibmsystemsmag.com/power-systems/i-can-blog

in older OS versions it is more manual, the steps are outlined in the WIKI:
https://wiki.midrange.com/index.php/QZDASOINIT

Bryan





On Fri, Dec 6, 2019 at 2:09 PM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

What you need to review is the prestart job entries. That along with the
class (in the PJE) control how those jobs run. Depending on how much
memory
you have consider putting them into their own pool and out of *BASE. Make
sure the activity level in the pool they do run in is high enough.

Those are the basic tuning steps for QZDASOSINIT jobs.

Then there's the whole be sure you have the correct indexes built for the
SQL that's getting submitted too, but that's a whole different
discussion.

All this is true in V4 as it is in V7.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Patrik
Schindler
Sent: Friday, December 6, 2019 12:45 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Reducing ODBC connection impact

Hello Stefan,

Am 06.12.2019 um 13:11 schrieb Stefan Tageson <Stefan.Tageson@xxxxxxxx>:

Hi, Normally if not adjusted the ODBC jobs run at prio 20. You can change
the class-object to prioritize down to 50 or similar.
Put a line in your startup program to set the prio ar evert IPL.

Interactive priority is set in the user profile and usually 3. That's way
more than 20, so reducing to 50 would not really help with my issue. AFAIR,
priorities are not an absolute setting but a relative-to-each-other
parameter. The machine isn't doing much when not processing bulk ODBC
inserts, so it's even not other jobs slowing down the interactive job.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.