HP3000-L Archives

June 1998, Week 2

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:
Glenn Cole <[log in to unmask]>
Reply To:
Date:
Thu, 11 Jun 1998 11:47:03 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Chris Bartram writes:
> I believe the problem stems from the fundamental problem in the posix
> implementation where when posix apps read MPE files, they count on getting
> actual "byte counts" of the contents of the file, where MPE with it's byte-
> filled fixed records (padding - which don't count as file contents) throw
> the byte counts off, causing the posix app to think there's more room in the
> file than there really is.
>
> Or I could be wrong. ;-)

Actually, I do not believe this is accurate.

I suspect that

        (1) the upload was done as an ASCII file with fixed-length records
        (2) EOF = LIMIT
and     (3) the "10 bytes" were on a new line.

Thus, the file *really is* full, and cannot be expanded.

Given an ASCII file with fixed-length records, you *can* use vi
to add bytes to the end of the record.

And if you make a copy of this file to expand its LIMIT
(or use the MPEX command %ALTFILE...;FLIMIT= ) then you *can*
add more records (up to the LIMIT).

All without changing the file to bytestream.

In this particular case, I believe POSIX is exonerated.

--Glenn Cole
  Software al dente, Inc.
  [log in to unmask]

.......................................................................

Item Subject: cc:Mail Text

ATOM RSS1 RSS2