|
If there so much as one write to that file, it will be pushed out of
memory by storage management. That’s to ensure the data integrity of the
file, Read only, that works, but don’t open it for input.
Jim Oberholtzer
Agile Technology Architects
On Jul 16, 2021, at 4:23 PM, Steve Pavlichek <spavlichek@xxxxxxxxxxx>wrote:
200MB and we have 1.5TB memory. This one file has A LOT of IO to it.
Mark,
We did create a private memory pool for this one object. It’s only about
midrange-l@xxxxxxxxxxxxxxxxxx>
From: Mark Waterbury<mailto:mark.s.waterbury@xxxxxxxxxxxxx>
Sent: Friday, July 16, 2021 4:54 PM
To: Midrange Systems Technical Discussion<mailto:
Subject: Re: SETOBJACC statuscreate a separate private memory pool, so that when you issue SETOBJACC, it
Steve,
That object will NEVER be "pinned" in memory when using SETOBJACC.
SETOBJACC does NOT "PIN" anything into memory. That is why you should
will do a "BRING" to bring (page in) the entire object into that memory
pool. But then, subsequent to that, if any other demands on that same
memory pool cause pages to be "stolen" -- well, TOO BAD, SO SAD...
performance.)
(If it did do a "pin" that could be VERY BAD for overall system
instruction SETACST (Set access state), see:
For more details or how you can write your own program to issue the MI
as built-in functions in any ILE language (C, CL, RPGLE).
MI instructions can be written in OPM MI assembler or you can embed them
spavlichek@xxxxxxxxxxx> wrote:
Hope that helps,
Mark S. Waterbury
On Friday, July 16, 2021, 04:02:56 PM EDT, Steve Pavlichek <
SETOBJACC command or a way to prove that an object you want pinned is
Is there a way to show what objects are pinned to memory with the
actually pinned to memory?
list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
link: https://amazon.midrange.com
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.