c++ TCP Server listener modification

This bid is for modifications to a TCP port listener that I have been using for 15 years. I have no plans to change this totally I just need modification to the listener part of the code. I will detail the job in the detail description. Good luck bidding. ## Deliverables I will try to be detailed as possible I am including two projects. Let me start off by saying don't worrry about the one error you get registering the ocx file. There is no need to worry about this. I have a small problem with my TCP socket client and server. I have a Inet daemon that listens on a specific port for incoming client calls. When it get a call from the client it starts and external program that has a TCP (socket)listener inside of it. This dll listens forever unless you specifiy a timeout period and then it will just end the process. The problem is as of late we have had many power outages and we have had many network failure problems like switches that go down, computers that just shut off things like that. The client get disconnected when this happens the server part of of the application is still running because the server is on a UPS. When the user tries to reconnect it opens a new process but the old one is still running the software and is sitting on a record making that record busy. There is no way to terminate this process without terminating all the programs or rebooting the server. We can have 200 to 2000 users using one server to run our applications. The front end can be 7 different languages but only one backend. So here are my thoughts. In the daemon if there is a way to start the process and place the mac address so it can be seen in the task manager or something like that. That would be good for a backup way of dealing with the problem. The second is the direction is where I want to head. I was hoping but I don't know enough about TCP sockets whether when the client gets diconnected to allow the same user to reattach to their same connection that they already have open that would require an os hack for sure and I am not sure how or if that can be done. The second option might be the one that I have to settle with. I know polling is not recommended but the current listener has a wait timeout and if I could set that and after so many minutes of idle time the server could check the client to see if it is still connected. If the connection has been lost the process can terminate. This may be the only option I have but this is why I am posting this job so that someone can tell me what my options are. So the RMCobol project is where all the code that needs to looked at the other projects are not important. The waitaction is the code that listens for the tcp process if you have any other questions please let me know.