Re: Performance Issues

On 8/19/2017 5:35 AM, Kevin Turner wrote:

Almost all memory pool config is retained following an upgrade and we have certainly never had to reset anything. It's the memory setup for IBM supplied subsystems that can change. The recommendation is to move the config to a non-IBM library and

use that - then no fiddling required post upgrade.

I suspect we're saying the same thing.

My comment is over-broad - it covers not only memory pools for QHTTPSVR,
but *SYSLIBL, *USRLIBL, other system values, subsystem descriptions, Q*
print files being set to *NOMAX or HOLD(*YES), etc.

Setting up one's own USRWEBSVR subsystem is a fine idea, and works well
for this specific problem. Don't forget the startup CL.

On 18 Aug 2017, at 16:05, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 8/18/2017 3:37 AM, Kevin Turner wrote:
The main issue was that the memory pool configuration for QHTTPSVR was reset to the default by the upgrade. iBM said that was expected behaviour and the subsystems provided by the OS should not have tailored memory pool(s) set up. The confit information is apparently stored in a location that gets replaced. Discuss!

It has been thus since I've been working in midrange computers. Almost
40 years, 7 generations or so of operating systems.

The recommended practise is to write a script (I use a CLP called
CUSTOMIZE) that configures the system the way you want it to look. The
very hard part is to remember that when I change a system setting (like
setting a pool to *CALC) I need to put that change in the CUSTOMIZE CLP.