|
On 12/09/2005, at 12:41 PM, M. Lazarus wrote:
Hmm. Unfortunately, this is very clumsy, since a *RPY can be received much later in time. So if I have an automated "message gatherer" utility and encounter a *RPY, it's effectively an orphan until I go back to retrieve ALL the *INQ msgs trying to match it up!
I guess I don't understand what you mean by a "gatherer" but it seems reasonable to me that when you encounter an *INQ message you check for a *RPY. If you don't find one then flag the message as waiting for a reply otherwise match the *INQ and the *RPY.
Of course if you're trying to avoid processing the messages more than once then that will be difficult but you could minimise the work by keeping a list of outstanding *INQ messages and just reprocess those.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
