Re: Memory pool , object question

Paul,

The rules around memory pools have not changed. Keep like jobs in like
memory.

So, interactive stuff in *INTERACT and batch in it's own pool. I even
split fast and slow moving batch jobs if there is enough memory.

If an object is being used in one job stream and another job needs it, it
still just creates a new "job package" with all the I/O buffers etc. needed
for that program object and calls it.

Remember with SETOBJACC we pin objects into a memory pool to keep them in
memory. Any process on the system can use that object.

So I think your fear is unfounded.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects

On Thu, Apr 5, 2018 at 4:08 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

If an object is in memory from an interactive job, (*INTERAACT pool) and a
batch job needs the same object, but batch runs in *SHRPOOL1, does the
object have to be brought in to memory again because it's in a different
pool?

Years ago, it made sense to keep interactive and batch in their own pool,
for multiple reasons.

I'm thinking the rules could be changing.
Batch and Interactive now use many of the same objects.
We also now have many "service" jobs, which are receiving requests from
either batch or interactive.

So wouldn't it make sense to now run them out of the same memory pool.

My thought is to collapse the batch pool *SHRPOOL1.
Interactive, Batch, "service" jobs would all run out of *INTERACT.

Result would be only 4 pools.

*MACHINE
*BASE
*INTERACT
*SPOOL

Any thoughts from the group?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD