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



Gerald,

The QMRRDQM API actually does return the sender ID. The 36 bytes
containing the sender ID are located immediately preceding the actual
message text in the message text field returned by the API, if the data
queue was created with SENDERID(*YES). If, for example, a message text
length of 106 bytes is returned for such a data queue, the first 36
bytes will hold the sender ID, and the following 70 bytes will contain
the 70 byte message that was put on the data queue.

Best regards,
Carsten

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: 1. marts 2012 17:46
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Data Queue - non-destructive reads

Thanks Chuck,
however, the QMHRDQM api will not pass me the Sender info, which are the

elements of information I need.

gerald




On 3/1/2012 10:40 AM, CRPence wrote:
On 01-Mar-2012 07:08 , Gqcy wrote:
I am attempting to read a data queue (non-keyed, FIFO) to determine
the Sender info, and am setting the remove entry to *NO.

however I keep reading the same (first) record. Is there a trick to
progress through the data queue???

I see that the DSPDTAQ utility uses DMPOBJ to get at the data queue
data, but I would like to use QRCVDTAQ if I can... >

If not for DDM DTAQ objects, then use the QMHRDQM API to get all of
the
messages. Limit the receiver size according to the number of messages
that should be read; use the 'R'everse invocation if\when alternate of
the LIFO or the FIFO is desirable.

i_ Retrieve Data Queue Message (QMHRDQM) API i_
"
The Retrieve Data Queue Message (QMHRDQM) API retrieves one or more
messages from a data queue.

The QMHRDQM API allows the retrieval of multiple messages per call.
The
message selection information parameter allows you to have some
control
over which messages are returned. The QMHRDQM API can be used to
retrieve the following:

* The first or last message of a data queue
* All messages of a data queue
* Selected messages from a keyed data queue

The QMHRDQM API is similar in function to the QRCVDTAQ API. However,
the
QRCVDTAQ API can remove the received message from the data queue;
QMHRDQM API does not remove received messages.

Distributed data management (DDM) data queues are not supported using
this API.

...

RDQS0100 Format

The following table describes the RDQS0100 format of the Message
selection information parameter. This format is used with data queues
when selection with keys is not necessary. This format cannot be used
with keyed data queues. ...
"

Regards, Chuck


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.