×
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.
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.
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.
midrange.com
