ypinn@UTORSCS.BITNET (Bruce Pinn (System Manager)) (03/14/88)
Possibly you should use SYS$FORCEX to kill off another process. The $FORCEX
system call will stop another process, after the process' exit handlers have
been run. I believe this is what you are trying to do.
Bruce W. Pinn Phone: (416) 978-6601
Ontario Centre for Large Scale Computation BITNET: YPINN@UTORSCS.BITNET
at the University of Toronto DATAPAC:PSI%1302091600440::YPINNmhg@MITRE-BEDFORD.ARPA (Mark H. Granoff) (03/15/88)
>Dec has already thought of this one for you. Look at the sys$forcex call. >It basically forces an error in another process and causes the exit handlers >to run, then the image exits. It's actually kind of nice, since I believe that >you could write a condition handler and use it like unix signals. > >bruce <xrbeo@vpfvm> on bitnet Just for the record, the $FORCEX system service issues a $EXIT system service on behalf of another process in the form of an AST. The $EXIT system service then executes any exit handlers for that process before issuing a $DELPRC system service (also in the form of an AST). ASTs pending before the $EXIT AST is issued (by $FORCEX) are completed first. Just my two cents... +---------------------------------------------------------------------+ | Mark H. Granoff Member of the Technical Staff | +---------------------------------------------------------------------+ | USMAIL: The MITRE Corporation | ARPAnet: mhg @ mitre-bedford.ARPA | | Burlington Rd. | UUCP : linus!mbunix!mhg | | M/S B015 |-----------------------------------| | Bedford, MA 01730 | A T & T: (617) 271 - 7506 | +--------------------------- Disclaimer ------------------------------+ |The views expressed herein are my own and do not necessarily reflect | | those of my employer. | +---------------------------------------------------------------------+