×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have a CLLE program that calls a C program which does some socket level
communications and then, when completed, returns to the CLLE program. The
CLLE then goes into a variable period of waiting for an external event
before calling the C program again.
The C program was recently changed and while testing the new version, it
works fine but 2 minutes after returning control to the CLLE program
(while it is legitimately waiting for the next event to happen), the whole
mess comes to a grinding halt with a CPC1224 message issued. The detail
on the message reads: "A SIGALRM signal was received for the job. The
action for the signal was to terminate the job.".
Is there some way to trap this in the CLLE and take some evasive action
rather than just terminating the whole mess?
Rich Loeber - @richloeber
Kisco Information Systems
[1]
http://www.kisco.com
--------------------------------------------------------------------------
References
Visible links
1.
http://www.kisco.com/
midrange.com
