On 15 Feb 2013 12:47, rob@xxxxxxxxx wrote:
Does SETOBJACC work across jobs?
What was purged from or is not yet in memory must be paged or faulted
into memory by some process that accesses the object, and whatever of
the object\data is then in memory due to that action, is available to
all other processes; whether the object\data was paged into memory by
SETOBJACC versus by some other request is not germane.
What is placed in memory is available to all jobs, irrespective of
the pool into which the object was loaded into memory. That is a
feature of [or side effect of] single-level storage.