<< had no idea how good MPE and HP-Cobol "was">>


They still are. No "was" about it.

BD.


On Wed, 18 Feb 2004 11:26:49 -0500, Michael Baier
<[log in to unmask]> wrote:

>In that case, the compiler would at least report the error.
>In my case, we have to work thru "strange behavior".
>Same with COMP-Fields KSAM-FILEs or FLAT-Files.
>
>Alot of trial and error.
>HP-Management incl the famous Winston, had no idea how good MPE and HP-
>Cobol was.
>
>Michael
>
>
>On Wed, 18 Feb 2004 09:05:33 -0600, Shahan, Ray
><[log in to unmask]> wrote:
>
>>Long ago and far away, the IBM's COBOL compiler would fail (severe error)
>if
>>it did not find a CLOSE statement for each OPEN statement in a COBOL
>>program...don't know if this still the case for IBM, nor do I recall if
>this
>>is/was an ANSII standard?
>>
>>Ray Shahan
>>
>>When you were born, you were crying
>>and everyone around you was smiling.
>>Live your life so at the end,
>>you're the one who is smiling and everyone
>>around you is crying.                Unknown
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Tracy Pierce [SMTP:[log in to unmask]]
>>> Sent: Wednesday, February 18, 2004 8:31 AM
>>> To:   [log in to unmask]
>>> Subject:      Re: [HP3000-L] HP COBOL closing files.
>>>
>>> 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 *
>>>
>>>
>>>
>>> ========================================================================
>>> This e-mail message has been scanned for Viruses and Content and cleared
>>> by School Specialty's email filtering solution.
>>
>>* 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 *

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