-=> Quoting Mike Bilow to Denis Tonn <=- 

 DT> On the other hand, REXX registers some exception handlers of
 DT> it's own, and these may be what it uses to detect and drive
 DT> a halt  condition. It would take a debugging session to be
 DT> sure. 

 MB> This is the key question.  I either knew or figured out all of the
 MB> other stuff.  If I could depend upon the other DLL (RXFTP, actually)
 MB> timing out, then I would not need this watchdog DLL.  The
 MB> documentation says that RexxSetHalt() sets a flag somewhere inside
 MB> Rexx, and the implication was that this would not be tested until the
 MB> other DLL returned from its called function, so this would not do what

 MB> When I get a chance, what I was going to do was test by passing the
 MB> main thread of execution into SysSleep() and seeing whether
 MB> RexxSetHalt() works from the watchdog thread.  I know that hitting
 MB> Ctrl-Break will terminate a Rexx script even if it is in a DLL
 MB> function such as SysSleep() or FtpGet(), so it is entirely possible
 MB> that RexxSetHalt() will work. 

RexxSetHalt() will not kill a call to SysSleep.  The Rexx program will
die as soon as it returns from SysSleep.

I just tested it.  I use RexxSetHalt() with Rexx scripts running from my
term program when Ctrl-Break is pressed.

Phil
Fido:  1:124/8014.1 | Internet:  phil.crown{at}bluecafe.com


--- Blue Wave/OS2 v2.30