×
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 08 Jan 2013 10:24, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
Multiple programs can access a user index at the same time. The key
is how they access it. You can do a 'destructive' read which removes
the entries when they are read or you can simply read the entries.
Obviously, if entries are removed when read they won't be available
for other programs to access.
What MI instruction or API provides a "destructive read" capability
for a User Index object? There is the by-default destructive-read of
messages read from a Data Queue, and there is an alternate means to
effect a non-destructive-read of messages\entries on a queue. Or was
perhaps a private interface that combines the effects of FNDINXEN and
RMVINXEN [or the equivalent APIs: Retrieve User Index Entries (QUSRTVUI)
API and Remove User Index Entries (QUSRMVUI) API] being described,
rather than a specific method provided by the OS to access the
Independent Index?
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
