Re: Socket vs. Dataq (was: RPG, Java and Classpath practices)

Hi Alan,

Let me know if anyone is interested. I can send it along.

Not that I'm in need of this solution right now, but - yes, pls.
send it along.

Just want to look at the code. A TXT- or SAVF is ok.

What's the schedule for your new version of Trigger Mediator ??

Leif
----- Original Message -----
From: "Alan Campin" <Alan.Campin@xxxxxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: 13. juni 2008 19:41
Subject: Re: Socket vs. Dataq (was: RPG, Java and Classpath practices)

Just my two cents on Data Queues vs Sockets. If have found that data
queues work fine on the AS/400 but when you start going out the 400, you
begin to have problems. The problem being that data queues are much
slower than using a socket.

We did some timing programs at a previous job from Java talking to data
queues and we found consistently that data queues would run real fast
for 5 records and then hang and sit for 3 or 4 seconds. This behavior
did not really surprise me because IBM does sell MqSeries.

On earlier jobs, I did timing with Data Queues vs. Sockets and the
difference was huge.

So the bottom line is if your task does not require high performance,
data queues can work fine but if you have a need for speed sockets are
definitely the way to go.

I have a service program that implements a socket client I wrote that
wrappers a C function I got from IBM years ago in RPG. Simple OPEN,
CLOSE, READ and WRITE. I have used it all over the place to talk to VB,
Java and socket server programs running on a PC. Very handy.

Let me know if anyone is interested. I can send it along.