Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!tektronix!hplabs!ucbvax!wucs.UUCP!brown
From: brown@wucs.UUCP.UUCP
Newsgroups: mod.computers.vax
Subject: VMS, FORTRAN & CTRL-c AST
Message-ID: <8611071454.AA25583@wucs.UUCP>
Date: Fri, 7-Nov-86 09:54:15 EST
Article-I.D.: wucs.8611071454.AA25583
Posted: Fri Nov  7 09:54:15 1986
Date-Received: Sun, 9-Nov-86 03:29:09 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 33
Approved: info-vax@sri-kl.arpa

Problem:

	FORTRAN analysis system with embedded command interpreter.  Need to
be able to interrupt processing(computational and i/o) via a ctrl-c and
return to analysis system's command interpreter.  This worked in
VMS v3 using the sys$unwind mechanism invoked from a condition handler.
This doesn't work in VMS v4.(I've tried it on 4.0-4.4, I don't know what
versions of the FORTRAN system were installed in all cases)

The FORTRAN run time library is apparently left in some bizarre state if
a read or write is interrupted.  Any further i/o operation terminates the
program with some error (which varies depending on the operation).

Question:

	Is there some function I can call which will cause the FORTRAN run
time library to restore itself to a consistent state?

	Is this a bug or a feature?

	I rarely work on VMS now and would appreciate any info or pointers
to documents which might show a way around this problem.

	Regards,
	Mike Brown		Biomedical Computer Laboratory
				Institute for Biomedical Computing
				Washington University
				700 S. Euclid Avenue
				St. Louis, MO  63110
				(314) 362-2135

arpa:	brown%wucs.uucp@seismo.css.gov
uucp:	{ihnp4,...}!wucs!brown