× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



From: Mark Waterbury <mark.s.waterbury@worldnet.att.net>
> The idea is, if you really need high-performance and you want the
> object loaded by SETOBJACC to "stay" in memory, you can just
> create a separate memory pool, using OS/400 storage management.
> One of the parameters on the SETOBJACC command is which
> POOL you want to "bring" the object pages into.  Then, so long as
> no one else is using that POOL, and the pool is sufficiently large,
> then none of the pages for your object will get "paged out", and
> so, the effect can be almost like "pinning" the pages in memory.

Mark, I don't think any of your suggestions would work. Sure, they
would bring in the pages, but would not block the system from
"dropping" them again as soon as other pages are needed by anybody
else. I think the paging takes place so far below the work management
layer that you can't influence it as you suggest. Now, I could be wrong,
so let's get some input from IBMers (current or ex-) on this.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.