Re: Sockets question -- MIDRANGE-L

I have worked with many different POS terminals myself. What you are saying confuses me. You are talking about tcp sockets but the reference data queues these are two different beasts. In general you have one server listening then spawn off the connections to the waiting prestart jobs. When you are finished with the transaction you must close the connection and return to wait state so the job can process another request. There is a way and need to signal the listening server job that the worker job is available again. You also can use multiple threads but I am not there yet.

Sent from my iPhone

On Mar 15, 2011, at 6:51 PM, "Renkema, Rick" <RenkemaR@xxxxxxxxxxxxxx> wrote:

I have used Scott Klement's Socket programs for years. I have recently
started at a new
company and am once again using these programs (and the "Socket
Tutorial" Scott wrote).

I have implemented a system that has a central connection program which
spawns jobs.
In testing at present, we get an average 5 - 6 spawned jobs (this is a
POS interface
and will have about 30 - 40 POS centres accessing the iSeries at
go-live).

I don't think I have a problem with the sockets as such, they are
working fine, doing
what they are supposed to and returning requested data. Socket server
instances (the
spawned jobs) are all sitting on a "RcvDtaQ", waiting for a request to
hit it, then
process it. I have proper processes in place to handle multiple
requests coming in
so I don't lose any.

Sockets are open and always stay open (I am working on finding a way to
close them after a
period of inactivity, but that is not my problem, I think). What does
happen is that all of
a sudden, after working perfectly for a period of time, the server
instances (all of them)
will no longer respond. A debug on the program shows nothing hitting
the dataqueue hence no
responses ... But data is sent from the POS station (we have a
simultaneous trace on it).

One minute it works, the next it doesn't. Stop SBS and start SBS, and
all is fine again.
Could be 24 hours, could be 10 minutes and I have to do it again. This
will not be acceptable
in a live environment of course.

I cannot find anything (tutorials, google or otherwise) that even hints
at this sort of
problem. I want to believe it may be as simple as a TCP/IP setting ...
somewhere.

Has anyone had anything similar (and I should brush up on my search
words)? Is this a known
problem? Is there anything else I can tell you that may help? I am NOT
a TCP/IP expert, I
know a little, enough to be dangerous.

Any help is much appreciated.

Rick

***********************************************************************************
The information in this e-mail message and any files transmitted with it are intended to be confidential and for the use of only the individual or entity to whom they are addressed. The message and files may be protected by legal professional privilege, or other legal rules. The confidentiality of and privilege applying to this message and files is not waived if this message or files has been sent to you by mistake. If the reader of this message or files is not the intended recipient, you are notified that retention, distribution or copying of this message and files are strictly prohibited. If you receive this message or files in error, please notify us immediately by telephone or return e-mail and delete all copies from your computer system. It is the recipient's responsibility to check this message and files for viruses.
Thank you.
***********************************************************************************

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.