My colleague heard back from one of her former colleagues. Apparently, the
issue they had with data queues was that they lost data if the data queue
got full. One solution, of course, is to monitor for the condition, and
create another data queue to start taking the overflow entries. Since our
data queue has only one source program for entries, this should be easy to
handle.

I appreciate all of the replies. I learned a few more things about data
queues.

- Dan

On Thu, Dec 22, 2016 at 10:04 PM, Dan <dan27649@xxxxxxxxx> wrote:

I have a project I'm designing that uses data queues. A colleague
remembered from a former job that they seemed to have problems using data
queues, but couldn't remember specifics. Apparently, they were deemed
unreliable there and so they redesigned their processes to avoid using
them. She is following up with a former colleague to refresh her memory,
but it may be awhile since we're in the holiday season.

I personally haven't done a lot of work using data queues, but what I have
done has proven to be absolutely reliable. I am certain that if there were
any issues with data queues, given their importance in many applications,
a) we would know about them, and b) IBM would have fixed them pronto a LONG
time ago.

Still, just doing my due diligence with this.

- Dan


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.