On Tuesday, April 6, 2021 at 7:16:21 AM UTC-7,
kilg...@gmail.com wrote:
I have the maintenance responsibility for a largeish program which makes PATHSENDs into an appliation pathway. in case the called program or children thereof, Abend, no answer is coming (ever),
the program just sits there. Pathcom reports it running, and to all outward appearences, nothing is wrong. but nothing happens in a big way.
Now, i know my work is now to read and analyse that program together with the pathsend programming guide; and i will. But i feel i could save a lot of time, if someone could give me a hint? (hopefully OK).
the deal is that I must *time out* on the pathsend call. currently, I obviously do not. it makes a whole interface subsystem unresponsive.
So, dare i hope for a hint in this case?
My best,
Henrik PM
It seems to me that if the process in the serverclass that is the target of the Pathsend you are talking about abended, its Pathmon should have started a new copy of the server process. Either the Pathsend to it should have been retried, or an error
should have been returned to the Pathsend call that you say has hung. Maybe I'm remembering wrong about how it is supposed to work.
Could it be that the target server process itself has hung? That still would be a problem, but it always is good to understand what actually is happening.
In addition to the timeout argument for the SERVERCLASS_SEND_ call that JShepherd pointed out, the SERVERCLASS object in Pathway has a TIMEOUT attribute. There are some differences in how the timeout in the SERVERCLASS_SEND_ call is handled vs. how the
TIMEOUT attribute of the serverclass is handled. I suggest you check both to see which is better for your needs. Of course, if you do not have control over the configuration of the target serverclass, you will have to use the timeout argument to
SERVERCLASS_SEND_
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)