If I read this correctly, you want to try to control how the system swaps
memory and uses memory when a job does not have an activity level. (meaning
it's most likely been paged out)
If that's your goal, then you are not using the correct tools. Work
Management will not keep memory from being swapped in/out, in fact it
encourages it. You would have to write all your applications in MI, and
even then I don't think you can keep the system from managing memory the way
it wants to.
Keep in mind that the system will protect a jobs memory space from other
jobs/processes while it is active. While I can speculate all day about why
you would want that memory management granularity, I can tell you work
management is not going to accomplish what I think you are suggesting below.
Agile Technology Architects
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik
Sent: Monday, December 30, 2019 9:38 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Reducing ODBC connection impact
Am 30.12.2019 um 13:33 schrieb Jim Oberholtzer
I had forgotten that was out there. Those are exactly the steps you
need, although it moves the ODBC jobs to a custom subsystem.
I'm fine with that if it prevents other jobs from being delete from memory
to be swapped in later when they're eligible for running again. Still need
to try out and also get a grip onto that complete SBS-thing beforehand.
PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
As an Amazon Associate we earn from qualifying purchases.