Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!uvaarpa!mcnc!ecsvax!urjlew
From: urjlew@ecsvax.UUCP (Rostyk Lewyckyj)
Newsgroups: comp.lang.fortran
Subject: Re: Using END= and ERR= in READs
Keywords: IBM VS Fortran, inquire, read
Message-ID: <6549@ecsvax.UUCP>
Date: 23 Feb 89 16:22:28 GMT
Distribution: usa
Organization: UNC Educational Computing Service
Lines: 47


   gilmore@vax1.acs.udel.EDU (Scott Gilmore) writes:
> 
> 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?
 
In the Language Reference manual and Programming guides
read the section on the extended errorhandling facility.
 There is a subroutine that you can call, to which
you pass the error code and how you want to handle it.
   call errset(ierno,inoal [,inomes][,itrace][,iusadr][,irange])
The inomes parameter controls whether the system will put out error
messages for this condition. The itrace parameter controls whether
there will be a traceback issued. Inoal controls how many times
this error will be allowed before aborting the program. Iusadr is
the name of a user supplied subroutine called to handle the error.
  
Perhaps you might wish to post a sample of your code that is
causing problems, then people might offer specific solutions.
  
> 
> (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.)
> 
Of course the extended error handling facility of IBM Fortran
is system specific and so will not meet your requirements.

From the tone of that last sentence I gather that you believe
the VMS VAx system allows you to develop programs that are "not
machine specific", and that the program you aere working on is
"not machine specific", But its just that IBM doesn't see it
as such?? ;-). 

-----------------------------------------------
  Reply-To:  Rostyslaw Jarema Lewyckyj
             urjlew@ecsvax.UUCP ,  urjlew@tucc.bitnet
       or    urjlew@tucc.tucc.edu    (ARPA,SURA,NSF etc. internet)
       tel.  (919)-962-9107