Re: Data Queue

Mark,

I use this approach in some custom "wizards" I've created for retrieving
data from the 400.  The client creates the data queue, calls an RPG program
to populate it, processes the resulting records, then deletes the queue as
part of a cleanup process. The time it takes to create the queue is measured
in milliseconds, and isn't even worth worrying about when you consider the
overall processing time required to transfer the records. Of course, this
assumes that you're transferring dozens of records (or more) at a time. I
certainly wouldn't use this approach for something like a lookup function
which only returns a single record, yet is called many times.


Regards,

John Taylor

----- Original Message -----
From: <MWalter@hanoverwire.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, June 12, 2002 1:30 PM
Subject: Data Queue


> Hello all,
>
> How expensive is Data Queue creation? What I'm trying to do is to get data
> from a VB application to the 400. I've thought of a number of different
> ideas and have decided to at least give a data queue a try. I was just
> wondering how expensive it is to create a unique data queue every time and
> then destroy it, or to fiddle with a keyed data queue.
>