Just a guess...
 
You may have inadvertently closed filenum 0 which is a reserved filenum as someone else explained. The next FOPEN grabs the first available filenum which is now 0. So, condition-code is 0 as the FOPEN is successful but filenum is also 0 which your program interprets as a failure.
 
That's my theory and I stick to it. Plus, it supports my earlier comment: do not rely on filenum=0 as a sign of failure.  ;-)
 
Thanks...François

________________________________

From: HP-3000 Systems Discussion on behalf of Brian Donaldson
Sent: Fri 4/23/2010 1:20 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] HP3000-L: Cobol/FOPEN/HPFOPEN Problem




I discovered the problem -- I was doing a funlock/fclose of the file 
(already closed) at the end of
the program loop -- for whatever the reason it was causing the subsequent 
fopen's to fail.

Go figure.

Anyway, I want to thank everyone who responded to my postings.

Brian.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *



* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *