I spent some of the time while the snow was falling in southeastern Wisconsin yesterday by searching for a newer version of the expert cache description than was published not long after it came out, without success. Doesn't mean one was not published but none of the popular search sites found anything given the search terms I was using.
So, lacking other evidence to the contrary, I'm sticking with *CALC in every place that it is available. The system does a fine job of managing memory and in 98% of the cases much better than manually tuning. (I do not use QPFRADJ on systems with heavy SQL, that just messes up the optimizer)
In the original post I remember Rob questioning why the support center would recommend turning it off for the *SPOOL shared pool. To this date I've seen nothing to support that suggestion, nor any evidence to suggest that expert cache is not the correct setting in all but very few instances.
Work management (setting subsystem memory pools to shared pools and managing activity levels, subsystem descriptions, classes, job and output queues, and general performance management etc.) is not the same as expert cache. To conflate the two is a complete misunderstanding of the problem. While related, they are not one in the same.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, February 10, 2020 7:04 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: WRKSHRPOOL paging *calc or *fixed recommendations
Paul,
If you look at that article, last modified 18 December 2019, and stating it was current up through 7.3, it had *SPOOL at *CALC.
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 Steinmetz, Paul via MIDRANGE-L
Sent: Friday, February 7, 2020 9:35 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: WRKSHRPOOL paging *calc or *fixed 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.
Jim,
I don't think so.
Here's a recent doc regarding *CALC (Expert Cache).
People have different views on performance adjusting.
I run with performance adjuster on, to allow nightly batch jobs to allocate more memory.
During the day, allocated back to interactive.
Document number:
638945
Modified date:
18 December 2019
https://www.ibm.com/support/pages/separating-batch-work-base-0
Shared Pool
A shared pool is a pool in which multiple subsystems can run jobs. The advantage of shared pools is the flexibility of sharing memory between pools if it is not being used. System value QPFRADJ adjusts memory to maximize resources on a dynamic system. Shared pools can also use Expert Cache by setting the paging option on the WRKSYSSTS or WRKSHRPOOL to *CALC.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, February 07, 2020 8:55 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: WRKSHRPOOL paging *calc or *fixed recommendations
I’d love to know why. For years IBM has been suggesting the opposite. There were some excellent write ups explaining the process that *CALC used some time back.. has something changed?
Jim Oberholtzer
Agile Technology Architects
On Feb 7, 2020, at 1:24 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
IBM Lab services is recommending that *MACHINE and *SPOOL are set to *FIXED while the rest are set to *CALC.
Sound reasonable?
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
--
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
midrange.com
