RE: QBASACTLVL recommendations.

Since the S/38 days, with every new release and added features, you always ended up needing a bigger and faster box.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, October 31, 2019 11:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QBASACTLVL recommendations.

Actually it isn't the paging and faulting which concern me as much as the activity level being exceeded thus stopping all new jobs from running. An absolute killer. Why have we had to more than double that when we went from 7.3 to 7.4?
We're doing a bunch of monitoring to see what is consuming that.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Thursday, October 31, 2019 11:25 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: QBASACTLVL recommendations.

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Rob:
In my world, if the activity level of *BASE needs to be 6050 or whatever
for that system, I set it and forget it, there's precious little reason to
lower it at that point.

I would want to know in your case why so much paging/faulting in that
pool? That means most likely all the remote SQL communications is going in
there, and it's likely there are other jobs running in *BASE that should be
moved out. I always tell customers if you application is running in *BASE
alongside many IBM processes, then the whole system slows down due to
resource contention with the IBM jobs.

I'd be far more concerned about that.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Oct 31, 2019 at 10:17 AM Rob Berendt <rob@xxxxxxxxx> wrote:

I appreciate all the QPFRADJ discussions but I really want to focus on
QBASACTLVL recommendations.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Patrik Schindler
Sent: Thursday, October 31, 2019 11:03 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: QBASACTLVL recommendations.

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Hello Rob,

Am 31.10.2019 um 15:32 schrieb Rob Berendt <rob@xxxxxxxxx>:

With our issues IBM has recommended we turn off the adjustment at IPL

for fear of an IPL setting it to too low. I agree that normally you want
an IPL to adjust this to take advantage of new memory you may have just
added.

I think that it's better to have adjustment only when running (3) but not
an IPL as default: The configuration should adapt to running conditions and
stay there, not these at IPL time.

When someone is adding more memory, adjustments will be done more slowly
but eventually they'll get through. This is even more true when doing
memory adjustments to an LPAR while running, so it's kind of a "no brainer".

Any thoughts on that?

Besides, if there's physical memory to be added and immediate remedies
must be taken, one can easily set adjustment to IPL time (1 or 2)
temporarily before shutdown.

: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

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