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

Shijith Chand wrote:

Can anyone please let me know what value is returned in the
BYTES-RETURNED field of RDQM0100. I want to predict the value
that may come in this even before I call QMHRDQM ?

The output depends on the inputs to the API and what is available to be retrieved for any one invocation. No reasonable response can be given without knowing at least the inputs. And if the inputs establish both fixed-length [i.e. maximum limits] and fixed-number of message(s), then someone could probably respond with some accuracy for a general maximum. However any response to such a limited invocation would then be moot, as just calling the program when such a message was available would suffice to infer from its value for /bytes returned/; i.e. an effective fixed-length with maximums invocation against a maximum message(s) would provide what should be the maximum bytes-returned on all invocations.

That value depends on what is being requested in selection, what of which messages selected is both requested and available to be returned, and the format that describes the /receiver variable/. The value of /bytes returned/ will reflect the amount of message details returned into the /receiver variable/ and that will be limited by both of the /length of receiver variable/ and the /message selection information/. 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/.

Regards, Chuck