While I understand the thinking about it upsetting work management, it
doesn't really. True you could have two jobs that share memory across
shared pool lines you still control what memory each job starts in, and
since the APIs are quite specific, I don't think it breaks rules since it is
a client/server model. The server needs to offer up the memory first, the
client cannot just come take it.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Calabro
Sent: Friday, May 12, 2017 9:31 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Is there an API to "deactivate" an "active" service program?
On 5/12/2017 9:28 AM, Mark Murphy/STAR BASE Consulting Inc. wrote:
I am unfamiliar with a shared memory API which allow sharing memory
between jobs. That seems to be a little counter to the work management
schemes on IBM i. How does that work? How can you coerce a job to access
memory outside it's job space. Are you using a special object like a user
space or something like that?
There are C functions for shared memory.
Start with shmget()
There's a working example at
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apiref/apiexusmem.h
tm
--
--buck
Try wiki.midrange.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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://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
midrange.com
