Re: QRCVDTAQ

Darrell A Martin wrote:

So, I'm almost afraid to ask, but ... 

Don't be.

what might be the basic advantages 
of using data queues to pass data between programs:

        all written in RPG
        all running on a single AS/400
        with all data stored on a single partition?

If you have a system where you want to process requests synchronously
(i.e., in the order they were received) from multiple application programs.

You setup a server that monitors a data queue for requests and processes
the requests as they are received.  Your client applications format the
data as required and put the entry on the data queue and listen to
another data queue (possibly keyed by job id) for the results.

The server receives the request from the client, processes it, and waits
for the next request.

The server job is running in a batch subsystem, so you're not adding to
the interactive workload, and (if you wish) you can also extend your
server to receive requests from non-RPG clients (java, VB, etc).

For a simple application, data queue's are probably not the best
solution ... but when you start getting into the area of multiple
applications interacting with each others, possibly from disparate
systems, data queue's are a excellent technique to employ.

david