Re: Storage pools and QHTTPSVR and QUSRWRK subsystems

Christen, Duane J. wrote:

We currently have subsystem QWAS6 (Websphere 6.0 server) in its own storage pool, which has seemed to improved the performance of our web interactions. I would like to move subsystems QHTTPSVR and QUSRWRK to the same pool as QWAS6, but in the back of my mind is a warning that QHTTPSVR should stay in the *BASE pool.

Duane:

Unless you have QWAS6 running a private, rather than shared, memory pool, I can't think of any reason why you should have any work at all running in *BASE. QHTTPSVR and QUSRWRK, and others, doing active work in *BASE only makes things harder for any performance adjustments to happen.

IMO, the first thing to do on any system where performance monitoring will be done is to stop using *BASE for jobs. All jobs.

Let the system decide when *BASE should be used, e.g., perhaps via QTSEPOOL. But don't route them there yourself without _expecting_ general performance to suffer with no good explanation.

(Routing to *BASE "yourself" means not changing IBM's default subsystem descriptions for pools and routing entries and prestart entries.)

As usual, here's hoping someone adds something authoritative. My opinion is purely from reading over the years about work management and performance maintenance.

Tom Liotta