RE: managing user indexes (*USRIDX) -- MIDRANGE-L

In the particular setup I mentioned we use both. There are several NEP 'client' jobs that read entries from a data queue. When an entry is received they take the key value in the data queue entry and retrieve all of the entries from the user index associated with that key and act on them individually as well as a group. When all of the user index entries have been processed the client waits for the next data queue entry.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, January 08, 2013 3:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: managing user indexes (*USRIDX)

Cool. I still wonder which object you are using - you mention both user index
and data queue in your post - just curious while looking for work!!

Vern

On 1/8/2013 2:59 PM, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

Chuck and Vern,

The QUSRMVUI API returns the entries that were removed from the index

effectively giving you a read and delete at the same time.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, January 08, 2013 10:55 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: managing user indexes (*USRIDX)

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?

--
Regards, Chuck
--
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.

Privileged and Confidential. This e-mail, and any attachments there to, is

intended only for use by the addressee(s) named herein and may contain
privileged or confidential information. If you have received this e-mail in
error, please notify me immediately by a return e-mail and delete this e-mail.
You are hereby notified that any dissemination, distribution or copying of this
e-mail and/or any attachments thereto, is strictly prohibited.

--
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.

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.