Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the first task after a GO SAVE or ENDTCP run on an endpoint result in the task failing with a connection failure?

April 26, 2017connection endpoint endtcp failing failure run Task

0

Posted

Why does the first task after a GO SAVE or ENDTCP run on an endpoint result in the task failing with a connection failure?

1 Answer

0

Posted

GO SAVE, ENDTCP, ENDSBS commands can all have the same affect on the Management Central server in that the Management Central server will not be able to notify the central system that the socket is going away. This results from TCP/IP ending and not notifying applications it is going away. When this occurs and the Management Central servers are back and running on the endpoint, the next task to that system will fail because the central system still believes it has a good connection to the endpoint. Before any action such as the three previous commands are run that result in TCP/IP being ended first, a user should run the command ENDTCPSVR SERVER(*MGTC). This will result in the central system knowing the socket is no longer usable, and a new connection will be established when the next task is run to the endpoint.