RE: Subsystem and memory pools

Is there really nothing unique about a memory pool, other than the name?
Sure the size also.
But other than size or name?
For example, shared vs calc on the paging? Are certain loads better in
one than the other?

Is there a reason to have jobs with certain contentious job properties out
of the same pool? For example, are any of the attributes shown in DSPJOB
OPTION(*RUNA) contentious between jobs of other settings?
Or subsystem routing entries utilizing different classes (WRKCLS)?
After all, it is the subsystem routing entry which determines what pool to
run a particular job in.

On our main production box QBATCH has two pools. Subsystem pool 1 points
to *BASE. Subsystem pool 2 points to *SHRPOOL1. Some of the subsystem
routing entries say use subsystem pool 1 and some say subsystem pool 2.


Rob Berendt