RE: Socket Application Question

Chris,

I am sending the data to an external host and must use sockets.  Here's 
some additional info that may help.  This is a point of sale application 
that is doing verification on a transaction. A store will connect to a 
corporate system and drop the message in DTAQ1.  There multiple jobs using 
SOCKETPGM waiting on a message to arrive in the DTAQ1.  Once a message 
placed in the DTAQ1, one of the jobs receive the message.  SOCKETPGM then 
sends it via sockets to the external vendor, receives reply message, and 
then places the response into DTAQ2.  The message is then sent back to the 
store by a separate process.  I have this process running on multiple 
systems so if a store can't connect to System A it will try System B. 

The process that sends the data to the external vendor is currently single 
threaded (one socket connection).  My question is if SOCKETPGM has 
multiple socket connections available to send data, what is the best way 
to send data using all four socket connections.  I have to use all four 
for redundancy and load balancing.  This process also has to perform well 
because I have customer waiting on the response. 

Thanks 

Mark Garton




date: Mon, 24 Jul 2006 08:54:12 -0700
from: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
subject: 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.