RE: Object Access and Memory Pools

My theory is kind of the opposite.  On a smaller system you might want
to run everything in *BASE, in order to not fragment your memory too
much.  On larger systems separate batch work into it's own pool to
better utilize activity levels and reduce contention with system jobs
that may run at higher priorities.  WebSphere and Domino servers are
also good candidates for their own pools.  These last two sometimes
require "pinning" some amount of memory to a pool to improve
performance.

Of course the real answer is "it depends."  I would say that the
complexity of your iSeries environment is probably the determining
factor, rather than the size of the box or the amount of main storage.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Tue, 11 Oct 2005 05:53:38 -0700
from: "Graap, Ken" <keg@xxxxxxxxxxxxx>
subject: RE: Object Access and Memory Pools

OK ... That's what I thought. This gets me to thinking about defining
several separate memory pools though. 

Unless you are certain that there is "real" separation between certain
kinds of work on the system, you would probably be better off just
running everything in *BASE, especially on today's systems with HUGE
amounts of memory.

What do you think?

Kenneth

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Monday, October 10, 2005 6:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Object Access and Memory Pools


On 11/10/2005, at 8:31 AM, Graap, Ken wrote:

> I assume that if a Lawson *FILE object is used in a process running in

> subsystem QBATCH and this *FILE is paged into the *SHRPOOL1 memory 
> pool... it is accessible by a process running in the Lawson subsystem 
> even though this subsystem is defined to use *SHRPOOL2. Is this 
> correct?

Yes. Otherwise techniques like SETOBJACC wouldn't work.

> Or is this *FILE object paged out of *SHRPOOL1 and paged back into
> *SHRPOOL2 before it can be accessed by the process running in the 
> LAWPRD subsystem?

No.

Pages from DASD are paged into the storage pool of the requester. Once
there they are in main storage and can be used by any other job. 
Storage management really only cares whether something is on DASD or in
main storage. If on DASD it has to be paged into main storage. If in
main storage it is simply used.

Regards,
Simon Coulter.