-=> Quoting Mike Bilow to Phil Crown <=- 

 MB> Phil Crown wrote in a message to Mike Bilow:
 
 MB> Again, if you issue a DosKillProcess() against the Rexx program, you
 MB> actually kill CMD.EXE.  If there is a parent batch which calls the
 MB> Rexx program, then this kills the parent batch also.  I suppose I can
 MB> get around this by running a second copy of CMD.EXE or something, but
 MB> this is not the key problem. 
 MB> What I am thinking about implementing with the DLL is a Rexx function
 MB> such as RxtSetTimeout(), which would return immediately.  This would
 MB> start some sort of asynchronous timer that, upon expiration, would
 MB> cause the Rexx program to be killed.  The Rexx program could make
 MB> periodic checkpoint calls into the DLL to notify the timeout routine
 MB> that everything was fine, and this would reset the timeout timer.  If,
 MB> however, the DLL did not hear from the Rexx program periodically, the
 MB> DLL would assume that the Rexx program was hung and kill it. 
 MB> -- Mike

I knew it was over my head to try to solve a problem *you* have.

Figured I'd try anyway...  :-)

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


--- Blue Wave/OS2 v2.30