Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucbvax.UUCP
Path: utzoo!linus!decvax!harpo!eagle!mhuxi!houxm!ihnp4!cbosgd!ucbvax!root
From: root@ucbvax.UUCP
Newsgroups: fa.info-vax
Subject: Re: Invoking the overdraft...
Message-ID: <103@ucbvax.UUCP>
Date: Tue, 11-Oct-83 03:28:35 EDT
Article-I.D.: ucbvax.103
Posted: Tue Oct 11 03:28:35 1983
Date-Received: Fri, 14-Oct-83 21:29:56 EDT
Sender: root@ucbvax.UUCP
Organization: U. C. Berkeley Computer Science
Lines: 11

>From GEOFF5@SRI-CSL  Tue Oct 11 00:28:02 1983
I implemented overdraft in FORTRAN much more simply.  Without looking at
the status codes, I try operations that cause errors twice.  If the
error can't be recovered (like exceeding the overdraft) you get one
useless try, but it handles the overdraft ok.  It sure was a pain tho...

I had to do something similar in a training system as part of power
failure recovery.  The recovery code was flawed & did not recover all
the time (thus the retry logic on errors).

  --Mark  (MHJohnson.F-15 @ HI-Multics)