HP3000-L Archives

October 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
Date:
Tue, 24 Oct 2000 07:52:37 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
I would not consider this an MPEX bug by any means. I have a command or XEQ file
that runs inside of MPEX. Deep down inside, it invokes the FINFO function.
Whether inside of MPEX or out, FINFO works, on a message file, it seems to work
the same way. My question is how can I have some routine return the same number
for EOF that LISTF returns for a message file. A LISTF seems to return the
number of records remaining to be read. FINFO seems to return the maximum number
of records at some point in the life of the file, perhaps a high-water mark.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431








FONTAIC <[log in to unmask]> on 10/23/2000 10:02:08 PM

Please respond to FONTAIC <[log in to unmask]>








 To:      [log in to unmask]

 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)



 Subject: Re: [HP3000-L] MSG file EOF in MPE/iX and MPEX








I've seen MPEX give some very strange output when accessing message files.  One
of the very few "bugs" I've ever found with a Vesoft product!

ATOM RSS1 RSS2