RE: Socket Application Question

Please do not use 1 job for multiple systems.  If one system is down,
all is down.  Have one job read the existing data queue and send to a
new data queue for each system.  Now forget your socket program.  Have a
remote data queue on each system that point to the local data queue on
the source system.  Now just read the remote data queue on each
destination system as if it was a local data queue.  To help organize
your systems and queues, create a library for each system and a data
queue for each application.  No communication programming necessary
cause IBM has done it for us.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
mgarton@xxxxxxxxxxxxxxx
Sent: Monday, July 24, 2006 8:27 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Socket Application Question

I have a socket application that receives messages from a data queue and
send the message to a remote host via sockets.  Currently the
application uses a single persistent socket connection.  However, the
application needs to be changed so that sends messages to four different
hosts for redundancy.  I am not sure the best way to switch between
sockets.  The easiest way to change the application would be to just
switch between sockets but each time I send a message it would have to
wait to receive a reply before processing a new message.  That doesn't
seem to be very efficient.  I would like to be able to send/receive
messages on all four socket connections at the same time but I don't
know how to do this.  I have very little socket programming experience
so any help would be appreciated.