MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: managing user indexes (*USRIDX)



fixed

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?






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact