Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!bloom-beacon!gatech!udel!udccvax1!gilmore From: gilmore@vax1.acs.udel.EDU (Scott Gilmore) Newsgroups: comp.lang.fortran Subject: Re: Using END= and ERR= in READs Keywords: IBM VS Fortran, inquire, read Message-ID: <2903@udccvax1.acs.udel.EDU> Date: 22 Feb 89 16:00:03 GMT References: <436@orange19.qtp.ufl.edu> <20692@agate.BERKELEY.EDU> Reply-To: gilmore@vax1.acs.udel.EDU (Scott Gilmore) Distribution: usa Organization: University of Delaware Lines: 40 In article <20692@agate.BERKELEY.EDU> jerry@violet.berkeley.edu ( Jerry Berkman ) writes: >In article <436@orange19.qtp.ufl.edu> bernhold@qtp.ufl.edu (David E. Bernholdt) writes: > >>I am writing code in which I want to trap I/O errors.... Logic tells me that > >There is no support in the standard for your "logic" that an >end-of-file condition should cause a branch via the "ERR=" label >if no "END=" is present. Sections 12.6 and 12.7 discuss error >conditions and end-of-file conditions as distinct entities. >A processor which takes the "ERR=" branch for an end-of-file >condition would be non-standard. > > - Jerry Berkman > U.C. Berkeley Computing Services > jerry@violet.berkeley.edu > I have a related problem for READs from the keyboard, as well as OPEN and INQUIRE statements. On an IBM 3090 running VM/CMS, I do in fact trap my errors with END= and ERR= parameters. However, the 3090 insists on producing a traceback dump when an end/error is encountered. After wading through all of the (many) pages of traceback, the program continues at the branch statement that I have specified in the END= or ERR= line. I know there is an error ... that's why I'm trapping it and handling it myself. I don't want the system to produce a traceback so that I can recover gracefully and transparently to the user!!! So, does anyone know how I can suppress these tracebacks? (I know that IBM VM is not the best Fortran environment. In fact, the codes I am speaking were developed on a VMS Vax and MUST be ported to the IBM machine without making them machine-specific. That is, I need to have the exact same code running on both machines.) Thanks. ------------------------------------------------------------------------------ Scott Gilmore Research Assistant University of Delaware gilmore@vax1.acs.udel.edu Center for Composite Materials gilmore@oscar.ccm.udel.edu Dept. of Mechanical Engineering gilmore@minnie.me.udel.edu ------------------------------------------------------------------------------