RE: QRCVDTAQ

The fundamental problem with data queues is your client 
code does not get a definitive return code from the server. 

While true, sometimes you don't want/need one. One of the great
advantages of DQs is that they can be used for async processing. In that
case, while you do need some way of reporting errors, the logic assumes
that there is no return code since the server job hasn't looked at the
sent request, and may not for a long time.

Another advantage is that you can have several jobs reading from the
same queue (and obviously many jobs sending to it) so if you've got a
resource intensive server process you can start as many jobs as you need
to keep the queue size "reasonable." I know in the past we've done
systems where there was a watcher job whose job it was to start and end
queue reader jobs as needed to ensure the backlog on the queue wasn't
too large.

-Walden