Re: QRCVDTAQ

On 7/10/06, Cassidy, Alan <CassidyA@xxxxxxxxxx> wrote:

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

...I handled that with a 2-way data queue process like described before.

I have found two way data queues very difficult to code. You have to
assign a transaction id to differentiate responses to other clients
from your client. The response queue has to be keyed by transaction
id. What happens when the server is down or stuck? Your client then
waits for how long for the return code?  Did you say 10 seconds?  Well
what if the system is running slow or another client has sent a large
transaction to the server?  When do you clear the return queue of
unreceived response messages? When the return message is more than 1
day old or the sending job is no longer in the system?  Then you have
to permanently store the transaction in in a file so you can calc the
job and age of the transaction.

With a program call none of these issues have to be addressed.

-Steve