Michael Baier wrote:
>>> "KENT WALLACE"  wrote:
>>> I was coding in VB .NET and failed to close a file.  I found that
records
>>> were missing from the end of the file, maybe 10.  Because I had failed
to
>>> close the file, it failed to clear the buffer.
>>
>>This shouldn't be a problem in COBOL.  COBOL automatically closes all
files
>>for you as part of normal run unit termination.
>>
>>Walter
>>
>
> Yes and NO,
>
> I just learned, that there could be a problem with some files.
> A printfile that I don't close is created as a TEMP-File instead of a
spool-
> file.  MPE and HP-Cobol never had that problem but when migrating, this
could
> cause some weird problems.  Finding more and more of them on my daily
work.
> USing MF-Cobol, HP-UX and Neartek-Shell But don't ask me where or who has
the
> problem now.  Was so easy with 1 vendor (HP) now I have at least 3 and of
> course always the other guy has the problem.  Oh, what a wonderful world
it
> was but no longer is.  Moving forward to the stone-age.
> Michael

I feel your pain.  I believe it's the MPE File System (or would it be some
process manager?) that takes care of closing your run unit's open files.  I
seem to remember demonstrating that Cobol's not doing it (try calling a
cobol subpgm from <any> and note that your files are still open after
cobol's long gone), but once again that might in my case be a concocted
memory.  Anyway, without that luxury, you'd better close your files!

Tracy Pierce

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