Re: Regarding BYTES-RETURNED field of RDQM0100 - Calling QMHRDQM

Chand,

To simplify what Chuck says below...

If you call the API with BytesProvided = 0, the BytesAvailable value
returned tells you how much data could have been returned. So you
could for example dynamically allocate that much space and call the
API again with the same parameters and with BytesProvided set to the
space you now have available.

Does that help?

Charles

On Tue, Jun 9, 2009 at 10:37 AM, CRPence<CRPbottle@xxxxxxxxx> wrote:

When the /bytes available/ is
greater than the /bytes provided/, that indicates there is more
message data than what was retrieved.  To /predict/ the size needed
to store all available messages that meet the selection for any one
invocation, the /bytes available/ provides an estimate for the next
invocation [performed immediately after]; such an invocation is
generally made with the /minimum length/ specified for the receiver
variable.  However in the next invocation with the same selection,
there may be more or fewer messages that meet the selection than on
an [even immediately prior] invocation used to obtain an estimate,
and thus any prediction for the next invocation may be nowhere near
accurate if message activity has transpired since the invocation
used to gauge the probable /bytes returned/.