Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!cmcl2!brl-adm!umd5!uflorida!beach.cis.ufl.edu!jdc From: jdc@beach.cis.ufl.edu (Jeff Capehart) Newsgroups: comp.os.vms Subject: exiting DCL comfiles Message-ID: <15873@uflorida.cis.ufl.EDU> Date: 3 Jun 88 02:33:06 GMT Sender: news@uflorida.cis.ufl.EDU Reply-To: jdc@beach.cis.ufl.edu () Organization: UF CIS Department Lines: 24 I am aware of a system service ($FORCEX) which will force the image exit rundown for a process with an active image. I am interested in something similar to this for a process which is currently executing a comfile, (like @login.com or something) but I can't seem to think of anything off hand. If it is not possible from outside the context of the process, is it possible for the process to terminate a comfile from within an image? For example: $ ! sample.com $ run terminate $ dir $ exit And then the 'terminate.exe' would do something suitable to erase the currently executing comfile. I have thought about reading from sys$input but RMS or VMS takes care of that and will stop at the next $ command. I am not looking for any solution that works under fixed conditions, I want a solution that will work under ANY condition. Any ideas? Jeff -- Jeff Capehart Internet: jdc@beach.cis.ufl.edu University of Florida UUCP: ..!ihnp4!codas!uflorida!beach.cis.ufl.edu!jdc